drm.edid_firmware fails to load firmware where crypsetup-initramfs is installed

This change was made by a bot.

[drm:drm_load_edid_firmware [drm]] *ERROR* Requesting EDID firmware "edid/edid1.bin" failed (err=-2)

user@user:~$ ls -la /usr/lib/firmware/edid/edid.bin
-rw-r--r-- 1 root root 256 1月 27 13:15 /usr/lib/firmware/edid/edid.bin

user@user:~$ ls -la /lib/firmware/edid/edid.bin
-rw-r--r-- 1 root root 256 1月 27 13:18 /lib/firmware/edid/edid.bin

user@user:~$ cat /etc/default/grub |grep firmware
GRUB_CMDLINE_LINUX_DEFAULT="drm.edid_firmware=/lib/firmware/edid/edid.bin quiet splash"

Is the EDID file in initramfs?

SOLVED.

Reponding to Kai-Heng question, the edid file was not in initramfs and I didn't know how to add it at the time.

I was using another monitor the last months and didn't encounter this problem.
This week I connected the monitor and found the same problem again, this time with Ubuntu 19.10 and Kubuntu 19.10.

This time I was using an encrypted root partition so the edid file must be in the initfd file to be found by the kernel.

I managed to include it by creating a file named /etc/initramfs-tools/hooks/edid with this content:
-----------
#!/bin/sh
PREREQ=""
prereqs()
{
    echo "$PREREQ"
}

case $1 in
prereqs)
    prereqs
    exit 0
    ;;
esac

. /usr/share/initramfs-tools/hook-functions
# Begin real processing below this line
mkdir -p "${DESTDIR}/lib/firmware/edid"
cp -a /lib/firmware/edid/modified_edid.bin "${DESTDIR}/lib/firmware/edid/modified_edid.bin"
exit 0
-----------

The file needs execution permission: chmod +x /etc/initramfs-tools/hooks/edid
And initrd must be updated: update-initramfs -u

After that "lsinitramfs /boot/initrd.img-5.3.0-40-generic | grep edid" shows the file included.

With this the kernel is able to load the file at boot, and the monitor works nicely.

I suppose the source of this bug is me not knowing how to manage Ubuntu boot process, so if no one more is affected by this problem I think the bug can be closed.
Thanks.

I can confirm that davidaf's work around worked. Though the interesting thing to me was that in 19.10 I didn't have to put the file in initrafs. After upgrading to the 20.04 daily builds this became necessary. Not sure if that means anything or not. Just thought I'd provide an extra data point.

hey there, I have the exact same problem, but I couldn't find a solution yet.
I included the edid file using the script given above:

lsinitramfs /boot/initrd.img-5.11.0-25-generic | grep edid
usr/lib/firmware/edid
usr/lib/firmware/edid/edid.bin

my grub config looks like this:

cat /etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash drm.edid_firmware=edid/edid.bin"
GRUB_CMDLINE_LINUX_DEFAULT="drm.edid_firmware=edid/edid.bin quiet splash"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=1920x1080-24

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

and dmesg logs the following:

sudo dmesg | grep edid
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=UUID=79d59e63-ceea-4975-abf4-b34964ea06c0 ro rootflags=subvol=@ drm.edid_firmware=edid/edid.bin quiet splash vt.handoff=7
[ 0.050890] Kernel command line: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=UUID=79d59e63-ceea-4975-abf4-b34964ea06c0 ro rootflags=subvol=@ drm.edid_firmware=edid/edid.bin quiet splash vt.handoff=7

Though, I still have a low monitor resolution at boot time, which becomes correct when completely booted.
Have I missed anything here?
I'm using Ubuntu 21.04.

I already tried to get the edid file using the nvidia control panel and the read-edid tool, both didn't work.

Running into the same problem. I have 2 Acer G6 G276HL (EDID: ACR Model 768) 27 inch monitors - one of them somehow got its EDID corrupted recently. Ideally, I'd like to write the good EDID into the monitor with the corrupted EDID, but barring that (edid-rw didn't work for me - IO error), I'd like to boot the system with a good EDID. I have two systems - one of which it works perfectly on, the other not so much.

Good system: Ubuntu 21.10 - only had to add good edid to /usr/lib/firmware/edid/acer_monitor.bin and update the grub conf accordingly - everything works.

Bad system: Ubuntu 20.04 based system. Steps tried:
- added good edid to /usr/lib/firmware/edid/acer_monitor.bin
- updated initramfs using script above as reference

In the good system: cat /sys/class/drm/card*/edid shows the updated edid for the card, while for the bad system, I don't see an edid override. cat /proc/cmdline confirms the edid override is in place.

e.g. for 20.04 based system (bad):

# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=f896afab-6f99-4478-a402-9d612972a5b5 ro drm.edid_firmware=DP1:ed
id/acer_monitor.bin quiet splash vt.handoff=7

# lsinitramfs /boot/initrd.img|grep edid
usr/lib/firmware/edid
usr/lib/firmware/edid/acer_monitor.bin

# cat /sys/class/drm/card0-DP-1/edid
... no overridden EDID ...