[Bug 3731] Re: Xorg resolution falling back to 640x480 and/or 800x600when h/v freqs incorrect
alacrityathome at sbcglobal.net
Fri Sep 28 17:13:14 UTC 2007
Nice progress, Bryce.
Yes, for me on Tribe 5 and on safe video (otherwise, I get a blank screen),
I get edidfail for the ddcprobe command.....so, I am one of the lucky ones.
By the way, is there a new web site for bug 3731? My old bookmarks for bug
3731 have disappeared.
From: bounces at canonical.com [mailto:bounces at canonical.com] On Behalf Of
Sent: Friday, September 28, 2007 1:26 AM
To: alacrityathome at sbcglobal.net
Subject: [Bug 3731] Re: Xorg resolution falling back to 640x480 and/or
800x600when h/v freqs incorrect
I'm just surfacing to report some progress made on resolution detection
for Gutsy. We've found a fix for a sub-class of this bug, for
situations involving LCDs with "analog" connections (I assume this is
VGA connections as opposed to DVI) where the highest (and most correct)
resolution gets lost. This is bug 27667 and is due to poor logic in
xresprobe/ddcprobe.sh that mixes up CRTs and LCDs. The logic is being
dropped, which will fix this bug. There were also a couple other
logical errors which may have caused other related monitor resolution
144956 also has a fix; it addresses an issue that cropped up after Tribe
5 for intel users that resulted in misdetected resolutions for some.
This was caused by a patch added in Tribe 5. The patch will be dropped
to fix the issue.
For others experiencing this problem, a couple tips: run ddcprobe to
see if it reports a series of timings for your monitor. If it instead
returns "edidfail", you're seeing bug 94994. If it returns a correct
list of resolutions, but the highest one is missing, and you're using an
LCD, then you're seeing bug 27667. For everyone else, stay tuned...
Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs
You received this bug notification because you are a direct subscriber
of the bug.
Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect
You received this bug notification because you are a member of Kubuntu
Team, which is a subscriber of a duplicate bug.
More information about the kubuntu-bugs