[mythtv-users] Can't get lirc or irw to work, but mode2 works

Sat Jun 27 19:19:43 UTC 2015

On Sat, 27 Jun 2015 14:23:25 -0400, you wrote:

>On Sat, Jun 27, 2015 at 2:09 PM, Stephen Worthington <
>stephen_agent at jsw.gen.nz> wrote:
>
>> On Sat, 27 Jun 2015 01:48:27 -0400, you wrote:
>>
>> >On Mon, Jun 22, 2015 at 1:23 AM, Jerry Rubinow <jerrymr at gmail.com> wrote:
>> >
>> >> On Sun, Jun 21, 2015 at 5:10 AM, Hika van den Hoven <hikavdh at gmail.com>
>> >> wrote:
>> >>
>> >>> Hoi Jerry,
>> >>>
>> >>> Sunday, June 21, 2015, 6:21:10 AM, you wrote:
>> >>>
>> >>> > I have a newly setup LIVA box, frontend only, using the latest
>> >>> mythbuntu.
>> >>> > It has a USB ir receiver, and I configured lirc to use mceusb remote.
>> >>>
>> >>> > If I stop lircd and run mode2, it spews out data when I press
>> buttons on
>> >>> > the remote.  So I know the hardware is working.  However I can't get
>> >>> irw to
>> >>> > print anything.  The receiver is the same ir receiver I was using
>> with
>> >>> my
>> >>> > original frontend, configured the same way, although with an older
>> >>> version
>> >>> > of mythbuntu a few years ago.
>> >>>
>> >>> > Info from the new machine:
>> >>>
>> >>> > jerry at squeek:~$ lsusb
>> >>> > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>> >>> > Bus 001 Device 003: ID 1784:0008 TopSeed Technology Corp. eHome
>> Infrared
>> >>> > Transceiver
>> >>> > Bus 001 Device 002: ID 04f2:0402 Chicony Electronics Co., Ltd Genius
>> >>> > LuxeMate i200 Keyboard
>> >>> > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> >>>
>> >>> > jerry at squeek:~$ lsmod | grep lirc
>> >>> > ir_lirc_codec          13062  3
>> >>> > lirc_dev               19980  1 ir_lirc_codec
>> >>> > rc_core                28718  13
>> >>> >
>> >>>
>> 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
>> >>>
>> >>> > jerry at squeek:~$ ls -l /dev/lirc*
>> >>> > crw------- 1 root root 250, 0 Jun 20 22:55 /dev/lirc0
>> >>> > lrwxrwxrwx 1 root root     15 Jun 20 22:55 /dev/lircd ->
>> /run/lirc/lircd
>> >>>
>> >>> > jerry at squeek:~$ ps aux  | grep lirc
>> >>> > root       566  0.0  0.1  33112  2000 ?        Ss   Jun20   0:00
>> >>> > /usr/sbin/lircd --output=/run/lirc/lircd --device=/dev/lirc0
>> >>>
>> >>> > Any suggestions?
>> >>>
>> >>> > -Jerry
>> >>>
>> >>> Have you read this thread from early this month "Anyone Using LIRC on
>> >>> CentOS 6.6?" A lot of possible issues come up there!
>> >>>
>> >>> Tot mails,
>> >>>   Hika                            mailto:hikavdh at gmail.com
>> >>>
>> >>> "Zonder hoop kun je niet leven
>> >>> Zonder leven is er geen hoop
>> >>> Het eeuwige dilemma
>> >>> Zeker als je hoop moet vernietigen om te kunnen overleven!"
>> >>>
>> >>> De lerende Mens
>> >>>
>> >>>
>> >> Thanks for the pointer, Hika.  I spent a few hours fiddling around,
>> mostly
>> >> with ir-keytables.  It sees the remote, but it seems to not be
>> interpreting
>> >> the signal properly.  Here's is the output of ir-keytables -t.  It's not
>> >> seeing any key events, and the scancodes don't look like they're broken
>> up
>> >> correctly.  This is from pressing the same button on the remote
>> repeatedly.
>> >>
>> >> Testing events. Please, press CTRL-C to abort.
>> >> 1434950415.277167: event type EV_MSC(0x04): scancode = 0x4007
>> >> 1434950415.277167: event type EV_SYN(0x00).
>> >> 1434950415.629476: event type EV_MSC(0x04): scancode = 0x4007
>> >> 1434950415.629476: event type EV_SYN(0x00).
>> >> 1434950416.141482: event type EV_MSC(0x04): scancode = 0x4007
>> >> 1434950416.141482: event type EV_SYN(0x00).
>> >> 1434950416.333429: event type EV_MSC(0x04): scancode = 0x2003e10
>> >> 1434950416.333429: event type EV_SYN(0x00).
>> >> 1434950417.197495: event type EV_MSC(0x04): scancode = 0x400
>> >> 1434950417.197495: event type EV_SYN(0x00).
>> >> 1434950417.357055: event type EV_MSC(0x04): scancode = 0x400782
>> >> 1434950417.357055: event type EV_SYN(0x00).
>> >> 1434950418.765469: event type EV_MSC(0x04): scancode = 0x2003e10
>> >> 1434950418.765469: event type EV_SYN(0x00).
>> >> 1434950418.893453: event type EV_MSC(0x04): scancode = 0x4007
>> >> 1434950418.893453: event type EV_SYN(0x00).
>> >>
>> >> -Jerry
>> >>
>> >I tried reinstalling mythbuntu 14.04 again, same issue.  Uninstalled lirc,
>> >didn't help.  I tried upgrading to Ubuntu 15.04, but same issue with the
>> >irregular scan codes.
>> >
>> >I tried installing the beta of Windows 10 and a Windows build of
>> >mythfrontend from here, http://sourceforge.net/projects/mythtvwindows/
>> >
>> >Mythfrontend started up and recognized button presses on the remote.  So
>> >it's not a hardware incompatibility between the IR receiver and the LIVA.
>> >I tried two different MCE remotes and both cause the same issue with
>> >scancodes.  I've googled a lot and I haven't been able to find information
>> >about trouble at this level.
>>
>> "Older version of mythbuntu" says it all - there have been big changes
>> in how IR receivers work in the kernel, and likely your old config is
>> for the old way and needs significant updating to work now.  The
>> driver for the MCE remotes has been moved into the kernel.
>>
>> So what is your config?  You might like to take a look at my working
>> Mythbuntu 14.04 config for my "SMK Manufacturing, Inc. eHome Infrared
>> Receiver" and my Hauppague Nova-TD 500 and HVR-900r2 IR receivers.  It
>> uses the new devinput driver and is available on my web server:
>>
>>   http://www.jsw.gen.nz/mythtv/mythbuntu-devinput-lirc.bz2
>>
>> Read the README file for some help with how to configure and test a
>> devinput lirc setup.

>
>Thanks, I'll take a look at your config, maybe it will shed some light.  To
>be clear though, the config on my old computer is not the issue.  I did a
>clean install on the new computer - didn't migrate any settings, wiped the
>disk.  So the default mythbuntu 14.04 did not produce a workable
>configuration.  I also tried uninstalling lirc and just dealing with
>ir-keytable - I'm not as familiar with that as with lirc, but the raw
>scancodes looked damaged.
>
>Thanks for straightening out my top posting, btw.
>
>-Jerry

Yes, I had the same thing.  The default Mythbuntu lirc config did not
work for using the devinput driver (that was in 12.04, IIRC, when I
had to update for the kernel driver).  But I never had bad keycodes
like you are getting.  That suggests that the wrong keymap file is
being used to translate them.  Or even the wrong protocol (RC-5, RC-6
etc) has been selected, so it is using the wrong wordsize for decoding
the bit patterns.