That matches up to the edid from xrandr, but there's some slight differences:
- 090d01030e261e8cea6f89a25a5d9424 # 5 vs 4
+090d01030e261e8cea6f89a25a4d9424
- 1a484ca1080081808140010103010101 # 3 vs 1
+1a484ca1080081808140010101010101
- 010101011101302a00985100aa403070 # a vs 2
+010101010101302a009851002a403070
- 1300782f1100001e000000fd0037411c # f vs d
+1300782d1100001e000000fd0037411c
- 410b400a202020202020000000fc0053 # 4 vs 0
+410b000a202020202020000000fc0053
The edid from xrandr and read-edid are identical but alternately inverted.
Note those edids are different from what I posted originally, although it's connected to the same kvm and monitor.
dmesg is returning this edid now:
[166049.859894] 00 ff ff ff ff ff ff 00 4d d9 90 10 01 01 01 01
[166049.859896] 09 0d 01 03 0e 26 1e 8c ea 6f 89 a2 5a 5d 94 24
[166049.859898] 1a 48 4c a1 08 00 81 80 81 40 01 01 03 01 01 01
[166049.859900] 01 01 01 01 11 01 30 2a 00 98 51 00 aa 40 30 70
[166049.859902] 13 00 78 2f 11 00 00 1e 00 00 00 fd 00 37 41 1c
[166049.859904] 41 0b 40 0a 20 20 20 20 20 20 00 00 00 fc 00 53
[166049.859906] 44 4d 2d 53 39 31 0a 20 20 20 20 20 00 00 00 ff
[166049.859907] 00 34 32 35 39 39 31 33 0a 20 20 20 20 20 00 d3
That matches up to the edid from xrandr, but there's some slight differences:
- 090d01030e261e8 cea6f89a25a5d94 24 # 5 vs 4 8cea6f89a25a4d9 424 081400101030101 01 # 3 vs 1 808140010101010 101 a00985100aa4030 70 # a vs 2 2a009851002a403 070 e000000fd003741 1c # f vs d 1e000000fd00374 11c 02020000000fc00 53 # 4 vs 0 202020000000fc0 053
+090d01030e261e
- 1a484ca10800818
+1a484ca1080081
- 010101011101302
+01010101010130
- 1300782f1100001
+1300782d110000
- 410b400a2020202
+410b000a202020