Power up the RPi without the SD card, then you should see a diagnostic screen.
Look for the "display" line, you should see "display: DISP0: HDMI HPD=1 EDID=ok".
Likely you have HPD=0 or no EDID which is not good - appending video=... to cmdline.txt will give you video output but no audio if the EDID is missing.
Check the display cable, if you use some adapter try with a straight micro-HDMI to HDMI cable, if you use an argon one case try without it.
so long,
Hias
Do you use a case? If yes, remove the RPi from it and connect the HDMI cable directly to the connector on the PCB.
so long,
Hias
info <general>: CDRMUtils::FindConnector - using connector: HDMI-A-2Same problem as above, use the other HDMI port (which will also give you the possibility to use 2160p60 on your RPi4).
so long,
Hias
The pwm-gpio-fan dtoverlay is included in LE12.0.2.
I haven't tested it myself though, so any feedback if it works or not would be welcome.
so long,
Hias
Based on Kodi 21.2?
yes
LE 12.0.2 is already in internal testing and should be released soon.
so long,
Hias
set the FIRMWARE_RELEASE_STATUS environment variable. eg
FIRMWARE_RELEASE_STATUS=latest rpi-eeprom-updateNote 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
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_busyso long,
Hias
FWIW: I've been simply using zcat for years without any issues:
zcat LibreELEC-RPi4.aarch64-12.0.1.img.gz > /dev/sdXIf you are using Linux, Windows or MacOS you can also simply use the Raspberry Pi Imager - LibreELEC is available in the Mediacenter section.
so long,
Hias
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/nullso 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