KMS doesn't play nice with vesa X driver

Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: vorlon 2655 F.... pulseaudio
 /dev/snd/pcmC0D0p: vorlon 2655 F...m pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xee240000 irq 17'
   Mixer name : 'Analog Devices AD1981'
   Components : 'HDA:11d41981,17aa2025,00100200'
   Controls : 20
   Simple ctrls : 11
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=f108133c-6b9d-4d28-9058-0b3a0c5549b4
MachineType: LENOVO 6371CTO
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=/dev/mapper/dario-root ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48+ureadahead2-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout fuse lpadmin mythtv plugdev sambashare
WpaSupplicantLog:

dmi.bios.date: 12/27/2006
dmi.bios.vendor: LENOVO
dmi.bios.version: 7IET23WW (1.04 )
dmi.board.name: 6371CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7IET23WW(1.04):bd12/27/2006:svnLENOVO:pn6371CTO:pvrThinkPadT60:rvnLENOVO:rn6371CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 6371CTO
dmi.product.version: ThinkPad T60
dmi.sys.vendor: LENOVO

I think this was accidentally tagged regression-proposed when it really should either be regression-release for Karmic or regression-potential for Lucid. Will use change this to regression-potential for now.

regression-proposed was deliberate, because this is exposed by the SRU to re-enable bulletproof X in karmic.

I'm not sure what to do with the xorg proposed update in bug 474806 now. This bug here wasn't introduced by the xorg/gdm changes, but I don't understand how it can suddenly be exposed on a system which previously had a correct xorg.conf/drivers.

Some insight as to whether this should block the -updates migration would be appreciated.

I upgraded my Karmicy system yesterday, problem occured on another machine...

@steve -- this seems like a very old Karmic issue, I would assume this was actually fixed for released? Can you remember?

Andy, I never saw a fix for this issue in karmic. In maverick, the vesa driver itself detects the presence of KMS and refuses to run, printing a message to the X log:

 (EE) VESA: Kernel modesetting driver in use, refusing to load

That seems to imply that if the vesa driver *did* load, it could still hork the KMS system. But maybe this is the correct fix all the same?

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

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