[i945gm] major screen corruption on X start with modesetting

[Mike Kaplinskiy]

Binary package hint: xserver-xorg-video-intel

When starting on the newest kernel on karmic (-14), everything goes well until X begins to start. First I see a blinking cursor, which then freezes (as is usual, I assume that's when X tries to start), then the screen turns blank.

After a little while, the blinking cursor comes back, freezes again (I assume X failed to start and is trying vesa mode), and majorly corrupts the screen. then X either starts (with only a cursor, 6 copies of it, all with stripes on them), or it doesn't and the console only shows a cursor which is shown in 2 places. Everything except the screen works fine (Alt+E restarts X, doesn't change the situation).

Booting with i915.modeset=0 is the only way to get into the system.

ProblemType: Bug
Architecture: i386
Date: Thu Oct 29 12:38:13 2009
DistroRelease: Ubuntu 9.10
MachineType: FUJITSU LifeBook T4215
Package: xserver-xorg-video-intel 2:2.9.0-1ubuntu2
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   product info: "O2Micro", "SmartCardBus Reader", "V1.0", ""
   manfid: 0xffff, 0x0001
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   5.0V 16-bit PC Card
   Subdevice 0 (function 0) [unbound]
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=cd5909b1-b49c-42a2-9baa-912b638d66d8 ro crashkernel=384M-2G:64M,2G-:128M quiet splash i915.modeset=0
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu7
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.15~git-0ubuntu0tormod
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
SourcePackage: xserver-xorg-video-intel
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 08/21/2007
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.15
dmi.board.name: FJNB1B9
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: AE5CJ1E526550000
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.15:bd08/21/2007:svnFUJITSU:pnLifeBookT4215:pvr:rvnFUJITSU:rnFJNB1B9:rvr:cvnAE5CJ1E526550000:ct10:cvr:
dmi.product.name: LifeBook T4215
dmi.sys.vendor: FUJITSU
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-14-generic

[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
     Subsystem: Fujitsu Limited. Device [10cf:1380]

[Mike Kaplinskiy (mike-kaplinskiy)]

Removing the vesa driver from the system eventually lets X start with KMS. Attached is the log for the first failed start (X starts on the second try). The normal log is EXACTLY the same up to that point, which then starts adding hal devices (the first is the tablet pen device). Is this a problem in VESA itself possibly?

[Vikram Dhillon (dhillon-v10)]

This issue was reported against karmic, so can you confirm if this issue exists with the most recent Lucid Lynx 10.04 Alpha release? ISO CD images are available at http://cdimage.ubuntu.com/releases/lucid/ . Thanks in advance.

[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.