[LE13 Amlogic] problem with ir-keytable: -c -w works, but -a reports an 'invalid parameter"

    my file /storage/.config/rc_keymaps/ru880_vcr-code131.toml:

    ir-keytable -c -w /storage/.config/rc_keymaps/ru880_vcr-code131.toml works:

    Code
    Read ru880_vcr-code131 table
Old keytable cleared
Wrote 30 keycode(s) to driver
Protocols changed to nec

    This is the ouput of ir-keytable:

    I am not sure if Default keymap: rc-odroid is right or if there should be reported the just configured custom toml. Anyway, the remote works (tested with evtest using meson-ir on /dev/input/event3)

    Code
    Event: time 1793725093.577050, type 1 (EV_KEY), code 28 (KEY_ENTER), value 1
Event: time 1793725093.577050, -------------- SYN_REPORT ------------
Event: time 1793725093.858062, type 1 (EV_KEY), code 28 (KEY_ENTER), value 2
Event: time 1793725093.858062, -------------- SYN_REPORT ------------
Event: time 1793725093.866751, type 1 (EV_KEY), code 28 (KEY_ENTER), value 0

    But after starting eventlircd and kodi nothing happens in kodi when I press any key. There is nothing in the kodi debug log.

    When I try to make the keymap permanently with ir-keytable -a /storage/.config/rc_keymaps/ru880_vcr-code131.toml -s rc0 I get an error:

    Code
    Invalid parameter on line 1 of /storage/.config/rc_keymaps/ru880_vcr-code131.toml
ir-keytable: Failed to read config file /storage/.config/rc_keymaps/ru880_vcr-code131.toml

    I don't see anything wrong in my toml and if so, I assume that this would have been reported by ir-keytable earlier when using -c -w  instead of -a.

    According to this: https://wiki.libreelec.tv/configuration/…iguration-basic the "-a" switch is to load the rc_maps.cfg not to load the toml file. So you should make a copy of /etc/rc_maps.cfg or create a empty one, add a line with a reference to your toml file and load afterwards the /storage/.config/rc_maps.cfg via ir-keytable -a /storage/.config/rc_maps.cfg.

    The line in the file `/storage/.config/rc_maps.cfg` might look something like this configuration

    Code
    meson-ir * ru880_vcr-code131.toml

    or

    Code
    em28xx * ru880_vcr-code131.toml

    depending on which IR receiver you wish to associate the configuration with.

    Edited 2 times, last by HarryH: Configuration examples added (November 3, 2026 at 6:09 PM).

    thank you, I looked for hours on the screen but did not see it :cry:

    Do you have an idea why Kodi does not react to the remote? I have already vdr (from https://github.com/Zabrimus/VDRSternELEC) running (while kodi is stopped). The vdr OSD reacts now fine to remote key presses. Kodi should be able to react to /dev/input devices with or without eventlircd, but no success. Even the Kodi debug log shows no remote key presses. Keyboard works fine.

    Do you have prepared the required rc_maps.cfg file now? I'm not familiar with the Amlogic devices and their culprits. Is it a recent LE13 version that do you have installed? Do you have already seen this: Important change in LE13 remote handling ?

    Keyboard events were different handled than remote keys. Do you have some customization in place from the past?

    yes, the rc_maps.cfg is fine now and the keytable is set permanently. I use the lastet nightly amlogic LE13 for Odroid N2.

    I saw the thread you mentioned but found no explaination. At a second look I think #5 could be important.

    Quote

    You had to map linux input codes (like KEY_MENU) to those kodi remote button codes via a Lircmap.xml and then map the kodi remote buttons to kodi actions in remote.xml.

    I will have a closer look into this... sounds very difficult. I already tested CoreELEC CE22-no. It is also bleeding edge, but there is no problem with linux input event codes.

    Unfortunately 'latest' contain never a kind of useful information. Could you please have a look for a date and the build hash like 'LibreELEC-Amlogic.aarch64-13.0-nightly-20261103-d3cd739-odroid-n2.img.gz'

    • 20261103
    • d3cd739

    Only in this way can the code state be checked and it be ensured that we are talking about the same starting point.

    I'm a little bit surprised if you would have the eventlird service available with a recent LE13. Do you have also verified with ir-keytable -t that the EV_MSC with the scancodes and EV_KEY are logged?

    Does it make a difference if you stop eventlircd and start KODI without that service?

    Edited 6 times, last by HarryH (November 3, 2026 at 10:13 PM).

    A newly installed LibreELEC (community): nightly-20261101-e54661c (Amlogic.aarch64) image does not have the problem. Kodi runs like a charm with my remote and you are right, eventlircd is not available.

    What I was testing before was this same image, but with an installed tar update file (https://github.com/Zabrimus/VDRSt….0-VDR-1031.tar) . This adds vdr to the SYSTEM filesystem. Zabrimus builds LE from source and according to https://github.com/Zabrimus/VDRSt…5b2c198ce1e186d he used a version which was a few days older. This results in a downgrade.

    So the problem was either in LE and is already solved, or it was introduced by patches and addons from Zabrimus. Eventlircd is something we need for vdr.

    Zabrimus is updating every week, so I will try again. But it seems pretty clear that this is no issue for LE support. Sorry!