lshw garbles display

[Daniel Hermansson]

Binary package hint: xorg

When i run sudo lshw it garbles my display. It's an Intel 945 GME graphics chip.

From a duplicated bug:
"The screen gets corrupted and it seems unrecoverable.
Ctrl+Alt+F1, Ctrl+Alt+F7 does not help.
Ctrl+Alt+F1, Ctrl+Alt+F8, Ctrl+Alt+F7 does help, but it makes the computer sleep a few seconds after."

ProblemType: Bug
Architecture: i386
Date: Sat Feb 27 13:46:49 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
Package: xorg 1:7.5+1ubuntu9
ProcEnviron:
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic-pae
SourcePackage: xorg
Uname: Linux 2.6.32-14-generic-pae i686

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GME Express Memory Controller Hub [8086:27ac] (rev 03)
     Subsystem: Acer Incorporated [ALI] Device [1025:015b]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03)
     Subsystem: Acer Incorporated [ALI] Device [1025:015b]

[Daniel Hermansson (daniel.h)]

Switching back to console and back fixes this untill i run lshw again.

[Bryce Harrington (bryce)]

Hi r-launchpad-allyourba-se,

Thanks for including the attached files. Could you also include your /var/log/Xorg.0.log (or Xorg.0.log.old) from after reproducing the issue?

Please attach the output of `lspci -vvnn` too.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Bryce Harrington (bryce)]

[This is an automatic notification.]

Thanks for reporting this bug to help making the Intel graphics driver
better. We hear from upstream that a number of bugs (possibly including
this one) have been fixed in the newer DRM code from the 2.6.33 kernel.
I don't know if your bug is one of the ones fixed in this release,
though, but we've prepared a PPA with this DRM update. Would you mind
installing this, rebooting, and testing if the original issue can be
reproduced with it or not?

The DRM PPA is here:

    https://edge.launchpad.net/~apw/+archive/red

Note there could be new bugs... please file these as new reports using
the command 'ubuntu-bug linux' (for kernel or DRM or KMS bugs) or
'ubuntu-bug xorg' if you suspect them to be X.org issues.

[GeorgeVita (8-launchpad-mhnyma-com)]

Also discussed and confirmed at: http://ubuntuforums.org/showthread.php?t=1372697
Some more issues (similar?) described there.

A possible point tocheck noticed by user davidryderuk (post#27):
'I have the same problem on my eeepc 1000 when running the lucid beta off a LiveUSB stick. However I do not get the problem if I boot using the "nomodeset" boot parameter.'

Regards,
George

[Robert Hooker (sarvatt)]

Ok, after finding one of the dupes that was having this issue on the same machine I'm using where I couldn't reproduce it I looked into it a bit more. It looks like having vga16fb loaded (which I had blacklisted) is what's causing the problem and I can reproduce it on a livecd.

[Bryce Harrington (bryce)]

On Tue, Mar 23, 2010 at 11:15:26PM -0000, Robert Hooker wrote:
> Ok, after finding one of the dupes that was having this issue on the
> same machine I'm using where I couldn't reproduce it I looked into it a
> bit more. It looks like having vga16fb loaded (which I had blacklisted)
> is what's causing the problem and I can reproduce it on a livecd.

From IRC discussion...

vga16fb was added to the kernel in november or december for plymouth.
But it doesn't interact well with KMS, so results in errors like this.

Could make lshw ignore vga16fb when drmfb is present... or could force
vga16fb fail to load when there is a real framebuffer...