MCE USB2 remote not working on MD (10.04)

[gtsupport]

I am persevering with my 10.04 install, but the biggest issue at the moment is the lack of the windows MCE usb2 remote functionality on my MD.  SWMBO is getting the hump now, as it works fine with my 8.10 install, but I'm keen to push forward with the 10.04 kernel so its now become urgent in our house!  I have checked the logs, and it appears that the device 107 is spawned correctly, but it doesn't actually respond to any button presses at all.  Is there another place I can check to see if the presses are actually being received?  If I unplug the device and re-plug it, LMCE shows the window to say its re-enabling the MCE_USB2 device.....installing software etc. then shows installing software_done.  Still nothing.  Numerous reboots, or reloading router etc doesn't seem to have any effect.  I tried removing the device from the webadmin, and then plugging it in again.  Same thing, it appears automatically, loads the software etc, but doesn't work. Booting back into 8.10 sees it working fine, so hardware is OK.

Anyone else have this problem, or suggest a resolution?

Cheers.
Matt.

[ardirtbiker]

similar issues with the Gyro remotes... you may have to re-determine the codes being sent for each button press... using the 'xev' ... then check the template for the remote and compare the codes.. fixing any that dont match...

Dennis

[gtsupport]

Found another log, after enabling log level 107 I have a message in the 107_LIRC_DCE.log that says "There are no remote controls --LIRC will be dormant"

followed by "Child device 108 is disabled"

Mean anything to anyone??

[pointman87]

A temporary workaround is to manually edit the /etc/lirc/hardware.conf file.


# /etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE="mceusb"
REMOTE_MODULES=""
REMOTE_DRIVER=""
REMOTE_DEVICE=""
REMOTE_SOCKET=""
REMOTE_LIRCD_CONF=""
REMOTE_LIRCD_ARGS=""

#Chosen IR Transmitter
TRANSMITTER="None"
TRANSMITTER_MODULES=""
TRANSMITTER_DRIVER=""
TRANSMITTER_DEVICE=""
TRANSMITTER_SOCKET=""
TRANSMITTER_LIRCD_CONF=""
TRANSMITTER_LIRCD_ARGS=""

#Enable lircd
START_LIRCD="true"

#Don't start lircmd even if there seems to be a good config file
#START_LIRCMD="false"

#Try to load appropriate kernel modules
LOAD_MODULES="true"

# Default configuration files for your hardware if any
LIRCMD_CONF=""

#Forcing noninteractive reconfiguration
#If lirc is to be reconfigured by an external application
#that doesn't have a debconf frontend available, the noninteractive
#frontend can be invoked and set to parse REMOTE and TRANSMITTER
#It will then populate all other variables without any user input
#If you would like to configure lirc via standard methods, be sure
#to leave this set to "false"
FORCE_NONINTERACTIVE_RECONFIGURATION="false"
START_LIRCMD=""


If you set the REMOTE statement to mceusb and START_LIRCD to true, then you get your remote to work.

Best regards, Daniel

[gtsupport]

A Thousand blessings on you Daniel, worked a treat and has reduced the pressure from SWMBO somewhat. 

Back to the 1001 other things to nitpick.

Matt.

[seth]

 
I can also confirm, making these changes has allowed for the MCE Remote/Receiver combo to work for me on 10.04.

Thanks, and Best regards,

Seth

[kyfalcon]

That fixed my problems as well. I guess the question to ask is, Did something happen to the install script in 1004? Is this really the best solution? If so should it be added to the install script?

[tschak909]

Can one of the devs look here and try to figure out what we need to change in LIRC_DCE? I can help, but I am swamped at the moment with paid work, and can't do the needed changes.

-Thom