Running "create-edid-cpio" is necessary each time you manually change the .config/firmware/edid/ file(s).
"getedid create" automatically calls that to create the initrd after retrieviing the edid from the TV. In addition to that it modifies config.txt and cmdline.txt to enable the edid override.
Since you already ran "getedid create" before you only need to run "create-edid-cpio".
so long,
Hias
MRudolph the EDID contains the physical HDMI port address so if you switch to a different TV or even to another HDMI port on your TV that'll easily break CEC if you ran "getedid create" before.
But since your RPi4 seems to detect the old TV fine you could use that to grab the EDID of your old TV and then use it on your RPi5:
Start LE12 on your RPi4 with HDMI-A-1 connected to the HDMI port of your TV which you'll then use for your RPi5.
First make sure you have no edid override in place, if in doubt run "getedid delete" and reboot so the RPi will actually read the EDID from the TV.
Now ssh in and run "getedid create" to grab the edid, you'll then have a edid-HDMI-A-1.bin file in /storage/.config/firmware/edid/ which you need to copy over to your RPi5.
On the RPi5 make sure you have an edid override (from getedid create) in place, the one from your new TV will do fine, then overwrite the /storage/.config/firmware/edid/edid-HDMI-A-1.bin file with the one from your RPi4 and run "create-edid-cpio" to also update the initrd (which contains the edid firmware override for early stage boot).
Now the RPi5 will have the correct edid of your old TV and hopefully CEC might work better - you may need to wipe CEC settings in kodi, it could also still have physical address overrides and then things go south.
But CEC is a bit of a mess, every TV vendor seems to implement it differently, so it could also be that you'll still need to switch TV inputs to get it working.
so long,
Hias
Then better go to the RPi forums. If only the second HDMI port shows HDMI/EDID in the bootloader but not the first one then this could also be a hardware fault of the RPi (in that case you should return it to the seller for a replacement) - but double-check with the RPi folks, they might have another clue or advice for you.
so long,
Hias
Do you have a source for me on how to do that?
Try creating an autostart.sh file with these two lines (see https://wiki.libreelec.tv/configuration/…wn#autostart.sh), then reboot:
rm -f /dev/cec0
ln -s /dev/cec1 /dev/cec0Note that I haven't tested this. If it doesn't work then remove the autostart.sh file.
so long,
Hias
Still nothing kodi related in your paste, but I noticed you are running piracy crap. You are in violation of our forum rules so support ends here.
so long,
Hias
We've got a fix for the RPi crash https://github.com/LibreELEC/LibreELEC.tv/pull/11147, it should land in nightlies soon.
so long,
Hias
After enabling debug logging you need to reboot, then reproduce the issue, then upload the crash log - the journal in your log didn't show any signs of a kodi crash.
Verify the uploaded crash log and be sure it contains the kodi log at the beginning - sometimes creating a crash log can fail if it gets too large.
so long,
Hias
There's no kodi log/crash info in the log. Please try again.
so long,
Hias
Please post a debug log instead of AI-slop, the latter doesn't help us much.
My guess is that could be caused by the recent addition of EAC3 transcoding in kodi https://github.com/xbmc/xbmc/pull/28001 which got included in LE build 20260329-14b0c24. In that case best open a kodi issue https://github.com/xbmc/xbmc/issues
I'll let your AI figure out if it's EAC3 related or not and if you should open an issue on kodi's repo
so long,
Hias
For me, the simplest solution would be if CEC were re-enabled for HDMI 1.
That's unfortunately not easily possible - libcec hardcoded /dev/cec0 as the device and the first attempt to support /dev/cec1 as well failed miserably.
The best workaround IIRC is to remove /dev/cec0 and symlink /dev/cec1 to /dev/cec0 (eg in autostart.sh).
so long,
Hias
As the bootloader has issues detecting the TV it could be some hardware issue/difference between RPi4/5 or some difference in the closed-source bootloaders.
It's best to either ask on the RPi forums https://forums.raspberrypi.com/ or open an issue on the rpi-eeprom bootloader repo https://github.com/raspberrypi/rpi-eeprom
so long,
Hias
The RPi crash in current nightlies is related to hardware deinterlacing.
If you disable that in "Settings"->"Player"->"Allow hardware deinterlacing with DRM PRIME" (you need to enable expert mode to see that) playback works fine and interlaced videos will use the bwdif deinterlacer (which gives better quality than the HW deinterlacer).
Still, we're trying to figure out what exactly causes the crash and fix that to get HW deinterlacing back (RPi2/3 don't have the CPU power to deinterlace HD videos in software).
so long,
Hias
Thanks a lot for the debug backtrace, we're already investigating the RPi issue
so long,
Hias
I can't comment on the C5 (no idea what that should be) but it's more likely that's standard network traffic in your LAN, coming from other devices (or your router) that reaches your device.
Lots of network protocols (ARP/ND, MDNS, ...) rely on small broadcast or multicast messages that are transmitted to all devices in a LAN segment - and those cause the network LEDs to blink.
You'll see the same blinking on PCs, switches etc, too - if they have LEDs.
so long,
Hias
OK, weird.
You could test if it makes a difference if the DAC is plugged in before you power up the RPi vs if you plug it in after you powered up the RPi.
If it never shows up it could also be some hardware fault.
so long,
Hias
There are no signs of a USB device in the log, not even an error during enumeration.
Please give the LE13 nightly a try (ideally on a separate SD card), if this doesn't work either then it's best to test with the Raspberry Pi OS and move testing over to the RPi forums - it all looks like a compatibility issue between the USB DAC and the RPi's USB controller.
so long,
Hias
If the DAC doesn't show up with lsusb it points to a general USB (compatibility) issue. Please run "pastekodi" with the DAC connected so we can see the full dmesg output and system logs.
It would be worth testing with the latest LE13 nightly, it ships with a newer kernel that might help.
so long,
Hias
Hello, seriously, just complaining without any info or logs?
Hint: if you only get 1024x768 and no HDMI audio this usually means the RPi couldn't detect the TV/receiver and was unable to read the EDID - and is running with some fail-safe defaults.
So check the cabling (especially avoid micro<->full-size HDMI adapters and keep in mind that cases with built-in HDMI adapters are rather prone to this sort of issue).
Time will be set correctly once you configured your timezone and are connected to the network/internet so time can be retrieved from NTP servers.
so long,
Hias