KDM not loading after kernel update

[trintadosete]

Hi, everybody

i am using kubuntu 8.10 without upgrade to kde 4.2

Thia morning, i upgraded the kernel (getting the 2......-11 version), but in this kernel version kdm is not loading.
If i boot using 2......-9 everything goes fine.
Does anybody know what is happening?

thanks

[trintadosete]

Re: KDM not loading after kernel update

This morning i got a upgrade for the kernel 2.6....-11, but the problem is still here: kdm not loading.

My computar is a DELL Vostro 1000 with ATI 1300.

[Teunis]

Re: KDM not loading after kernel update

I had a similar issue but for me it was not unexpected.
I used EnvyNG to install the Nvidia driver and it needs to be reinstalled after every major kernel upgrade.
The command is:

sudo envyng -t

Next you select the number representing the driver you need etc.
Hopefully you have the same problem but with the ATI driver.

[trintadosete]

Re: KDM not loading after kernel update

I booted on recovery mode and ran "Fix X server". Since then i am using fglrx instead of the proprietary driver, but i still cant boot on kernal 2.6....-11, just on 2.6......-9

Any idea?

[trintadosete]

Re: KDM not loading after kernel update

I upgraded to kde 4.2 reconfiguring almost everything on X.
Now, i am using flgrx but i still cant boot using the kernel 2.6.27-11 and everything works fine under 2.6.27-11

any suggestion?

[trintadosete]

Re: KDM not loading after kernel update

acidentaly, i booted on 2.6.27-11 and everything worked fine!
I dont know the reason, but it is solved...

[Zorael]

Re: KDM not loading after kernel update

When X doesn't start it's usually because of an old driver that you compiled or installed yourself, with the prime example being the Nvidia proprietary driver. envyNG usually takes care of this automatically, but in the rare case it doesn't, you'll have to take care of it yourself. The easiest way is to boot up in recovery mode, pick Fix X, and then rerun envyNG and reinstall the driver.

The log file for X is located at /var/log/Xorg.0.log, but it gets overwritten if you pick Fix X and start X successfully, so you'll likely want to look for older logs in the same directory (/var/log/). I think they're named something in the lieu of Xorg.0.log.old, but might be Xorg.1.log. You'll want to look at the very end of this file to get an inkling of what went wrong.