[SOLVED] LibreELEC + PCTV 461e + XBox One Remote

nicobee · July 27, 2017 at 11:37 AM

Hello everybody!

I searched the net for a while but did not find a solution for my problem. So I am hopeful, that somebody of you can help me out.

I am running LibreELEC 8.0.2 on a RPi 3.

An IR receiver is connected via GPIO. It is feeded with an XBox One Media Control.

For Live-TV I am using an PCTV 461e USB stick (DVB-S/S2).

Everything works fine until I connect the DVB-stick. From then on the responsiveness of the remote control is unreliable, since some of the button pushes are not recognized by Lirc/Kodi.

In my opinion this behaviour is reasoned in the fact that the DVB-stick has got it's own IR receiver and therefore two IR receivers are working inside the system and interfere with each other.

Part of dmesg output:

Code

[    3.638898] lirc_dev: IR Remote Control driver registered, major 243
[    3.682150] lirc_rpi: module is from the staging directory, the quality is unknown, you have been warned.
[    3.693577] Linux video capture interface: v2.00
[    3.693588] WARNING: You are using an experimental version of the media stack.
[    3.693588]     As the driver is backported to an older kernel, it doesn't offer
[    3.693588]     enough quality for its usage in production.
[    3.693588]     Use it with care.
[    3.693588] Latest git patches (needed if you report a bug to linux-media@vger.kernel.org):
[    3.693588]     a02ff2e02bee64e9955dbfd8811874c3f3880f58 cx231xx: Fix TBS MAC reading.
[    3.893160] usb 1-1.3: New device PCTV PCTV 461 @ 480 Mbps (2013:0258, interface 0, class 0)
[    3.893170] usb 1-1.3: DVB interface 0 found: isoc
[    3.893264] usb 1-1.3: em28178#0: chip ID is em28178
[    4.027912] usbcore: registered new interface driver brcmfmac
[    4.267965] brcmfmac: Firmware version = wl0: May 27 2016 00:13:38 version 7.45.41.26 (r640327) FWID 01-df77e4a7
[    4.270440] usb 1-1.3: em28178#0: EEPROM ID = 26 00 01 00, EEPROM hash = 0xa63c76a0
[    4.270450] usb 1-1.3: em28178#0: EEPROM info:
[    4.270455] usb 1-1.3: em28178#0:     microcode start address = 0x0004, boot configuration = 0x01
[    4.279598] usb 1-1.3: em28178#0:     AC97 audio (5 sample rates)
[    4.279608] usb 1-1.3: em28178#0:     500mA max power
[    4.279614] usb 1-1.3: em28178#0:     Table at offset 0x27, strings=0x148c, 0x1874, 0x0a6a
[    4.279934] usb 1-1.3: em28178#0: Identified as PCTV DVB-S2 Stick (461e) (card=92)
[    4.279946] usb 1-1.3: em28178#0: dvb set to isoc mode.
[    4.280015] usbcore: registered new interface driver em28xx
[    4.299687] WARNING: You are using an experimental version of the media stack.
[    4.299687]     As the driver is backported to an older kernel, it doesn't offer
[    4.299687]     enough quality for its usage in production.
[    4.299687]     Use it with care.
[    4.299687] Latest git patches (needed if you report a bug to linux-media@vger.kernel.org):
[    4.299687]     a02ff2e02bee64e9955dbfd8811874c3f3880f58 cx231xx: Fix TBS MAC reading.
[    4.313582] usb 1-1.3: em28178#0: Binding DVB extension
[    4.331678] i2c i2c-4: Added multiplexed i2c bus 5
[    4.386096] uart-pl011 3f201000.serial: no DMA platform data
[    4.395083] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[    4.395191] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    4.409591] ts2020 5-0060: Montage Technology TS2022 successfully identified
[    4.417771] a8293 4-0008: Allegro A8293 SEC successfully attached
[    4.417801] dvbdev: DVB: registering new adapter (1-1.3: em28178#0)
[    4.417813] usb 1-1.3: em28178#0: DVB: registering adapter 0 frontend 0 (Montage Technology M88DS3103)...
[    4.421764] usb 1-1.3: em28178#0: DVB extension successfully initialized
[    4.421775] em28xx: Registered (Em28xx dvb Extension) extension
[    4.428415] usb 1-1.3: em28178#0: Registering input extension
[    4.474889] Registered IR keymap rc-pinnacle-pctv-hd
[    4.475200] input: 1-1.3: em28178#0 IR as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3: em28178#0/rc/rc0/input0
[    4.475422] rc rc0: 1-1.3: em28178#0 IR as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3: em28178#0/rc/rc0
[    4.475605] usb 1-1.3: em28178#0: Input extension successfully initalized
[    4.475611] em28xx: Registered (Em28xx Input Extension) extension
[    4.631531] lirc_rpi: auto-detected active low receiver on GPIO pin 18
[    4.631738] lirc_rpi lirc_rpi: lirc_dev: driver lirc_rpi registered at minor = 0
[    4.631741] lirc_rpi: driver registered!
[    4.841739] input: lircd-uinput as /devices/virtual/input/input1
[    4.911719] m88ds3103 4-0068: found a 'Montage Technology M88DS3103' in cold state
[    4.923906] m88ds3103 4-0068: downloading firmware from file 'dvb-demod-m88ds3103.fw'
[    4.976436] input: eventlircd as /devices/virtual/input/input2
[    5.128676] m88ds3103 4-0068: found a 'Montage Technology M88DS3103' in warm state
[    5.128685] m88ds3103 4-0068: firmware version: 3.B

Display More

If I run ir-keytable, I got the following output:

Code

# ir-keytable 
Found /sys/class/rc/rc0/ (/dev/input/event0) with:
    Driver em28xx, table rc-pinnacle-pctv-hd
    Supported protocols: rc-5 nec rc-6 
    Enabled protocols: rc-5 
    Name: 1-1.3: em28178#0 IR
    bus: 3, vendor/product: 2013:0258, version: 0x0001
    Repeat delay = 500 ms, repeat period = 125 ms

If I run ir-keytable without the DVB-stick attached to the RPi (the case when everything works fine!), the output is as follows:

Code

# ir-keytable 
Couldn't find any node at /sys/class/rc/rc*.

For my limited knowledge of lirc it seems strange that the best working config seems not to use the lirc components.

Perhaps it is useful to know the lirc-processes that are running on my Pi:

Code

# ps -ef | grep -i lirc
  281 root       0:00 /usr/sbin/eventlircd -f --evmap=/etc/eventlircd.d --socket=/run/lirc/lircd
  420 root       0:00 /usr/sbin/lircd --driver=default --device=/dev/lirc0 --output=/run/lirc/lircd-lirc0 --pidfile=/run/lirc/lircd-lirc0.pid --release=_LIRCUP /storage/.config/lircd.conf
  421 root       0:00 /usr/sbin/lircd-uinput --release=_LIRCUP /run/lirc/lircd-lirc0
  457 root       0:00 {kodi.sh} /bin/sh /usr/lib/kodi/kodi.sh --standalone -fs --lircdev /run/lirc/lircd
  463 root       3:04 /usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd
  861 root       0:00 grep -i lirc

I think that the solution for my problem is to disable the IR receiver of the DVB-stick, but I don't know how to achieve it.

May somebody help me? Thank you very much in advance!

Nico.

**HiassofT** · July 27, 2017 at 12:00 PM

Looks like the Pinnacle driver (em28xx) has an option to disable IR. Create a file .config/modprobe.d/pinnacle-disable-ir.conf with the following content:

Code

options em28xx disable_ir=1

alternatively, blacklisting the em28xx-rc module should also work

Code

blacklist em28xx-rc

so long,

Hias

nicobee · July 27, 2017 at 12:12 PM

Hello Hias!

Thank you for your really quick answer!!!

After creating the conf-file, ir-keytable says

Code

# ir-keytable 
Couldn't find any node at /sys/class/rc/rc*.

... so your solution seems to work (since the DVB-stick is currently connected to my RPi).

I will try a few hours in the evening and update this topic.

Thank you very much for your great and fast help!

Kind regards, Nico.

nicobee · July 27, 2017 at 1:27 PM

Hello HiassofT,

I tried both of your proposals (creating .config/modprobe.d/pinnacle-disable-ir.conf and echo "blacklist em28xx-rc" > /storage/.config/modprobe.d/blacklist.confand restarting the RPi, of course) but the behaviour of the remote (not all button pushes are recognized) has not changed as long as the DVB-stick is connected to the RPi. When I disconnect it - even while the RPi and Kodi are running - the recognition is immediately good!

Do you have some other ideas or recommendations for isolating the problem?

Thank you in advance, Nico.

**HiassofT** · July 27, 2017 at 8:28 PM

That looks like you are running into RPi issue #906 Issues · raspberrypi/linux · GitHub (sorry, stupid forum software thinks I'm posting spam because the title of the bug report contains the censored word "sens*t*ve" - just add 906 at the end of the URL to get to the details). Heavy USB traffic, like it's generated by DVB sticks, can interfere with proper operation of GPIIO IR receivers. Unfortunately there's no solution to that.

Since your DVB stick has an IR receiver built in the best solution would be to use that, and disable the GPIO IR receiver (either by uncommenting the dtoverlay line in config.txt or by disabling lirc in LibreELEC settings).

LibreELEC already ships with a keytable for the xbox one remote (let's hope it's the correct one) and the IR receiver of your DVB stick seems to support the remote protocol (NEC) as well.

To get that working just create a .config/rc_maps.cfg file with the following content:

Code

* * xbox_one

so long,

Hias

nicobee · July 28, 2017 at 10:23 PM

Hello HiassofT ,

first I want to thank you for your great, fast and useful help!!!

It works great as you described. Kodi is now responding immediately to my button presses. I just had to place the IR receiver a little bit more visible since the IR transmitter of the PCTV 461e seems not to be as sensitive as a TSOP 4838.

Thank you that you took the time to wrote such a detailed instruction!

And I am sorry that I have to ask you again for another topic: The only problem that is left, is that some of the buttons seems not to be correctly assigned in the standard keymap for the XBOX One Remote: UP, DOWN, LEFT, RIGHT are all working great, but OK/Select and BACK (for example) are not recognized in Kodi.

Can you tell me how to correct these codes in the keymap file? Is there a tool like lirc's mode2 to get the right codes for the various buttons on the remote? Unfortunatey these codes differ from that ones I recorded with irrecord.

Or do I have to create some assignment instructions as I did with lircmap.xml to get these buttons working in Kodi?

Another question is: although I disabled lirc (in config.txt and LibreELEC-Settings), there are some lirc processes running on my LibreELEC-Pi:

Code

# ps -ef | grep -i lirc
  266 root       0:00 /usr/sbin/eventlircd -f --evmap=/etc/eventlircd.d --socket=/run/lirc/lircd
  424 root       0:00 {kodi.sh} /bin/sh /usr/lib/kodi/kodi.sh --standalone -fs --lircdev /run/lirc/lircd
  429 root       1:43 /usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd
  765 root       0:00 grep -i lirc

Is that correct?

Thank you very much for your help again!

Kind regards!

nicobee · July 28, 2017 at 11:25 PM

In addition to my previous post:

Perhaps some of the keys are not correctly assigned because it seems like there is a wrong table used:

Code

# ir-keytable -c -w /storage/.config/rc_keymaps/xbox_one -p NEC
Read xbox_one table
Old keytable cleared
Wrote 21 keycode(s) to driver
Protocols changed to nec

# ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event0) with:
        Driver em28xx, table rc-pinnacle-pctv-hd
        Supported protocols: rc-5 nec rc-6
        Enabled protocols: nec
        Name: 1-1.5: em28178#0 IR
        bus: 3, vendor/product: 2013:0258, version: 0x0001
        Repeat delay = 500 ms, repeat period = 125 ms

Display More

It seems that table rc-pinnacle-pctv-hd is used instead of xbox_one or am I wrong?

**HiassofT** · July 29, 2017 at 2:20 PM

The eventlircd process running is fine, it's needed to feed the remote button presses into kodi.

The table you are seeing in ir-keytable output is also OK, that's the name of default table loaded by the kerrnel and won't change if you override the map via ir-keytable. You can view the currently active map and protocol with "ir-keytable -r" - that should produce about the output as the table you loaded.

Here's a thread with more details about working with ir-keytable: WD TV Live remote

Since you already have a somewhat working configuration start with that, run "ir-keytable -t" to see if the scancodes are mapped correctly to KEY_ codes, and change your keymap file accordingly (change the 0x... scancodes in that file).

If, for some reason, the correct KEY_ codes show up but don't make it into kodi, please run the following command after a fresh reboot (with kodi and everything else running) and post the output. Also your keymap file and rc_maps.cfg would be helpful.

Code

cat /proc/bus/input/devices
lsof | grep /dev/input

I've seen some odd reports that seemed like kodi picked up the input device (instead of eventlircd) and thus several buttons (like OK) weren't working. But so far I couldn't reproduce that issue reliably enough to analyze it. Maybe I'm barking up the wrong tree, but anyways, if you run into that every info will help me.

so long,

Hias

nicobee · July 29, 2017 at 4:36 PM

Hi HiassofT ,

executing the commands that are described in the "WD TV Live"-Thread show, that the buttons "OK" and "BACK"/"EXIT" are successfully received:

Code

# ir-keytable -c -w /storage/.config/rc_keymaps/xbox_one -t
Read xbox_one table
Old keytable cleared
Wrote 21 keycode(s) to driver
Protocols changed to nec
Testing events. Please, press CTRL-C to abort.
1501341812.400852: event type EV_MSC(0x04): scancode = 0x80d822
1501341812.400852: event type EV_KEY(0x01) key_down: KEY_OK(0x0001)
1501341812.400852: event type EV_SYN(0x00).
1501341812.607541: event type EV_MSC(0x04): scancode = 0x80d822
1501341812.607541: event type EV_SYN(0x00).
1501341812.874051: event type EV_KEY(0x01) key_up: KEY_OK(0x0001)
1501341812.874051: event type EV_SYN(0x00).
1501341813.124210: event type EV_MSC(0x04): scancode = 0x80d823
1501341813.124210: event type EV_KEY(0x01) key_down: KEY_EXIT(0x0001)
1501341813.124210: event type EV_SYN(0x00).
1501341813.227542: event type EV_MSC(0x04): scancode = 0x80d823
1501341813.227542: event type EV_SYN(0x00).
1501341813.330849: event type EV_MSC(0x04): scancode = 0x80d823
1501341813.330849: event type EV_SYN(0x00).
1501341813.594049: event type EV_KEY(0x01) key_up: KEY_EXIT(0x0001)
1501341813.594049: event type EV_SYN(0x00).

Display More

The codes are equal to the ones that are configured in the rc_keymaps-file, so my assumption that these are not correct was wrong.

Here is the output of the both commands you mentioned:

Code

# cat /proc/bus/input/devices
I: Bus=0003 Vendor=2013 Product=0258 Version=0001
N: Name="1-1.5: em28178#0 IR"
P: Phys=usb-3f980000.usb-1.5/input0
S: Sysfs=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5: em28178#0/rc/rc0/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=100013
B: KEY=108c0000 102041 0 0 0 4 10000 4110 1 e1680 0 0 0
B: MSC=10

# lsof | grep /dev/input
440     /usr/lib/kodi/kodi.bin  /dev/input/event0

Display More

My rc_maps.cfg:

Code

# cat /storage/.config/rc_maps.cfg
* * xbox_one

The /storage/.kodi/userdata/keymaps/folder is empty. Could that be the reason for my problem?

Thank you again for your help!!!

Kind regards, Nico

**HiassofT** · July 30, 2017 at 9:36 AM

Thanks for the info! Unfortunately I still could not reproduce the issue here (tried with gpio-ir and a hauppauge dvb-t stick).

Could you post the contents of your xbox_one keymap and the output of this command:

Code

udevadm info -a -n /dev/input/event0

Do you have an local udev rules in .config/udev.rules.d/?

As a very wild guess, could you try to disable joystick support in Kodi (Add-ons->My Add-ons->Peripheral libraries->Joystick support, then disable that addon), and then reboot?

so long,

Hias

nicobee · July 30, 2017 at 10:22 AM

Hi HiassofT,

my xbox_one keymap is:

Code

# cat /storage/.config/rc_keymaps/xbox_one
# table xbox_one, type: NEC
0x80d864 KEY_MEDIA
0x80d820 KEY_LEFT
0x80d821 KEY_RIGHT
0x80d81e KEY_UP
0x80d81f KEY_DOWN
0x80d822 KEY_OK
0x80d823 KEY_EXIT
0x80d80e KEY_MUTE
0x80d810 KEY_VOLUMEUP
0x80d811 KEY_VOLUMEDOWN
0x80d812 KEY_CHANNELUP
0x80d813 KEY_CHANNELDOWN
0x80d814 KEY_FASTFORWARD
0x80d815 KEY_REWIND
0x80d870 KEY_PLAYPAUSE
0x80d819 KEY_STOP
0x80d81a KEY_NEXT
0x80d81b KEY_PREVIOUS
0x80d826 KEY_INFO
0x80d86f KEY_EPG
0x80d86e KEY_ZOOM

Display More

udevadm:

Code

# udevadm info -a -n /dev/input/event0

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/rc/rc0/input0/event0':
    KERNEL=="event0"
    SUBSYSTEM=="input"
    DRIVER==""

  looking at parent device '/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/rc/rc0/input0':
    KERNELS=="input0"
    SUBSYSTEMS=="input"
    DRIVERS==""
    ATTRS{name}=="1-1.5: em28178#0 IR"
    ATTRS{phys}=="usb-3f980000.usb-1.5/input0"
    ATTRS{properties}=="0"
    ATTRS{uniq}==""

  looking at parent device '/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/rc/rc0':
    KERNELS=="rc0"
    SUBSYSTEMS=="rc"
    DRIVERS==""
    ATTRS{protocols}=="rc-5 [nec] rc-6"

  looking at parent device '/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5':
    KERNELS=="1-1.5"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{authorized}=="1"
    ATTRS{avoid_reset_quirk}=="0"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bDeviceClass}=="00"
    ATTRS{bDeviceProtocol}=="00"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{bMaxPower}=="500mA"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{bcdDevice}=="0100"
    ATTRS{bmAttributes}=="80"
    ATTRS{busnum}=="1"
    ATTRS{configuration}==""
    ATTRS{devnum}=="4"
    ATTRS{devpath}=="1.5"
    ATTRS{idProduct}=="0258"
    ATTRS{idVendor}=="2013"
    ATTRS{ltm_capable}=="no"
    ATTRS{manufacturer}=="PCTV"
    ATTRS{maxchild}=="0"
    ATTRS{product}=="PCTV 461"
    ATTRS{quirks}=="0x0"
    ATTRS{removable}=="removable"
    ATTRS{serial}=="0011530448"
    ATTRS{speed}=="480"
    ATTRS{urbnum}=="11117442"
    ATTRS{version}==" 2.00"

  looking at parent device '/devices/platform/soc/3f980000.usb/usb1/1-1':
    KERNELS=="1-1"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{authorized}=="1"
    ATTRS{avoid_reset_quirk}=="0"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bDeviceClass}=="09"
    ATTRS{bDeviceProtocol}=="02"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{bMaxPower}=="2mA"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{bcdDevice}=="0200"
    ATTRS{bmAttributes}=="e0"
    ATTRS{busnum}=="1"
    ATTRS{configuration}==""
    ATTRS{devnum}=="2"
    ATTRS{devpath}=="1"
    ATTRS{idProduct}=="9514"
    ATTRS{idVendor}=="0424"
    ATTRS{ltm_capable}=="no"
    ATTRS{maxchild}=="5"
    ATTRS{quirks}=="0x0"
    ATTRS{removable}=="unknown"
    ATTRS{speed}=="480"
    ATTRS{urbnum}=="38"
    ATTRS{version}==" 2.00"

  looking at parent device '/devices/platform/soc/3f980000.usb/usb1':
    KERNELS=="usb1"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{authorized}=="1"
    ATTRS{authorized_default}=="1"
    ATTRS{avoid_reset_quirk}=="0"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bDeviceClass}=="09"
    ATTRS{bDeviceProtocol}=="01"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{bMaxPower}=="0mA"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{bcdDevice}=="0409"
    ATTRS{bmAttributes}=="e0"
    ATTRS{busnum}=="1"
    ATTRS{configuration}==""
    ATTRS{devnum}=="1"
    ATTRS{devpath}=="0"
    ATTRS{idProduct}=="0002"
    ATTRS{idVendor}=="1d6b"
    ATTRS{interface_authorized_default}=="1"
    ATTRS{ltm_capable}=="no"
    ATTRS{manufacturer}=="Linux 4.9.29 dwc_otg_hcd"
    ATTRS{maxchild}=="1"
    ATTRS{product}=="DWC OTG Controller"
    ATTRS{quirks}=="0x0"
    ATTRS{removable}=="unknown"
    ATTRS{serial}=="3f980000.usb"
    ATTRS{speed}=="480"
    ATTRS{urbnum}=="26"
    ATTRS{version}==" 2.00"

  looking at parent device '/devices/platform/soc/3f980000.usb':
    KERNELS=="3f980000.usb"
    SUBSYSTEMS=="platform"
    DRIVERS=="dwc_otg"
    ATTRS{busconnected}=="Bus Connected = 0x1"
    ATTRS{buspower}=="Bus Power = 0x1"
    ATTRS{bussuspend}=="Bus Suspend = 0x0"
    ATTRS{devspeed}=="Device Speed = 0x0"
    ATTRS{driver_override}=="(null)"
    ATTRS{enumspeed}=="Device Enumeration Speed = 0x1"
    ATTRS{fr_interval}=="Frame Interval = 0x1d4b"
    ATTRS{ggpio}=="GGPIO = 0x00000000"
    ATTRS{gnptxfsiz}=="GNPTXFSIZ = 0x01000306"
    ATTRS{gotgctl}=="GOTGCTL = 0x001c0001"
    ATTRS{gpvndctl}=="GPVNDCTL = 0x00000000"
    ATTRS{grxfsiz}=="GRXFSIZ = 0x00000306"
    ATTRS{gsnpsid}=="GSNPSID = 0x4f54280a"
    ATTRS{guid}=="GUID = 0x2708a000"
    ATTRS{gusbcfg}=="GUSBCFG = 0x20001700"
    ATTRS{hcd_frrem}=="HCD Dump Frame Remaining"
    ATTRS{hcddump}=="HCD Dump"
    ATTRS{hnp}=="HstNegScs = 0x0"
    ATTRS{hnpcapable}=="HNPCapable = 0x1"
    ATTRS{hprt0}=="HPRT0 = 0x00001005"
    ATTRS{hptxfsiz}=="HPTXFSIZ = 0x02000406"
    ATTRS{hsic_connect}=="HSIC Connect = 0x1"
    ATTRS{inv_sel_hsic}=="Invert Select HSIC = 0x0"
    ATTRS{mode}=="Mode = 0x1"
    ATTRS{mode_ch_tim_en}=="Mode Change Ready Timer Enable = 0x0"
    ATTRS{rd_reg_test}=="Time to read GNPTXFSIZ reg 10000000 times: 913 msecs (274 jiffies)"
    ATTRS{regdump}=="Register Dump"
    ATTRS{regoffset}=="0xffffffff"
    ATTRS{regvalue}=="invalid offset"
    ATTRS{rem_wakeup_pwrdn}==""
    ATTRS{remote_wakeup}=="Remote Wakeup Sig = 0 Enabled = 0 LPM Remote Wakeup = 0"
    ATTRS{spramdump}=="SPRAM Dump"
    ATTRS{srp}=="SesReqScs = 0x1"
    ATTRS{srpcapable}=="SRPCapable = 0x1"
    ATTRS{wr_reg_test}=="Time to write GNPTXFSIZ reg 10000000 times: 366 msecs (110 jiffies)"

  looking at parent device '/devices/platform/soc':
    KERNELS=="soc"
    SUBSYSTEMS=="platform"
    DRIVERS==""
    ATTRS{driver_override}=="(null)"

  looking at parent device '/devices/platform':
    KERNELS=="platform"
    SUBSYSTEMS==""
    DRIVERS==""

