From: Martin B. <mbl...@gm...> - 2005-03-22 00:55:32
|
Jim Oltman wrote: >Why am I only getting it once? Why does irrecord only work with >/dev/lircd? SO CONFUSED!! Thanks Martin and EC! > > I'm as puzzled as you are. Try mode2 for testing. You don't need irrecord, there's already a working config file in the tar archive on my download page. I just installed lirc-0.7.0 with my version of lirc-mceusb.c on top on a freshly installed machine (stock SuSE 9.2 with updated kernel). Works fine. mode2 gives me output each time I press a button. It's a UHCI machine though. And note that initialization of the USB device does not work reliably on kernels older than 2.6.10. If you have problems with initialization (it says something like "receive request FAILED!" in /var/log/messages after plugging in the device), try to remove the device and plug it in again after a few seconds. Thanks for testing. >On Tue, 22 Mar 2005 01:30:32 +0100, Martin Blatter <mbl...@gm...> wrote: > > >>I'll look into that. Need to find someone who owns an ohci mobo ;-) >>Otherwise the output looks good. It's the raw data from the remote. >> >>Jim Oltman wrote: >> >> >> >>>u r right in saying i have ohci. NForce2 mobo >>> >>> >>>On Mon, 21 Mar 2005 18:15:10 -0600, Jim Oltman <cnl...@gm...> wrote: >>> >>> >>> >>> >>>>I only received this data once. I have rebooted 2 times (no changes >>>>to config other than the initial debug) and haven't received it again. >>>>There is a lot here because I wanted to include the length 10 >>>>message: >>>> >>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 81 >>>>5f 9f 01 01 9f 15 00 00 80 (length=10) >>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84 >>>>b4 13 88 0a (length=5) >>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84 >>>>88 0a 88 13 (length=5) >>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84 >>>>87 12 9a 14 (length=5) >>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84 >>>>87 0a 88 0c (length=5) >>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84 >>>>86 09 88 0a (length=5) >>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84 >>>>88 0b 87 0b (length=5) >>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84 >>>>87 0c 86 0b (length=5) >>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84 >>>>86 0b 87 0d (length=5) >>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84 >>>>8d 0a 88 1d (length=5) >>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84 >>>>86 0f 82 28 (length=5) >>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84 >>>>86 0b 87 0d (length=5) >>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84 >>>>8d 15 86 0e (length=5) >>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84 >>>>83 0b 87 0b (length=5) >>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84 >>>>87 10 8b 27 (length=5) >>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84 >>>>85 7f 7f 7f (length=5) >>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84 >>>>7f 7f 7f 7f (length=5) >>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 81 >>>>5f 9f 01 01 9f 15 00 00 80 (length=10) >>>> >>>> >>>>On Tue, 22 Mar 2005 00:26:16 +0100, Martin Blatter <mbl...@gm...> wrote: >>>> >>>> >>>> >>>> >>>>>Jim Oltman wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>># LIRC Setup >>>>>>alias char-major-61 lirc_mceusb >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>please add the following right below the above line in >>>>>modprobe.conf: >>>>>options lirc_mceusb debug=1 >>>>> >>>>>then reboot your machine without the transciever plugged in. >>>>>(lircd doesn't need to run after rebooting!). plug in the ir transciever, >>>>>wait a few seconds, press a few keys on the remote and mail me >>>>>the output of /var/log/mesages. >>>>> >>>>>am i right in the assumption that you have an ohci type usb >>>>>host controller? because all the people I know who use the driver >>>>>sucessfully have an uhci/ehci (e.g. intel) usb host controller. there >>>>>may be a problem related to ohci host controllers. but it's just a >>>>>guess. >>>>> >>>>>regards >>>>>martin >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>> >>> >>> >> >> > > > |