[mythtv-users] LIRC v ir-keytable -- Remote Control

Alec Leamas leamas.alec at gmail.com
Mon Feb 9 15:39:19 UTC 2015


On 09/02/15 16:09, jim wrote:
>
> On 02/09/2015 09:54 AM, Alec Leamas wrote:
>> On 09/02/15 15:34, jim wrote:
>>
>>> Some of the keys, such as volume up, result in a temporary pop-up window
>>> showing a speaker icon with associated increase in volume, but nothing
>>> is shown by ir-keytable -t on the command line.
>>
>> Is it  that the kernel sees your device as a keyboard rather than a
>> remote? This should be obvious when looking at the dmesg output.

> Here is the relevant part of dmesg. I can't claim to be an expert in
> reading this output. Is there any significance to rc0/input17 here vice
> the input14 in the ir-keytable output?
>
> [    9.895438] Registered IR keymap rc-rc6-mce
> [    9.895741] input: Media Center Ed. eHome Infrared Remote Transceiver

> [    9.910085] IR LIRC bridge handler initialized
> [   10.054795] mceusb 3-4:1.0: Registered Topseed Technology Corp. eHome
> Infrared Transceiver with mce emulator interface version 2
> [   10.054798] mceusb 3-4:1.0: 2 tx ports (0x0 cabled) and 2 rx sensors
> (0x1 active)
> [   10.054817] usbcore: registered new interface driver mceusb


All right, it is indeed a remote.

Now, where are the lost events?

Just a shot in the dark: have you a ir_mce_kbd_decoder  kernel module 
loaded. What happens if you unload (reboots without) it? Is this module 
stealing your events (I know nothing more than what the name implies...)

Another way would be to try the lirc bridge.  You might have to enable 
the lirc protocol for this. After doing so, make a simple "cat 
/dev/lirc0" and press remote buttons. There should be visible garbage 
coming from the device for each press. If so, you know for sure that 
there is timing data passed from the driver. That would be a start.


Cheers!

--alec


More information about the mythtv-users mailing list