[mythtv-users] iMON IR config on Fedora 14 is broken
Todd Brunhoff
toddb at nvr.com
Mon Jan 3 16:04:39 UTC 2011
> I have five imon devices in my possession, and they all work perfectly
> fine under Fedora 14.
Excellent... this means that my conclusion was incorrect and I don't
have to wait for fedora 15. I'd have to say that if all your devices
work, and mine does not, then my configuration is incorrect. Lots more
testing and the problem appears to be caused by the lircd.conf file. I
have been trying one I got from a recent posting of yours and one from
http://lirc.sourceforge.net/remotes/devinput/lircd.conf.devinput
Either .conf file produces irw output for only ENTER, BACKSPACE and ESC.
All the other buttons produce kernel debug output from the imon driver,
but irw does not see an event (part of my silly thinking that "nothing
works" comes from my testing only up,down,left,right keys).
Here is the output from 'tail -f /var/log/messages& irw' while pressing
ENTER, BACKSPACE, ESC followed by UP, DOWN, LEFT, RIGHT. Note the lack
if irw events for the latter four:
Jan 3 00:05:54 myth3 kernel: [ 2141.230975] intf0 decoded packet:
02 00 00 00 00 00 00 00
000000008001001c 00 KEY_ENTER devinput
Jan 3 00:05:54 myth3 kernel: [ 2141.238969] intf0 decoded packet:
02 00 00 28 00 00 00 00
Jan 3 00:05:54 myth3 kernel: [ 2141.342971] intf0 decoded packet:
02 00 00 28 00 00 00 00
Jan 3 00:05:54 myth3 kernel: [ 2141.438963] intf0 decoded packet:
02 00 00 00 00 00 00 00
000000008001001c 00 KEY_ENTER_UP devinput
Jan 3 00:05:56 myth3 kernel: [ 2143.350852] intf0 decoded packet:
02 00 00 00 00 00 00 00
000000008001000e 00 KEY_BACKSPACE devinput
Jan 3 00:05:56 myth3 kernel: [ 2143.358845] intf0 decoded packet:
02 00 00 2a 00 00 00 00
Jan 3 00:05:56 myth3 kernel: [ 2143.454029] intf0 decoded packet:
02 00 00 2a 00 00 00 00
Jan 3 00:05:56 myth3 kernel: [ 2143.558841] intf0 decoded packet:
02 00 00 00 00 00 00 00
000000008001000e 00 KEY_BACKSPACE_UP devinput
Jan 3 00:06:02 myth3 kernel: [ 2149.446507] intf0 decoded packet:
02 00 00 00 00 00 00 00
0000000080010001 00 KEY_ESC devinput
Jan 3 00:06:02 myth3 kernel: [ 2149.454013] intf0 decoded packet:
02 00 00 29 00 00 00 00
Jan 3 00:06:02 myth3 kernel: [ 2149.550507] intf0 decoded packet:
02 00 00 29 00 00 00 00
Jan 3 00:06:03 myth3 kernel: [ 2149.654498] intf0 decoded packet:
02 00 00 00 00 00 00 00
0000000080010001 00 KEY_ESC_UP devinput
Jan 3 00:06:09 myth3 kernel: [ 2155.910160] intf0 decoded packet:
02 00 00 00 00 00 00 00
Jan 3 00:06:09 myth3 kernel: [ 2155.918154] intf0 decoded packet:
02 00 00 52 00 00 00 00
Jan 3 00:06:09 myth3 kernel: [ 2156.014153] intf0 decoded packet:
02 00 00 52 00 00 00 00
Jan 3 00:06:09 myth3 kernel: [ 2156.118145] intf0 decoded packet:
02 00 00 00 00 00 00 00
Jan 3 00:06:10 myth3 kernel: [ 2157.310085] intf0 decoded packet:
02 00 00 00 00 00 00 00
Jan 3 00:06:10 myth3 kernel: [ 2157.318080] intf0 decoded packet:
02 00 00 51 00 00 00 00
Jan 3 00:06:10 myth3 kernel: [ 2157.414079] intf0 decoded packet:
02 00 00 51 00 00 00 00
Jan 3 00:06:10 myth3 kernel: [ 2157.518072] intf0 decoded packet:
02 00 00 00 00 00 00 00
Jan 3 00:06:12 myth3 kernel: [ 2158.902001] intf0 decoded packet:
02 00 00 00 00 00 00 00
Jan 3 00:06:12 myth3 kernel: [ 2158.909995] intf0 decoded packet:
02 00 00 50 00 00 00 00
Jan 3 00:06:12 myth3 kernel: [ 2159.005992] intf0 decoded packet:
02 00 00 50 00 00 00 00
Jan 3 00:06:12 myth3 kernel: [ 2159.109989] intf0 decoded packet:
02 00 00 00 00 00 00 00
Jan 3 00:06:14 myth3 kernel: [ 2160.781902] intf0 decoded packet:
02 00 00 00 00 00 00 00
Jan 3 00:06:14 myth3 kernel: [ 2160.789896] intf0 decoded packet:
02 00 00 4f 00 00 00 00
Jan 3 00:06:14 myth3 kernel: [ 2160.885897] intf0 decoded packet:
02 00 00 4f 00 00 00 00
Jan 3 00:06:14 myth3 kernel: [ 2160.989889] intf0 decoded packet:
02 00 00 00 00 00 00 00
There must be a secret decoder ring for the decoded packet because the
numbers in the packets don't correspond with the entries in the
lircd.conf file. For example, the packets that correspond to ENTER
contain a 0x28, but the lircd.conf value for ENTER is 0x1C. I wonder why
this does not work for the iMON mini. How do you decode/map these to
lircd.conf entries?
Other details follow...
/etc/sysconfig/lirc:
LIRCD_OPTIONS="--release --permission=666"
LIRC_DRIVER="devinput"
LIRC_DEVICE="/dev/input/by-id/usb-15c2_0042-event-if00"
ENABLE_LIRCMD="no"
/var/log/messages after boot with debug=1 set for the imon kernel module:
Jan 2 23:30:30 myth3 kernel: [ 11.305012] Registered IR keymap
rc-imon-pad
Jan 2 23:30:30 myth3 kernel: [ 11.305130] input: iMON Remote
(15c2:0042) as
/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/rc/rc0/input5
Jan 2 23:30:30 myth3 kernel: [ 11.305187] rc0: iMON Remote
(15c2:0042) as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/rc/rc0
Jan 2 23:30:30 myth3 kernel: [ 11.313145] imon 3-1:1.0: iMON
device (15c2:0042, intf0) on usb<3:2> initialized
Jan 2 23:30:30 myth3 kernel: [ 11.313168] imon 3-1:1.1: iMON
device (15c2:0042, intf1) on usb<3:2> initialized
Jan 2 23:30:30 myth3 kernel: [ 11.313198] usbcore: registered new
interface driver imon
Jan 2 23:30:30 myth3 kernel: [ 11.315086] IR RC5(x) protocol
handler initialized
Jan 2 23:30:30 myth3 kernel: [ 11.402080] IR RC6 protocol handler
initialized
Jan 2 23:30:30 myth3 kernel: [ 11.443348] IR JVC protocol handler
initialized
Jan 2 23:30:30 myth3 kernel: [ 11.476558] IR Sony protocol
handler initialized
Jan 2 23:30:30 myth3 kernel: [ 11.518928] lirc_dev: IR Remote
Control driver registered, major 250
Jan 2 23:30:30 myth3 kernel: [ 11.520340] IR LIRC bridge handler
initialized
default output after reboot running 'ir-keytable' (note the empty
enables protocol):
Found /sys/class/rc/rc0/ (/dev/input/event5) with:
Driver imon, table rc-imon-pad
Supported protocols: RC-6 Enabled protocols:
output after setting the protocol with 'ir-keytable -p RC-6; ir-keytable':
Protocols changed to RC-6
Found /sys/class/rc/rc0/ (/dev/input/event5) with:
Driver imon, table rc-imon-pad
Supported protocols: RC-6 Enabled protocols: RC-6
Thanks,
Todd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20110103/8165c611/attachment.htm>
More information about the mythtv-users
mailing list