[mythtv-users] MCE remote after 0.21 -> 0.27 upgrade

[Jerome Yuzyk]

On Monday, September 07, 2015 07:55:27 PM Alec Leamas wrote:
> On 07/09/15 19:00, Jerome Yuzyk wrote:
> 
> > [250159.289045] usb 5-1: new full-speed USB device number 3 using uhci_hcd
> > [250159.448065] usb 5-1: New USB device found, idVendor=0609, idProduct=031d
> > [250159.448073] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> > [250159.448078] usb 5-1: Product: eHome Infrared Transceiver
> > [250159.448083] usb 5-1: Manufacturer: SMK
> > [250159.448088] usb 5-1: SerialNumber: SM007OxF
> > [250159.456072] Registered IR keymap rc-rc6-mce
> > [250159.456239] input: Media Center Ed. eHome Infrared Remote Transceiver (0609:031d) as /devices/pci0000:00/0000:00:1a.2/usb5/5-1/5-1:1.0/rc/rc0/input16
> > [250159.456298] rc0: Media Center Ed. eHome Infrared Remote Transceiver (0609:031d) as /devices/pci0000:00/0000:00:1a.2/usb5/5-1/5-1:1.0/rc/rc0
> > [250159.456399] input: MCE IR Keyboard/Mouse (mceusb) as /devices/virtual/input/input17
> > [250159.457540] rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0
> > [250159.600066] mceusb 5-1:1.0: Registered SMK eHome Infrared Transceiver with mce emulator interface version 1
> > [250159.600074] mceusb 5-1:1.0: 2 tx ports (0x0 cabled) and 2 rx sensors (0x1 active)
> 
> OK, basically this looks good. Now, following [1], there is two ways, 
> both of which should work from what we know now:
> 
>    - Use the kernel decoding. This means configuring the lirc-keytable 
> device maps so it works, and then let lirc work on top of this using the 
> devinput driver on a /dev/input/event* device.
>    - Or let LIRC do the decoding itself, reading the raw timing data 
> from the kernel using a correct, perhaps custom-specific lircd.conf. 
> This means using the default driver, probably on  the /dev/lirc0 device
> 
> Have you any idea what route you would prefer?
> 
> [1] http://lirc.sourceforge.net/lirc.org/html/configuration-guide.html

I've been using kernel decoding (devinput) because that's all that would work at first, recommended by a Fedora user when I first started asking.

I have read and tried that guide more than few times - very handy. But I think I have become befuddled by the whole remote-as-keyboard layer. ir-keytable is generating scancodes that map into X keycodes that X and MythTV can't see. I have edited some of /etc/rc_keymaps/rc6_mce to use scancodes that are recognized by Myth at least - enough to get it more workable. They're also seen by an open terminal in the foreground. When I've loaded lircd irw has never generated anything than escape codes for arrow keys and Enter; mode2 just returns.

What I would like is to have PVR-500 MCE Kit on Fedora the "stock" way for the modern in-kernel mceusb and lirc bits. My setup can't be custom - in 0.21 way back I just dropped a file for the 500 Kit from the contribs folder into lircd.conf and it worked for 9 years. There must be a proper modern config for these Kits - they're not clones.

I would like to be able to use the remote with non-Myth apps including irexec. Fundamentally I don't want the remote to be a keyboard at all I guess, whatever that means for the setup I need. Though, I don't understand why not-a-keyboard remotes are treated as keyboards anyway.

I could send a snapshot of my configs, or you could tell me what lines I need to set. I have fiddled with "device=devinput" to try "mceusb" or "default" in /etc/lirc/lirc_options.conf as that's the only valid place I see to set a driver in Fedora 22. Ubuntu uses a /etc/lirc/hardware.conf that sets a number of things that I don't see in Fedora configs so maybe that matters. Apparently /etc/sysconfig/lirc is obsolete now and wasn't created by any package.

Appreciate your efforts.


-- 
A little of Jerome's MythTV World: http://mythtv.bss.ab.ca