Display More

udev-rules:

Code

# ls -la .config/udev.rules.d/
total 4
drwxr-xr-x    2 root     root          1024 May 19 16:01 .
drwxr-xr-x   14 root     root          1024 Jul 28 11:45 ..
-rw-r--r--    1 root     root          1170 May 19 16:01 README

Regarding the test with disabled Joystick-support:

I've already disabled this addon since I tried to reduce the possible interfering factors. So I've already tested it.

If I should try with ENABLED Joystick-support again, please let me know.

Thank you, that you stay furthermore on that topic!!!

Best regards, Nico.

**HiassofT** · July 30, 2017 at 12:02 PM

Damn, everything looks OK so far. But I'm not giving up yet

Could you enabling debug logging in kodi, reboot, then press some buttons on the remote, and then get us the kodi log?

Code

paste .kodi/temp/kodi.log

Then disable both kodi and eventlircd (via systemctl stop).

Next start eventlircd and check via lsof (as above) if it had picked up the /dev/input/event0 device.

If that worked, start kodi. Check again via lsof who is using the event0 device. Then press some buttons, tell us if that worked and grab another kodi log.

so long,

Hias

nicobee · July 31, 2017 at 7:00 AM

Hi HiassofT,

thank you for your endurance

Here are the outputs of the steps that I made in the order you specified:

