Bug 13151 - PreferredMode ignored on startup
Summary: PreferredMode ignored on startup
Status: RESOLVED DUPLICATE of bug 10625
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 7.3 (2007.09)
Hardware: x86 (IA32) FreeBSD
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-08 14:12 UTC by Kevin Dorne
Modified: 2007-11-08 14:42 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
xorg.conf (2.14 KB, text/plain)
2007-11-08 14:12 UTC, Kevin Dorne
no flags Details
Xorg.0.log (45.86 KB, text/plain)
2007-11-08 14:13 UTC, Kevin Dorne
no flags Details
xrandr output (733 bytes, text/plain)
2007-11-08 14:14 UTC, Kevin Dorne
no flags Details

Description Kevin Dorne 2007-11-08 14:12:12 UTC
I have an HP/Compaq nx8220 laptop with native resolution 1680x1050, with external Philips 170s monitor on the VGA port, 1280x1024.

When I start X, the initial resolution for the laptop panel is set to 1024x768, with the the external monitor at 1280x1024.  This happens despite an entry in the Monitor section with a PreferredMode of 1680x1050, and despite a detected native panel resolution of 1680x1050.

I can set the resolution after X starts up using xrandr, but can't get it to start  in the desired modes.
Comment 1 Kevin Dorne 2007-11-08 14:12:46 UTC
Created attachment 12410 [details]
xorg.conf
Comment 2 Kevin Dorne 2007-11-08 14:13:33 UTC
Created attachment 12411 [details]
Xorg.0.log
Comment 3 Kevin Dorne 2007-11-08 14:14:37 UTC
Created attachment 12412 [details]
xrandr output
Comment 4 Brice Goglin 2007-11-08 14:18:51 UTC
Looks like my bug #10625, already fixed in git.
Comment 5 Kevin Dorne 2007-11-08 14:42:47 UTC
The patch worked -- this is a duplicate.  Thanks!

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


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.