Hello to everyone,
I am running a waveshare 7inch LCD on a Pi4.
Since switching to Bookworm, I am experiencing problems setting the resolution to 1024x600.
I believe I have read almost all forum posts, blogposts and articles related to issues reading the EDID since bookworm in the past 6 months.Nevertheless, it accepts the custom resolution and everything is working fine.
Howver, after upgrading all packages to the latest release, this workaround does not work any more, dmesg shows no error messages at all anymore. Looks like it isn't even trying to load the given EDID. I tried both the valid EDID from the monitor, as well as intentionally corrupted ones, as suggested in some threads on this issue.
xrandr --verbose does not show the monitor EDID, but some fallback with standard resolutions I believe.
I have tried changing disable_fw_kms_setup in the config.txt, as well as auto_initramfs. Nothing makes a difference.
Is there a fix or even an idea what could be causing this on the horizon?
I am running a waveshare 7inch LCD on a Pi4.
Since switching to Bookworm, I am experiencing problems setting the resolution to 1024x600.
I believe I have read almost all forum posts, blogposts and articles related to issues reading the EDID since bookworm in the past 6 months.
- The monitor reports a valid EDID, I have confirmed this by connecting to a windows PC and to a Laptop with LinuxMint. Both recognize the monitor profile and set the resolution correctly out-of-the-box
- I pulled the EDID from one of those machines, confirmed it is valid, turned it into the binary form with xrandr + edid-decoder.
- If I launch the Pi without an SD card, the Debug info scree shows "EDID ok"
- Into /boot/firmware/cmdline.txt I inserted video=HDMI-A-1:1024x600M@60e drm.edid_firmware=HDMI-A-1:1024x600.bin
Code:
dmesg | grep HDMIplatform HDMI-A-1: Direct firmware load for 1024x600.bin failed with error -2Howver, after upgrading all packages to the latest release, this workaround does not work any more, dmesg shows no error messages at all anymore. Looks like it isn't even trying to load the given EDID. I tried both the valid EDID from the monitor, as well as intentionally corrupted ones, as suggested in some threads on this issue.
xrandr --verbose does not show the monitor EDID, but some fallback with standard resolutions I believe.
I have tried changing disable_fw_kms_setup in the config.txt, as well as auto_initramfs. Nothing makes a difference.
Is there a fix or even an idea what could be causing this on the horizon?
Statistics: Posted by photoberry4B — Wed Jun 26, 2024 9:52 am
