LibreElec + Cinergy DVB-S2 Dual Tuner + Terratec Remote generates double key events

finsher · December 7, 2018 at 8:28 PM

My Cinergy s2 card has an issue with double key events. I basically located the root cause but I don't know how to config what to avoid the double key event issue.

Problem: The card generates two similar ir devices, the only different is rc0 / rc1 resp. the device eventx / event y. ir-keytable sows the following:

Code

LibreELEC:/usr/lib/udev/rules.d # ir-keytable
Found /sys/class/rc/rc1/ (/dev/input/event14) with:
        Driver dw2102, table rc-terratec-cinergy-s2-dual
        Supported protocols: nec
        Enabled protocols:
        Name: IR-receiver inside an USB DVB re
        bus: 3, vendor/product: 153b:1182, version: 0x0000
        Repeat delay = 500 ms, repeat period = 125 ms
Found /sys/class/rc/rc0/ (/dev/input/event9) with:
        Driver dw2102, table rc-terratec-cinergy-s2-dual
        Supported protocols: nec
        Enabled protocols:
        Name: IR-receiver inside an USB DVB re
        bus: 3, vendor/product: 153b:1181, version: 0x0000
        Repeat delay = 500 ms, repeat period = 125 ms

Display More

I have successfully loaded a keytable and modified the rc_maps.cfg. But irw and kodi generate double key events if I press a button once on the remote:

Code

LibreELEC:/usr/lib/udev/rules.d # irw
160 0 KEY_OK devinput
160 0 KEY_OK devinput
67 0 KEY_UP devinput
67 0 KEY_UP devinput
6c 0 KEY_DOWN devinput
6c 0 KEY_DOWN devinput
69 0 KEY_LEFT devinput
69 0 KEY_LEFT devinput
6a 0 KEY_RIGHT devinput
6a 0 KEY_RIGHT devinput

Display More

I found out, that the keytable is loaded automatically for both devices rc0 and rc1, but I have just one remote. The output from ir-keytable -r -s rc0 is identical to ir-keytable -r -s rc1. if I clear the keytable for rc1 (ir-keytable -c -s rc1), everythings works fine.

Code

LibreELEC:/usr/lib/udev/rules.d # ir-keytable -c -s rc1
Old keytable cleared
LibreELEC:/usr/lib/udev/rules.d # irw
160 0 KEY_OK devinput
67 0 KEY_UP devinput
6c 0 KEY_DOWN devinput
69 0 KEY_LEFT devinput
6a 0 KEY_RIGHT devinput

Currently I have no idea how to disable either rc1 oder load the keytable only for rc0.

Any help is appreciated.

Thanks

**Iridium** · December 8, 2018 at 6:23 PM Official Post

I've changed the title for you to make it more "interesting" for other users.

1) We know it's LE - that's why you're here,

2) Cinergy DVB-S2 Dual Tuner shouldn't be relevant.

However, a good explanation of the issue.

Have you searched for "double key press" ?

**Da Flex** · December 8, 2018 at 6:56 PM Official Post

Deactivating the CEC add-on is maybe worth a try.

**HiassofT** · December 8, 2018 at 10:43 PM

Quote from Iridium

I've changed the title for you to make it more "interesting" for other users.

1) We know it's LE - that's why you're here,

2) Cinergy DVB-S2 Dual Tuner shouldn't be relevant.

I beg to differ, Cinergy DVB-S2 Dual Tuner could be very relevant - could you change the title back?

This is nothing I've seen before, as 2 IR devices are created and as they are identical the same configuration will be applied to both devices - and both will decode the signals thus giving double button presses.

Unless the device really should have 2 IR receivers (which would be very strange) I suspect this could be a driver bug and should be reported upstream.

finsher which LE version are you using, and which platform? Are you using the CrazyCat / TBS drivers or the standard kernel drivers?

The easiest workaround is to add "ir-keytable -s rc1 -c" to .config/autostart.sh for now.

so long,

Hias

finsher · December 9, 2018 at 7:40 PM

Thanks for changing this title back. As Hias wrote, that is espically related to this kind of dual tuner card. There was a similar issue, mentioned in the German vdr forum. I don't know if I am allowed to past other forum links, here is it: vdr-forum Link. Unfortunaltely this does not help me.

Back to your question: it is an Intel Atom 525 based mini PC with the Zotac IONITX S-E mainboard. The system is LE 8.2.5

I am using the standard kernel driver, lirc is disabled in Kodi. The card has one remote receiver plug for only one remote. This card is identical to the TeVii 480/482. Here is a picture of this card:

I will try adding "ir-keytable -s rc1 -c" to .config/autostart.sh as a workaround, but I am supporting as good as I can to fix this issue.

**HiassofT** · December 10, 2018 at 11:14 AM

Could you test with the latest LE alpha release (currently 8.90.009)?

By default it uses the official DVB drivers from the Linux kernel. With the driver addon chooser you can switch to 2 alternative sets of DVB drivers: latest drivers from linux kernel is a backport of (currently only a bit) newer official kernel drivers and TBS / CrazyCat add some out-of-tree drivers and patches that are not included in the official Linux kernel. LE 8.2 always used the CrazyCat drivers.

It would be interesting to know which set of drivers is required for your card and if the IR problem shows up with all of them or only on some specific ones.

Please also grab dmesg output when testing with the various DVB drivers and post them here (just run "dmesg | paste" and post the URL).

so long,

Hias

finsher · December 11, 2018 at 9:28 AM