Code

##############################################
#                 LibreELEC                  #
#            http://libreelec.tv             #
##############################################

LibreELEC (official) Version: 8.0.2

# paste .kodi/temp/kodi.log
http://sprunge.us/JXbL

# systemctl stop kodi

# systemctl stop eventlircd

# ps -ef | grep kodi
  351 root       0:13 vdr.bin -g /tmp --no-kbd --log=1 --port=0 --dirnames=,,1 --config=/storage/.kodi/userdata/addon_data/service.multimedia.vdr-addon/config --resdir=/storage/.kodi/addons/service.multimedia.vdr-addon/res --cachedir=/storage/.kodi/userdata/addon_data/service.multimedia.vdr-addon/cache --lib=/storage/.kodi/addons/service.multimedia.vdr-addon/plugin --video=/storage/videos -P dvbapi -P wirbelscan -P wirbelscancontrol -P restfulapi --ip 127.0.0.1 --port 8002 --epgimages="/storage/.kodi/userdata/addon_data/service.multimedia.vdr-addon/epgimages" --channellogos="/storage/.kodi/userdata/addon_data/service.multimedia.vdr-addon/channellogos" -P vnsiserver
  759 root       0:00 grep kodi

# ps -ef | grep eventlircd
  761 root       0:00 grep eventlircd

