Posts by HiassofT

  • Booting Pi with Kodi by remote?

    The RPi doesn't contain any circuitry to wake it up by an IR remote so this won't work out-of-the box.

    IIRC there are addon boards that can do that (can't remember the name though). Or you can install a momentary-push button on GPIO pins 5 and 6 and use the gpio-shutdown overlay - the button will then act as a power on/off button.

    The RPi3 will get warm a bit, some 40-50°C are normal though and nothing to worry about. If it gets hotter than that check if some addon has gone bezerk and keeping the RPi busy.

    Run "top", on idle the summary line on the top should show something between 90 and 97% idle and in the process list kodi should be around 10-15% (here on RPi3B+ I see about 97% idle and 10% kodi).

    so long,

    Hias

  • Trying to disable IR Receiver

    You can disable the IR receiver in your DVB dongle by creating a file /storage/.config/modprobe.d/dvb-usb-disable-ir.conf with the following content:

    Code
    options dvb-usb disable_rc_polling=1

    Or just put a piece of black (gaffer) tape over the IR receiver.

    so long,

    Hias

  • Weird remote behaviour on ZBOX nano

    It's best to use the Microsoft MCE / Kodi profile on your Harmony remote - this will work out of the box.

    The scancodes sent by your current profile seem tio contain a toggle bit (the 5th digit flipping between 8 and 0 on alternating button presses), but since the first 4 digits don't match the MCE "customer code" "800f" the kernel doesn't handle it as a toggle bit - and you get two different scancodes.

    so long,

    Hias

  • How to change files on Read-only file system

    Quote from vpeter

    Well, I tried the same and I didn't saw files from brcm folder. But maybe I made some small mistake. If you are saying that it works then it is ok.

    But you don't see files/folder from /storage/.config/firmware on /usr/lib/firmware/ right?

    It's a bit of a symlink jungle, easy to get lost (maybe I should clean that up a bit some time):

    /lib/firmware symlinks to /var/lib/firmware, a directory in a ramdisk

    /var/lib/firmware gets populated with symlinks to the various kernel overlay directories, from /usr/lib/kernel-overlays and/or addons.

    Currently only /usr/lib/kernel-overlays/base/lib/firmware contains firmware files and that directory has a symlink "updates" pointing to /storage/.config/firmware

    Thinking about it we may run into problems when we add firmwares via overlays (which we don't do at the moment) as that may create symlinks in /storage/.config/firmware. Tricky. maybe handling .config/firmwares via a special case in the kernel overlay system may be better - I'll think about it some more.

    so long,

    Hias

  • How to change files on Read-only file system

    Quote from vpeter

    HiassofT: What about setting overlay automatically from /storage/.config/firmware/ folder? So only files in appropriate should be copied there and after reboot it would work. Without making .conf file.

    I had thought about that as well. But it was puzzling me why adding firmware via .config/firmware shouldn't work so I gave it a try and - guess what - it worked as expected.

    I created an RPi2 image with the RPi wifi firmwares removed and added them in .config/firmware/brcm/:

    Then booted on a RPi3B (which needs the brcmfmac43430-sdio bin and txt files) with dyndbg="module firmware_class +p" on the kernel command line to trace the kernel firmware loader.

    The kernel first checks /lib/firmware/updates/4.19.4, then /lib/firmware/updates which is a symlink to /storage/config/firmware - and succeeds for the bin and txt files and fails for the clm_blob (which isn't available anywhere). In the clm_blob calls one can see though that /lib/firmware/4.19.4 and /lib/firmware are probed afterwards.

    bin:

    Code
    [ 6.223611] firmware_class: __allocate_fw_priv: fw-brcm/brcmfmac43430-sdio.bin fw_priv=1d7ef5e3
[ 6.223669] brcmfmac mmc1:0001:1: loading /lib/firmware/updates/4.19.4/brcm/brcmfmac43430-sdio.bin failed with error -2
[ 6.244375] firmware_class: fw_set_page_data: fw-brcm/brcmfmac43430-sdio.bin fw_priv=1d7ef5e3 data=0caa91ae size=388739

    txt:

    Code
    [ 6.244390] firmware_class: __allocate_fw_priv: fw-brcm/brcmfmac43430-sdio.txt fw_priv=bcdb1585
[ 6.244425] brcmfmac mmc1:0001:1: loading /lib/firmware/updates/4.19.4/brcm/brcmfmac43430-sdio.txt failed with error -2
[ 6.245707] firmware_class: fw_set_page_data: fw-brcm/brcmfmac43430-sdio.txt fw_priv=bcdb1585 data=6ad77431 size=1125

    clm_blob:

    Code
    [ 6.417063] firmware_class: __allocate_fw_priv: fw-brcm/brcmfmac43430-sdio.clm_blob fw_priv=1d7ef5e3
[ 6.417107] brcmfmac mmc1:0001:1: loading /lib/firmware/updates/4.19.4/brcm/brcmfmac43430-sdio.clm_blob failed with error -2
[ 6.417145] brcmfmac mmc1:0001:1: loading /lib/firmware/updates/brcm/brcmfmac43430-sdio.clm_blob failed with error -2
[ 6.417167] brcmfmac mmc1:0001:1: loading /lib/firmware/4.19.4/brcm/brcmfmac43430-sdio.clm_blob failed with error -2
[ 6.417188] brcmfmac mmc1:0001:1: loading /lib/firmware/brcm/brcmfmac43430-sdio.clm_blob failed with error -2

[ 6.417199] firmware_class: __free_fw_priv: fw-brcm/brcmfmac43430-sdio.clm_blob fw_priv=1d7ef5e3 data= (null) size=0

    So I'd say everything's fine and if loading firmware via .config/firmware doesn't work on some systems that has to be investigated in detail.

    so long,

    Hias

  • How to change files on Read-only file system

    Thanks a lot for the detailed feedback!

    It looks like we were not only missing the kernel driver but also the brcmfmac43455-sdio.bin file - we'll include that in the next release.

    You'll still have to take care about the brcmfmac43455-sdio.txt file yourself, but adding just that single file to the my-firmware directory and sticking to the kernel overlay mechanism should be fine I guess (this file is not only missing in Linux mint but also in the linux kernel firmware repository so there's not much we can do about it for now).

    As for the kodi crash: If it wasn't a one-off glitch and you are able to reproduce that please open a ticket with some more information here: Ticket System - LibreELEC Forum with a link to your log. Best use the logfile upload function in LibreELEC settings, that will upload all relevant logs including the kodi_crash.log file with hopefully some useful information.

    so long,

    Hias

  • How to change files on Read-only file system

    Quote from sandin

    Sorry for being newbish (I am actually new to this), but how do I access LE system partition? When I plugin the MicroSD into my PC, all I see is the Storage folder. I have 2 partitions, of which one is the EFI (I presume). But when I try to explore the sdb/sdb2, all I can see is the storage. How do I access the root, and extract SYSTEM file? I know I can use SSH to extract the SYSTEM file, but I cannot replace the SYSTEM file with a new one via SSH because read-only file system won't let me.

    The SYSTEM file is in /flash, but you shouldn't replace it from a running system via ssh as that'll crash your box (it's being used and if you swap it out behind LibreELEC's back things will go really crazy - I accidentally did that once). You'd have to do that without LibreELEC running, eg from a Linux live boot or Windows on a separate partition.

    Better switch to LE9 and use the kernel overlay approach then you don't have to patch your installation on each upgrade.

    so long,

    Hias

  • How to change files on Read-only file system

    Quote from vpeter

    Doesn't LE 9 has new kernel modules and firmware overlay?

    Hmm, yes, good idea! I should have thought about that :)

    The following approach should work:

    Create a /storage/my-firmware/lib/firmware/brcm directory:

    Code
    mkdir -p /storage/my-firmware/lib/firmware/brcm/

    and copy the brcmfmac43455-sdio.txt file in there.

    Then configure the kernel-overlay system to pick up stuff from /storage/my-firmware:

    Code
    echo "/storage/my-firmware" > /storage/.cache/kernel-overlays/90-my-firmware.conf

    Now reboot and the firmware files should be picked up.

    so long,

    Hias