Uninstalled KDE -> lost GUI

[jjrom]

Hi. A newbie here, well pleased with Fedora Linux, but with a problem I can't work out:

Originally I installed both GNOME and KDE. Later, grew tired of KDE and its applications making space on my menu, so I decided to uninstall it, using yum groupremove.

Silly me, didn't notice that yum was also removing NetworkManager and other programs needed by GNOME. Then, when I restarted the computer, it freezed before it could show the "user login".

I'm able to access the Linux command line if I press F1 during loadig, but I dont know what to do next! I tried to fix the GRUB configuration, but it didn't have any effect.

Any clues??

[renkinjutsu]

this might fix your problem

yum groupinstall "Gnome Desktop Environment"

[jjrom]

I'm not able to connect to the internet..
Any way in which I can install GNOME from the Installation DVD?

[forkbomb]

As for clues, does GRUB throw an error? GRUB should still be on the MBR. If all it removed was GDM you still should be able to muster a runlevel 3 boot and fix things with yum (no, you don't strictly need NetworkManager for networking).

My guess by running "yum groupremove" on the KDE group on my machine shows that yum removed GDM on you (which it shouldn't and that's asinine). Hopefully yum didn't go fully nuts and remove your kernel or yum itself.

When GRUB comes up, hit a key to stop it, hit "a" with your most recent kernel installed, and add 3 to the end (after a space).

Then try reinstalling GDM with yum (yum install gdm). While you're at it, if you want it, reinstall NetworkManager. While you're at it check that the GNOME group is still installed.

[jpollard]

You could try the following in a console terminal logged in as root:

service network start

This should start your network without the network manager.
Then you should be able to try the groupinstall.

[jjrom]

the IP recognition for wlan0 fails.
Is'nt there a way to make service network connect only to the eth0 connetion?

[forkbomb]

Originally Posted by jjrom

the IP recognition for wlan0 fails.

Probably because you have some security on your access point. The network service can't read your passphrases for wireless security that you saved using NetworkManager/nm-applet. Further, getting the network service to work with wireless and especially secured wireless can get a bit... ugly.

Is'nt there a way to make service network connect only to the eth0 connetion?

Cable up temporarily.

service NetworkManager stop
service network restart

If the network script for your eth0 in /etc/sysconfig/network-scripts doesn't have eth0 set to automatically start (and I don't believe it does by default), you can try

dhclient eth0

after you stop NetworkManager and start network.