Subject : [REGRESSION] [2.6.39-rc3] Wrong resolution in framebuffer and X Window
Submitter : Maciej Rutecki <firstname.lastname@example.org>
Date : 2011-04-17 16:04
Message-ID : email@example.com
References : http://marc.info/?l=linux-fbdev&m=130305625114863&w=2
This entry is being used for tracking a regression from 2.6.38. Please don't
close it until the problem is fixed in the mainline.
Still present in -rc5
Still present in -rc6
Still present in -rc7.
Still unresolved and present in 2.6.39.
Still cannot use kernel newer than 2.6.38. That any kernel (intel) developer can say how resolve this? This bug has been over a month, and still has the status of "new".
Your monitor doesn't supply a valid EDID. Attach an Xorg.log+dmesg from a working kernel so that I can see why it might have been judged invalid.
Created attachment 60872 [details]
dmesg from 2.6.38
Created attachment 60882 [details]
Xorg.log from 2.6.38
Result of bisection:
8f9a3f9b63b8cd3f03be9dc53533f90bd4120e5f is the first bad commit
Author: Chris Wilson <firstname.lastname@example.org>
Date: Tue Feb 1 09:01:13 2011 +0000
drm/i915: Enable GMBUS for post-gen2 chipsets
With the recent SDVO fix, this is working on all the machines I have to
hand - except for an 845G.
Signed-off-by: Chris Wilson <email@example.com>
:040000 040000 eb835ca9bf353d1d548b69d415801720a577184a 3e0a9430c43030735dfe2f694a1ad694cc01d483 M drivers
Revert this commit from 3.0-rc1 solves problem.
Tested 3.0-rc4 (changelog shows that this commit has been reverted): work fine. Close bug.