FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Last night I spent updating KDE and Gnome to 3.3 and 2.8.0 respectively. Everything went smoothly, dependencies were solved and both worked like a charm. However, I didn't reboot after the update of Gnome and just logged out instead and logged in Gnome right away just to make sure that everything is working and it was.
When I switched on the computer today, however, Fedora refused to start. The last message I get is "Red Hat hash version..." and then it restarts the PC.
I read something in this forum about removing the "quiet" arguments of the kernel parameters in grub's config file, so that you can actually see what the problem is. I got into rescue mode, but I couldn't find anything about that in /boot/grub/grub.conf.
Any suggestions or comments would be more than welcome.
Thanks!
if you get to the rescue mode, why not check out /var/log/messages and so on? and dmesg. I would believe there were some lines of information about the error...
I think the problem is linked to UDEV, which I believe is required by Gnome 2.8(at least when I was going to update it wanted to wipe out DEV, install UDEV).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.