Oneiric X/LightDM doesn't start on an Intel GMA500

[H3g3m0n]

I'm using the Ubuntu 11.10 Daily LiveCD from 21 Jul 2011.

I'm on a Asus EeePC T91MT.

The Intel GMA500 has always been problematic with Intel basically refusing to support it, however in the past it did at least start on older Ubuntu versions (although in an incorrect resolution and normally required quite a bit of screwing around with drivers to get something decent running).

The new 3.0 kernel (and 2.6.39) now has some built in psb-gfx drivers for the chipset, they don't support hardware acceleration but should give ok normal 2D graphics.

On boot, I get stuck at a terminal. The terminal flashes black continuously until I 'sudo stop lightdm' (LightDM seems to fail to detect that it's broken and just keeps trying to start, but that's probably a different bug).

I notice in the Xorg.log there is a "vesa: Ignoring device with a bound kernel driver".

There is a kernel module 'poulsbo' loaded.

If it 'rmmod poulsbo' and then 'sudo start lightdm' then xorg starts correctly.

My best guess is xorg isn't correctly configured to use the new psb-gfx drivers.
---
Architecture: i386
CasperVersion: 1.271
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
DistUpgraded: Fresh install
DistroCodename: oneiric
DistroRelease: Ubuntu 11.10
DistroVariant: ubuntu
GdmLog:

GdmLog1:

GdmLog2:

GraphicsCard:
 Intel Corporation System Controller Hub (SCH Poulsbo) Graphics Controller [8086:8108] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:8398]
LightdmGreeterLog:

LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110721)
MachineType: ASUSTeK Computer INC. T91MT
Package: xorg 1:7.6+7ubuntu4
PackageArchitecture: i386
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --
ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
Renderer: Unknown
Tags: oneiric unity-2d ubuntu
Uname: Linux 3.0.0-5-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 11/26/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0601
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: T91MT
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.:bvr0601:bd11/26/2009:svnASUSTeKComputerINC.:pnT91MT:pvrx.x:rvnASUSTeKComputerINC.:rnT91MT:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: T91MT
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
peripherals:
 /desktop/gnome/peripherals/mouse:
   cursor_theme = DMZ-White
version.compiz: compiz 1:0.9.5.0-0ubuntu1
version.libdrm2: libdrm2 2.4.26-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 7.11~1-0ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.11~1-0ubuntu4
version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.2-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.0-3ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1

[Brendan Donegan (brendan-donegan)]

Hi,

Are you able to run 'apport-collect 815000'?

Thanks,

[H3g3m0n (h3g3m0n)]

apport information

[H3g3m0n (h3g3m0n)]

apport information

[H3g3m0n (h3g3m0n)]

apport information

[H3g3m0n (h3g3m0n)]

apport information

[H3g3m0n (h3g3m0n)]

apport information

[H3g3m0n (h3g3m0n)]

apport information

[H3g3m0n (h3g3m0n)]

apport information

[H3g3m0n (h3g3m0n)]

apport information

[H3g3m0n (h3g3m0n)]

apport information

[H3g3m0n (h3g3m0n)]

apport information

[H3g3m0n (h3g3m0n)]

apport information

[H3g3m0n (h3g3m0n)]

apport information

[H3g3m0n (h3g3m0n)]

apport information

[H3g3m0n (h3g3m0n)]

apport information

[H3g3m0n (h3g3m0n)]

apport information

[H3g3m0n (h3g3m0n)]

apport information

[H3g3m0n (h3g3m0n)]

apport information

[H3g3m0n (h3g3m0n)]

apport information

[H3g3m0n (h3g3m0n)]

apport information

[H3g3m0n (h3g3m0n)]

apport information

[H3g3m0n (h3g3m0n)]

Note: The above was done after rmmoding the poulsbo module and restarting lightdm since there is no easy way to get the laptop onto my wifi and appaport authorized for launchpad from the console.

[Chris Halse Rogers (raof)]

Gah! The poulsbo driver couldn't do something useful, like log *anything* to dmesg, could it?

So, we either need the DDX component of the poulsbo driver or to blacklist the kernel module. I lean towards blacklisting the kernel module.

[Chris Halse Rogers (raof)]

Hm. Or, perhaps, since the poulsbo module appears to be a kms driver, it should work with fbdev at native resolution.

Could you please attach dmesg from a boot with “drm.debug=0x0f” appended to the kernel command line?

[H3g3m0n (h3g3m0n)]

drm debug dmesg attached.

[Bryce Harrington (bryce)]

If X just needs to be changed to use fbdev instead, then can you verify this?
Put the following into your /etc/X11/xorg.conf and restart X:

Section "Device"
        Identifier "Configured Video Device"
        Driver "fbdev"
EndSection

Section "Monitor"
        Identifier "Configured Monitor"
EndSection

Section "Screen"
        Identifier "Default Screen"
        Monitor "Configured Monitor"
        Device "Configured Video Device"
EndSection

If that works, then perhaps we merely need to s/vesa/fbdev/ in xorg-server for poulsbo.

[H3g3m0n (h3g3m0n)]

Not working, there's no /dev/fb0

I tried 'modprobe fbdev' and 'rmmod poulsbo' but nothing appeared (fbdev didn't show up in lsmod either).

[Bryce Harrington (bryce)]

Okie doke, thanks for testing that! Too bad, that would have been an easy fix.

So seems to be an issue with the loading of the kernel driver. Bumping to the kernel team. Maybe the psb module should be blacklisted for now until it works more reliably.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel currently in the release pocket than the one you tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help.

[H3g3m0n (h3g3m0n)]

This is still broken as of 15 Sep 2011 using 3.0.0-11.18.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

[H3g3m0n (h3g3m0n)]

I just posted that I was using that version =/

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

[SethWoodworth (seth-woodworth)]

I have the same chipset, and the same problem as of the latest development version 02011 Oct 6th, which I believe is the Release Candidate.

[Dan (daniel-myre-gmail)]

I confirm the DVD Release Oct 13th is with Kernel 3.0.0.12 is sill not working. Require to boot command :

sudo rmmod poulsbo
sudo start lightdm

System info Tool confirm as Graphics card: VESA: Intel(r) Poulsbo Graphics
With experience Standard.
Display not Detected. Resolution limited to 800X600

Touch screen works OK as Single touch. No Multi-touch supported in fresh install.

[David Ayers (ayers)]

This issue seems to be fixed with 3.0.0-13-generic-pae

(Well, you probably don't need the pae but I had installed the 32-bit oneiric onto a USB-Stick on my 4GB notebook, which probably caused the -pae kernel to be installed onto the USB-Stick.) I was able to boot my Dell Mini 12 from that USB-Stick. The kernel package is version: 3.0.0-13.22 and both lightdm and compiz seam to be working well.

Thanks!
PS: I'm not sure whether I should change the status to "Fix Released"...

[Dan (daniel-myre-gmail)]

Confirmed 3.0.0-13-generic fixed the startup with lightdm.

For the specific hardware of the Asus T91MT (with GMA500), the monitor is not recognized and stuck to 800X600.
ACPI not complete either, missing the Flip screen feature and touchscreen only compatible in single touch.

Will try the FIX with xorg.conf to validate a manual settings.

[Launchpad Janitor (janitor)]

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