[Bug 18370] Monitor refresh rate not set correctly

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Nov 7 06:47:36 PST 2008


http://bugs.freedesktop.org/show_bug.cgi?id=18370


Alex Deucher <agd5f at yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |NOTABUG




--- Comment #8 from Alex Deucher <agd5f at yahoo.com>  2008-11-07 06:47:36 PST ---
(In reply to comment #7)
> Thanks a lot, it is now working. I can not more use CTRL-ALT"+" and -"-" to
> change resolution, but I can live with that. That point was, that I had to
> comment out the Option "NoDDC" in the Device section for my driver. It seems
> that this entry was blocking the EDID information from my monitor, but DDC was
> used anyways. The EDID is now reported by xrandr. I did also delete the
> HorizSync and VertRefresh entries and the Modelines completely (not required to
> delete, but also not more necessary).

I'm not sure I follow why you want to block DDC.  DDC is the method by which
the EDID from your monitor is obtained. The "NoDDC" option works as expected
which is why the driver was not able to get an EDID for your monitor.

> 
> Still I don't understand, that the prefeered mode as shown by xrandr ist not
> generally used after resolution changes, for example from a game, without the
> EDID information. The preferred mode got only used at X startup. See below:

This sounds like a bug in the xserver, not the driver.  The driver just does
what the xserver tells it to do.

> I think, this should be fixed and I would also suggest to implement a way to
> turn of DDC completely.

That's what "NoDDC" does.  You said it yourself, with "NoDDC" in your config
DDC didn't happen and the driver was not able to get an EDID from your monitor.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the xorg-driver-ati mailing list