On Sun, 14 Sep 2025, Tiago Martins Araújo <tiago.martins.ara...@gmail.com> wrote: > Complete EDID Data: > > 00000000 00 ff ff ff ff ff ff 00 36 74 5a 09 00 00 00 00 > |........6tZ.....| > 00000010 00 21 01 04 b5 22 16 78 03 ee 95 a3 54 4c 99 26 > |.!...".x....TL.&| > 00000020 0f 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01 > |.PT.............| > 00000030 01 01 01 01 01 01 40 e7 00 6a a0 a0 67 50 08 98 > |......@..j..gP..| > 00000040 08 00 58 d7 10 00 00 18 00 00 00 fd 00 30 78 87 > |..X..........0x.| > 00000050 87 3c 01 0a 20 20 20 20 20 20 00 00 00 fe 00 43 |.<.. > .....C| > 00000060 53 4f 54 33 0a 20 20 20 20 20 20 20 00 00 00 fe |SOT3. > ....| > 00000070 00 4d 4e 45 30 30 37 5a 41 31 2d 35 0a 20 01 98 |.MNE007ZA1-5. > ..| > 00000080 70 13 79 00 00 03 01 14 9a 0f 01 05 3f 0b 9f 00 > |p.y.........?...| > 00000090 2f 00 1f 00 07 07 69 00 02 00 05 00 00 00 00 00 > |/.....i.........| > 00000100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > |................| > 00000110 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > |................| > 00000120 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > |................| > 00000130 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > |................| > 00000140 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > |................| > 00000150 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > |................| > 00000160 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > |................| > 00000170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0 98 > |................|
That's not the complete EDID data, though. It's missing 6*16 bytes. If you go by the hex offsets, 0x100 does not follow 0x090. > As an experiment to understand the failure, I commented out the checksum > validation code. Results with validation bypassed: Running that, please grab the EDID from sysfs. edid-decode does a good job of decoding, but also includes the hex in case we want to run it on a newer or modified edid-decode. BR, Jani. -- Jani Nikula, Intel
