[Intel-gfx] Intel 965 and Custom Resolutions

[Nasa]

> ----- "Lucas" <lucas at dmglobal.net> wrote:
> 
> > Okay,
> > 
> > So I used xrandr to add my modeline but  X just shows half a screen
> > and then restarts.  When I use CVT to create Modelines they all
> fail. 
> > 
> > 
> > The modeline from my xorg.conf file works perfectly on an NVidia
> > machine, what would the difference be?
> > 
> Lucas,
> 
> Did you look at the link given below?
>  
> "Did you miss
> http://lists.freedesktop.org/archives/intel-gfx/2010-August/007917.html
> or
> didn't it help any?"
> 
> And yes Felix it was of great help!!
Damn,

My excitement was so short lived....  Yes, creating monitor sections in the 
xorg.conf.d directory does get read by the drivers -- certain items are still
ignored.  My 10-monitor.conf file has two monitor section (btw: doing this 
from memory as I am now at work).  One for the VGA screen, which I am using, and 
one for LVDS, which I am not.  The LVDS monitor section just has an option to
have it ignored and that work perfectly (doesn't even show up when I use
xrandr).  The VGA section has Vertical Refresh rate defined, a couple of modelines
I created with CVT, and a preferred resolution option.  By default X starts up
my screen at 1024x768.  If I set the preferred option to a *known* resolution, 
that resolution is now set when X starts (yeah).  However, *known* resolutions are
ones X finds itself and modelines that fit into default parmaters defined by X.  
Remember, my monitor doesn't provide EDID and/or DDC info.  What about the option for
Vertical Refresh?  X logs don't show anything about that line -- at all.  There is 
a section of the log that goes through the options from the monitor section, including
the modelines (this is where it will say the resolution is being ignored because of what
ever reason).  The Vertical Refresh rate line isn't shown; no error message, no warning
message, and nothing stating what refresh rates it is using.  

BTW: some of the modelines were ignored due to Horizontal Sync, which CVT doesn't seem to 
have a way to account for.

So the xrandr option maybe the only way to go to get what ever resolution you actually need.
Or did I still miss something?

Nasa