Description of problem:
LIRC daemon starts but fails as soon as something tries to connect to it (irw or mythfrontend) with "atilibusb" driver. It worked on kernel 2.6.41 and earlier, quit when 2.6.42 was installed on Fedora 15. Still does not work with 3.3.0 on Fedora 16. Log as follows:
Mar 28 12:27:48 localhost lircd-0.9.0: accepted new client on /var/run/lirc/lircd
Mar 28 12:27:48 localhost lircd-0.9.0: couldn't claim USB interface: Device or resource busy
Mar 28 12:27:48 localhost lircd-0.9.0: Failed to initialize hardware
Mar 28 12:27:48 localhost lircd-0.9.0: reading in mode LIRC_MODE_LIRCCODE failed
Mar 28 12:27:48 localhost lircd-0.9.0: caught signal
Mar 28 12:27:48 localhost lirc: Stopping infrared remote control daemon (lircd): [FAILED]
Device listing (lsusb):
Bus 004 Device 003: ID 0bc7:0008 X10 Wireless Technology, Inc. Wireless Transceiver (ACPI-compliant)
This is a "Firefly" RF remote.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install lirc package, connect USB remote receiver.
2. Install "/etc/lirc/lircd.conf" file from MythTV site.
3. Edit "/etc/sysconfig/lirc" to specify "atilibusb" driver.
4. Enable and start "lircd". "Services" shows "running".
5. Execute "irw" command as root.
"irw" returns immediately without output, Services shows lircd "Inactive"
Should display codes for buttons pressed on remote.
99% sure this is NOTABUG, and atilibusb is simply failing to bind to the device because the in-kernel ati_remote driver has already grabbed it. Either use ati_remote, forgoing atilibusb, or blacklist ati_remote, and you should be fine.
OK, LIRC does not seem to support "ati_remote" at this time but blacklisting it does allow "atilibusb" to work properly. I will at least update the MythTV wiki. Thanks for the help and sorry for the bother!
(In reply to comment #2)
> OK, LIRC does not seem to support "ati_remote" at this time but blacklisting it
> does allow "atilibusb" to work properly. I will at least update the MythTV
> wiki. Thanks for the help and sorry for the bother!
The ati_remote driver is a native linux input layer driver. You *can* use lirc with it, but the lirc "driver" you use is devinput, not ati_remote.
Yes, it does work with:
in the file "/etc/sysconfig/lirc" which is a neater solution. This probably should be the default in the version of this file supplied with the LIRC package but otherwise, it is a documentation issue and I will do what I can about that. Thanks again!