Thanks for all your replies. I didn't get a chance to test again until the weekend. Stupid work week.
Responses inline.
Assuming you are trying to use LIRC to process the remote signals: what does "cat /sys/class/rc/rc0/protocols" show? If more than one item is enclosed in square brackets, then something other than LIRC is getting those signals. There is now an in-kernel IR driver, this started sometime around F18. In order to get my remote to work with my MythTV system, I have to execute# echo lirc > /sys/class/rc/rc0/protocolsAfter that, the above "cat" command shows only lirc bracketed, and then LIRC works fine.
I've tried using just LIRC and I've tried going through the native route -- the IR driver for MCEUSB appears to be in-kernel now -- and neither worked.
I tried your approach just now:
cat /sys/class/rc/rc0/protocols
rc-5 nec rc-6 jvc sony sanyo sharp mce_kbd [lirc]
ir-keytable shows:
=== start ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event5) with:
Driver mceusb, table rc-rc6-mce
Supported protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC other
Enabled protocols: LIRC
Name: Media Center Ed. eHome Infrared
bus: 3, vendor/product: 0471:0815, version: 0x0000
Repeat delay = 500 ms, repeat period = 125 ms
=== end ir-keytable
My /etc/lirc/lircd.conf:
===
include "/usr/share/lirc-remotes/hauppauge/lircd.conf.hauppauge"
===
The LIRCD logs when I start LIRCD and then run IRW
=== start lirc logs
sh[2217]: lircd-0.9.0[2217]: lircd(devinput) ready, using /var/run/lirc/lircd
lircd-0.9.0[2217]: lircd(devinput) ready, using /var/run/lirc/lircd
sh[2217]: lircd-0.9.0[2217]: accepted new client on /var/run/lirc/lircd
sh[2217]: lircd-0.9.0[2217]: initializing '/dev/input/event5'
lircd-0.9.0[2217]: accepted new client on /var/run/lirc/lircd
lircd-0.9.0[2217]: initializing '/dev/input/event5'
sh[2217]: lircd-0.9.0[2217]: removed client
sh[2217]: lircd-0.9.0[2217]: closing '/dev/input/event5'
lircd-0.9.0[2217]: removed client
lircd-0.9.0[2217]: closing '/dev/input/event5'
=== end lirc logs
But when I run IRW and click a bunch of buttons on the remote, nothing shows up.
feature is grabbing control of the remote? (Though I'm not sureTotal speculation: Have you checked to see if some "helpful" new
how to check for such a thing). Maybe look through release notes
for something about wonderful new and improved remote support?
I checked, and it's possible that X is actually grabbing the remote and using it as a keyboard. I added a file /etc/X11/xorg.conf.d/90-disable_mce.conf:
=== start 90-disable_mce.conf
Section "InputClass"
Identifier "Ignore MCE IR Keyboard/Mouse"
MatchProduct "MCE IR Keyboard/Mouse (mceusb)"
MatchIsKeyboard "true"
Option "Ignore" "true"
EndSection
Section "InputClass"
Identifier "Remote"
MatchProduct "Media Center Ed. eHome Infrared Remote Transceiver (0471:0815)"
Option "Ignore" "true"
EndSection
=== end 90-disable_mce.conf:
When I start X I see this in the logs:
=== start Xorg.0.log snippets
[1366421.127] (II) config/udev: Adding input device Media Center Ed. eHome Infrared Remote Transceiver (0471:0815) (/dev/input/event5)
[1366421.127] (**) Media Center Ed. eHome Infrared Remote Transceiver (0471:0815): Ignoring device from InputClass "Remote"
[...]
[1366421.127] (II) config/udev: Adding input device MCE IR Keyboard/Mouse (mceusb) (/dev/input/event16)
[1366421.127] (**) MCE IR Keyboard/Mouse (mceusb): Ignoring device from InputClass "Ignore MCE IR Keyboard/Mouse"
[1366421.127] (II) config/udev: Adding input device MCE IR Keyboard/Mouse (mceusb) (/dev/input/mouse2)
[1366421.127] (**) MCE IR Keyboard/Mouse (mceusb): Ignoring device from InputClass "Ignore MCE IR Keyboard/Mouse"
=== end Xorg.0.log snippets
To me this says that X is ignoring this device and all its interfaces in /dev/input.
So as far as I can tell, nothing is grabbing the IR receiver as input, lirc recognizes the device and is able to attach clients to it, but neither 'irw' nor 'ir-keytable -t' sees anything from the remote.
More info:
ir-keytable says that it's using keytable 'table rc-rc6-mce', and my /etc/rc_maps.cfg file has this:
=== start /etc/rc_maps.cfg
#driver table file
* rc-rc6-mce rc6_mce
=== end /etc/rc_maps.cfg
I copied /usr/lib/udev/rc_keymaps/rc6_mce to /etc/rc_keymaps/ and then unplugged and re-plugged in my IR receiver. dmesg shows this:
=== start dmesg snippet
[1784677.192171] Registered IR keymap rc-rc6-mce
[1784677.192354] input: Media Center Ed. eHome Infrared Remote Transceiver (0471:0815) as /devices/pci0000:00/0000:00:14.0/usb3/3-7/3-7:1.0/rc/rc0/input38
[1784677.192601] rc0: Media Center Ed. eHome Infrared Remote Transceiver (0471:0815) as /devices/pci0000:00/0000:00:14.0/usb3/3-7/3-7:1.0/rc/rc0
[1784677.192775] input: MCE IR Keyboard/Mouse (mceusb) as /devices/virtual/input/input39
[1784677.194120] rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0
=== end dmesg snippet
According to this the lirc_dev driver noticed it getting plugged in and loaded the ir-lirc-codec module to expose button presses to userspace. BUT here are all the kernel modules which are currently related to MCE:
=== start lsmod snippets
mceusb 28026 0
ir_mce_kbd_decoder 13214 0
rc_rc6_mce 12502 0
rc_core 27490 13 ir_sharp_decoder,lirc_dev,ir_lirc_codec,ir_rc5_decoder,ir_nec_decoder,ir_sony_decoder,mceusb,ir_mce_kbd_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_sanyo_decoder,rc_rc6_mce
=== end lsmod snippets
In there I see kernel modules for plain old mceusb, the new in-kernel keyboard decoder (ir_mce_kbd_decoder) the old lirc drivers (lirc_dev, irc_lirc_codec) and rc_rc6_mce (whatever that is).
Which kernel module is grabbing the input? Are there multiple modules trying to grab the input? If so, which one SHOULD be grabbing the input and how do I disable the other ones? It feels like there are at least two different systems trying to handle the IR input and all of them are failing miserably.
Here are some other pages with LIRC-related configurations I've tried to follow, none of which have worked for me:
This is all so frustrating. It just feels like IR configuration is being shoved into the same bin as sound and printing: theoretically perfect but practically a pain in the ass. Between this and continued PulseAudio wonkiness I'm getting to the point where I feel it would be easier just to get MythTV running on Ubuntu or Windows or a pre-Fedora-18 system.
Thanks,
-jdm
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
