http://bugs.freedesktop.org/show_bug.cgi?id=22853
Alex Deucher <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Driver/Radeon |Server/general --- Comment #6 from Alex Deucher <[email protected]> 2009-07-21 07:01:52 PST --- (In reply to comment #5) > Well: > - according to its specs, Acer 77e can do 1280x1...@67hz > - 1280x1024 did was supported with the SiS driver with this Acer > The monitor's edid does not contain an modeline for 1280x1...@67hz, as such you'd need to add a modeline to use it. The edid does contain a a 1280x1...@75hz mode, however it conflicts with the max pixclock specified in the same edid. So either the max pixclock is wrong or the the 1280x1...@75hz mode shouldn't be there. If the 1280x1...@75hz mode does work, then an edid quirk needs to be added to the xserver. > AFAIC, there's two bugs in ati driver: > - when a mode is not supported, it should be written down in > the logs, thus it's easier to understand the issues This is handled by the common randr code in the xserver, not the driver. If you enable more verbose server logging you can see which modes get rejected and why. > - we should select alesser refresh frequency when the suggested > one is too high. > You'll need to specify an modeline if you want to use a mode that's not in the monitor's edid. It's not really feasible to add every possible mode to the output there are just too many possibilities. Plus, most monitors (especially LCDs) are very picky about what mode timings they will accept. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ xorg-driver-ati mailing list [email protected] http://lists.x.org/mailman/listinfo/xorg-driver-ati
