Posts by nosen

I share chewitt's hunch. When my RPi5 didn't output any video, it was because I hadn't updated the firmware on it. More info here: Important: LibreELEC 13 on RPi5 requires bootloader EEPROM 2025-02-12 or newer

Audio works on RPi 3B running 12.2.1, I just tried a fresh install.

HDMI options are not put in config.txt anymore, as HDMI configurations should be made using cmdline.txt instead (different format, don't just copy and paste the old lines). Source

Sanity check: Have you observed any other device being able to play audio on this Sharp TV using the same HDMI port and the same HDMI cable? HDMI ports and cables vary greatly in capabilities.

VLouis you think I'm OP? Why are you giving me attitude?

Will the "bad" RPi4 boot Raspberry Pi OS if you flash that onto an SD card? That could rule out LibreELEC being the issue.

What process seems to be leaking? Could be identified in top via ssh for instance

In bluetoothctl, you need to connect too (pair MAC, trust MAC, connect MAC).

Sounds like the affected video file is slightly broken. The RPi4 uses hardware decoding, which is much stricter about h264 correctness than your mac (which uses software decoding). I'd recommend you to remux the problematic file.

It sounds like you're happy with your setup as-is, but in case you encounter problems again: What you experienced sounds like an EDID issue with your old plasma TV.

I had the same issue when connecting to certain HDMI ports on my old Samsung KS7000 TV. Only one port correctly performed the EDID negotiation (a.k.a. the HDMI handshake). The other three ports restricted my LibreELEC box to a max resolution of 1024x768.

I'd try other HDMI ports in case your TV has them. They're not necessarily all equal, evidently.

Does it happen with a fresh new install, right out of the box?

Does it happen with the generic-legacy version too?

A picture of this graphical glitch would help!

It sounds like something in your config isn't quite right yet. In my experience wireguard isn't clear when the keys aren't right, it just hangs on the handshake and all traffic stalls. You'd think you'd get an error message or something, but no.

Recheck the config! Test the config on a pc where it's easier to debug.

It sounds like you're stuck until wifi 7 gets more adoption and someone adds in-tree kernel-level support for it. My guess (for what it's worth), is that it understandably won't receive explicit attention from the LE devs anytime soon.

That should work. I can't see how the extra load from the fan would be too much for the 3V3 regulator.

Quote from tokul

Not official Raspberry fan, but. Screenshot from sales page.

That is a different fan than in OPs post. Their fan has three wires, the one pictured here only has two.

Maybe it's thermal throttling? Do you have any cooling on the RPis?

I think you are just very unfortunate. I have used many different raspberry pis and sd cards for 10+ years and I have had this happen only once in all that time. I have heard an argument that sd cards in raspberry pis are actually not ideal, because the read/write of the pi will wear out the sd cards' internal nand flash.

If you want to boot from a more robust media, there is a config that lets you use an external ssd. Nvme should be more suited for the r/w load.

Thanks! I got it working!

First, I did a non-persistent test by running

systemctl stop kodi
kmstest -c HDMI-A-1 -P "Broadcast RGB=1" < /dev/null
systemctl start kodi

When I saw that it worked, I made it persistent with this command:

echo 'kmstest -c HDMI-A-1 -P "Broadcast RGB=1" < /dev/null' >> /storage/.config/autostart.sh
systemctl restart kodi

I want to force full RGB (0-255) HDMI output.

This is because my TV (a 2016 Samsung KS7000) thinks the RPi5 is a PC, so it expects full RGB, and skips parts of a full EDID handshake. The Pi does not receive a full EDID, so it falls back on limited range. This mismatch causes lifted blacks and muted highlights, resulting in a washed-out picture. I tried configuring the TV for limited range, but that only persisted until I changed the source back and forth, then the mismatch came back (it's a glitchy and bad TV set honestly).

Is there some way to configure the config files to force full RGB (0-255)?

Ah, that looks like the solution. Thanks!

Starting with nightly version 2025-12-13, I don't get HDMI output after clean installs. LibreELEC-RPi5.aarch64-13.0-nightly-20251210-dd92255.img.gz is the last version that works out of the box. All versions later than that do not output any HDMI. I think Kodi is still running, because I can ping the Pi, and I notice that the Pi reboots after first power on (after resizing the partition, i guess, I'm not certain because I don't have video output).

My setup is a RPi5 connected via HDMI0 (the port closest to the USB-C power port) using an original Raspberry Pi Micro-HDMI to full size HDMI cable. It is connected to a 2016 Samsung KS7000 TV. I suspect this older TV might exhibit this quirky behavior: it may skip EDID handshakes with PCs (it identifies the Raspberry Pi as a PC), but I have not confirmed this yet. I have noticed that if the source is configured as a PC, the TV applies a picture profile that is very restrictive: It disables a lot of the picture settings and forces full HDMI color range, so that is why I suspect the TV to be weird about PC inputs in general.

Sidenote: I am currently trying to find some config.txt option that restores HDMI output but it's cumbersome, since SSH is disabled and I don't know if I can enable it without seeing the GUI. This leaves me with the only option of pulling out the RPi5's power cable, removing the SD card and putting it into my laptop, tweaking the config.txt file, putting the SD card back into the RPi5 and reinserting the power cable. If there is a way to enable SSH by configuring the SD card somehow, I'd love to know.