After updating to latest Maverick 2.6.35-20 X.org does not start anymore

[John Sanders]

I had a maverick install from 10/10/2010 Alpha 3 and although it had a few issues (Alpha!) it was more or less working 99% and was pretty fast (compared to Karmic that I was running on the box prior.)

My computer is an IBM Thinkpad X40 it has an Intel integrated graphics card:

00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)

The problem started this morning, yesterday I did the usual "apt-get update" and "apt-get dist-upgrade" switched the computer off and went to bed.

To my surprise this morning X was not starting any more the error message I get is:

[ 26.893] (EE) intel(0): No kernel modesetting driver detected.
[ 26.893] (II) UnloadModule: "intel"
[ 26.893] (EE) Screen(s) found, but none have a usable configuration.
[ 26.893]
Fatal server error:
[ 26.893] no screens found

I've found that this happens when I boot with the latest kernel; 2.6.35-20-generic, and does not happen with the one from Alpha 3: 2.6.35-19-generic

I tried to disable KMS writing "options i915 modeset=0" on /etc/modprobe.d/i915-kms.conf but it doesn't make any difference.

The only way for me to get a desktop is to boot the "Alpha 3: 2.6.35-19-generic" kernel.

[John Sanders (jpfsanders)]

X.org full Log when the machine can not boot the desktop

[watcheroftheskies (kramermj)]

Same problem: A week ago I installed Maverick Beta 1 on my old Dell Dimension 2400. This was after I had problems with Mint 9 (Lucid based); sytem dies after apr. 10 min and top half of screen with white lines flashing, which is well known it seems, and an Ubuntu Lucid tutorial proposed the Maverick kernel as workaround. So I decided to try maverick beta itself. > Worked perfectly, no problems at all. Maverick remained stable. Shame that the streaming video rendering (after installing restricted) was still so 'choppy'

Tried Mint 9 again, but with kernel 2.6.35 upgrade. > Big problem, X dies after changing just the screensaver.

Today I reinstalled Maverick B1, but with option 'install codecs' and 'update during install'. After install I upgraded by using the upgrade manager as I always do. I noticed a kernel upgrade 2.6.35.20 passing by. After this the boot screen shows a low resolution Ubuntu 'logo' (just text really) then a tty1 login screen. After login I start X manually (startx or X) and this produced exactly the same report.

So: this is really a bug.

[watcheroftheskies (kramermj)]

appendum: I wrote this on a fresh re- reinstall of maverick B1. I won't touch upgrade manager for now. I still have to try a restart....praying...

[John Sanders (jpfsanders)]

Well, In my case as long as I run 2.6.35-19 the system can boot to a decelerated desktop, and I'm only subjected to random X crashes that bring down the whole system every hour or so.

[John Sanders (jpfsanders)]

Good news everyone...

Under Kernel "2.6.35-21-generic #31-Ubuntu SMP Mon Sep 13 22:39:43" The desktop boots again. (Hurrah!)

However still no desktop effects and no nice graphic logo when booting, but compared to the last few previous days this is a great improvement.

[Jim Rees (rees)]

There used to be a working video driver for the Intel 855GM, but since it actually worked, it was removed from Xorg. You now have three choices. You can go with the default, which is fbdev, and suffer crashes every few days. Or you can use the new intel driver, but it doesn't work either. I'm using the vesa driver, which gives you only very simple functionality, no higher resolutions, multiple monitors, effects, acceleration, etc. But at least it doesn't crash nearly as often. You do have to disable kernel mode setting with "nomodeset" on your kernel options.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 635047

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]