x switches to low graphics at first try to start. second works!

Bug #486702 reported by Felix
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
New
Undecided
Unassigned

Bug Description

I'm using Kubuntu Karmic x64 with a nvidia 8400m.

The problem:

-i start my notebook
-short time after usplash disappeared, x tries to start but obviously does NOT use the driver specified in my xorg.conf.
 Therefore it crashes to low-graphics mode and gives me a few error and solution messages. (reconfigure your graphics etc)
-when i cancel them all in about 5 seconds, i'm thrown back to startuplog and x starts again (!) after a few secs with the right settings and therefore with my nvidia-glx-185 driver! everything works fine!
-when i'm too slow X won't start again on its own and i have to start it manually with "startx" or "sudo stop kdm" and "sudo start kdm" from tty (kdm seems to run, even after the crashed X server has closed)

I don't think this is driver related, cause X does not use the driver ( i do not see the nvidia SPLASH) when it fails.
Imo X is started way too early in the progress of booting so that not everything is "ready" to get X up.

When a disk check is forced the boot progress is delayed for at least 5 minutes. When it continues to boot, X will start immediately into the "right" instance and it will work. Therefore i really think it is started too fast while normal booting.

logs enclosed

Revision history for this message
Felix (apoapo) wrote :
  • logs Edit (80.0 KiB, application/x-tar)
Revision history for this message
Felix (apoapo) wrote :

This only happens while using KDM. GDM works fine. I would use it but it is annoying to have no shutdown button in KDE..

The Errors i see with KDM are a few different ones:

sometimes:

- (EE) XKB: No components provided for device Virtual core keyboard

or most of the time:

- Your screen, graphics card, and input device settings could not be detected correctly. You will need to configure them yourself.

Waiting about 10 seconds "solves" the problem and i'm able to start kdm through "sudo stop kdm" and "sudo start kdm"

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.