# systemctl start eventlircd

# ps -ef | grep eventlircd
  768 root       0:00 /usr/sbin/eventlircd -f --evmap=/etc/eventlircd.d --socket=/run/lirc/lircd
  770 root       0:00 grep eventlircd

# lsof | grep /dev/input

# systemctl start kodi

# lsof | grep /dev/input
789     /usr/lib/kodi/kodi.bin  /dev/input/event0

# paste .kodi/temp/kodi.log
http://sprunge.us/EYWi

Display More

I think the relevant part is:

Code

23:06:36.839 T:1961955328   DEBUG: CLinuxInputDevice::KeyEvent: TranslateKey returned XBMCK_UNKNOWN from code(352)
23:06:38.607 T:1961955328   DEBUG: Previous line repeats 5 times.
23:06:38.607 T:1961955328   DEBUG: CLinuxInputDevice::KeyEvent: TranslateKey returned XBMCK_UNKNOWN from code(174)

... isn't it!?

Regarding your question "[...] tell us if that worked [...]":

the behaviour after the (re-)start of kodi via systemctl was not better than before (if I did understand your question right).

But if I try to verify the same behaviour within the logfile, it is strange to see, that the second attempt seemed to be successful:

First attempt:

Code

23:06:34.969 T:1961955328   DEBUG: OnKey: up (0xf080) pressed, action is Up
23:06:35.339 T:1961955328   DEBUG: Keyboard: scancode: 0x67, sym: 0x0111, unicode: 0x0000, modifier: 0x0
23:06:35.589 T:1961955328   DEBUG: Keyboard: scancode: 0x6c, sym: 0x0112, unicode: 0x0000, modifier: 0x0
23:06:35.589 T:1961955328   DEBUG: OnKey: down (0xf081) pressed, action is Down
23:06:36.072 T:1961955328   DEBUG: Keyboard: scancode: 0x6c, sym: 0x0112, unicode: 0x0000, modifier: 0x0
23:06:36.228 T:1961955328   DEBUG: Keyboard: scancode: 0x67, sym: 0x0111, unicode: 0x0000, modifier: 0x0
23:06:36.228 T:1961955328   DEBUG: OnKey: up (0xf080) pressed, action is Up
23:06:36.672 T:1961955328   DEBUG: Keyboard: scancode: 0x67, sym: 0x0111, unicode: 0x0000, modifier: 0x0
23:06:36.839 T:1961955328   DEBUG: CLinuxInputDevice::KeyEvent: TranslateKey returned XBMCK_UNKNOWN from code(352)
23:06:38.607 T:1961955328   DEBUG: Previous line repeats 5 times.
23:06:38.607 T:1961955328   DEBUG: CLinuxInputDevice::KeyEvent: TranslateKey returned XBMCK_UNKNOWN from code(174)

