Posts by Dr. Seltsam

  • Official LE13 Test Images for Amlogic (Kodi-22)

    ist it important that /sys/class/rc/rc0/device/power/wakeup does not exist?

    The Google KI suggested to modify the dtb. I recompiled meson-g12b-odroid-n2-plus.dtb (yes, I have a N2+) with this change (adding wakup-source)

    but it doesn't help. The Google KI suggested a lot of stupid things and may be not qualified...

  • Official LE13 Test Images for Amlogic (Kodi-22)

    Unfortunately I don't have the original Hardkernel remote. But I have a USB IR transmitter and can generate codes with ir-ctl (example: ir-ctl -S nec:0xdc).

    According to odroid.toml the scancode for "KEY_POWER" is 0xb2dc. Odroid wiki says that it is 0xdc.

    This thread is confusing. It mentions several other codes. I tried all of them, sending the Code to N2 and logged the output also on another machine running CoreELEC, using their ir-keytable -u feature:

    None of them makes the LibreELEC N2 wakeup... but 0xb2dc works out of the box to make Kodi show the power off dialogue. But it can't wake the machine up. Tested with LibreELEC-Amlogic.aarch64-13.0-nightly-20261101-e54661c-odroid-n2

  • Official LE13 Test Images for Amlogic (Kodi-22)

    I have an Odroid N2 with internal IR receiver. The Google KI says "configuring this for LibreELEC requires adjusting how U-Boot reads your remote parameters". Then it suggests using a config.ini or boot.ini to supply the custom hex values directly to U-Boot at startup. This sounds like the method CoreELEC uses with amlogic vendor kernel, so the KI may be confused. Is IR wakeup yet possible and if so, what does it require? There is no *.ini-file on the flash partition.

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

    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!

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

    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.

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

    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.

  • [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.

  • nano editor can üöä but not ß (locale = de_DE.UTF-8)

    Kann es daran liegen:

    LibreELEC:~ # nano -V
    GNU nano, version 7.2
    (C) 2023 the Free Software Foundation and various contributors
    Compiled options: --disable-libmagic --disable-wrapping --disable-nls --disable-utf8

    Allerdings sieht das bei CoreELEC auch so aus, und da gibt es das Problem nicht.

    Im vi-Editor werden gar keine Umlaute akzeptiert - der schreibt nur Punkte. Tastaturlayout scheint zu stimmen - y und z entsprechen der deutschen Tastatur

  • nano editor can üöä but not ß (locale = de_DE.UTF-8)

    I am using Xubuntu with xfce4-terminal, configured for utf-8. I use an ssh connection to Libreelec. The locale addon is installed and configured:

    The cat command shows text with right german 'Umlaute', including ß. I can also type ß in console and it shows right.

    But when I open nano, I can only write äöü. When I type ß it shows =. Same with existing ß in text.

    What am I missing? Version is LibreELEC (official): 12.0.2 (RPi2.arm)

  • cec-ctl for LE 9.2.8?

    I now find a way to switch a Samsung D series to HDMI3 and back to TV tuner with cec-client:

    Code
    #switch to HDMI3
echo "tx 4F:82:30:00" | cec-client RPI -s -d 1
    Code
    #switch back to TV
echo "tx 40:9d:00:00" | cec-client RPI -s -d 1

  • cec-ctl for LE 9.2.8?

    Because of the WLAN invalid-key-problem I downgraded to LE 9.2.8

    Unfortunately there is no cec-ctl included. Is it possible to install this from any add-on or repository? Or is it impossible to work with the 4.9 kernel?

    I have a script which works fine with cec-ctl on LE 11. LE 9 includes cec-client, but I wasn't able to get the same result with it.

    I copied the cec-ctl from version 11 into the 9, but it doesn't run because of the wrong glibc version.

  • Network (WLAN/Wifi) only sporadic available

    When I was at home visiting my parents I checked the wifi connection via OSD menu. I tried to connect to the router and got "invalid key" answer. Tried it again several times and suddenly it works. A few hours later the Raspi was again unreachable...

    As I am on LE 11.0.1 I believe I have the infamous invalid-key-bug: https://github.com/LibreELEC/LibreELEC.tv/issues/7166

    Is there anything I can do to fix this?

    In /storage/.cache/connman/wifi_08beac0ef069_4d442d3231323739_managed_psk there is a valid settings file for the router.