[SOLVED]....after..... .... PC boots into Grub and then into command line..

[hansdevr]

The subject says it all, I think...

After the upgrade, all I got is the Grub menu (so far, so good).. After selecting the first line, I don't get the usual Kubuntu spash screen with the login, but a command line that prompts me to log in. When I do, it just shows the command line, period. Any ideas anyone?!? (please, keep it as simple as possible, I still consider myself to be somewhat of a noob...)

[mfabry]

Re: after upgrade to 11.04 (64 bit), PC boots into Grub and then into command line..

Do you use Nvidia or ATI proprietary drivers?

[Jonas]

Re: after upgrade to 11.04 (64 bit), PC boots into Grub and then into command line..

The subject says it all, I think...

After the upgrade, all I got is the Grub menu (so far, so good).. After selecting the first line, I don't get the usual Kubuntu spash screen with the login, but a command line that prompts me to log in. When I do, it just shows the command line, period. Any ideas anyone?!? (please, keep it as simple as possible, I still consider myself to be somewhat of a noob...)

This sound as a graphical issue, your system spec/hardware/model would be of great help, especially the graphics chip. While in command line interface, once logged in, startx should give you a GUI, if not you're likely to be given a error message and/or what to do. Post that here.

b.r
Jonas

[hansdevr]

Re: after upgrade to 11.04 (64 bit), PC boots into Grub and then into command line..

I have an ATI Sapphire HD 3870.... Under Lucid, it worked fine, both with the ATI drivers as with the standard (K)Ubuntu drivers.. I never got desktop effects working tho....

I will try the startx command and make a note of everything I see. I am at work now, so that's going to have to wait until I get home..

[hansdevr]

Re: after upgrade to 11.04 (64 bit), PC boots into Grub and then into command line..

after typing startx I got a screen full of messages, most about that fglrx couldn't connect to a PCI device. At the end there were some messages that xinit could not start up or connect to the server. Below that the $ prompt. So yeah, it feels like something is AGAIN the matter with that !@^%&#^ ATI card....

[hansdevr]

Re: after upgrade to 11.04 (64 bit), PC boots into Grub and then into command line..

I found a link about ATI drivers (http://askubuntu.com/questions/33092...hics-cards-yet), at which it was recommended to update the fglrx drivers doing this:
sudo apt-get install fglrx
sudo update-alternatives --config gl_conf
(select line with fglrx) - in my case there were 2, so I ran it twice...

sudo update-initramfs -u
Then do a reboot.

I tried this and lo and behold - I saw the Kubuntu splash screen!! After which I was back at the Linux prompt again....
startx rendered the same errors as before....

I know I went on a wild chase here - hope I didn't break anything that didn't need fixing in the first place....

[sithlord48]

Re: after upgrade to 11.04 (64 bit), PC boots into Grub and then into command line..

your problem is more then likely w/ teh FGLRX driver it self. try removeing it and your /etc/xorg.conf file then reboot that will force the use of the open driver, from there you should have a desktop. if you do then you can try again w/ fglrx if you want or just use the free driver.

[hansdevr]

Re: after upgrade to 11.04 (64 bit), PC boots into Grub and then into command line..

could you please tell me how to do that from the command line?!? Because I haven't got the foggiest how to go about it...

[sithlord48]

Re: after upgrade to 11.04 (64 bit), PC boots into Grub and then into command line..

sure, we can do it the easy way , first we back up your xorg.conf file

sudo cp /etc/X11/xorg.conf /etc/X11/xorg.conf.backup

then remove the file to prevent the fglrx driver from being loaded

sudo rm /etc/X11/xorg.conf

after that you can try to restart kde ,if you get an error about it not running , use "start" in place of "restart"

sudo /etc/init.d/kdm restart

if all goes well you should be pushed over to the X session where you can log in .

we have not uninstalled the fglrx driver, we are just not using it. if this gets you to a desktop you can remove the driver w/ hardware driver program as normal.

[el_koraco]

Re: after upgrade to 11.04 (64 bit), PC boots into Grub and then into command line..

Sithlord, I would hazard to suggest that services are best managed with the simplest Upstart command:
sudo service <service> <action>. So in this case, sudo service kdm restart.

OP, if the above method (I urge you to try it first) does not work, there are other avenues you can take. See the list of possible solutions here.

Please, do your backups now, I've personally had dealliings with fglrx going crazy, and it is not in any way certain you'll not end up with a messed up screen after purging it. Backup everything you can't live without before doing anything, boot with the Live CD and transfer it to a USB stick or something.

[hansdevr]

Re: after upgrade to 11.04 (64 bit), PC boots into Grub and then into command line..

Thanks for all of the help, ppl! I am again amazed with the speed, patience and eagerness people in the Kubuntu community are giving support to us dim users.. And yes, el_koraco - you make a valid point with urging me to back up stuff... Thanks!!

Will get back to y'all when I tried these suggestions!

[hansdevr]

Re: after upgrade to 11.04 (64 bit), PC boots into Grub and then into command line..

Alas, deleting xorg.conf didn't do the trick.. There were many xorg files in that folder, btw - xorg.conf.fglrx0, xorg.conf.fglrx1, xorg.conf.dist-upgrade20110429 etcetera.. should I delete those too?!?

it didn't matter whether I typed kde start or kde restart - neither worked. The Live CD booted fine tho. No problem whatsoever. I tried to back up my data on a dvd rw, but k3b wouldn't let me go on the hard drive to select files. I'll better buy a large USB stick before I go any further with this...

[sithlord48]

Re: after upgrade to 11.04 (64 bit), PC boots into Grub and then into command line..

Alas, deleting xorg.conf didn't do the trick.. There were many xorg files in that folder, btw - xorg.conf.fglrx0, xorg.conf.fglrx1, xorg.conf.dist-upgrade20110429 etcetera.. should I delete those too?!?

no since the Xserver only uses xorg.conf to set its settings if its not there the system should auto detect and set it self correctly ,but not a properitary driver, since they should require the xorg.conf to load them.

The Live CD booted fine tho. No problem whatsoever.

its a good sign that you get correct video from a live cd this means the open driver should work just fine for you and simply removing the fglrx driver should get you back you (after a reboot that is)

first lets check the status of that fglrx driver

jockey-text --list

you should get some output that says

Error: root: <more text ingore this >
xorg:fglrx - ATI/AMD proprietary FGLRX graphics driver (Proprietary, Enabled, In use)

now if its enabled we are going to disable it,

sudo jockey-text --disable=xorg:fglrx

when its finished you can reboot and will *hopefully* have a desktop.

I tried to back up my data on a dvd rw, but k3b wouldn't let me go on the hard drive to select files.

the live cd will not auto mount your hard drive but, you should be able to mount your hard drive using dolphin by just clicking on it .You might even see it in the "Device Notifier" and could also mount it from there. either way you want mount your hard drive before you try to burn a disk w/ k3b. then your should see your files

[hansdevr]

Re: after upgrade to 11.04 (64 bit), PC boots into Grub and then into command line..

When entering

jockey-text --list

I got an error, like you predicted. Ignored it and entered

sudo jockey-text --disable=xorg:fglrx

This time I just got

ERROR:root:Could not find any typelib for AppIndicator

..which was in fact the same error when I entered the first command..

[sithlord48]

Re: after upgrade to 11.04 (64 bit), PC boots into Grub and then into command line..

im not sure if there is other output then that. from cli tool its finished when u get back to a prompt (name@machine:$) then you should be able to reboot (with sudo reboot) and when the machine comes up after that (hopefully) you have a working X server.if your not sure if the driver got removed check its status again using the command above.