From: Josu L. <jos...@gm...> - 2013-08-22 20:08:51
|
Hello all, I have a problem with the mce module in a Debian machine. I am using 0.9.0-pre1 version with a usb mce reciver: Bus 007 Device 002: ID 0471:0815 Philips (or NXP) eHome Infrared Receiver In other machines I got it working with this hardware configuration: # /etc/lirc/hardware.conf # LIRCD_ARGS="" LOAD_MODULES=true DRIVER="default" DEVICE="/etc/lirc/lircd.conf" MODULES="lirc_dev lirc_mceusb2" LIRCD_CONF="/etc/lirc/lircd.conf" LIRCMD_CONF="" But now, when I try to start the daemon, I got this: # /etc/init.d/lirc start [ ok ] Loading LIRC modules:. [FAIL] Unable to load LIRC kernel modules. Verify your ... failed! [FAIL] selected kernel modules in /etc/lirc/hardware.conf ... failed! I can't found the "lirc-modules-source" packege in Debian Wheezy. I will appreciate your help. Thanks and best regards. -- Josu Lazkano |
From: Adrian D. <de...@ch...> - 2013-08-25 18:31:35
|
A word of caution: I am not an LIRC expert! Your problem looks like a conflict between in-kernel and standard LIRC decoding. Since kernel version 2.6.36 or so, most LIRC functions are handled by the kernel itself, eliminating the need for LIRC. In particular, the lirc_mceusb module has been moved into the kernel and is no longer supported by LIRC. For your hardware, it is possible to receive remote keypresses using only the linux kernel, with the output being interpreted as actual (configurable) keyboard presses. In this case, irw does not work. You will need to use ir-keytable. It is also possible to disable the kernel LIRC functions and use the standard LIRC daemon. It is also possible to have the kernel decode the remote signals, then pass them to the LIRC daemon through the devinput interface. No wonder people are getting confused! To make things worse, documentation for the above is REALLY hard to find. Here are the best sources I have found. Good luck! General overview of when/how LIRC moved into the linux kernel: http://wilsonet.com/?page_id=95 ir-keytable configuration: http://forum.xbmc.org/showthread.php?tid=101151 HTH, Adrian On Thu, 22 Aug 2013 13:08:45 -0700, Josu Lazkano <jos...@gm...> wrote: > Hello all, > > I have a problem with the mce module in a Debian machine. I am using > 0.9.0-pre1 version with a usb mce reciver: > > Bus 007 Device 002: ID 0471:0815 Philips (or NXP) eHome Infrared Receiver > > In other machines I got it working with this hardware configuration: > > # /etc/lirc/hardware.conf > # > LIRCD_ARGS="" > LOAD_MODULES=true > DRIVER="default" > DEVICE="/etc/lirc/lircd.conf" > MODULES="lirc_dev lirc_mceusb2" > LIRCD_CONF="/etc/lirc/lircd.conf" > LIRCMD_CONF="" > > But now, when I try to start the daemon, I got this: > > # /etc/init.d/lirc start > [ ok ] Loading LIRC modules:. > [FAIL] Unable to load LIRC kernel modules. Verify your ... failed! > [FAIL] selected kernel modules in /etc/lirc/hardware.conf ... failed! > > I can't found the "lirc-modules-source" packege in Debian Wheezy. > > I will appreciate your help. > > Thanks and best regards. |
From: Josu L. <jos...@gm...> - 2013-08-25 18:49:31
|
2013/8/25 Adrian DeLeon <de...@ch...>: > A word of caution: I am not an LIRC expert! > > Your problem looks like a conflict between in-kernel and standard LIRC > decoding. Since kernel version 2.6.36 or so, most LIRC functions are > handled by the kernel itself, eliminating the need for LIRC. In > particular, the lirc_mceusb module has been moved into the kernel and is > no longer supported by LIRC. > > For your hardware, it is possible to receive remote keypresses using only > the linux kernel, with the output being interpreted as actual > (configurable) keyboard presses. In this case, irw does not work. You will > need to use ir-keytable. > > It is also possible to disable the kernel LIRC functions and use the > standard LIRC daemon. > > It is also possible to have the kernel decode the remote signals, then > pass them to the LIRC daemon through the devinput interface. > > No wonder people are getting confused! To make things worse, documentation > for the above is REALLY hard to find. Here are the best sources I have > found. Good luck! > > General overview of when/how LIRC moved into the linux kernel: > http://wilsonet.com/?page_id=95 > > ir-keytable configuration: > http://forum.xbmc.org/showthread.php?tid=101151 > > HTH, > > Adrian > > > On Thu, 22 Aug 2013 13:08:45 -0700, Josu Lazkano <jos...@gm...> > wrote: > >> Hello all, >> >> I have a problem with the mce module in a Debian machine. I am using >> 0.9.0-pre1 version with a usb mce reciver: >> >> Bus 007 Device 002: ID 0471:0815 Philips (or NXP) eHome Infrared Receiver >> >> In other machines I got it working with this hardware configuration: >> >> # /etc/lirc/hardware.conf >> # >> LIRCD_ARGS="" >> LOAD_MODULES=true >> DRIVER="default" >> DEVICE="/etc/lirc/lircd.conf" >> MODULES="lirc_dev lirc_mceusb2" >> LIRCD_CONF="/etc/lirc/lircd.conf" >> LIRCMD_CONF="" >> >> But now, when I try to start the daemon, I got this: >> >> # /etc/init.d/lirc start >> [ ok ] Loading LIRC modules:. >> [FAIL] Unable to load LIRC kernel modules. Verify your ... failed! >> [FAIL] selected kernel modules in /etc/lirc/hardware.conf ... failed! >> >> I can't found the "lirc-modules-source" packege in Debian Wheezy. >> >> I will appreciate your help. >> >> Thanks and best regards. > > ------------------------------------------------------------------------------ > Introducing Performance Central, a new site from SourceForge and > AppDynamics. Performance Central is your source for news, insights, > analysis and resources for efficient Application Performance Management. > Visit us today! > http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk Hello, I get it working commenting this line: MODULES="lirc_dev lirc_mceusb2" It looks like I don't need to load the modules. Thanks! -- Josu Lazkano |
From: Stefan Lippers-H. <s....@gm...> - 2013-08-25 21:03:37
Attachments:
signature.asc
|
Hi On Thursday 22 August 2013, Josu Lazkano wrote: > Hello all, > > I have a problem with the mce module in a Debian machine. I am using > 0.9.0-pre1 version with a usb mce reciver: > > Bus 007 Device 002: ID 0471:0815 Philips (or NXP) eHome Infrared Receiver > > In other machines I got it working with this hardware configuration: > > # /etc/lirc/hardware.conf > # > LIRCD_ARGS="" > DRIVER="default" > LOAD_MODULES=true > MODULES="lirc_dev lirc_mceusb2" the modules for mceusb are autoloaded, furthermore lirc_mceusb or lirc_mceusb2 do not exist anymore, as their functionality has been ported to RC_CORE. > DEVICE="/etc/lirc/lircd.conf" > LIRCD_CONF="/etc/lirc/lircd.conf" > LIRCMD_CONF="" > > But now, when I try to start the daemon, I got this: > > # /etc/init.d/lirc start > [ ok ] Loading LIRC modules:. > [FAIL] Unable to load LIRC kernel modules. Verify your ... failed! > [FAIL] selected kernel modules in /etc/lirc/hardware.conf ... failed! > > I can't found the "lirc-modules-source" packege in Debian Wheezy. All functionality is provided by the kernel these days, out-of-tree modules are not supported anymore (but all previous modules provided by lirc-modules-source are now in the mainline kernel, be it in staging or as proper RC_CORE driver). See https://lists.debian.org/debian-backports/2012/04/msg00076.html for configuration details, basically you can configure it in two orthogonal ways, using the classic lirc protocol or using the input protocol and ir-keytable. Regards Stefan Lippers-Hollmann |