How to install nvidia drivers?

[JekylHyde]

Hi
i have fedora 16 live usb
How to install nvidia drivers?
i have the *.run file
i click it & nothing happens

another question... in live usb i can't change file permissions?

thanks

[daark.child]

You could try the instructions here .

[Mudgen]

You could try the instructions here .

Yes, that should also be good for F16. Be sure to read the comments, they tell you how to make the settings persistent.

[jayd512]

i have fedora 16 live usb

If this is truly a Live version, you should know that nothing you do now will remain between sessions. You'll need to re-install everything every time tou boot.

another question... in live usb i can't change file permissions?

Live installs are intended to be read-only.

Are you looking to do a full install onto a USB drive?

[Rubberman]

1. FC16 will use the nouveau (open source nVidia) driver by default for systems with nVidia cards. Most of the time, this will work fine - nouveau is constantly getting better. Myself, I still use the proprietary driver on my workstation (nouveau on my laptop), but then you will have to reinstall the driver whenever you update the kernel. That's a PITA, but RH doesn't update the kernel more than once a month...
2. In order to install the proprietary nVidia driver, you need to install the OS on your system and boot that - not the Live CD/DVD/USB image.
3. When you download the .run file, it doesn't have execute permissions, so you have to change permissions to run it: chmod +x filename.run
4. You need to run the installation script as root.
5. You need to run the installation script in runlevel 3 (text mode - no X server running).
6. You need to run the installation script from the directory it is installed into, as in: ./filename.run

[Mudgen]

I've not checked the F15-F16 repolists, but nVidia proprietary drivers were in RPMFusion non-free through F14.

[Rubberman]

I've not checked the F15-F16 repolists, but nVidia proprietary drivers were in RPMFusion non-free through F14.

True, but I have not had much success with them. On the other hand, I've had zero problems (other than an occasional bug) with installing them directly from nVidia. As for occasional bugs, I haven't had issues for almost 2 years now. A few years ago, they had some rendering problems, resulting in big red/black pixel blinks when rendering full-screen/motion videos. That required a bunch of back-and-forths between me and their senior engineers, but that has been resolved for a LONG time now.

[JekylHyde]

1. FC16 will use the nouveau (open source nVidia) driver by default for systems with nVidia cards. Most of the time, this will work fine - nouveau is constantly getting better. Myself, I still use the proprietary driver on my workstation (nouveau on my laptop), but then you will have to reinstall the driver whenever you update the kernel. That's a PITA, but RH doesn't update the kernel more than once a month...
2. In order to install the proprietary nVidia driver, you need to install the OS on your system and boot that - not the Live CD/DVD/USB image.
3. When you download the .run file, it doesn't have execute permissions, so you have to change permissions to run it: chmod +x filename.run
4. You need to run the installation script as root.
5. You need to run the installation script in runlevel 3 (text mode - no X server running).
6. You need to run the installation script from the directory it is installed into, as in: ./filename.run

its not a live cd
i know changes will not be saved on a cd...
but this is a disk on key...you can write into it.
i still can't?

what could i do if i want to run it from usb?
i don't want to install it just yet

[Mudgen]

Is it an iso image burned to a USB key? If so, it's getting loop mounted as an ISO image, and will be read only. I think there's a way to get it semi-persistent as to settings by telling it to create another r/w filesystem, but I've not done it.

[JekylHyde]

Is it an iso image burned to a USB key? If so, it's getting loop mounted as an ISO image, and will be read only. I think there's a way to get it semi-persistent as to settings by telling it to create another r/w filesystem, but I've not done it.

"burned"?
copied with unetbootin-windows-563.exe