Description of problem: After installing lirc on a Macbook Pro 5,3 the apple remote doesn't work -- the machine has no response to it in irw or xev. Version-Release number of selected component (if applicable): kernel-2.6.38.8-35.fc15.x86_64 How reproducible: Steps to Reproduce: 1. Install lirc, lirc-remotes, and gnome-lirc-properties 2. Install hal so that gnome-lirc-properties doesn't crash immediately 3. Run autodetect in gnome-lirc-properties Actual results: After detecting the hardware, the computer remains unresponsive to the remote. Expected results: The apple remote should be able to control volume and play/pause media. Additional info: -Trying to configure the remote manually using "learn" in gnome-lirc-properties throws the error "Remote Configuration failed: could not initialize hardware" -listed in lsusb as "Bus 003 Device 002: ID 05ac:8242 Apple, Inc. IR Receiver [built-in]" -lsmod shows that appleir is loaded -no output with irw -no /dev/lirc0 or /dev/hiddev -cat /dev/input/by-id/usb-Apple_Computer__Inc._IR_Receiver-event-if00 returns "cat: usb-Apple_Computer__Inc._IR_Receiver-event-if00: Resource temporarily unavailable" -report of the same problem on a Mac-mini in http://forums.fedoraforum.org/showthread.php?t=267077
Still doesn't work in F16. Device is still listed with lsusb, but there is no mention of an IR receiver in /dev/input/by-id or by-path. It appears that the appleir module was dropped from the kernel. I admit that I just don't know what harm including it could do, but there is no replacement for its functionality. The IR receiver doesn't work with lirc, and lirc itself is broken -- gnome-lirc-properties requires hal, which is deprecated.
The appleir driver we were carrying was an out-of-tree addition. It was NAK'd upstream as the proper solution is to do something in the IR framework instead. Moving this bug to rawhide.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
Is this still a problem with 3.9 based F19 kernels?
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.