Thanks for reporting back, glad to hear it's working now!
I've PR'ed the changes for LE13 and LE12.2. It will take a while until it's in nightlies so in the meantime here's a LE12.2 image - would be nice if you could confirm if that's working, too:
https://www.horus.com/~hias/tmp/libreelec/LibreELEC-RPi5.aarch64-12.2-devel-20251214204956-b7754e4.img.gz
so long,
Hias
Please first update the bootloader (in LE12.2.1 go to Settings->LibreELEC->Update, scroll down to the end) and then test with a fresh installation of this image (leave config.txt alone for now):
https://www.horus.com/~hias/tmp/libreelec/LibreELEC-RPi5.aarch64-13.0-devel-20251214122221-2bad22a.img.gz
SATA support isn't enabled in our RPi images ATM, the above image adds that.
If it doesn't work please again post a 'pastekodi' log.
so long,
Hias
Please update to LE 12.2.1 and provide a full log if it doesn't work
so long,
Hias
We just added a fix for this issue, see https://github.com/LibreELEC/LibreELEC.tv/pull/10785, images are currently building and will be available in about 12-24h.
If you use an RPi5 please note that you need to update your bootloader before updating to current nightlies - see Important: LibreELEC 13 on RPi5 requires bootloader EEPROM 2025-02-12 or newer
so long,
Hias
With the update to kernel 6.18 RPi5 requires bootloader EEPROM 2025-02-12 or newer to be installed, otherwise LE won't work properly (eg you won't get any output on the screen).
Make sure your EEPROM is at this version, or newer, before updating to LE 13 builds after 2025-12-10:
If you are running LE12.2 or LE13 go to Settings->LibreELEC->Update, check Bootloader EEPROM update option at the end and install the update if needed.
Older LE versions don't ship with new enough bootloader EEPROM updates, if you want to update to LE13 either update to LE12.2 first or use a spare SD card and the Raspberry Pi Imager to create a bootloader recovery card and boot from that:
Download Raspberry Pi Imager from https://www.raspberrypi.com/software/ and install it, then choose device Raspberry Pi 5 and OS Misc Utilities->Bootloader->SD or NVME/USB or network boot (depending on your setup). Boot the RPi5 from this rescue SD card, after a few seconds you should get a green screen which means "success".
Audio is a bit tricky.
It's best to leave the EDID of the second HDMI port as is (using "getedid create" to fetch and force the EDID read from the AVR etc is fine), so it's using the info from the connected AVR/audio extractor/... - it you use some display mode not supported by the AVR, force some speaker allocation that doesn't match what's connected to the AVR etc things will go south.
For the EDIDs used by the first HDMI port / monitor it's best to create 3 different ones for 2.0, 5.1 and 7.1 setups (this is eg also what my HDFury VRROM offers in it's built-in EDIDs).
Enabling higher sample rates than 48kHz or compressed formats like AC3, DTS, MLP etc shouldn't hurt but keep in mind that there are audio bandwith limitations on the lower res modes. 720p50 and above will do 192kHz 8ch fine, but modes below are quite limited (eg 640x480p60 only allows up to 8ch 48kHz or 2ch 192kHz) - IIRC there's some info about that in HDMI or CEA specs.
If you use some HDMI audio extractor or similar (or even just a TV/monitor with audio capability) you'll also have to test if it actually works with the custom modes you added - some may only work fine with the standard HDMI modes but not with anything else.
so long,
Hias
There isn't really anything we can do here.
Modifying EDIDs would be something that needs to be done deep down in the linux kernel and that has a high risk of breaking things - just look at the cheap chinese HDMI audio splitters which modify EDID on the fly and break stuff because they didn't get it 100% right.
Also adding modes that are not supported by a monitor may at best confuse users (I did a test with your EDID and my monitor didn't like 1440 × 1080 and 640 × 480 96Hz modes - signal out of range) or even worse interfere with kodi's whitelist because it may pick one of the additional modes instead of the actually supported modes reported by the display.
The way forward is that you create a curated, known working set of EDIDs that pepole can choose from - similar to what HDFury is doing, see eg https://hdfury.com/tools/HDfury_EDID_collection.zip
People can then pick one of those EDIDs that match their setup (eg either 1440x1080 or 640 × 480 96Hz), verify on their own that it really works with their display device and use one of the standard methods to inject it - either the edid override you get "for free" with linux, with an external "EDID fixer" device like the HDFury Dr.HDMI, VRROOM or similar ones, or by patching/reprogramming the HDMI sink (the latter would risky and often might not be possible to do though).
so long,
Hias
sinbad74 That's expected. since you have the Digi 2 Pro you also need the digi-pro dtoverlay, not the digi one (which is for the older, non-pro card)
so long,
Hias
For some reason the ext4 / storage partition has a different UUID.
Adjust the disk=UUID=783... option in cmdline.txt so it matches the actual UUID (disk=UUID=0cb...)
so long,
Hias
Drop all workarounds you added so far, it should simply work out-of-the-box with the new image.
so long,
Hias
I've managed to identify the culprit, it was iptables: https://github.com/LibreELEC/LibreELEC.tv/pull/10757
The fix will be included in the next nightly image.
so long,
Hias
You can't have kodi output on both HDMI connectors. The best thing you can do is to force output to a specific HDMI port via advancedsettings.xml and then restart kodi. See RE: [RPi4] HDMI Audio with Touchscreen
so long,
Hias
It's best to stay away from the MCE keyboard protocol, it's a bit of a mess and as you noticed it doesn't work well.
Reprogram your Logitech remote to use the standard RC6 MCE (remote) protocol and it should work fine out of the box.
so long,
Hias
I couldn't find any info what the Hifiberry folks changed between rev 2.1 and 2.2 but I found a post where a user got his Digi+ pro working with a slight hardware modification - something similar might work with the Digi2 Pro as well:
https://support.hifiberry.com/hc/en-us/community/posts/15842018863261/comments/16381227323677
From the looks of it Hifiberry messed up their hardware design and I'm wondering why they didn't wire up the WM8804 reset to a GPIO pin like outlined in the reference design in the WM8804 datasheet, this likely would have avoided the powerup issues.
The Linux driver supports this and the Allo DigiOne and the Cirrus WM5102 dtoverlays use this, just not the Hifiberry and other WM8804 based SPDIF soundcards.
so long,
Hias
Reset the CEC settings in kodi to defaults and then reboot.
so long,
Hias
Check the revision number on your hifiberry PCB, this seems to be a common problem with RPi4s and all but the latest Hifiberry PCB revision:
so long,
Hias
Latest firmware for RPi5 is from 2025-11-05 but in LE 12.2.1 is from 2025-05-08.
Our time machine is currently on repair, and as LE 12.2.1 was released before that we weren't able to include that in our images - sorry.
so long,
Hias
Hint: after disabling the geo-blocked content in SVT addon settings everyone is able to test. Works on my personal LE12.2 Generic development image.
Good hint, the non-geoblocked content works fine here on LE12.2.1 / RPi5 as well.
so long,
Hias
