[Pkg-lirc-maint] Bug#872375: lirc: irrecord segfaults when recording a button

Francois Gouget fgouget at free.fr
Fri Sep 29 23:30:07 UTC 2017

On Sun, 24 Sep 2017, Alec Leamas wrote:
> I note that you seemingly havn't used mode2 (?) This is the tool to determine
> what kind of data the kernel makes available to lirc which in the end
> determines what driver to use. This is described in the configuration guide.

I ran it at some point and ir-keytable too but It did not really 
enlighten me.

# mode2 --driver devinput --list-devices
/dev/input/event13 [147a:e03e] Formosa21 eHome Infrared Transceiver version:  2.00 serial: 000100B6
/dev/input/by-id/usb-Formosa21_eHome_Infrared_Transceiver_000100B6-event-if00 -> ../event13
/dev/input/by-path/pci-0000:03:00.0-usb-0:1.4:1.0-event -> ../event13

# mode2 --driver default --list-devices
/dev/lirc0 [147a:e03e] Formosa21 eHome Infrared Transceiver version:  2.00 serial: 000100B6

# ir-keytable 
Found /sys/class/rc/rc0/ (/dev/input/event13) with:
        Driver mceusb, table rc-rc6-mce
        Supported protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp 
        Enabled protocols: lirc 
        Name: Media Center Ed. eHome Infrared 
        bus: 3, vendor/product: 147a:e03e, version: 0x1201
        Repeat delay = 500 ms, repeat period = 125 ms

> > but I had to recreate
> >    the remote configuration file from scratch as the one I used with lirc
> >    0.9.4c wouldn't work. The official guidelines don't talk about that
> >    incompatibility either.
> Actually, there shouldn't be anything incompatible between 0.9.4c and 0.10.0.
> This seems strange...

My configuration files were actually a bit older so maybe that's why. Or 
it's yet again a devinput issue. I don't know if that will offer a clue 
but here are the three generations:

 * http://fgouget.free.fr/tmp/lirc/Hauppauge_PVR350.conf.0.9.0-pre1.0
   I think this is the oldest one, created with lirc 0.9.0-pre1 and 
   apparently using devinput. This one has two sets of numbers for each 
   key but the second one is always 0.

   E.g.: KEY_MENU 0x04000400001F0D 0x00000000000000

 * http://fgouget.free.fr/tmp/lirc/Hauppauge_PVR350.conf.0.9.0-pre1
   This is the same as the previous one except I removed the extra 0x0 
   values. I think I had to do so to keep the configuration file 
   (I also removed flags and tweaked the gap at some point)

   E.g.: KEY_MENU 0x04000400001F0D

 * http://fgouget.free.fr/tmp/lirc/Hauppauge_PVR350.conf.0.10.0
   This is the new configuration, recreated from scratch with Lirc 
   0.10.0-2 using the default driver.
   The values are completely different.

   E.g.: KEY_MENU 0x17CD

Unfortunately I don't remember exactly when the second generation 
stopped working, but it was probably 6 to 12 months ago.

Francois Gouget <fgouget at free.fr>              http://fgouget.free.fr/
 "Only wimps use tape backup: _real_ men just upload their important stuff on
       ftp, and let the rest of the world mirror it ;)" -- Linus Torvalds

More information about the Pkg-lirc-maint mailing list