kms howto - is there one?
Adam Williamson
awilliam at redhat.com
Fri Mar 19 07:12:52 UTC 2010
On Fri, 2010-03-19 at 02:49 -0400, Felix Miata wrote:
> FWIW, I do now have the 845G with F13 running 2048x1536, but the amount of
> work required to set it up is just nuts compared to how automatic it was
> before auto configuration development "progressed" up to now. The xorg.conf
> and Xorg.0.log resulting:
> http://fm.no-ip.com/tmp/Linux/Xorg/xorg.conf.08-t2240-i845G-f13-2048x1536x144x24bpp-withxorgconf
> http://fm.no-ip.com/tmp/Linux/Xorg/xorg.0.log-t2240-i845G-f13-2048x1536x144x24bpp-withxorgconfgmodelines
Erm. There's exactly three lines in there that are actually necessary
for what you're doing:
Modeline "2048x1536_60.00" 267.25 2048 2208 2424 2800 1536 1539 1543 1592 -hsync +vsync
HorizSync 30-107
Modes "2048x1536" "1920x1440" "1856x1392" "1792x1344" "1600x1200" "1400x1050" "1280x960" "1152x864" "1024x768"
The rest are commented out or irrelevant. In fact, even the Modes line
may not be necessary, looking at the X log.
(Although I note "VertRefresh 56-61" - don't you get headaches?!)
This would not be a problem on any monitor which correctly communicates
its correct HorizSync range to the system. In the case where the monitor
doesn't have functioning EDID or DDC, *every* choice X can make is
'wrong' in some sense, so it doesn't make much sense to complain about
the particular wrongness of the particular choice we go with.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
More information about the test
mailing list