[mythtv-users] Ortek VRC-1100 IR receiver on Gentoo

[mythtv]

On 04/05/2017 04:33 PM, Karl Newman wrote:
> On Wed, Apr 5, 2017 at 12:47 PM, mythtv <mythtv at mdabbs.org 
> <mailto:mythtv at mdabbs.org>> wrote:
>
>     On 04/05/2017 01:00 PM, Karl Newman wrote:
>
>         On Wed, Apr 5, 2017 at 10:36 AM, mythtv <mythtv at mdabbs.org
>         <mailto:mythtv at mdabbs.org> <mailto:mythtv at mdabbs.org
>         <mailto:mythtv at mdabbs.org>>> wrote:
>
>             On 04/05/2017 12:08 PM, Peter Bennett wrote:
>
>
>
>                 On 04/05/2017 12:45 PM, mythtv wrote:
>
>                     Can anyone assist me with getting the Ortek VRC-1100
>                     working on Gentoo.  Everything I read seems to be
>         Ubuntu
>                     related with hardware.conf files and what not.  Gentoo
>                     doesn't have that. I've seen some info on using
>         devinput
>                     but I don't think I have my kernel, my udev rules, and
>                     other stuff configured correctly.  irw does
>         nothing and
>                     mode2 says it doesn't work with this hardware
>         yet.  Please
>                     help. Thanks!
>
>
>                 I think you are over-complicating matters. It emulates a
>                 keyboard, so just plug it in and it works. I have 5 of
>         these
>                 on Ubuntu and raspbian systems. They are detected as a
>                 keyboard by the system. If that is not happening then
>         check
>                 logs to see what the error is. If you run lsusb you
>         should see
>                 this
>
>                 Bus 001 Device 004: ID 05a4:9881 Ortek Technology, Inc. IR
>                 receiver [VRC-1100 Vista MCE Remote Control]
>
>                 There are instructions in the wiki for making it work with
>                 lirc, but that seems rather a waste of time. It works fine
>                 without.
>
>                 Peter
>
>
>             If you're not using it with lirc, how do you map all of
>         the keys?
>             Is that explained in the inputlircd portion of the wiki
>         page? And
>             do you have to use the remote that came with it, or can
>         you use
>             other generic IR remotes like a Hauppauge or other MCE remote?
>
>
>         I'm using one of these on Gentoo without lirc. Here's my
>         section of the Wiki:
>         https://www.mythtv.org/wiki/Adesso_ARC-1100#Alternate_Configuration
>         <https://www.mythtv.org/wiki/Adesso_ARC-1100#Alternate_Configuration>
>         You map the keys using the key editor in MythFrontend setup.
>
>         Karl
>
>     Ok, so when I disable the lirc stuff in the kernel, and shutdown
>     lircd, I see entries in dmesg that it recognizes the device, but
>     following some guidance on https://www.mythtv.org/wiki/HID_Remotes
>     <https://www.mythtv.org/wiki/HID_Remotes>, ir-keytable doesn't see
>     any device.  What kernel settings do I need for ir-keytable to
>     even see it?  Nothing is happening with this thing except when I
>     plug it in, the red LED comes on for a second, then nothing.
>
>
> ir-keytable will not see it by default, because it doesn't exist in 
> /sys/class/rc/. Mine created devices at /dev/input/event5 (keyboard) 
> and /dev/input/event6 (mouse) by default. The udev rules I posted on 
> the wiki add a symlink at /dev/input/irremote0 (keyboard) and 
> /dev/input/irremote1 (mouse). You could try to find it using 
> `ir-keytable -d /dev/input/event0` and increment the number after 
> event until you find it. My receiver says this for that command:
> Name: HID 05a4:9881
> bus: 3, vendor/product: 05a4:9881, version: 0x0110
> Then you can show the scancode-key map by `ir-keytable -r -d 
> /dev/input/event4` or whatever event# you find it at.
>
>
Ok, I have the udev rules in place, and irremote0 and irremote1 show up 
under /dev/input.  They are linked to input2 and input4. But when Itry 
to test them with ir-keytable -d /dev/input/event2 -t I get nothing.  
I'm using a different remote, could that be the problem? Its an MCE 
remote but not the one that came with the receiver.