[i845G] xserver locks up

[blazerw]

Binary package hint: xserver-xorg-video-intel

Basically, installation of the Intel driver is done using the basic empty xorg.conf file. However, for the 845G, X cannot start this way on Ubuntu. Adding any of the following options to xorg.conf will make it work:
Option "DRI" "false"
Option "EXANoComposite" "true"
Option "NoAccel" "true"

NoAccel to true seems like it will absolutely, always work, but produces a very sluggish X.
DRI to false seems to always work, but I can't be as confident in it as NoAccel. Nice and Snappy X.
EXANoComposite to true "worksforme", but I've seen references to it not working. It produces an X desktop that is indistinguishable from DRI to false.

When installing Ubuntu Jaunty and an Intel 845G (reported as "Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device rev 3") is detected, the installation should add one of the above xorg.conf options.

I will include xorg.conf (note it has many options in it that are remarked out).
I will include Xorg.0.log.bad (for a crashed session).
I will include Xorg.0.log.good (for a good session using 'Option "EXANoComposite" "true"')

Release:
Description: Ubuntu jaunty (development branch)
Release: 9.04

Package Versions:
xserver-xorg-video-intel: 2:2.5.1-1ubuntu7
xserver-xorg: 1:7.4-5ubuntu10
FYI: X.org X Server 1.5.99.3

[blazerw (randy-1702)]

Xorg.0.log.bad is the log for x session that crashes using the above xorg.conf (or an empty one).

[blazerw (randy-1702)]

Xorg.0.log.good is the log for an X session that works using the 'Option "EXANoComposite" "true"'.

[Geir Ove Myhr (gomyhr)]

Thank you for reporting this bug and helping make ubuntu better. We will need some more information from you regarding this problem.
1. Could you please include the output of `lspci -vvnn` (`lspci -vvnn >lspci-vvnn.txt` on the command line will make a file that you can upload)
2. I don't see any signs of a crash in the file "Xorg.0.log file for a crashed X" (often we would see a backtrace in this file). This means that we will need a more elaborate description of the crash.
- What exactly happens? Do you see a black screen or random garbage instead of the login screen? If you still try to log in (blindly), do you hear the login sound?
- Does CapsLock turn the corresponding keyboard LED on and off?
- Does Ctrl+Alt+F2 give you a text terminal? If it does, do you see anything (even briefly) if you press Ctrl+Alt+F7?
- Does Ctrl+Alt+Backspace do anything when you have the following lines to the end of xorg.conf?
Section "ServerFlags"
       Option "DontZap" "no"
EndSection

[Randy Wilson (blazerw)]

Used sudo because without it, there were some lines relating to access denied.

[Randy Wilson (blazerw)]

The "crash" is X only. The GDM screen displays (perfectly, no garbage) and then usually that's it. I have, once or twice, been able to type the first character of my username. That's it. No more keyboard response. I can't switch to a terminal using Ctrl+Alt+F2 (or any other). I can't kill X with Ctrl+Alt+Backspace. I have not tried 'Option "DontZap" "no"'.

I can ssh in IF the laptop is connected via Ethernet (wireless doesn't get an address until you log in). From SSH I can reboot. Restarting X using '/etc/init.d/gdm restart' doesn't kill the locked X server.

I'll restart one more time with adding DontZap and remarking the EXANoComposite line to test Ctrl+Alt+Backspace and the *-Lock keys.

[Randy Wilson (blazerw)]

First, note about my previous comment. I CAN move the mouse. Clicking does nothing, but the cursor moves.

I restarted with the options as mentioned above (default settings except for DontZap). I did this twice. Both times I was able to type one key before the lockup. The first time I just typed a character. Pretty boring. The second time, I did the Ctrl+Alt+Backspace. This restarted GDM (which might mean it restarted X). It was locked up when it came back. Perfect GDM screen, no garbage. Couldn't type a thing. Still could move the mouse, no clicks registered. Also, the Caps Lock and Num Lock keys did not toggle the appropriate lights.

One point I thought I'd make. This bug was created so that the Ubuntu installer might set an option during setup so users with Intel 845g chips would get a working install. Not necessarily about fixing the underlying problem with the driver. Although that is a worthy goal. The issue may be fixed in Intel's 2.6.0 release of the driver. I couldn't try it because the build requires a version of lbdrm that is not available in Jaunty. It is available in Debian Experimental, but I wasn't THAT motivated to compile 2.6.0.

[Geir Ove Myhr (gomyhr)]

About your suggested solution: I don't think the Ubuntu installer nowadays sets anything in xorg.conf during installation. Therefore, it would probably involve a lot of extra work to fix this specific problem in that way. I think there are other ways to blacklist features or set default options for specific cards. Moreover, to do that one needs to be sure that this is a general problem that applies to all users with this chipset. From bug 304871 it seems that most people with 845G don't experience your problem (that bug report describes a different problem). Finally, the Ubuntu developers will have to decide what is the best way to resolve a bug, given all the available information. They know better how Ubuntu works on the inside.

SInce you can log in with ssh (when on ethernet) after the crash, it means the kernel does not crash, but you may still take a look in /var/log/kern.log if there are any messages from the time of the crash.

You've done a pretty good job in providing lots of useful information, so a developer should be able to have a look at it. I'm setting the status to confirmed.

PS: It is possible to test the latest git source code without compiling it yourself. See https://launchpad.net/~xorg-edgers/+archive .

[Randy Wilson (blazerw)]

It'd probably be worth checking to see if the installer can do something for Intel 845G's IF Jaunty goes out with the 2.5.x version of the driver. However, with the 2.6.x driver it seems to work great. I've had one blank screen, but that was when I switched to UXA and just logged out. After a reboot, using UXA has been error free in an entire 15 minutes of use.
I also got desktop effects to work. The intel 845G is blacklisted in /usr/bin/compiz. I remarked out the line for the 845's blacklisting. The blacklist is there because of bug 259385.

If any other information is needed, I'll provide it.

FYI:
I added the sources for the xorg-edgers that provides packages based closely on the current GIT repository. I upgraded the packages, deleted my xorg.conf file (well moved it) and rebooted. X configured everything perfectly. I don't recommend this for folks that can't have a bricked box. However, it did work for me.

[Geir Ove Myhr (gomyhr)]

It looks like Jaunty will be shipped with 2.6.x. Package version 2:2.6.1-1ubuntu1 just hit the respositories...

[Geir Ove Myhr (gomyhr)]

Since 2:2.6.1-1ubuntu1 is now in jaunty and seems to be working well, I'm closing this bug. Thank you for reporting it.