Display More

Second attempt:

Code

23:23:07.976 T:1961910272   DEBUG: OnKey: 166 (0xa6, obc89) pressed, action is Up
23:23:10.152 T:1961910272   DEBUG: OnKey: 168 (0xa8, obc87) pressed, action is Right
23:23:10.953 T:1961910272   DEBUG: OnKey: 11 (0x0b, obc244) pressed, action is Select
23:23:14.674 T:1961910272   DEBUG: OnKey: 167 (0xa7, obc88) pressed, action is Down
23:23:15.180 T:1961910272   DEBUG: OnKey: 11 (0x0b, obc244) pressed, action is Select
23:23:17.566 T:1961910272   DEBUG: OnKey: 166 (0xa6, obc89) pressed, action is Up
23:23:18.641 T:1961910272   DEBUG: OnKey: 11 (0x0b, obc244) pressed, action is Select
23:23:19.572 T:1961910272   DEBUG: OnKey: 168 (0xa8, obc87) pressed, action is Right
23:23:20.319 T:1961910272   DEBUG: OnKey: 11 (0x0b, obc244) pressed, action is Select

**HiassofT** · August 3, 2017 at 9:09 AM

Thanks a lot for testing and for the logs!

The core issue is that eventlircd isn't picking up the input device at all and therefore the button presses end up as keyboard input in kodi (and kodi doesn't "understand" many of the keycodes, thus the "TranslateKey returned XBMCK_UNKNOWN" messages).

