Lirc stops working - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111) +---- Forum: Linux (https://forum.kodi.tv/forumdisplay.php?fid=52) +---- Thread: Lirc stops working (/showthread.php?tid=46491) Pages:
1
2
|
Lirc stops working - latumus - 2009-03-06 hey guys im having some trouble with Lirc, it all works fine but out of nowhere it stops working then after a reboot it works again anyone have any ideas? - rodercot - 2009-03-06 latumus Wrote:hey guys im having some trouble with Lirc, it all works fine but out of nowhere it stops working then after a reboot it works again You could try unplugging the dongle and plug it back in when it happens if not then give us some details, what remote are you using, what does you /etc/lirc/hardware.conf and lircd.conf look like. like cat /var/log/syslog - The last few lines of this file. and dmesg | grep -i lirc and ls -l /dev/lirc* and ps ax | grep lirc lircd --version xbmc rev ppa or svn And finally a log file or debug report would help. rgds, Dave - latumus - 2009-03-06 im running xbmc vdpau latest svn but xbmc isnt the problem seeing 'irw' wont give output either when it starts to fail Bus 002 Device 003: ID 0471:060c Philips and im using a logitech harmony 885 configured as philips srm5100 mceusb remote i hope this is all the info you requested syslog: Mar 6 13:05:33 sodom kernel: [ 76.440025] usb 2-3: new full speed USB device using ohci_hcd and address 3 Mar 6 13:05:33 sodom kernel: [ 76.665965] usb 2-3: configuration #1 chosen from 1 choice Mar 6 13:05:33 sodom kernel: [ 76.836029] usb 2-3: reset full speed USB device using ohci_hcd and address 3 Mar 6 13:05:33 sodom kernel: [ 77.045964] lirc_dev: lirc_register_plugin: sample_rate: 0 Mar 6 13:05:33 sodom kernel: [ 77.051748] lirc_mceusb2[3]: BB+ Dongle(e.d) on usb2:3 Mar 6 13:05:33 sodom lircd-0.8.3[5771]: caught signal Mar 6 13:05:33 sodom lircd-0.8.3[6252]: lircd(userspace) ready Mar 6 13:06:08 sodom lircd-0.8.3[6252]: accepted new client on /dev/lircd Mar 6 13:06:25 sodom kernel: [ 128.764523] ppdev0: registered pardevice Mar 6 13:06:25 sodom python: io/hpmud/pp.c 627: unable to read device-id ret=-1 Mar 6 13:06:25 sodom kernel: [ 128.812258] ppdev0: unregistered pardevice Mar 6 13:06:25 sodom kernel: [ 128.842127] ppdev0: registered pardevice Mar 6 13:06:25 sodom hp: io/hpmud/pp.c 627: unable to read device-id ret=-1 Mar 6 13:06:25 sodom kernel: [ 128.888247] ppdev0: unregistered pardevice Mar 6 13:06:26 sodom kernel: [ 129.968453] ppdev0: registered pardevice Mar 6 13:06:26 sodom kernel: [ 130.012039] ppdev0: unregistered pardevice ~# dmesg | grep -i lirc [ 26.626820] lirc_dev: IR Remote Control driver registered, major 61 [ 26.645418] lirc_mceusb2: Philips eHome USB IR Transceiver and Microsoft MCE 2005 Remote Control driver for LIRC $Revision: 1.44 $ [ 26.645422] lirc_mceusb2: Daniel Melander <[email protected]>, Martin Blatter <[email protected]> [ 26.650905] usbcore: registered new interface driver lirc_mceusb2 [ 77.045964] lirc_dev: lirc_register_plugin: sample_rate: 0 [ 77.051748] lirc_mceusb2[3]: BB+ Dongle(e.d) on usb2:3 ~# ls -l /dev/lirc* crw-rw---- 1 root root 61, 0 2009-03-06 13:05 /dev/lirc0 srw-rw-rw- 1 root root 0 2009-03-06 13:05 /dev/lircd ps ax | grep lirc 6252 ? S<s 0:00 /usr/sbin/lircd --device=/dev/lirc0 6429 pts/0 S+ 0:00 grep lirc ~# lircd --version lircd 0.8.3 - rodercot - 2009-03-06 Is this with it working? I would try moving the USB dongle to another USB port and off that particular bus also check your /etc/lirc/hardware.conf file and make sure that in the remote section you have DEVICE="/dev/lirc0" and the MODULES sections reads "lirc_dev lirc_mceusb2" and then sudo /etc/init.d/lirc restart. See if that works. you can also put your modules in /etc/modules to force load on startup but with 8.10 they automagically start any how if you do this then you had better change the load MODULES in your hardware.conf file to "false" or it will try and load the lirc_mceusb2 module more than once. One more thing you may try as well is below this will put your lirc startup back in the order of loading if by chance it was moved down the list, I have this issue in the past where it moved it to like s and k 90 instead of 20 or 21. sudo /etc/init.d/lirc stop sudo update-rc.d -f lirc remove sudo update-rc.d lirc defaults sudo /etc/init.d/lirc restart Dave - latumus - 2009-03-06 yes above is with working remote gonna try the suggestions now - latumus - 2009-03-06 and indeed when i plug out and plug in (in the same socket it works) - latumus - 2009-03-10 ok its still not working tried all steps you've said when i turn on my box the ir receiver doesnt seem to be started (no green light on it) then when i plug out the usb and plug it back in (in the same slot) it works. then after a while it just stops working - rodercot - 2009-03-10 Have you tried plugging it into another USB port alltogether and not the same one this is sometimes a common problem in linux. Try another port and restart the system or restart lirc. Dave - latumus - 2009-03-10 yup, same problem - latumus - 2009-03-10 after it stops taking input lirc seems to still be running root 6363 0.0 0.0 18012 716 ? S<s 13:04 0:00 /usr/sbin/lircd --device=/dev/lirc0 also the ir device registers all input the remote gives irw shows up nothing - opdenkamp - 2009-03-11 sounds like a lirc driver bug or hardware error to me. try compiling lirc in debugging mode (with the -d[level] flag) en look at it's debugging output. - rodercot - 2009-03-11 latumus Wrote:after it stops taking input lirc seems to still be running Yes and this is why I was leaning to trying it on another USB port, as I an irq issue may be popping up. By chance and this is a long shot, does your board have 5v usb jumpers on it. Are you plugged into the blackplane USB ports or ports that you have added a cable to and plugged into the mainboard. The lirc debug is a good idea never thought of that. the only time I had lirc locking up was with my playback profiles in mythtv. Have you searched this at ubuntu forums as well. Can you tail -f /var/log/syslog or tail dmesg on another machine via ssh while it is working until it stops and then see what those errors maybe and also check the xbmc logs. Dave - latumus - 2009-03-11 dmesg/syslog show no error when it stops functioning it just stops taking input, i've ran lirc without a daemon so i could see in foreground when something messed up, this wasnt the case : strange@sodom:~$ sudo /etc/init.d/lirc stop && sudo /usr/sbin/lircd --device=/dev/lirc0 --nodaemon * Stopping remote control daemon(s): LIRC [fail] lircd-0.8.3[6434]: lircd(userspace) ready lircd-0.8.3[6434]: accepted new client on /dev/lircd lircd-0.8.3[6434]: accepted new client on /dev/lircd it just sits there first client = irw second client = xbmc then it worked for over 10 hours (amazingly ofcourse it didnt die after 5 minutes when i wanted it to die so i could see if i found an error) but once it did die, no errors i currently have it running in the front usb port had it in every port of my machine so far (front usb lasts the longest appearantly) - latumus - 2009-03-12 any ideas? - gquiring - 2009-03-13 I have lost my Lirc about 6 or 7 times now. It requires an odd fix. I have to power down my computer and physically unplug it from the wall so no power is on the system. It works every time. |