Re: Modeline behavior changed (broken)?

On Wed, 16 Feb 2005, David Dawes wrote:

> On Wed, Feb 16, 2005 at 06:07:43PM -0800, Mark Vojkovich wrote:
> >   It used to be that if you specified a modeline, say "1600x1200" in
> >the XF86Config file, that modeline would take preference over any
> >internal modelines of the same name.  This no longer appears to be
> >the case.  If I have a "1600x1200" modeline in the XF86Config file,
> >it no longer gets used, but another mode instead (I presume the
> >internal mode).  I have to name my mode to something else in order
> >to use it.
> >
> >   It seems like the server was changed to ignore modes placed
> >in the monitor section if they conflict with internal modes.  Was
> >this change intentional?
>
> It works correctly for me.  If explicitly provided modes are not
> overriding the default modes then it is a bug.  Can you send your
> log file?

   It appears that what's happening is modes from the monitor's
edid take precedence over Section "Monitor" overrides.  I specified
mode "1600x1200" in my SubSection "Display" Modes.  I provided a custom
modeline in the Section "Monitor":

# 1600x1200 @ 79.1 Hz, 98.9 kHz
   Modeline  "1600x1200" 213.6 1600 1664 1856 2160 1200 1201 1204 1250

but the monitor is reporting 86 Hz, 106 kHz.

(**) NV(0): *Preferred EDID mode "1600x1200": 230.0 MHz, 106.5 kHz, 85.2 Hz

  ...

(**) NV(0):  Mode "1600x1200": 213.6 MHz, 98.9 kHz, 79.1 Hz
(II) NV(0): Modeline "1600x1200"  213.60  1600 1664 1856 2160  1200 1201 1204 1250

   I think the priority should be:  Section "Monitor", EDID, builtin.
But it appears that it's EDID, Section "Monitor", builtin.


			Mark.