Fedora wont boot, displays nvidia splash screen over and over
FedoraThis forum is for the discussion of the Fedora Project.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Fedora wont boot, displays nvidia splash screen over and over
I am a total newbie here, so bear with me...and my apologies for the length of this thread...
I am running Fedora Core, with kernel 2.4.22-1.2174.nptl. I installed the Nvidia drivers for my GeForce card back when running 2.4.22-1.2149, and since then have updated the kernal twice with no problems. The other day, however, everything went wrong...
Linux inexplicably froze at 4:44 AM, and at 5:10 I attempted a reboot. Everything appears fine, right up until the Nvidia splash screen appears. Instead of leaving the splash screen and going to the screen which shows everthing starting (with the progress bar and all that, just before you'd get to the login screen), it loops over and over into the nvidia splash screen. This will not stop.
I tried to use interactive startup, and once it worked (which 80% of the time it doesn't...I hit "I" and it just ignores it and tries to boot normally) I chose not to load the nvidia driver. All this did was stop the splash screen from appearing, but it still looped endlessly on a black screen, and the monitor clikced like it does when going in and out of the nvidia screen.
I finally used putty from another computer (while it was looping), and set my runlevel to 3 in the /etc/inittab file, and now I can at least get to a command shell. Below is a portion of the /var/log/messages file in which you can see the error I expect is causing this...
Mar 10 05:10:37 localhost atd: atd startup succeeded
Mar 10 05:10:38 localhost messagebus: messagebus startup succeeded
Mar 10 05:10:38 localhost nvidia: Checking for nvidia kernel module succeeded
Mar 10 05:10:38 localhost nvidia: Enabling nvidia driver succeeded
Mar 10 05:10:39 localhost kdm_config: Unrecognized section name [Desktop0] at /usr/sha
Mar 10 05:10:40 localhost kernel: 0: nvidia: loading NVIDIA Linux x86 NVIDIA Kernel Module
1.0-5336 Wed Jan 14 18:29:26 PST 2004
Mar 10 05:10:40 localhost insmod: Warning: loading /lib/modules/2.4.22-1.2174.nptl/kernel/dr
ivers/video/nvidia/nvidia.o will taint the kernel: non-GPL license - NVIDIA
Mar 10 05:10:40 localhost insmod: See "this was a url but I had to remove it to post this"
ion about tainted modules
Mar 10 05:10:40 localhost insmod: Module nvidia loaded, with warnings
Mar 10 05:10:43 localhost kernel: Linux agpgart interface v0.99 (c) Jeff Hartmann
Mar 10 05:10:43 localhost kernel: agpgart: Maximum main memory to use for agp memory: 439M
Mar 10 05:10:43 localhost kernel: agpgart: Detected Via Apollo Pro KT266 chipset
Mar 10 05:10:43 localhost kernel: agpgart: AGP aperture is 64M @ 0xe8000000
Mar 10 05:10:51 localhost kdm: IO Error in XOpenDisplay
Mar 10 05:10:51 localhost kdm: Display :0 cannot be opened
Mar 10 05:11:01 localhost kdm: IO Error in XOpenDisplay
Mar 10 05:11:01 localhost kdm: Display :0 cannot be opened
Mar 10 05:11:10 localhost kdm: IO Error in XOpenDisplay
Mar 10 05:11:10 localhost kdm: Display :0 cannot be opened
Mar 10 05:11:20 localhost kdm: IO Error in XOpenDisplay
Mar 10 05:11:20 localhost kdm: Display :0 cannot be opened
Mar 10 05:11:20 localhost kdm: Display :0 is being disabled (restarting too fast)
Mar 10 05:11:20 localhost kdm_config: Unrecognized section name [Desktop0] at /usr/sha
Mar 10 05:11:30 localhost kdm: IO Error in XOpenDisplay
Mar 10 05:11:30 localhost kdm: Display :0 cannot be opened
Mar 10 05:11:40 localhost kdm: IO Error in XOpenDisplay
Mar 10 05:11:40 localhost kdm: Display :0 cannot be opened
Mar 10 05:11:41 localhost shutdown: shutting down for system reboot
Mar 10 05:11:41 localhost init: Switching to runlevel: 6
Mar 10 05:11:45 localhost shutdown: shutting down for system reboot
Mar 10 05:11:45 localhost nvidia: Disabling nvidia driver succeeded
Mar 10 05:11:45 localhost messagebus: messagebus -TERM succeeded
Mar 10 05:11:45 localhost atd: atd shutdown succeeded
Mar 10 05:15:47 localhost syslogd 1.4.1: restart.
Mar 10 05:15:47 localhost syslog: syslogd startup succeeded
And here is my XF86Config file:
# XFree86 4 configuration created by redhat-config-xfree86
# RgbPath is the location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
# Option "XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# Or if you just want both to be control, use:
# Option "XkbOptions" "ctrl:nocaps"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
# If the normal CorePointer mouse is not a USB mouse then
# this input device can be used in AlwaysCore mode to let you
# also use USB mice at the same time.
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
So, can somebody please help me out here? What do I do next? As I mentioned, I am quite the newbie still. It took me forever to correctly install the nvidia drivers, and I honestly dont even remember everything I did. Any help here is GREATLY appreciated.
Okay, I just noticed an error message when typing startx from the command line. It had said:
Could not init font path element unix/:7100, removing from list!
Fatal server error:
could not open default font 'fixed'
So I commented out the line
in XF86Config and typed startx. Now, the splash screen comes on for only a moment (as it used to) and then it goes the the black X cursor that you see when booting right before you see the boot progress. I almost jumped out of my seat, as I though it was fixed. But after about two seconds it went back to command line, and shows the following error:
Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list!
/root/.Xclients: line 8: /root/.Xclients-default: No such file or directory
/root/.Xclients: line 8: exec: /root/.Xclients-default: cannot execute: No such file or directory
So, what does this tell you anything? I think I will start a new thread with this subject, but feel free to reply to either.
You mentioned that you have upgraded your kernel but didn't mention anything about recompiling the nvidia drivers. You have to redo rerun the nvidia-installer script and recreate the kernel modules each time you upgrade your kernel. When you say you upgraded your kernel twice and it all worked I'm assuming that you rebooted after upgrading/updating your kernel? Since you are using the nvidia-installer from nvidia it wants the kernel source installed so it can create its own modules. Do you have the kernel source installed? If you have the kernel source installed and currently have nvidia drivers installed you should be able to type nvidia-install --update as root at a command prompt and it should run you through the process and indicate a success at the end of the process.
It turns out it was related either to the font path element or the "/root/.Xclients: line 8: /root/.Xclients-default: No such file or directory" error, because I commented out the 'FontPath "unix/:7100" ' from the XF86Config file, and copied my existing .Xclients-localhost..... file to .Xclients-default and EVERYTHING is fine again!!
Still dont understand what happened to cause all this, or what "all this" even was about, but for now I'm glad it's fixed.
This forum is such a great resource! What a lifesaver it has been for a guy trying to dump windows, but who has NO programming experience. Thanks to all!