<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, Jun 27, 2015 at 3:19 PM, Stephen Worthington <span dir="ltr"><<a href="mailto:stephen_agent@jsw.gen.nz" target="_blank">stephen_agent@jsw.gen.nz</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Sat, 27 Jun 2015 14:23:25 -0400, you wrote:<br>
<br>
>On Sat, Jun 27, 2015 at 2:09 PM, Stephen Worthington <<br>
><a href="mailto:stephen_agent@jsw.gen.nz">stephen_agent@jsw.gen.nz</a>> wrote:<br>
><br>
>> On Sat, 27 Jun 2015 01:48:27 -0400, you wrote:<br>
>><br>
>> >On Mon, Jun 22, 2015 at 1:23 AM, Jerry Rubinow <<a href="mailto:jerrymr@gmail.com">jerrymr@gmail.com</a>> wrote:<br>
>> ><br>
>> >> On Sun, Jun 21, 2015 at 5:10 AM, Hika van den Hoven <<a href="mailto:hikavdh@gmail.com">hikavdh@gmail.com</a>><br>
>> >> wrote:<br>
>> >><br>
>> >>> Hoi Jerry,<br>
>> >>><br>
>> >>> Sunday, June 21, 2015, 6:21:10 AM, you wrote:<br>
>> >>><br>
>> >>> > I have a newly setup LIVA box, frontend only, using the latest<br>
>> >>> mythbuntu.<br>
>> >>> > It has a USB ir receiver, and I configured lirc to use mceusb remote.<br>
>> >>><br>
>> >>> > If I stop lircd and run mode2, it spews out data when I press<br>
>> buttons on<br>
>> >>> > the remote. So I know the hardware is working. However I can't get<br>
>> >>> irw to<br>
>> >>> > print anything. The receiver is the same ir receiver I was using<br>
>> with<br>
>> >>> my<br>
>> >>> > original frontend, configured the same way, although with an older<br>
>> >>> version<br>
>> >>> > of mythbuntu a few years ago.<br>
>> >>><br>
>> >>> > Info from the new machine:<br>
>> >>><br>
>> >>> > jerry@squeek:~$ lsusb<br>
>> >>> > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub<br>
>> >>> > Bus 001 Device 003: ID 1784:0008 TopSeed Technology Corp. eHome<br>
>> Infrared<br>
>> >>> > Transceiver<br>
>> >>> > Bus 001 Device 002: ID 04f2:0402 Chicony Electronics Co., Ltd Genius<br>
>> >>> > LuxeMate i200 Keyboard<br>
>> >>> > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br>
>> >>><br>
>> >>> > jerry@squeek:~$ lsmod | grep lirc<br>
>> >>> > ir_lirc_codec 13062 3<br>
>> >>> > lirc_dev 19980 1 ir_lirc_codec<br>
>> >>> > rc_core 28718 13<br>
>> >>> ><br>
>> >>><br>
>> ir_sharp_decoder,lirc_dev,ir_lirc_codec,ir_rc5_decoder,ir_nec_decoder,ir_sony_decoder,mceusb,ir_mce_kbd_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_sanyo_decoder,rc_rc6_mce<br>
>> >>><br>
>> >>> > jerry@squeek:~$ ls -l /dev/lirc*<br>
>> >>> > crw------- 1 root root 250, 0 Jun 20 22:55 /dev/lirc0<br>
>> >>> > lrwxrwxrwx 1 root root 15 Jun 20 22:55 /dev/lircd -><br>
>> /run/lirc/lircd<br>
>> >>><br>
>> >>> > jerry@squeek:~$ ps aux | grep lirc<br>
>> >>> > root 566 0.0 0.1 33112 2000 ? Ss Jun20 0:00<br>
>> >>> > /usr/sbin/lircd --output=/run/lirc/lircd --device=/dev/lirc0<br>
>> >>><br>
>> >>> > Any suggestions?<br>
>> >>><br>
>> >>> > -Jerry<br>
>> >>><br>
>> >>> Have you read this thread from early this month "Anyone Using LIRC on<br>
>> >>> CentOS 6.6?" A lot of possible issues come up there!<br>
>> >>><br>
>> >>> Tot mails,<br>
>> >>> Hika mailto:<a href="mailto:hikavdh@gmail.com">hikavdh@gmail.com</a><br>
>> >>><br>
>> >>> "Zonder hoop kun je niet leven<br>
>> >>> Zonder leven is er geen hoop<br>
>> >>> Het eeuwige dilemma<br>
>> >>> Zeker als je hoop moet vernietigen om te kunnen overleven!"<br>
>> >>><br>
>> >>> De lerende Mens<br>
>> >>><br>
>> >>><br>
>> >> Thanks for the pointer, Hika. I spent a few hours fiddling around,<br>
>> mostly<br>
>> >> with ir-keytables. It sees the remote, but it seems to not be<br>
>> interpreting<br>
>> >> the signal properly. Here's is the output of ir-keytables -t. It's not<br>
>> >> seeing any key events, and the scancodes don't look like they're broken<br>
>> up<br>
>> >> correctly. This is from pressing the same button on the remote<br>
>> repeatedly.<br>
>> >><br>
>> >> Testing events. Please, press CTRL-C to abort.<br>
>> >> 1434950415.277167: event type EV_MSC(0x04): scancode = 0x4007<br>
>> >> 1434950415.277167: event type EV_SYN(0x00).<br>
>> >> 1434950415.629476: event type EV_MSC(0x04): scancode = 0x4007<br>
>> >> 1434950415.629476: event type EV_SYN(0x00).<br>
>> >> 1434950416.141482: event type EV_MSC(0x04): scancode = 0x4007<br>
>> >> 1434950416.141482: event type EV_SYN(0x00).<br>
>> >> 1434950416.333429: event type EV_MSC(0x04): scancode = 0x2003e10<br>
>> >> 1434950416.333429: event type EV_SYN(0x00).<br>
>> >> 1434950417.197495: event type EV_MSC(0x04): scancode = 0x400<br>
>> >> 1434950417.197495: event type EV_SYN(0x00).<br>
>> >> 1434950417.357055: event type EV_MSC(0x04): scancode = 0x400782<br>
>> >> 1434950417.357055: event type EV_SYN(0x00).<br>
>> >> 1434950418.765469: event type EV_MSC(0x04): scancode = 0x2003e10<br>
>> >> 1434950418.765469: event type EV_SYN(0x00).<br>
>> >> 1434950418.893453: event type EV_MSC(0x04): scancode = 0x4007<br>
>> >> 1434950418.893453: event type EV_SYN(0x00).<br>
>> >><br>
>> >> -Jerry<br>
>> >><br>
>> >I tried reinstalling mythbuntu 14.04 again, same issue. Uninstalled lirc,<br>
>> >didn't help. I tried upgrading to Ubuntu 15.04, but same issue with the<br>
>> >irregular scan codes.<br>
>> ><br>
>> >I tried installing the beta of Windows 10 and a Windows build of<br>
>> >mythfrontend from here, <a href="http://sourceforge.net/projects/mythtvwindows/" rel="noreferrer" target="_blank">http://sourceforge.net/projects/mythtvwindows/</a><br>
>> ><br>
>> >Mythfrontend started up and recognized button presses on the remote. So<br>
>> >it's not a hardware incompatibility between the IR receiver and the LIVA.<br>
>> >I tried two different MCE remotes and both cause the same issue with<br>
>> >scancodes. I've googled a lot and I haven't been able to find information<br>
>> >about trouble at this level.<br>
>><br>
>> "Older version of mythbuntu" says it all - there have been big changes<br>
>> in how IR receivers work in the kernel, and likely your old config is<br>
>> for the old way and needs significant updating to work now. The<br>
>> driver for the MCE remotes has been moved into the kernel.<br>
>><br>
>> So what is your config? You might like to take a look at my working<br>
>> Mythbuntu 14.04 config for my "SMK Manufacturing, Inc. eHome Infrared<br>
>> Receiver" and my Hauppague Nova-TD 500 and HVR-900r2 IR receivers. It<br>
>> uses the new devinput driver and is available on my web server:<br>
>><br>
>> <a href="http://www.jsw.gen.nz/mythtv/mythbuntu-devinput-lirc.bz2" rel="noreferrer" target="_blank">http://www.jsw.gen.nz/mythtv/mythbuntu-devinput-lirc.bz2</a><br>
>><br>
>> Read the README file for some help with how to configure and test a<br>
>> devinput lirc setup.<br>
<br>
><br>
</div></div><span class="">>Thanks, I'll take a look at your config, maybe it will shed some light. To<br>
>be clear though, the config on my old computer is not the issue. I did a<br>
>clean install on the new computer - didn't migrate any settings, wiped the<br>
>disk. So the default mythbuntu 14.04 did not produce a workable<br>
>configuration. I also tried uninstalling lirc and just dealing with<br>
>ir-keytable - I'm not as familiar with that as with lirc, but the raw<br>
>scancodes looked damaged.<br>
><br>
>Thanks for straightening out my top posting, btw.<br>
><br>
>-Jerry<br>
<br>
</span>Yes, I had the same thing. The default Mythbuntu lirc config did not<br>
work for using the devinput driver (that was in 12.04, IIRC, when I<br>
had to update for the kernel driver). But I never had bad keycodes<br>
like you are getting. That suggests that the wrong keymap file is<br>
being used to translate them. Or even the wrong protocol (RC-5, RC-6<br>
etc) has been selected, so it is using the wrong wordsize for decoding<br>
the bit patterns.<br>
<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div><br></div><div>When I used ir-keytable, I had it configured for RC6, which as far as I can tell is what mce uses. Part of the difficulty I'm having is I don't really understand the relationship between lirc, ir-keytables, and the IR kernel drivers.</div><div><br></div><div>Looking over your readme, it seems like the udev rules map a particular usb-connected hardware device to a node in /dev, and that's where the raw bit stream from the device ends up. Then there's some magic which controls which driver is used to interpret the bits and produce scancodes - I don't really know how that happens. Then rc_maps.cfg associates a driver with a keymap file. Then the keymap controls how the scancodes are converted to keys.</div><div><br></div><div>I don't really follow the all the comments in rc_maps.cfg about uevent. I also don't understand why one would need lirc at all if ir-keytable is working.</div><div><br></div><div>-Jerry</div></div></div></div>