-   SUSE / openSUSE (
-   -   On booting Suse 10.1 KDE doesn't start - all I can get is the command line (

ScoobySnacks 09-20-2006 05:43 PM

On booting Suse 10.1 KDE doesn't start - all I can get is the command line

I am a Linux newbie so please be gentle.

I have recently installed Suse 10.1 with KDE GUI and have got it to work adequately and spent a fair amount of time reconfiguring it. Unfortunately, since installing updates a week ago as recommended by that orange exclamation mark in the system try, I have been having problems. When I boot up Suse now I get the command line up prompting me to login, which I do but I am unclear what has happened to the desktop and how to restore it. I have tried logging in as root and using the "init" command to change runlevels and I have been able to access YAST with the command line but frankly I don't know what I should do to correct this issue and restore the more familiar KDE GUI desktop.

I would be grateful for any advice.


google01103 09-20-2006 05:49 PM

from command line type "startx" and post results

it could be you upgraded your kernel and now must re-install your video drivers as the drivers are kernel specific

ScoobySnacks 09-21-2006 05:18 PM

Many thanks google 01103 ... it worked
Most grateful, you were absolutely right I just needed to re-install the graphics driver.

Thanks again!

Ion Flux 10-27-2006 12:21 PM

Hi. I'm having the same problem but reinstalling my graphics drivers from the command line doesn't seem to help.

Running startx from the command line results in this:

hostname: Unknown host
xauth: creating new authority file /home/ion_flux/.serverauth.3666

Fatal server error:
Could not create lock file in /tmp/.tX0-lock

giving up.
/usr/X11R6/bin/xinit: Connection refused (errno 111): unable to connect to X server
/usr/X11R6/bin/xinit: No such process (errno 3): Server error.

Any help is immensely appreciated!

Ion Flux 10-27-2006 12:33 PM

After searching the web with the error message, I think I know what may have caused the problem.

I tried to mount my Windows partition using the YAST2 partition manager. I set the mount point to /tmp. If this is the problem, then:

A. How can I fix it, and ...

B. ... what's the correct way to be able to access files on the Windows partition without buggering my linux install?

Thanks again for any help!

gkiagia 10-27-2006 12:43 PM

Mount your windows partition on /windows
/tmp must not be used for mounting such filesystems.

To fix it, run yast from the command line and fix it in the same way that you messed it up. (You have to use the arrows and tab to navigate. Press enter to click)

To quick fix it and load X, try "umount /tmp" as root. You can then use the yast GUI.

Ion Flux 10-27-2006 01:04 PM

Awesome. X server and KDE are back and running. I love you.


All times are GMT -5. The time now is 06:06 AM.