It sounds like you have a dodgy cable or adapter which isn't allowing the Pi to read the EDID from the display.
From the firmware log, it's tried and given up reading the EDIDThe kernel has tried and got something invalid (it may have not created the edid file in /sys/class/drm because it's invalid, although that isn't overly helpful!)
Extracting that lump from the kernel log, edid-decode can decode it.There's the error of the checksum being 0x79 when it should be 0x8b.
I've done that quick hack, and converted it back to binary (xxd -r -ps hexdump.txt > binary.bin). That's attached to this post.
From the firmware log, it's tried and given up reading the EDID
Code:
004297.186: HDMI1:EDID error reading EDID block 0 attempt 0004298.203: HDMI1:EDID giving up on reading EDID block 0Extracting that lump from the kernel log, edid-decode can decode it.
Code:
edid-decode (hex):00 ff ff ff ff ff ff 00 5c 94 ce 18 f6 c3 08 0017 15 01 03 80 84 4c 78 0a 01 c1 a0 57 47 98 2700 4c 4c a1 08 00 31 40 45 40 61 40 81 80 95 00b3 00 01 01 01 01 02 3a 80 18 71 38 2d 40 58 2c46 00 30 eb 52 00 00 1e 00 00 00 ff 00 36 33 3530 48 31 32 33 30 31 32 32 36 00 00 00 fc 00 5652 2d 36 30 32 35 5a 0a 20 20 20 20 00 00 00 fd00 30 3e 0e 44 0f 00 0a 20 20 20 20 20 20 01 79----------------Block 0, Base EDID: EDID Structure Version & Revision: 1.3 Vendor & Product Identification: Manufacturer: WDT Model: 6350 Serial Number: 574454 Made in: week 23 of 2011 Basic Display Parameters & Features: Digital display Maximum image size: 132 cm x 76 cm Gamma: 2.20 RGB color display First detailed timing is the preferred timing Color Characteristics: Red : 0.6250, 0.3398 Green: 0.2773, 0.5947 Blue : 0.1552, 0.0000 White: 0.2968, 0.2978 Established Timings I & II: IBM : 720x400 70.082 Hz 9:5 31.467 kHz 28.320 MHz DMT 0x04: 640x480 59.940 Hz 4:3 31.469 kHz 25.175 MHz DMT 0x09: 800x600 60.317 Hz 4:3 37.879 kHz 40.000 MHz DMT 0x10: 1024x768 60.004 Hz 4:3 48.363 kHz 65.000 MHz Standard Timings: DMT 0x04: 640x480 59.940 Hz 4:3 31.469 kHz 25.175 MHz DMT 0x09: 800x600 60.317 Hz 4:3 37.879 kHz 40.000 MHz DMT 0x10: 1024x768 60.004 Hz 4:3 48.363 kHz 65.000 MHz DMT 0x23: 1280x1024 60.020 Hz 5:4 63.981 kHz 108.000 MHz DMT 0x2f: 1440x900 59.887 Hz 16:10 55.935 kHz 106.500 MHz DMT 0x3a: 1680x1050 59.954 Hz 16:10 65.290 kHz 146.250 MHz Detailed Timing Descriptors: DTD 1: 1920x1080 60.000 Hz 16:9 67.500 kHz 148.500 MHz (1328 mm x 747 mm) Hfront 88 Hsync 44 Hback 148 Hpol P Vfront 4 Vsync 6 Vback 35 Vpol P Display Product Serial Number: '6350H12301226' Display Product Name: 'VR-6025Z' Display Range Limits: Monitor ranges (GTF): 48-62 Hz V, 14-68 kHz H, max dotclock 150 MHz Extension blocks: 1Checksum: 0x79 (should be 0x8b)I've done that quick hack, and converted it back to binary (xxd -r -ps hexdump.txt > binary.bin). That's attached to this post.
Statistics: Posted by 6by9 — Tue Jan 27, 2026 7:45 pm