kdm does not start

[Goh Lip]

Binary package hint: kdebase-workspace

2.6.32-16-generic
kde 4.4.1
lucid 64 alpha

After upgrade to 2.6.32-16-generic, boots to blank screen.
Have to ctl + alt + prt scr + k
or boot using recovery and then at prompt sudo kdm start

Similar to bug 437067 on karmic alpha which I reported on bug 437283

However 2.6.32-15-generic boots okay.

Goh Lip

[Goh Lip (gohlip)]

A better way to boot 2.6.32-16 is to modify grub.cfg to remove splash and quiet.
Since this had happened earlier in Karmic alpha, just wondering if this is something unavoidable.
(not a criticism, just trying to understand). If this is due to programming constraints, that is quite alright as alpha users/testers should have some awareness to handle this. Thanks.

[Goh Lip (gohlip)]

Removing "nouveau" interface solved the problem. Can boot with quiet and splash.
However 'plymouth' still starts with error.

[Bryce Harrington (bryce)]

Hi Goh,

Please attach the output of `lspci -vvnn` and `dmesg`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue. If you're using a custom /etc/X11/xorg.conf please attach that as well.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Goh Lip (gohlip)]

Here's the attached lspci, dmesg and Xorg log. No xorg.conf file.

Thanks.

[Goh Lip (gohlip)]

One file per message? here's lspci

[Goh Lip (gohlip)]

And dmesg

[Goh Lip (gohlip)]

After some upgrades, reinstalled xserver-xorg-video-nouveau to try out. Booted okay with my plymouth uninstalled. Then reinstalled plymouth, and the problem returned and can only be booted with the 'splash' removed (again) at grub kernel menu.

The problem seems (to me) not to be with nouveau but with plymouth.
Hope this information helps.

Thanks.

[Goh Lip (gohlip)]

lspci -vvnn attached

[Goh Lip (gohlip)]

Problem solved. See bug 538524. Problem is traced to plymouth splash screen where kdm is not booted.
Thanks.

[Chris Halse Rogers (raof)]

Duping to bug #538524 as this seems to have been the problem.