[i945] Issues with the xserver-xorg-video-intel[?] on an Intel Mobile 945GME.

[sitronen]

When I start my eeePc 1000H with kernel 2.6.31-11-generic, compiz won't work and start.
Starting in the terminal, there's said that there is another software rasterizer.
Further, the screen is sometimes going black - even stays so after restarting the XServer, it stays until rebooting the hole system. Perhaps it is turned off?
On kernel 2.6.31-10-generic, there are no problems.

release: Ubuntu Karmic 9.10 development branch
Kernel: 2.6.31-11-generic
Xserver-xorg-video-intel: 2:2.8.1ubuntu-2
compiz: 1:0.8.3+git20090917-0ubuntu4 0
Intel Corporation Mobile 945GME (rev03)
System: Asus eeePC 1000h

[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03)
     Subsystem: ASUSTeK Computer Inc. Device [1043:8340]

[Philip Muškovac (yofel)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:

apport-collect 442197

This will help us to find and resolve the problem. Bear in mind that you may need to install the python-launchpadlib package from the universe repository. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report. Thanks in advance!

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Philip Muškovac (yofel)]

Note: please run the command after booting with 2.6.31-11-generic

[László Torma (tormalaszlo)]

I think I had the same issue on my Asus Eee PC 701.
I filed a bugreport under linux because downgrading to the previous kernel solved the issue:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/441577

So these bugs may be duplicates of each other...

[László Torma (tormalaszlo)]

An another possible duplicate of this bug (with more info):
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/442256

[sitronen (peter-ullinger-deactivatedaccount)]

Architecture: i386
DistroRelease: Ubuntu 9.10
MachineType: ASUSTeK Computer INC. 1000H
Package: xserver-xorg-video-intel 2:2.8.1-1ubuntu2
PackageArchitecture: i386
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-11-generic root=UUID=1830164f-444f-4afe-bd30-f7d7627b1b11 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=de_DE.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu5
 libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu7
 libdrm2 2.4.13-1ubuntu1
 xserver-xorg-video-intel 2:2.8.1-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu2
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
dmi.bios.date: 07/21/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2102
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1000H
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2102:bd07/21/2009:svnASUSTeKComputerINC.:pn1000H:pvrx.x:rvnASUSTeKComputerINC.:rn1000H:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 1000H
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-11-generic

[Pres-Gas (presgas)]

I have a Dell Lattitude 2100 with similar issues (Intel Mobile 945GME Express). Would you like to add my apport data as well? I do not want to add needless data if you do not need it.

[Pres-Gas (presgas)]

Installed 2.6.31-11-386 kernel and graphics seem fine from package version 2.6.31.11.8. Booting back to the generic kernel (version 2.6.31.11.22 has issues above.

[Johannes Frank (jmfrank)]

Architecture: i386
CheckboxSubmission: cbbc77c8a1946ce5742eb67db7065c9a
CheckboxSystem: 4189098363a6ad0365cb1899f85542bb
DistroRelease: Ubuntu 9.10
MachineType: ASUSTeK Computer INC. 1000H
Package: xserver-xorg-video-intel 2:2.9.0~git20091007.03e8e64f-0ubuntu0tormod3
PackageArchitecture: i386
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-12-generic root=UUID=7f47d654-fec9-4827-b743-3e54586a3b8c ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 LANGUAGE=de_DE:de:en_GB:en
ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu5
 libgl1-mesa-glx 7.7.0~git20091007.0083d2e4-0ubuntu0tormod
 libdrm2 2.4.14+git20091007.3a7dfcdf-0ubuntu0tormod
 xserver-xorg-video-intel 2:2.9.0~git20091007.03e8e64f-0ubuntu0tormod3
 xserver-xorg-video-ati 1:6.12.99+git20091007.e59ae082-0ubuntu0tormod
Tags: ubuntu-unr
Uname: Linux 2.6.31-12-generic i686
UserGroups:

XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
Xrandr: Error: command ['xrandr', '--verbose'] failed with exit code 1: Can't open display
dmi.bios.date: 12/30/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1305
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1000H
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1305:bd12/30/2008:svnASUSTeKComputerINC.:pn1000H:pvrx.x:rvnASUSTeKComputerINC.:rn1000H:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 1000H
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
fglrx: Not loaded
glxinfo: Error: command ['glxinfo'] failed with exit code 255: Error: unable to open display
setxkbmap: Error: command ['setxkbmap', '-print'] failed with exit code 255: Cannot open display "default display"
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-12-generic
xdpyinfo: Error: command ['xdpyinfo'] failed with exit code 1: xdpyinfo: unable to open display "".
xkbcomp:
 Error: command ['xkbcomp', ':0', '-w0', '-'] failed with exit code 1: Error: Cannot open display ":0"
                   Exiting

[Johannes Frank (jmfrank)]

Well since this morning I am unable to start X. I have an asus eeepc 1000H and the only way to get this information is to ssh into.
The screen goes blank, and Ctrl-Alt-Fx doesn't work anymore.
I used standard supplied ubuntu as well as xorg edgers X server but no difference.
I hope my information i usable.

[Jonathan Thomas (echidnaman)]

From the /var/log/Xorg.0.log.old, it looks like DRM failed to become master. I'm experiencing a similar problem where a software rasterizer kicks in (making everything very slow) at bug 446641.

[Johannes Frank (jmfrank)]

Well, I know don't be impationed, but I got no X on an eeepc for three days now. I don't expect a fix right now, but importance undecided is maybe a littlebit misplaced. I will be glad to help you in tracing down this bug.
But I also would appreciate seeing this bug as critical. I got no X on a portable device, have to plug in a cable and ssh into my portable to have access at all. This is a mega show stopper, don't you think?

[Johannes Frank (jmfrank)]

Hmm, I was impationed, and did a reinstall. And, the problem vanished. So this might have probably been related to the fact, I ran karmic for four month now. (Yes it was usable all the time, except for the last three days.) So I withdraw my request for critical, as the problem is very like to be unique to me.

[sitronen (peter-ullinger-deactivatedaccount)]

Problem seems to be solved with kernel.12. I don't have any problems at the monent.

[Pres-Gas (presgas)]

My issues seem to be fixed as well. I vote this get at least turned into a question...or just fixed.

[Geir Ove Myhr (gomyhr)]

Since the original reporter has reported that this is fixed (a long time ago), I'm closing this bug report.