Summary: | Invalid resolution being selected on ATI Radeon 9200 SE RV280 | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Bryce Harrington <bryce> | ||||||||||||
Component: | Server/General | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> | ||||||||||||
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||||||||
Severity: | major | ||||||||||||||
Priority: | high | CC: | freedesktopbugzilla | ||||||||||||
Version: | 7.4 (2008.09) | ||||||||||||||
Hardware: | All | ||||||||||||||
OS: | Linux (All) | ||||||||||||||
URL: | https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/274290 | ||||||||||||||
Whiteboard: | |||||||||||||||
i915 platform: | i915 features: | ||||||||||||||
Attachments: |
|
Description
Bryce Harrington
2008-11-12 19:44:45 UTC
Created attachment 20275 [details]
Xorg.0.log.old
This is a "bug" in the randr code in the xserver. Your monitor's edid does not specify a preferred mode and the xserver picks 1400x1050 based on the sync ranges. We should probably patch the xserver to only pick modes from the edid by default at least on digital monitors. Created attachment 20280 [details] [review] untested fix This patch should do the right thing. Created attachment 20284 [details] [review] randr-target-exact-harder.patch I think xf86TargetExact should just try harder when there's only one monitor attached. I'd still be in favor of not adding the default modes if the monitor doesn't claim to be continuous-frequency, but I think this patch is correct on its own. Created attachment 20285 [details] [review] untested fix This patch only added the default modes if the GTF bit is set in the edid. Pushed! c232f3d673fb00d7fceb8e82741349d64e5ac0ad 81fd17f5f49cdd2c10d0bf3b7ddeb8b5953886a5 although it certainly looks correct to me, it caused the loss of all VESA modes that can be quite useful: https://bugs.freedesktop.org/show_bug.cgi?id=19203 danny |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.