I'll prepare a test with LE 8.90.009 as soon as I can. I have to swap the HDD, since I don't want to tinker with my current system. I'll let you know the results.

**HiassofT** · December 11, 2018 at 12:42 PM

I think you should be able to test by booting LE 8.90.009 from an USB stick and using live / run mode instead of the installer.

so long,

Hias

finsher · December 14, 2018 at 9:10 PM

I did a live test with LE 8.90.009. The rusult from ir-keytable right after the system start:

Code

LibreELEC (official): 8.90.009 (Generic.x86_64)
LibreELEC:~ # ir-keytable
/sys/class/rc/: No such file or directory
No devices found
LibreELEC:~ #

dmesg | paste result: http://ix.io/1w0l

To choose other drivers (i.e newer kernel drivers) I have to reboot. I am not sure if it make sense to reboot a live system for a driver change, since the selection might not be stored...?

lsusb shows at least the card is there:

Code

LibreELEC:/dev/input/by-path # lsusb
Bus 001 Device 003: ID 1908:1320 GEMBIRD PhotoFrame PF-15-1
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 013 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 012 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 011 Device 002: ID 05af:0630 Jing-Mold Enterprise Co., Ltd
Bus 011 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 153b:1182 TerraTec Electronic GmbH Cinergy S2 PCIe Dual Port 2
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 153b:1181 TerraTec Electronic GmbH Cinergy S2 PCIe Dual Port 1
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 015 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 014 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Display More

**HiassofT** · December 15, 2018 at 10:52 AM

Thanks a lot for the logs!

As suspected the card isn't supported by the official linux kernel drivers but uses the out-of-tree CrazyCat drivers.This is good to know since we now know whom to bother with this issue.

I haven't used Live/Run mode myself yet but I thought it would store user/configuration data on the USB stick. So selecting a different DVB driver set might work. Could you give that a try?

so long,

Hias

finsher · December 16, 2018 at 7:35 PM

Interesting, I haven't done any driver swap in LE 8.2.5...

The CrazyCat driver package did not install in life boot. I did a clean install on a new hard disk and swapped the driver to CrazyCat. The result is now:

Code

LibreELEC (official): 8.90.009 (Generic.x86_64)
LibreELEC:~ # ir-keytable
Found /sys/class/rc/rc1/ (/dev/input/event13) with:
        Name: Terratec Cinergy S2 Dual (tuner 2)
        Driver: dw2102, table: rc-terratec-cinergy-s2-dual
        lirc device: /dev/lirc1
        Supported protocols: nec
        Enabled protocols: nec
        bus: 3, vendor/product: 153b:1182, version: 0x0000
        Repeat delay = 500 ms, repeat period = 125 ms
Found /sys/class/rc/rc0/ (/dev/input/event12) with:
        Name: Terratec Cinergy S2 Dual (tuner 1)
        Driver: dw2102, table: rc-terratec-cinergy-s2-dual
        lirc device: /dev/lirc0
        Supported protocols: nec
        Enabled protocols: nec
        bus: 3, vendor/product: 153b:1181, version: 0x0000
        Repeat delay = 500 ms, repeat period = 125 ms

Display More

dmesg | paste can be found here: http://ix.io/1w9x

The remote is running out of the box, means no special keytable is necessary, but with the same result. One key press will show two key presses.

Code

LibreELEC:~ # irw
67 0 KEY_UP devinput
67 0 KEY_UP devinput
6c 0 KEY_DOWN devinput
6c 0 KEY_DOWN devinput
69 0 KEY_LEFT devinput
69 0 KEY_LEFT devinput
6c 0 KEY_DOWN devinput
6c 0 KEY_DOWN devinput

I compared the results between ir-keytable -r -s rc0 and ir-keytable -r -s rc1, both are equal. Clearing the keytable with ir-keytable -c -s rc1 shows the same effect as in 8.2.5: One press, one result.

Code

LibreELEC:~ # irw
67 0 KEY_UP devinput
6c 0 KEY_DOWN devinput
69 0 KEY_LEFT devinput
6a 0 KEY_RIGHT devinput
160 0 KEY_OK devinput

I have seen, that the lirc driver is loaded. I am not able to disable lirc, since the menu item in Kodi is not available anymore.

**HiassofT** · December 16, 2018 at 9:13 PM

Thanks a lot for testing and the logs, everything's fine (except that the CrazyCat driver registers IR devices for both of the 2 receivers).

The lirc device is fine, you usually get it with IR receivers (the Lirc option in LE 8.2 settings controlled the lircd userspace daemon, this is something different).

crazycat I think this could be fixed by registering an rc-core device only for one of the 153b:1181 / 153b:1182 USB devices. Looks like the IR receiver is connected to both of the devices on the dual tuner card so enabling IR on both of them results in doubled IR events. Can you have a look at that?

finsher · December 16, 2018 at 9:53 PM

Okay, I am in standby. If you need me to test fixes, let me know.

**crazycat** · December 17, 2018 at 1:54 AM

Quote from HiassofT

crazycat I think this could be fixed by registering an rc-core device only for one of the 153b:1181 / 153b:1182 USB devices. Looks like the IR receiver is connected to both of the devices on the dual tuner card so enabling IR on both of them results in doubled IR events. Can you have a look at that?

so IR sensor connected to both Cypress FX2 ?

**HiassofT** · December 17, 2018 at 8:59 AM

Quote from crazycat

so IR sensor connected to both Cypress FX2 ?

Yes, looks like that.

so long,

Hias