Posts by HiassofT

  • apple ir remote (atvclient) not working after upgrade from 9.0.2. to 9.1.002

    atvclient has been dropped in LibreELEC master and 9.2 because it was constantly causing troubles.

    The remote should be supported by the linux kernel, but probably the buttons need to be remapped - the hid-appleir kernel driver sends volume-up/down and back/forward when you press the navigation keys.

    Please post dmesg, lsusb and journal from LE 9.1.002 and a kodi debug log where you pressed the various buttons on the remote - this should allow us to create a proper default config for the remote.

    so long,

    Hias

  • MCE keyboard (mce_kbd) not working for 'text' keys after upgrading to versions 9.1.00x

    This is due to an upstream kernel change, previously the mce keyboard events were sent from a separate linux input device, with recent kernels they are sent from the standard rc core input device - and the events are routed through eventlircd (so normal keyboard handling is semi-broken in kodi).

    You can disable routing through eventlircd by creating an empty 98-eventlircd.rules udev rules file:

    Code
    : > /storage/.config/udev.rules.d/98-eventlircd.rules

    This will re-establish keyboard functionality with mce_kbd but also means IR remote events (eg from an MCE remote) will show up as keyboard events in kodi and several buttons like KEY_OK won't work anymore.

    This can be solved quite easily, as you are already use a custom rc keymap just change the non working keycodes in it (eg use KEY_ENTER instead of KEY_OK).

    so long,

    Hias

  • gpio-shutdown question

    Actually this is more of a Kodi thing than a Linux one. keyboard.xml is one of Kodi's configuration files where user settings are stored.

    Kodi first loads it's default configuration files (from /usr/share/kodi/system) and then the user config files (from /storage/.kod/userdata). The user config files can add new key mappings or override existing ones - we are doing the latter here, the default mapping for the power button is ActivateWindow(ShutdownMenu) - which brings up the shutdown menu.

    For more details have a look at the Kodi wiki: Keymap - Official Kodi Wiki

    PS: you can also change keyboard mapping with the "Keymap Editor" addon, but personally I find it a bit cumbersome to use. Creating the config files manually with an editor (nano or vi) isn't much more complicated, you see all changes you made without having to navigate through tons of submenus in the addon, and is even more flexible as you are not restricted to the functions/mappings the addon knows about.

    so long,

    Hias

  • gpio-shutdown question

    You need to create a /storage/.kodi/userdata/keymaps/keyboard.xml file with the following contents:

    Code
    <keymap>
  <global>
    <keyboard>
      <power>ShutDown()</power>
    </keyboard>
  </global>
</keymap>

    The default kodi configuration is to show the shutdown menu.

    so long,

    Hias

  • Raspberry PI gpio-fan overlay

    Quote from Noltari

    I was wondering if you could enable support for gpio-fan overlay on Raspberry Pi images, since both the 3B+ and 4B would benefit from it.

    Ah, yes, that makes sense. I though we already had the gpio-fan driver enabled, but at a closer look we only enabled the fan driver for the RPi POE HAT.

    I've added the config change to the LE9.2 kernel update PR so it should be included in LE 9.1.003

    linux (RPi) update to 4.19.58+ by HiassofT · Pull Request #3696 · LibreELEC/LibreELEC.tv · GitHub

    so long,

    Hias

  • rpi 3B and Logitech k400

    If you stuck your RPi somewhere in the back of your TV/shelf/... try connecting the receiver with a ~1m USB extension cable and place it somewhere in the front of the TV - so there's nothing (metal) between the keyboard and the receiver that might block RF.

    so long,

    Hias

  • rpi 3B and Logitech k400

    The interesting line in your dmesg is this one, 2 minutes after system startup:

    Code
    [ 121.582064] logitech-hidpp-device 0003:046D:400E.0004: HID++ 2.0 device connected.

    I can get this on my RPi4, too, when I switch the keyboard off and then back on.

    So it very much looks like the Logitech unifying receiver lost the connection to your keyboard and then reconnects. This can be for a number of reasons - RF interference, keyboard switched off/on, keyboard too far away from receiver or receiver shielded by some metal etc.

    Not much we can do about it, you have to check for these things in your setup.

    BTW: A couple of years ago I had connection issues with the unifying receiver plugged directly into one of the back USB ports of my PC (with metal case). Using the ~5cm adapter that shipped with it was enough to cure these. Problem in this case was the metal case shielded the receiver. So if in doubt always use the adapter.

    so long,

    Hias

  • Raspberry PI 4B, Sharp Aquos (~2011), LibreElec = Scrambled Video

    I just noticed that the latest RPi firmware contains a fix for 1366x768 mode - see bug discussion here rpi4 hdmi not working with motorola atrix lapdock · Issue #1202 · raspberrypi/firmware · GitHub

    Testing with that might be worth a try (drop hdmi_drive/group/mode from config.txt and only keep hdmi_force_hotplug=1). Use the following commands to update to the latest firmware:

    Code
    mount -o remount,rw /flash