I have no idea why kodi suddenly seems to recognize the input as obc events in the second log. At the beginning of the log we have the "Keyboard: ..." and "OnKey: ..." messages as expected. Then the screensaver kicked in, after that there are no longer any "Keyboard: ..." events, only "OnKey: " with obcXXX codes. Odd.

Coming back to the eventlircd issue, could you post the output of the following command?

Code

udevadm test -a add /sys/class/rc/rc0/input0/event0

Then power down the RPi, unplug the DVB stick and power up the RPi without it. Then, run the following command:

Code

udevadm control -l debug

Now plug in the DVB stick and then, after some 5 or 10 seconds, grab dmesg and journal output

Code

dmesg | paste
journalctl -a | paste

With this info I should hopefully get some clues where to start looking further - if it's an udev issue or an eventlircd issue.

BTW: as a temporary workaround you can change the keytable to use keycodes that kodi understands. eg use KEY_ENTER instead of KEY_OK, KEY_BACK instead of KEY_EXIT etc.

so long,

Hias

nicobee · August 3, 2017 at 5:15 PM

Hi HiassofT,

here is the output of the first udevadm command:

Code

# udevadm test -a add /sys/class/rc/rc0/input0/event0
calling: test
version 232
This program is for debugging only, it does not run any program
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.

