Created attachment 19655 [details] Xorg.0.log I'm forwarding this bug report from a Ubuntu user. The user has a 19" Sony Trinitron E400 Monitor that reports invalid EDID. The recommended resolution for this monitor is 1280x1024, but it defaults to 1280x768. The user has tested with stock xorg.confs as well as hand-customized configurations. He is attempting to use an ATI RV200 QW [Radeon 7500] card; the motherboard has an onboard SiS630/730 card; both graphics cards are showing invalid EDID, so we're guessing it's the monitor that's buggy, and must need an xserver quirk. 19" Sony Trinitron E400 Information: Horizontal Freq. 30-96 kHz Vertical Freq. 48-120 Hz ATI card: 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon RV200 QW [Radeon 7500] [1002:5157] (prog-if 00 [VGA]) Subsystem: ATI Technologies Inc Radeon 7500 [1002:013a] qsomi@qsomi-desktop:~/Desktop$ sudo get-edid > edid.dat get-edid: get-edid version 1.4.1 Performing real mode VBE call Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0 Function supported Call successful VBE version 200 VBE string at 0x11110 "ATI RV200" VBE/DDC service about to be called Report DDC capabilities Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0 Function supported Call successful Monitor and video card combination does not support DDC1 transfers Monitor and video card combination supports DDC2 transfers 0 seconds per 128 byte EDID block transfer Screen is not blanked during DDC transfer Reading next EDID block VBE/DDC service about to be called Read EDID Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0 Function supported Call failed The EDID data should not be trusted as the VBE call failed qsomi@qsomi-desktop:~/Desktop$ xxd edid.dat 0000000: ffa2 00ff ffff ff00 4dd9 9003 f24a 7b00 ........M....J{. 0000010: 2f0a 0102 0e25 1b96 eb0c c9a0 5747 9b27 /....%......WG.' 0000020: 1248 4cff ff80 c280 a94f 8159 814f 7159 .HL......O.Y.OqY 0000030: 6159 4559 3159 863d 00c0 5100 3040 40a0 aYEY1Y.=..Q.0@@. 0000040: 1300 6008 1100 001e 0000 00fd 0030 781e ..`..........0x. 0000050: 601e 000a 2020 2020 2020 0000 00fc 0053 `... .....S 0000060: 4f4e 5920 4350 442d 4534 3030 0000 00ff ONY CPD-E400.... 0000070: 0038 3038 3031 3134 0a20 2020 2020 00d8 .8080114. .. http://launchpadlibrarian.net/17528516/edid.dat With the onboard SiS 630/730: qsomi@qsomi-desktop:~/Desktop$ sudo get-edid > edid.dat get-edid: get-edid version 1.4.1 Performing real mode VBE call Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0 Function supported Call successful VBE version 300 VBE string at 0x11110 "SiS" VBE/DDC service about to be called Report DDC capabilities Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0 Function supported Call successful Monitor and video card combination does not support DDC1 transfers Monitor and video card combination does not support DDC2 transfers 0 seconds per 128 byte EDID block transfer Screen is not blanked during DDC transfer Reading next EDID block VBE/DDC service about to be called Read EDID Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0 Function supported Call failed The EDID data should not be trusted as the VBE call failed qsomi@qsomi-desktop:~/Desktop$ xxd edid.dat 0000000: ffa2 00ff ffff ff00 4dd9 9003 f24a 7b00 ........M....J{. 0000010: 2f0a 0102 0e25 1b96 eb0c c9a0 5747 9b27 /....%......WG.' 0000020: 1248 4cff ff80 c280 a94f 8159 814f 7159 .HL......O.Y.OqY 0000030: 6159 4559 3159 863d 00c0 5100 3040 40a0 aYEY1Y.=..Q.0@@. 0000040: 1300 6008 1100 001e 0000 00fd 0030 781e ..`..........0x. 0000050: 601e 000a 2020 2020 2020 0000 00fc 0053 `... .....S 0000060: 4f4e 5920 4350 442d 4534 3030 0000 00ff ONY CPD-E400.... 0000070: 0038 3038 3031 3134 0a20 2020 2020 00d8 .8080114. .. http://launchpadlibrarian.net/17528747/edid.dat Example tested with xserver 1.4.99.906-x: xorg.conf: http://launchpadlibrarian.net/16991298/xorg.conf Xorg.0.log: http://launchpadlibrarian.net/16991306/Xorg.0.log http://launchpadlibrarian.net/16991342/xrandr.txt
Well, if you decode that EDID as though it were legitimate (ignoring the header), then it decodes more or less legitimately. I suspect the BIOS is just doing something wrong in EDID fetch, since neither radeon nor sis will use the VBE method to get it; can you get the output of 'xrandr --prop' from this machine too, so we can see what EDID block we're actually interpreting?
Hi Ajax, sorry for the late reply; we've only recently gotten the information from the original reporter. qsomi@qsomi-desktop:~$ xrandr --prop Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 1680 x 1200 VGA-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 0mm x 0mm load_detection: 1 (0x00000001) range: (0,1) 1280x1024@85 85.0*+ 1600x1200 75.0 70.0 65.0 60.0 1680x1050 84.9 74.9 69.9 60.0 1600x1024 60.2 1400x1050 85.0 74.8 70.0 60.0 1280x1024 85.0 75.0 59.9 60.0 1440x900 59.9 1280x960 85.0 60.0 1360x768 59.8 1152x864 100.0 85.1 85.0 75.0 75.0 70.0 60.0 1024x768 85.0 75.0 70.1 60.0 832x624 74.6 800x600 85.1 72.2 75.0 60.3 56.2 640x480 85.0 72.8 75.0 59.9 720x400 85.0 640x400 85.1 640x350 85.1 DVI-0 disconnected (normal left inverted right x axis y axis) dvi_monitor_type: auto scaler: off load_detection: 0 (0x00000000) range: (0,1) S-video disconnected (normal left inverted right x axis y axis) tv_standard: ntsc tv_vertical_position: 0 (0x00000000) range: (-5,5) tv_horizontal_position: 0 (0x00000000) range: (-5,5) tv_horizontal_size: 0 (0x00000000) range: (-5,5) load_detection: 0 (0x00000000) range: (0,1)
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/374.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.