wget -O /flash/start.elf https://github.com/raspberrypi/firmware/raw/master/boot/start4x.elf
wget -O /flash/fixup.dat https://github.com/raspberrypi/firmware/raw/master/boot/fixup4x.dat

    so long,

    Hias

  • Raspberry PI 4B, Sharp Aquos (~2011), LibreElec = Scrambled Video

    Edit the cmdline.txt file on the FAT partition of the SD card and add "ssh" (after "quiet", with a space between) - ths will enable ssh. You can do this from Windows, but make sure you use an editor that uses unix line endings, like Notepad++

    Then ssh in and post the outputs of the following commands

    Code
    journalctl -a | pastebinit
tvservice -s
tvservice -m CEA
tvservice -m DMT
pastebinit .kodi/temp/kodi.log

    BTW: Do you see the LibreELEC splash screen when the system starts or is the screen scrambled from the beginning?

    so long,

    Hias

  • Is there an addon or a command to detect remote key for RF remote like LIRC ?

    Another option would be to tell eventlircd to translate the keyboard events from your remote into lirc events - then you can use kodi's Lircmap.xml plus remote.xml (or keymap editor addon) to map the button codes.

    To do this you first need to find out the USB vendor and model/product id using "lsusb" - note the "ID" output from your RF receiver, the first 4-digit hex number (before the colon) is the vendor ID, the second 4-digit hex number (after the colon) is the model/product ID.

    Then copy LibreELEC's eventlircd udev rule to /storage/.config/udev.rules.d and edit it:

    Code
    cp /usr/lib/udev/rules.d/98-eventlircd.rules /storage/.config/udev.rules.d/
nano /storage/.config/udev.rules.d/98-eventlircd.rules

    At the beginning of the USB section in that file (around line 90, after the 'ENV{ID_USB_INTERFACES}=="", IMPORT{builtin}="usb_id"') add a line with the following content. Substitute XXXX/ / YYYY with your vendor / model IDs from lsusb and make sure everything is on a single line:

    Code
    ENV{ID_VENDOR_ID}=="0bc7", ENV{ID_MODEL_ID}=="0006", ENV{eventlircd_enable}="true"

    After a reboot eventlircd should pick up your remote and the buttons should show up as Lirc events instead of keyboard events in kodi.log.

    so long,

    Hias

  • Is there an addon or a command to detect remote key for RF remote like LIRC ?

    As suspected the remote is sending some keycodes that kodi doesn't handle.

    You can change the keycodes with a hwdb file - eg map the scancodes to some function keys like f1, f2, f3, ... Read this post for more info Ok button doesn't work on H1 remote

    Also look at the /lib/udev/hwdb.d/60-keyboard.hwdb file in LE, it contains the documentation of the hwdb file format and several entries for keyboards that you can use as a reference.

    so long,

    Hias

  • My 12GB SD card has filled up in a day

    Sorry, I had a stupid typo in that command - it should have been /storage/.cache/cores, not /storage/cache/.cores - this is what I get for not using copy&paste but typing stuff manually :)

    It looks like you already found the culprit, so I think you should be fine and we won't need more info.

    so long,

    Hias

  • My 12GB SD card has filled up in a day

    Check the contents of the /storage/cache/.cores/ directory - the core file names should include the program name.

    eg post the output of

    Code
    ls -l /storage/cache/.cores/ | head -10

    When you notice that a new core file had been created it'd also be useful to post your journal - that should contain some additional info what crashed, and maybe why. run the following command and post the output:

    Code
    journalctl -a | pastebinit

    BTW: probably the number one reason for unexplainable crashes on RPis is a bad power supply. The official RPi power supply is known to be good, use that if in doubt.

    so long,

    Hias

  • LibreELEC (Leia) 9.2 ALPHA1 with Raspberry Pi 4B Support

    Quote from Monie

    Also even after 9.1.002 update there still seems to be a very minor amount of stuttering on a 1080p x265 video. Is there any way to generate a report on this and upload it here?

    A debug log might help. Enable debug logging in Kodi, reboot your RPi, play that file until you see the stuttering, then stop it and use the logfile upload function in LE settings and post the URL here.

    See Provide Log File [LibreELEC.wiki] for details

    so long,

    Hias