This is taken directly from user "pucko" from the nvidia linux forum. I, as well as others, seemed to have a strange issue getting the nvidia drivers to work after a reboot; I followed what he did below, and I got it to work!
So I just installed Fedora Core 3 plus the nVidia drivers on my Amd64, and the result was a system that hang on "Configuring kernel parameters.
Here what I did to fix it:
1) Interrupt Grub from booting, edit the bootparameters with "e"-key, and remove the "rhgb"-parameter from the boot parameters. The continue booting normally. (This will skip the graphical boot in Fedora.)
2) Fedora complains about not being able to start GDM, ignore it and cancel all questions to get to the login prompt.
3) Login as root, enter "init 3" to go to single-user mode. Enter "modprobe nvidia" to load the nvidia-module.
4) Finally, enter "cp -a /dev/nvidia* /etc/udev/devices/" to fix the boot problem.
5) Now just enter "init 5" and you're back in business.
This solved my problem and now it boots fine. Maybe my experience will help others too?
I should mention I don't have an athlon 64, I've got a 32 bit athlon XP, so that doesn't matter.
Second - I could into gnome with the nvidia drivers after that (after editing /etc/X11/xorg.conf and replaceing driver "nv" with driver "nvidia" like you are supposed to do), but when running 3D-accelerated programs, I'd get a strange error that reffered me to the readme file from nvidia. Here's the fix for that, taken right out of the readme file:
Q: OpenGL applications exit with the following error message:
Error: Could not open /dev/nvidiactl because the permissions
are too restrictive. Please see the FREQUENTLY ASKED QUESTIONS
section of /usr/share/doc/NVIDIA_GLX-1.0/README for steps
A: It is likely that a security module for the PAM system may be
changing the permissions on the NVIDIA device files. In most cases
this security system works, but it can get confused. To correct this
problem it is recommended that you disable this security feature.
Different Linux distributions have different files to control this;
please consult with your distributor for the correct method of
disabling this security feature. As an example, if your system has
then you should edit the file and remove the line that starts with
"<dri>" (we have also received reports that additional references to
<dri> in console.perms must be removed, but this has not been verified
by NVIDIA). If instead your system has the file
then you should edit the file and remove the line that lists
/dev/nvidiactl. The above steps will prevent the PAM security system
from modifying the permissions on the NVIDIA device files. Next,
you will need to reset the permissions on the device files back
to their original permissions and owner. You can do that with the
chmod 0666 /dev/nvidia* chown root /dev/nvidia*
This also worked. Make sure
that you not only remove (or just place a '#' in front of) the line that starts with <dri>, but also do the same to the line at the bottem which contains <dri> in it as well. I didn't edit out the latter one the first time around, and as a result, I couldn't login as anything but root when I rebooted! (not sure why). In a nutshell, remove or edit out every line in console.perms that contains "<dri>"
As a side note, aren't these fixes sort of stupid? I mean the fact that you have to do them at all. Not pointing fingers, its just another reason newbies may fear linux.
Could anyone sticky this to the top of the fedora thread for a little while, in case lots of people come looking for a solution?