Bug 697 - autoconfig picks wrong default mode for some LCD monitors
Summary: autoconfig picks wrong default mode for some LCD monitors
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: 6.7.0
Hardware: x86 (IA32) Solaris
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-31 17:31 UTC by Alan Coopersmith
Modified: 2007-03-12 08:03 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Alan Coopersmith 2004-05-31 17:31:07 UTC
When letting Xorg autoconfig itself, it chooses a non-native default resolution
for the ViewSonic VX2000 LCD.  It picks a 1400x1050 resolution with a 74.8 Hz
refresh rate, instead of the native 1600x1200 at 60Hz, because the
autoconfiguration template in
xc/programs/Xserver/hw/xfree86/common/xf86AutoConfig.c specifies
"TargetResolution 75Hz" - removing that line from xf86AutoConfig.c causes it to
pick the correct default resolution, but may cause CRT monitors to use a lower
than ideal refresh rate - perhaps this property should only be set by the
autoconfig code when the VESA EDID does not report DFP mode?
Comment 1 Erik Andren 2006-04-04 05:23:23 UTC
Is this still an issue with a current version of xorg?
Comment 2 Alan Coopersmith 2006-04-04 05:54:49 UTC
Yes.   Bug is still present in modular CVS head.
Comment 3 Luc Verhaegen 2006-04-04 06:05:32 UTC
Nobody will die from looking at 60Hz on a CRT. I'd have to look into
xf86AutoConfig.c but maybe that line should just be removed.

Anyone wanting a higher refresh rate for his CRT can always use the conf file or
wait for #5386 to happen (or for further advances in X configuration).
Comment 4 Daniel Stone 2007-02-27 01:23:37 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 5 George - 2007-03-12 08:03:56 UTC
Should be fixed in HEAD.


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.