[mythtv-users] Remote suddenly stopped working

[James Crow]

On Wed, 2008-11-19 at 17:10 -0800, Steve Peters - Priority Electronics
wrote:
> >
> >Do you have an lirc log file in the /var/log directory? I had one grow
> >to a huge size and it shut down lirc. That was awhile back on the lirc
> >log file size issue so that could have been fixed.
> >
> >You could also try looking in the dev folder to see if a socket is
> >being created. I'd also do
> >
> >#lsmod | grep mceusb
> >
> >to make sure the module is loaded
> >
> >and
> >
> >#dmesg | grep lirc
> >
> >to see if you're getting any errors.
> 
> 
> 
> Ok, no lirc logs found, and here is what I get from the command line:
> 
> $ lsmod | grep mceusb
> lirc_mceusb2           20228  1
> lirc_dev               20020  1 lirc_mceusb2
> usbcore               148848  7
> lirc_mceusb2,usb_storage,usbhid,libusual,ehci_hcd,uhci_hcd
> 
> 
> $ dmesg | grep lirc
> [   21.143152] lirc_dev: IR Remote Control driver registered, major 61
> [   21.253662] lirc_mceusb2: Philips eHome USB IR Transceiver and Microsoft
> MCE 2005 Remote Control driver for LIRC $Revision: 1.44 $
> [   21.253665] lirc_mceusb2: Daniel Melander <lirc at rajidae.se>, Martin
> Blatter <martin_a_blatter at yahoo.com>
> [   21.438830] lirc_dev: lirc_register_plugin: sample_rate: 0
> [   21.439699] lirc_mceusb2[8]: Topseed eHome Infrared Transceiver on usb5:8
> [   21.439993] usbcore: registered new interface driver lirc_mceusb2
> 
> 
> Seems fine to me. Any other ideas?
> -Thanks
> -Steve
> 
> 

Steve,

 This line:

[   21.439699] lirc_mceusb2[8]: Topseed eHome Infrared Transceiver on
usb5:8

indicates that the LIRC driver is seeing your receiver. Do you have
a /dev/lirc0 entry? Or compare the results of ls -l /dev/lir* with and
without the usb receiver attached. Mythbuntu 8.10 (and 8.04) create
a /dev/lirc0 entry. If that entry is there stop lirc
'sudo /etc/init.d/lirc stop' and run mode2. Point the remote at the
receiver and press some buttons. You should see info on screen. If you
see output from mode2 it is likely that the /etc/lirc/lircd.conf file
has been altered.

Cheers,
James