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?
latumus
Junior Member Posts: 10 Joined: Feb 2009 Reputation: 0 |
2009-03-06 13:56
Post: #1
|
| find quote |
rodercot
Donor Posts: 795 Joined: Feb 2008 Reputation: 25 Location: Ottawa, Canada |
2009-03-06 14:03
Post: #2
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 |
| find quote |
latumus
Junior Member Posts: 10 Joined: Feb 2009 Reputation: 0 |
2009-03-06 14:11
Post: #3
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 <lirc@rajidae.se>, Martin Blatter <martin_a_blatter@yahoo.com> [ 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 |
| find quote |
rodercot
Donor Posts: 795 Joined: Feb 2008 Reputation: 25 Location: Ottawa, Canada |
2009-03-06 14:21
Post: #4
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
(This post was last modified: 2009-03-06 14:30 by rodercot.)
|
| find quote |
latumus
Junior Member Posts: 10 Joined: Feb 2009 Reputation: 0 |
2009-03-06 14:38
Post: #5
yes above is with working remote
gonna try the suggestions now |
| find quote |
latumus
Junior Member Posts: 10 Joined: Feb 2009 Reputation: 0 |
2009-03-06 14:41
Post: #6
and indeed when i plug out and plug in (in the same socket it works)
|
| find quote |
latumus
Junior Member Posts: 10 Joined: Feb 2009 Reputation: 0 |
2009-03-10 00:25
Post: #7
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
|
| find quote |
rodercot
Donor Posts: 795 Joined: Feb 2008 Reputation: 25 Location: Ottawa, Canada |
2009-03-10 01:31
Post: #8
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 |
| find quote |
latumus
Junior Member Posts: 10 Joined: Feb 2009 Reputation: 0 |
2009-03-10 09:53
Post: #9
yup, same problem
|
| find quote |
latumus
Junior Member Posts: 10 Joined: Feb 2009 Reputation: 0 |
2009-03-10 15:23
Post: #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 |
| find quote |

Search
Help