[i945gm] Screen black with colored noise bars after upgrade from Hardy to Jaunty

[Francis J. Lacoste]

Binary package hint: xorg

After upgrading from Hardy to Jaunty, once I rebooted the screen was trashed (black with some coloured noise bars).

I rebooted and use the 'recover' menu to reset the X configuration. The display is working correctly after that.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: xserver-xorg 1:7.4~5ubuntu17
ProcEnviron:
 LANGUAGE=fr_CA.UTF-8:fr_FR:fr:en_GB:en
 PATH=(custom, user)
 LANG=fr_CA.UTF-8
 LC_MESSAGES=en_CA.UTF-8
 SHELL=/bin/bash
ProcVersion: Linux version 2.6.28-11-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #38-Ubuntu SMP Fri Mar 27 09:00:52 UTC 2009
SourcePackage: xorg
Uname: Linux 2.6.28-11-generic i686

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03)
     Subsystem: Dell Device [1028:01d8]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
     Subsystem: Dell Device [1028:01d8]

[Francis J. Lacoste (flacoste)]

I'm attaching the old xorg.conf.

[Francis J. Lacoste (flacoste)]

Other backup config.

[Francis J. Lacoste (flacoste)]

Last one

[Bryce Harrington (bryce)]

Hi Francis,

Are you able to reproduce the failure if you boot with the old backup?

Also, you attached two old config files, xorg.conf.20090330204509 and xorg.conf.20090330181256. Which of those two was in place when the error occurred?

While obviously we wouldn't want to see the user's system "trashed", at least it sounds like the recovery process worked okay for you.

Also, it is generally recommend that people upgrade from Hardy to Intrepid, and then Intrepid to Jaunty. Testing generally focuses on Distro -> Distro +1 upgrades, and Distro -> Distro + 2 upgrades are not usually supported.

[Francis J. Lacoste (flacoste)]

> Also, it is generally recommend that people upgrade from Hardy to Intrepid,
> and then Intrepid to Jaunty. Testing generally focuses on Distro -> Distro
> +1 upgrades, and Distro -> Distro + 2 upgrades are not usually supported.

I know, but then I just followed the instructions provided on. If that's not
supported, it shouldn't be advertised as the recommended way to ugprade :-)

As to your question, both config fails in slightly different way. The i810
(1st)
driver simply gives a black screen and then dies. The intel (2nd) one gives
the black screen with coloured bars.

I am attaching the Xorg.0.log associated with each files.

[Francis J. Lacoste (flacoste)]

> provided on:

I meant to say provided on http://www.kubuntu.org/news/9.04-beta

[Bryce Harrington (bryce)]

[This is an automatic notification.]

A new major version of the -intel driver is now available in Karmic.

This version includes a major reworking of the acceleration
architecture, which resolves a huge number of issues. We do not know
whether it resolves the issue you reported.

Would you mind testing Karmic Alpha-2 and seeing if it is still a
problem? CD ISO images are available here:

  http://cdimages.ubuntu.com/releases/karmic/

If the issue can still be reproduced on karmic, please report here with
your findings, and attach a fresh Xorg.0.log from your test, and we will
be able to forward the bug upstream.

Otherwise, if the bug no longer exists in Karmic, let us know that as
well.

In the off chance you encounter different bugs while attempting to test
Karmic, please report those as new bug reports.

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

It seems likely to me this bug is gone; the -intel driver has improved immensely in Karmic and a lot of bugs are being reported as no longer present. So hopefully that's the case here too.