=== trie on-disk ===
tool version:          232
file size:         4864507 bytes
header size             80 bytes
strings            1353939 bytes
nodes              3510488 bytes
Load module index
Found container virtualization none
Created link configuration context.
timestamp of '/etc/udev/rules.d' changed
timestamp of '/usr/lib/udev/rules.d' changed
Reading rules file: /usr/lib/udev/rules.d/30-disable-wakeup.rules
Reading rules file: /usr/lib/udev/rules.d/40-modeswitch.rules
Reading rules file: /usr/lib/udev/rules.d/50-udev-default.rules
Reading rules file: /usr/lib/udev/rules.d/60-block.rules
Reading rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules
Reading rules file: /usr/lib/udev/rules.d/60-drm.rules
Reading rules file: /usr/lib/udev/rules.d/60-evdev.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-alsa.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-input.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage-tape.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules
Reading rules file: /usr/lib/udev/rules.d/60-serial.rules
Reading rules file: /usr/lib/udev/rules.d/61-cdrom.rules
Reading rules file: /usr/lib/udev/rules.d/64-btrfs.rules
Reading rules file: /usr/lib/udev/rules.d/70-infrared.rules
Reading rules file: /usr/lib/udev/rules.d/70-input-repeat.rules
Reading rules file: /usr/lib/udev/rules.d/70-mouse.rules
Reading rules file: /usr/lib/udev/rules.d/70-power-switch.rules
Reading rules file: /usr/lib/udev/rules.d/70-touchpad.rules
Reading rules file: /usr/lib/udev/rules.d/70-uaccess.rules
Reading rules file: /usr/lib/udev/rules.d/71-seat.rules
Reading rules file: /usr/lib/udev/rules.d/73-seat-late.rules
Invalid rule /usr/lib/udev/rules.d/73-seat-late.rules:15: RUN{builtin}: 'uaccess' unknown
Reading rules file: /usr/lib/udev/rules.d/75-net-description.rules
Reading rules file: /usr/lib/udev/rules.d/75-probe_mtd.rules
Reading rules file: /usr/lib/udev/rules.d/78-sound-card.rules
Reading rules file: /usr/lib/udev/rules.d/80-clock.rules
Reading rules file: /usr/lib/udev/rules.d/80-drivers.rules
Reading rules file: /usr/lib/udev/rules.d/90-alsa-restore.rules
Reading rules file: /usr/lib/udev/rules.d/90-pulseaudio.rules
Reading rules file: /usr/lib/udev/rules.d/90-rpi-add-serial.rules
Reading rules file: /usr/lib/udev/rules.d/95-udevil-mount.rules
Reading rules file: /usr/lib/udev/rules.d/97-hid2hci.rules
Reading rules file: /usr/lib/udev/rules.d/98-eventlircd.rules
Reading rules file: /usr/lib/udev/rules.d/98-lircd.rules
Reading rules file: /usr/lib/udev/rules.d/99-systemd.rules
Reading rules file: /usr/lib/udev/rules.d/99-wakeup-eth.rules
rules contain 24576 bytes tokens (2048 * 12 bytes), 13362 bytes strings
2153 strings (27556 bytes), 1443 de-duplicated (14905 bytes), 711 trie nodes used
IMPORT builtin 'input_id' /usr/lib/udev/rules.d/50-udev-default.rules:14
capabilities/ev raw kernel attribute: 100013
capabilities/abs raw kernel attribute: 0
capabilities/rel raw kernel attribute: 0
capabilities/key raw kernel attribute: 108c0000 102041 0 0 0 4 10000 4110 1 e1680 0 0 0
properties raw kernel attribute: 0
test_key: checking bit block 0 for any keys; found=0
test_key: checking bit block 32 for any keys; found=0
test_key: checking bit block 64 for any keys; found=0
test_key: checking bit block 96 for any keys; found=1
test_key: checking bit block 128 for any keys; found=1
test_key: checking bit block 160 for any keys; found=1
test_key: checking bit block 192 for any keys; found=1
test_key: checking bit block 224 for any keys; found=1
GROUP 199 /usr/lib/udev/rules.d/50-udev-default.rules:30
IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/60-evdev.rules:8
IMPORT builtin 'hwdb' returned non-zero
IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/60-evdev.rules:17
IMPORT builtin 'hwdb' returned non-zero
IMPORT builtin 'usb_id' /usr/lib/udev/rules.d/60-persistent-input.rules:9
unable to access usb_interface device of '/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/rc/rc0/input0/event0'
IMPORT builtin 'usb_id' returned non-zero
IMPORT builtin 'path_id' /usr/lib/udev/rules.d/60-persistent-input.rules:33
LINK 'input/by-path/platform-3f980000.usb-usb-0:1.5-event' /usr/lib/udev/rules.d/60-persistent-input.rules:38
IMPORT builtin skip 'usb_id' /usr/lib/udev/rules.d/98-eventlircd.rules:89
RUN 'wakeup_enable' /usr/lib/udev/rules.d/98-eventlircd.rules:193
update old name, '/dev/input/by-path/platform-3f980000.usb-usb-0:1-event' no longer belonging to '/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/rc/rc0/input0/event0'
no reference left, remove '/dev/input/by-path/platform-3f980000.usb-usb-0:1-event'
handling device node '/dev/input/event0', devnum=c13:64, mode=0660, uid=0, gid=199
preserve permissions /dev/input/event0, 020660, uid=0, gid=199
preserve already existing symlink '/dev/char/13:64' to '../input/event0'
creating link '/dev/input/by-path/platform-3f980000.usb-usb-0:1.5-event' to '/dev/input/event0'
creating symlink '/dev/input/by-path/platform-3f980000.usb-usb-0:1.5-event' to '../event0'
created db file '/run/udev/data/c13:64' for '/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/rc/rc0/input0/event0'
ACTION=add
DEVLINKS=/dev/input/by-path/platform-3f980000.usb-usb-0:1.5-event
DEVNAME=/dev/input/event0
DEVPATH=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/rc/rc0/input0/event0
ID_INPUT=1
ID_INPUT_KEY=1
ID_PATH=platform-3f980000.usb-usb-0:1.5
ID_PATH_TAG=platform-3f980000_usb-usb-0_1_5
MAJOR=13
MINOR=64
SUBSYSTEM=input
USEC_INITIALIZED=4458237
eventlircd_enable=true
eventlircd_evmap=default.evmap
run: 'wakeup_enable'
Unload module index
Unloaded link configuration context.

