Bug#606340: This bug not completely fixed in 2:2.13.0-5
I confirm the issue still exists for
xserver-xorg-video-intel/2:2.13.0-5 for at least one Intel-based
system (32-bit 945GME) but also does not exist for another Intel-based
system (64-bit g33). Both systems had the same monitor (ASUS VH198T).
The 945GME was connected with DVI while the g33 was connected with
VGA. In both cases the other alternative connection (VGA for the
945GME or DVI for the g33) is not available.
For the 945GME the tail of the server log was
(II) Primary Device is: PCI 00@00:02:0
(EE) No devices detected.
Fatal server error:
no screens found
If I downgrade the 945GME system to 2:2.13.0-2, that error message
disappears, and X on that system works normally.
More hardware details for the 945GME that fails with 2:2.13.0-5
but which succeeds with 2:2.13.0-2:
Linux meadowlark 2.6.32-5-686 #1 SMP Wed Jan 12 04:01:41 UTC 2011 i686
GNU/Linux
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME
Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME,
943/940GML Express Integrated Graphics Controller (rev 03)
(This is the 32-bit ASUS Eee box [b202 version] with dvi connection to a
ASUS VH198T LCD monitor. The chipset for this box is identified
everywhere but the Linux space as the 945GSE chipset).
More hardware details for the g33 that succeeds with the 2:2.13.0-5
version of the driver:
Linux raven 2.6.32-5-amd64 #1 SMP Fri Dec 10 15:35:08 UTC 2010 x86_64
GNU/Linux
00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express
Integrated Graphics Controller (rev 02)
00:02.1 Display controller: Intel Corporation 82G33/G31 Express
Integrated Graphics Controller (rev 02)
(This is a 64-bit generic "white box" desktop PC built about 3 years ago with
ASUS P5K-V motherboard with VGA connection to a ASUS VH198T LCD
monitor.)
Both systems are running Debian testing.
When I first got the failure on the 945GME (during the initial Debian
testing install for the system), I compared the log in detail with the
g33 log. The logs were essentially identical until the above error
message occurred for the 945GME. There were no obvious error messages
with similar time stamp in any other file in /var/log. So it seemed
pretty hopeless until I discovered the workaround suggested in this
thread to downgrade (from 2:2.13.0-5 in my case) to 2:2.13.0-2.
For what it is worth, the guy who sold me this used 945GME never had
issues with it on Ubuntu, but I don't know what version of Ubuntu was
the last he tried, or whether this issue (whatever it is) was in his
future if he had hung on to the box and done further Ubuntu upgrades
as time progressed.
I would be happy to send any further data from any of the 945GME
(using 2:2.13.0-2 or 2:2.13.0-5) or g33 (using 2:2.13.0-5) systems to
help track down what the problem is. I am very happy that the
workaround of downgrading to 2:2.13.0-2 makes it possible to use the
945GME system, but obviously that workaround is not a permanent
solution.
Alan
__________________________
Alan W. Irwin
Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).
Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__________________________
Linux-powered Science
__________________________
Reply to: