Bug 16065 - 6.8.0 ati driver doesn't honnor aymore resolution specified in xorg.conf
Summary: 6.8.0 ati driver doesn't honnor aymore resolution specified in xorg.conf
Status: RESOLVED DUPLICATE of bug 16063
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 7.2 (2007.02)
Hardware: Other All
: medium major
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-22 07:52 UTC by Thierry Vignaud
Modified: 2008-05-22 09:28 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
xorg log without the new options (684.04 KB, text/plain)
2008-05-22 07:54 UTC, Thierry Vignaud
no flags Details

Description Thierry Vignaud 2008-05-22 07:52:35 UTC
Latest 6.8.0 ati driver doesn't honnor resolution specified in /etc/X11/xorg.conf unlike previous 6.6.x versions.

On a flat panel, this is especially bad since not using native resolution results in unoptimal display (zomm).

I'd to add the following options to make it use the native resolution:

    Option "Monitor-VGA" "monitor1"
    Option "PreferredMode"  "1280x1024"

Maybe linked to that issue, xrandr only list the current working resolution instead of all possible resolutions  (see Bug #16063).

See https://bugs.freedesktop.org/attachment.cgi?id=16683 for xorg.conf and https://bugs.freedesktop.org/attachment.cgi?id=16685 for xorg.log with the above options.
Comment 1 Thierry Vignaud 2008-05-22 07:54:29 UTC
Created attachment 16689 [details]
xorg log without the new options

Note that "interestingly", when not using the native resolution of my flat panel, the xorg server segfaults when using mplayer (but gracefully handle the error by killing the client)
Comment 2 Thierry Vignaud 2008-05-22 07:58:09 UTC
You can find stack traces of the segfault which happens in VidModeGetCurrentModeline() at https://qa.mandriva.com/show_bug.cgi?id=40959
Comment 3 Thierry Vignaud 2008-05-22 09:14:48 UTC
I opened a bug report for the segfault at
https://bugs.freedesktop.org/show_bug.cgi?id=16067
Comment 4 Alex Deucher 2008-05-22 09:28:11 UTC
This is the same issue as bug 16063.  The root cause is that DDC is not reliable on XPRESS chips so it's nearly impossible to tell what outputs are connected.

*** This bug has been marked as a duplicate of bug 16063 ***


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.