Bug 18276

Summary: Server picks 2048x1536 for monitor only supporting up to 1600x1200
Product: xorg Reporter: Bryce Harrington <bryce>
Component: Server/GeneralAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED INVALID QA Contact: Xorg Project Team <xorg-team>
Severity: major    
Priority: high CC: murrayc, sklist
Version: 7.4 (2008.09)   
Hardware: x86 (IA32)   
OS: Linux (All)   
URL: https://bugs.edge.launchpad.net/ubuntu/+bug/290156
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Parsed EDID info
none
Xorg.0.log from failed session none

Description Bryce Harrington 2008-10-28 14:04:59 UTC 
Forwarding this bug from a Ubuntu reporter:
https://bugs.edge.launchpad.net/ubuntu/+bug/290156

[Problem]
Intel D945Gnt + Hitachi CM721F monitor gets display out of range error on xserver 1.5.2.

[Discussion]
From the Xorg.0.log it appears confused what resolution to use, and ends up picking one the monitor can't do:

(II) intel(0): Using fuzzy aspect match for initial modes
(II) intel(0): Output VGA using initial mode 2048x1536

From the EDID it appears this monitor provides one modeline:

        Mode    "1600x1200"     # vfreq 75.000Hz, hfreq 93.750kHz
                DotClock        202.500000
                HTimings        1600 1664 1856 2160
                VTimings        1200 1201 1204 1250
                Flags   "+HSync" "+VSync"
        EndMode

I'm assuming that it ought to be matching this modeline:

(II) intel(0): Modeline "1600x1200"x75.0  205.99  1600 1720 1896 2192  1200 1201 1204 1253 -hsync +vsync (94.0 kHz)

So why might it not be matching up properly?  Where is the 2048x1536 resolution coming from?  Is that what it's actually trying to use?  Is there a way (e.g. a quirk) to force it to not use anything above 1600x1200?
Comment 1 Bryce Harrington 2008-10-28 14:07:58 UTC 
Created attachment 19915 [details]
Parsed EDID info
Comment 2 Bryce Harrington 2008-10-28 14:08:23 UTC 
Created attachment 19916 [details]
Xorg.0.log from failed session
Comment 3 Adam Jackson 2010-05-10 11:41:06 UTC 
The raw edid block is much more useful than the parsed one...
Comment 4 Adam Jackson 2010-08-09 13:16:06 UTC 
No EDID block means I can't work on this.
Comment 5 Scott Kitterman 2010-08-09 14:02:46 UTC 
Tell me how to collect the information and I'll be glad to do it.
Comment 6 Julien Cristau 2010-08-22 04:02:52 UTC 
(In reply to comment #5)
> Tell me how to collect the information and I'll be glad to do it.

xrandr --prop should list it.  Or, with kms, /sys/class/drm/card0-$output/edid.
Comment 7 Adam Jackson 2018-06-12 18:43:41 UTC 
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please file a new report if you continue to experience issues with a current server.

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.