Display More

You can find the dmesg output at: http://sprunge.us/NSEA

and the journalctl output at: http://sprunge.us/ibKD

I will try the workaround you mentioned - thank you for the hint!

Best regards, Nico.

nicobee · August 3, 2017 at 8:50 PM

Hi HiassofT,

your workaround performs good. But perhaps it is an important information for you, that the both keys KEY_ENTER and KEY_BACK are responding a bit slower to my button presses than the KEY_UP/DOWN/LEFT/RIGHT buttons for instance.

One question for a better understanding of Kodi:

how do one get the list of the keycodes that will be unterstood by kodi? Is it the list at http://kodi.wiki/view/Action_IDs with a leading "KEY_" before the ActionID!? Or do I have to take a look into the kodi sourcecode for it?

Kind regards, Nico.

**HiassofT** · August 3, 2017 at 10:32 PM

Thanks a lot, again, for testing!

From the system/udev side everything looks fine, these were the 2 lines I was looking for:

Code

eventlircd_enable=true
eventlircd_evmap=default.evmap

So the problem most certainly resides in libudev or eventlircd. Unfortunatley eventlircd is very quiet and nothing was logged to the journal that could provide additional hints.

Before I go down the rabbit hole of digging into eventlircd/libudev - which could take me a while - there's one last thing I'd like you to do: Could you do a quick test with the latest milhouse build, using your existing rc_maps.cfg config, and see if eventlircd picks up the input device there (post the output of "lsof | grep /dev/input")? That build contains a newer systemd version, so if it's really a libudev/systemd issue there's a slight chance that could already be fixed.

Builds are available from here: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0) (just pick the latest, currently #0802). But better use a separate SD card for testing - going back to 8.0.2 will result in a mess because several databases, addons etc will have been updated to newer versions.

As for KEY_ENTER/BACK being slower: that's normal and caused by the long-press support in Kodi, configured via the default keyboard.xml file:

Code

<return>Select</return>
<return mod="longpress">ContextMenu</return>
<enter>Select</enter>
<enter mod="longpress">ContextMenu</enter>
...

That feature allows you to map different functions to a key/button, depending on if you press it shortly or longer. That feature is only available on keyboards, not on (remote-) events that come in via the lirc socket.

For a full list of keycodes supported in Kodi best look into the source code (the keyMap definition at around line 120): xbmc/LinuxInputDevices.cpp at Krypton · xbmc/xbmc · GitHub

so long,

Hias

nicobee · August 3, 2017 at 10:51 PM

Hello HiassofT,

thank you (again) for your detailed information and for your support!!!

Of course I will test with the dev build. But this will take while since I have to order a new sd card. But I'll try to hurry and give you feedback asap!

Best regards! Nico