Kubuntu only boots into command line

[Rob]

Eeek , Finally managed to install the latest NVIDIA drivers on my Kubuntu 8.10 machine, but now it will only boot to command line :cry2:
How do I get from command line to gui, and how can I make it automatically boot to gui again. Or have I broken it & need to do a complete reinstall :hbang:

EDIT: OK worked out how to start it "startx". But it still doesn't work.
Goes through a series of lines & gets to line 18 which says "usr/bin/x11/x [0x432ad9]"
It then says "Saw signal 11. Server aborting.
                   giving up.
                   xinit:  Connection refused (erno 111):  unable to connect to xserver
                   xinit:  No such process (errno 3):  server error."

Looks like I broke it :cry2:

[yoda]

Type: startx

No guarantee it will work - depends how broken it is!

[Wang Solutions]

startx has always worked for me when Kubuntu has "lost" its GUI, and it then is usually right again once you reboot.

[Rob]

Can I assume Boinc  is still crunching in this state ???. It's the version from the repositories with the boinc, boincmgr, & boinccmd files replaced with 6.6.20 so from what I understand it should at least still be crunching.

[Wang Solutions]

Yes, it loads before the GUI so should be running.  Did you try startx? Or a reboot? I have had the issue before in Kubuntu 7.04 and that has always worked.

[WikiWill]

A couple of ways you can check BOINC is running are:

1) use the "w" command and check that load level is approx equal your number of cores.  Load average shows three numbers which is CPU load (number of runable processes) averaged over something like 1 minute, 5 mins, and 15 mins.

2) use the boinccmd --get_state command and see what's happening.  In the Results section you should see WUs with "active_task_state = 1" when they are running.

[Rob]

1) use the "w" command and check that load level is approx equal your number of cores

That gives a whole heap of 0's beside load average

use the boinccmd --get_status command and see what's happening.  You should see WUs with something like "active_state = 1" or similar.

can't connect to local host

Looks like I broke it good

Did you try startx

Yep, you & Yoda replied while I was editing my first post. Tried rebooting once with no joy. I'll try one more time. If it doesn't work I might as well turn it off until tomorrow afternoon when I'll have to do a reinstall. No use wasting power for nothing :-\

[Rob]

Rebooting again didn't work so I'm going to turn it off now & go to bed. If nobody can come up with a fix it looks like I'll have to reinstall tomorrow when I finish work  :hbang:

[WikiWill]

You might be able to start BOINC manually and at least do some processing...  Can you log in?

If you can get a shell and change to the BOINC folder (might be in your home folder), you could use:

% ./run_client --daemon

[Mike Mitchell]

type top and see if anything is running at 100%, that should be the applications. You may need to cd to the boinc directory to get boinccmd to work.

[Rob]

I can log in but % ./run_client --daemon just gives me an error message (boinc is in /usr/bin).
Nothing is running at more than a couple of percent.
Thought I'd take a chance & reinstall the nvidia driver. Now I get a whole new bunch of error messages when I type startx. But the one that catches my eye is "Error: API mismatch: the NVIDIA kernel module has version 177.82, but this NVIDIA driver component has version 180.29. Please make sure that the kernel module & all NVIDIA driver components have the same version."

So it looks like it didn't overwrite the old kernel. When it was installing it said it couldn't find a kernel for my system so was compiling it's own. Did I do something wrong ???

[Rob]

Buggerit, I don't have the time or patience to keep playing around with this. :hbang: Looks like a system reinstall is in order  :cry2:

[yoda]

If I had a quick fix (in Ubuntu) I'd give it to ya to try in Kubuntu, but I don't have one.

The only thing I can think of is to delete your /etc/X11/xorg.conf file and reinstall the drivers using envy.  But you seem to have done that (or similar) already

[WikiWill]

Buggerit, I don't have the time or patience to keep playing around with this. :hbang: Looks like a system reinstall is in order  :cry2:

I concur!   :cry2:

[Cruncher Pete]

I was going to suggest to do this earlier but I did not  as it would have suggested my ignorance, which would have been true. I did have a similar issue with my system and I found that it was quicker to reinstall than trying to find answers how to fix it..  It seems that the already installed drivers needs to be deactivated first before installing newer ones.