855GM not changing resolutions for games
Wayne Smith
tuxrocks at cox.net
Sat Jan 21 11:36:18 PST 2006
On Saturday 21 January 2006 4:24 am, Alan Hourihane wrote:
> On Fri, 2006-01-20 at 20:16 -0600, Wayne Smith wrote:
> > On Friday 20 January 2006 4:08 pm, Alan Hourihane wrote:
> > > Does adding
> > >
> > > Option "NoDDC"
> > >
> > > to your Device Section fix it ?
> > >
> > > Alan.
> >
> > Unfortunately, no. I discovered that option (byproduct of solving
> > problems ;) ) and tried setting it to "true", but the module (ddc) is
> > still loaded, and the error message persists.
> >
> > Thanks for the idea, though. Keep 'em comin...
>
> Can you attach a log with that specified so I can see what's going on.
>
> Alan.
Okay, maybe it was because I tried so many different things yesterday, but I
passed the option "NoDDC" today, and it eliminates the error. However, it
still uses a range that I do NOT specifiy, the one that it used when it
kicked the error, 45.71-50.33. It then says that it will only use the
"built-in" modes of 1280x800 and 1024x768. The video bios still shows the
other, desired modes when using 855resolution and 915 resolution.
Now the odd thing is that when I use 6.8.2, the HorizSync gets set to the
range I specify (30-50), and then kicks 1280x800 out because it doesn't fall
into that range. When I run 6.8.2 w/o specifying the HorizSync, then it says
it's using the "default" range of 28-33, and includes all desired modes
(1280x800, 1024x768, 800x600, and 640x480).
I think the real issue is why my HorizSync does not seem to be honored in 6.9
like it is in 6.8.2, and why Xorg is defaulting to the much higher hsync
range in 6.9.
xorg.conf: http://staff.norman.k12.ok.us/~wsmith/xorg.conf
xorg log: http://staff.norman.k12.ok.us/~wsmith/Xorg.0.log
Thanks,
Wayne
More information about the xorg
mailing list