[mythtv-users] Need help to setup iMON remote and VFD on Fedora 14

[Jarod Wilson]

On Nov 12, 2010, at 2:25 AM, Andrew Junev wrote:

> Hello Jarod,
> 
> Friday, November 12, 2010, 8:37:11 AM, you wrote:
> 
>>> When keys are pressed on the remote, I get these in /var/log/messages:
>>> 
>>> Nov 11 19:25:22 fedora kernel: [ 4390.670952] imon 5-2:1.0: imon_incoming_packet: unknown keypress, code 0x100000c
>>> Nov 11 19:25:22 fedora kernel: [ 4390.702935] intf0 decoded packet: 01 00 00 0e 00 00 00 00
>>> Nov 11 19:25:22 fedora kernel: [ 4390.702947] imon 5-2:1.0: imon_incoming_packet: unknown keypress, code 0x100000e
> 
>> Hm. Can you isolate exactly which keys are generating these? The issue
>> here is that these scancodes aren't mapped to any keycodes in the
>> driver, as I/we haven't ever seen them before.
> 
> 
> Yes, of course I can do this. But I get these messages even if lirc
> daemon is stopped. Do you think that's a "proper" behavior?

Yes, it is. Those are from the kernel driver, which has absolutely
no reliance upon lirc.


>>> Nov 11 19:25:22 fedora kernel: [ 4390.742932] intf0 decoded packet: 01 00 7f 00 00 00 00 00
> 
>> Note no 'unknown keypress' after this one, as that scancode maps to KEY_DOWN.
> 
>>> Nov 11 19:25:22 fedora kernel: [ 4390.782934] intf0 decoded packet: 01 00 ff 0e 00 00 00 00
>>> Nov 11 19:25:22 fedora kernel: [ 4390.782948] imon 5-2:1.0: imon_incoming_packet: unknown keypress, code 0x100ff0e
>>> 
>>> 
>>> Am I right thinking it's not going through lirc?
> 
>> Yes. If we fail to find a scancode, then we are unable to send a
>> keycode, and lircd in devinput mode relies upon keycodes.
> 
> 
>> We just need to add some more scancode->keycode
>> mappings to the driver. If you can figure out which button each of
>> those unknown scancodes maps to, I can get them added to the driver.
> 
> Sure! I'll get the "missing" scancodes list and will send it to you.
> If I get it right, irrecord doesn't work with devinput so the easiest
> way is to get the codes from /var/log/messages?

In this case, irrecord definitely won't work. There's no input layer
mapping that exists for the codes, so they're not coming through the
input device. So yes, grabbing from /var/log/messages (or from dmesg
output) is the way to go.

> P.S. Is it Ok that 'irw' doesn't show anything as well, even for the
> codes known by the driver?

No, irw should report all the known keys, so things must not actually
be entirely correct w/your config setup. Actually, now that I think
about it... You have lircd pointed at the -event-mouse by-id symlink,
but I think there's another symlink that should be in there, and its
the one you actually want here.

-- 
Jarod Wilson
jarod at wilsonet.com