edid firmware load attempted before firmware overlay

tudorapo · January 4, 2024 at 4:08 PM

Hi!

I'm trying to use my Pi5 on an old bravia television, and I managed to make it work by loading the edid from the kernel command line. But this stopped working now.

LibreELEC (community): nightly-20231222-581a2fe (RPi5.aarch64)
pocok:~ # dmesg | grep firm
[ 0.000000] psci: PSCIv1.1 detected in firmware.
[ 0.000000] Kernel command line: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 smsc95xx.macaddr=D8:3A:DD:9C:61:C1 vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000 boot=UUID=2212-4031 disk=UUID=5fb8b51f-c02e-4893-9d19-c1e7f928512e console=ttyAMA10,115200 console=tty0 drm.edid_firmware=HDMI-A-1:braviaedid.bin drm.edid_fixup=0
[ 0.719435] raspberrypi-firmware soc:firmware: Attached to firmware from 2023-10-18T17:30:17, variant start_cd
[ 0.732825] raspberrypi-firmware soc:firmware: Firmware hash is c2da2ae700000000000000000000000000000000
[ 2.590147] vc4-drm axi:gpu: Direct firmware load for braviaedid.bin failed with error -2
[ 2.590151] vc4-drm axi:gpu: [drm] *ERROR* [CONNECTOR:32:HDMI-A-1] Requesting EDID firmware "braviaedid.bin" failed (err=-2)
[ 2.605023] vc4-drm axi:gpu: Direct firmware load for braviaedid.bin failed with error -2
[ 2.611372] vc4-drm axi:gpu: [drm] *ERROR* [CONNECTOR:32:HDMI-A-1] Requesting EDID firmware "braviaedid.bin" failed (err=-2)
[ 3.153476] kernel-overlays-setup: added firmware from /usr/lib/kernel-overlays/base/lib/firmware
[ 3.158760] kernel-overlays-setup: added firmware from /storage/.config/firmware

For my untrained eyes this looks like a wrong order of things. Do my eyes deceive me?

The file is there:

pocok:~ # ls /storage/.config/firmware/
braviaedid.bin

The fixup parameter does nothing useful, the output is the same without it.

Thanks in advance.

**Da Flex** · January 4, 2024 at 4:39 PM

Please provide a full debug log.

How to post a log (wiki)

1. Enable debugging in Settings>System Settings>Logging
2. Restart Kodi
3. Replicate the problem
4. Generate a log URL (do not post/upload logs to the forum)

use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link

**HiassofT** · January 4, 2024 at 5:00 PM

Did you create and enable the edid.cpio initrd as well?

getedid create will all do this automatically but braviaedid.bin looks like you set this up manually.

so long,

Hias

tudorapo · January 4, 2024 at 5:26 PM

The link of the log: https://paste.libreelec.tv/patient-monster.log

tudorapo · January 4, 2024 at 6:07 PM

Quote from HiassofT

Did you create and enable the edid.cpio initrd as well?
getedid create will all do this automatically but braviaedid.bin looks like you set this up manually.

No, I did not - no idea how and why should I have done it. I copied the edid from a pi zero which was able to use the tv, and this firmware load etc worked a week ago.

**HiassofT** · January 4, 2024 at 11:56 PM Best Answer

You can find some - rather outdated, somewhat incorrect and PC specific - background info in the wiki here: https://wiki.libreelec.tv/configuration/edid

Long story short: remove all the stuff you manually added, connect the RPi to your TV and reboot, then run getedid create via ssh and you are done.

That will dump the edid of your TV to .config/firmware/edid, create the necessary edid.cpio initrd so that the edid is also available in very early boot stage - before the .config/firmware overlay is enabled and everything will be fine - no need to manually fiddle around with duming edids, adjusting config.txt and cmdline.txt etc

so long,

Hias

tudorapo · January 5, 2024 at 9:41 AM

thanks. worked like a charm! I wonder why google did not found this.

Anyways, be your display drivers tear-free for ever!