Posts by HiassofT

set the FIRMWARE_RELEASE_STATUS environment variable. eg

FIRMWARE_RELEASE_STATUS=latest rpi-eeprom-update

Note though that rpi-eeprom and bootloader firmwares are included in the images so if you want to use current bootloader versions you have to use nightly images (LE 12.0.1 ships with latest firmware from about half a year ago, current LE12 and LE13 nightlies have 2025-01-08 latest bootloader ATM)

If you want to use more recent versions just download them from rpi-eeprom github and use rpi-eeprom-update -f YOUR_PI_EEPROM.BIN

GitHub - raspberrypi/rpi-eeprom: Installation scripts and binaries for the closed sourced Raspberry Pi 4 EEPROMs

Installation scripts and binaries for the closed sourced Raspberry Pi 4 EEPROMs - GitHub - raspberrypi/rpi-eeprom: Installation scripts and binaries for the…

github.com

so long,

Hias

Bluetooth uses the 2.4GHz band so will be affected the same way.

Get the extension cord, or some hub and move the dongle away a bit.

so long,

Hias

It's a well-known interference issue between USB 3.0 and 2.4GHz wireless devices (Wifi, pretty much all RF remotes/keyboards/mice/...)

https://www.usb.org/sites/default/files/327216.pdf

It's not RPi specific but affects all devices (PCs etc) with USB 3 . As your RPi3 only has USB 2.0 ports you won't see this issue with it.

so long,

Hias

Try to connect the dongle with a USB extension cable and place it about half a meter or a meter away fron the RPi and any USB3 devices and cables.

so long,

Hias

Better yet create a new toml file with a name matching your remote and reference that in rc_maps.cfg

so long,

Hias

Make sure your TV is connected to the first HDMI port (on the RPi4/5 PCBs that's the one next to the USB-C power socket).

The commit you linked was an attempt to support CEC on the second HDMI port as well, but it was incomplete and caused more problems than it solved so we needed to revert it.

so long,

Hias

It indeed looks like a bad SD card, try with a new one:

Jan 07 16:39:49 LibreELEC-RPi4 kernel: mmc0: Card stuck being busy! __mmc_poll_for_busy

so long,

Hias

FWIW: I've been simply using zcat for years without any issues:

zcat LibreELEC-RPi4.aarch64-12.0.1.img.gz > /dev/sdX

If you are using Linux, Windows or MacOS you can also simply use the Raspberry Pi Imager - LibreELEC is available in the Mediacenter section.

Raspberry Pi OS – Raspberry Pi

From industries large and small, to the kitchen table tinkerer, to the classroom coder, we make computing accessible and affordable for everybody.

www.raspberrypi.com

so long,

Hias

Quote from Froggy

I've just tested the latest nighly 20230310-91357b0

You've picked the oldest nightly, the newest one (20241205) is at the bottom of the page.

Yes, the sorting is a bit confusing and you are not the first one to pick an old nightly by accident.

so long,

Hias

The internal id changed from 32 to 33 (the IDs are not guaranteed to be stable).

Either adjust the modetest line or use kmstest instead where you can specify the connector by name:

kmstest -c HDMI-A-1 -P "Broadcast RGB=1" < /dev/null

so long,

Hias

You need to use the FLIRC software on a PC to configure the dongle.

To linux/LibreELEC the dongle looks like a keyboard, not an IR receiver, and there's nothing you can configure.

so long,

Hias

FYI: the fixed inputstream.adaptive addon (version 22.1.10.2) is now available in the LE addon repo.

so long,

Hias

The "undefined symbol" error is caused by a recent change in inputstream.adaptive and affects widevine on all aarch64 platforms

I've PR'ed fixes to inputstream.adaptive and LE repos so this should work soon again without needing to fiddle around with the widevine library.

Fix widevine on aarch64 by HiassofT · Pull Request #1729 · xbmc/inputstream.adaptive

Description The switch to hidden symbol visibility broke widevine on aarch64 as the functions in the aarch64 cdm_loader.cpp were no longer exported: error…

github.com

so long,

Hias

use "ARCH=aarch64" - arm is 32bit but RPi5 only supports 64bit

PROJECT=RPi DEVICE=RPi5 ARCH=aarch64 make image 

so long,

Hias

Use the other HDMI port. CEC is only supported on the first HDMI port (HDMI-A-1, the one next to the power connector).

LE 12.0.1 contained a change to support CEC on both ports, but kodi didn't cope with this well so this had to be dropped again.

so long,

Hias

Try adding vc4.force_hotplug=1 to /flash/cmdline.txt, see also this thread TV/AVR turns back on right after turning them off

so long,

Hias

It seems you are using a RPi4 with only 1GB of RAM and according to the logs it's running out of memory.

Try adding the following line to the end of /flash/config.txt

dtoverlay=cma,cma-384

so long,

Hias

Even if you install the python modules for getting the netflix key this won't help much in LibreELEC as they'll spawn a chrome browser - which only exists for Generic Legacy and resides in a rather non-standard location so likely you'd have to modify the scripts.

Just run the script on a Windows/Linux PC or Mac.

so long,

Hias