© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
(In reply to comment #18)
> Ok, I will try that. I'm simply surprised that a section like
>
> Section "Screen"
> Identifier "Screen0"
> Device "Videocard0"
> DefaultDepth 24
> SubSection "Display"
> Viewport 0 0
> Depth 24
> Modes "1400x1050"
> EndSubSection
> EndSection
>
> doesn't work anymore. All this EDID/xrandr magic is certainly great but when
> the user decides to overrule this autodetection stuff [following standard
> xorg.conf conventions], one would expect his choices to be honoured.
thus is the price of progress. In the randr world the xorg.conf changes a bit as the screen section no longer maps to a single monitor. While on a card like yours with a single crtc and output it's easy to wonder why the mode listed there doesn't get added, but consider a card with a local LVDS panel, a DVI port, a VGA port, and a TV out port. Which output should be mode get added to? all of them? what if your laptop panel only supports 1024x768? Also when you say 1400x1050 what mode exactly do you mean 1400x1050@60Hz? 1400x10505@85Hz? 72Hz? With randr you can assign hardcoded/
Section "Device"
Identifier "My Radeon"
Driver "ati"
Option "Monitor-VGA-0" "My Monitor"
EndSection
Section "Monitor"
Identifier "My Monitor"
...
EndSection
within the monitor section you can specify new modelines you want to use as well as specify the orientation of the monitor in relation to the other monitors driven by the same card (in the case of dualhead cards). Unfortunately, I think there are still some issues to be worked out with this method in the xserver. See this page for more:
http://