Fedora 17 Beta Installed with Nvidia Drivers

[Magickman]

Tried the Pre-Upgrade from 16 first, that didn't work at all, would not boot up after restarting. Lucky me, last night I downloaed Fedora 17 DVD, so I erased the HDD, and installed. Nivida Drivers went right in, and everything else is working fine. Good job, Fedora, this one looks Gold!

[sonoran]

Yeah, after a week or so of update issues F17 seems to have settled down nicely. I leave the nouveau driver in place until the official release just in case I can contribute to reporting problems, but it's good to know the proprietary driver works. So far, though, nouveau is handling everything well - maybe I'll stick with it for F17.

[creating2000]

Tried the Pre-Upgrade from 16 first, that didn't work at all, would not boot up after restarting. Lucky me, last night I downloaed Fedora 17 DVD, so I erased the HDD, and installed. Nivida Drivers went right in, and everything else is working fine. Good job, Fedora, this one looks Gold!

nvidia GeForce GT240,can't support

[VernDog]

Yesterday I installed F17 without cloning the partition. (big mistake). After someone stated that the Guides to Nvidia installation (http://forums.fedoraforum.org/showthread.php?t=204752) that was for F14, F15 and F16 worked, i tried it. Failed big time.

On Ubuntu I always use Nvidia proprietary installs, that works perfectly.

[secipolla]

Hi VernDog, I (and others) am using the 295.40 driver from the rpmfusion repo for F17.
How did it fail for you?

-edit- make sure you have /etc/X11/xorg.conf (if for some reason the package didn't copy it, copy /etc/X11/nvidia-xorg.conf to /etc/X11/xorg.conf).

[VernDog]

Hi VernDog, I (and others) am using the 295.40 driver from the rpmfusion repo for F17.
How did it fail for you?

-edit- make sure you have /etc/X11/xorg.conf (if for some reason the package didn't copy it, copy /etc/X11/nvidia-xorg.conf to /etc/X11/xorg.conf).

I'm not sure what version was installed at the time. I just installed per step: "2. Install the nvidia driver."

I will try again later because I have F17 fully backed up.

[secipolla]

First do step one (update kernel and reboot)
Then step two (I had added the rpmfusion repo from their site beforehand)
yum install akmod-nvidia xorg-x11-drv-nvidia-libs.i686
Now note that above it's a i686 package. That's ok for me as my system is 32-bit, but if yours is 64-bit I would guess that there's a package for it which should be replaced in that command (or just omit the architecture extension).
Third do the step three, then reboot. If X doesn't come up, check that xorg.conf is there as I said before.

After 'all is well' then if you like you can add
GRUB_GFXPAYLOAD_LINUX="1024x768"
in /etc/default/grub (replace with your resolution) and '# grub2-mkconfig -o /boot/grub2/grub.cfg' to get back the plymouth 'bubble'.

[raymon99]

I have Fedora 17 Beta installed. When I install the nvidia drivers Fedora boot hangs at the sendmail service. I have twin Nvidia GTS450 cards and run 3 monitors. Fedora 17 runs fine until I install the nvidia drivers and the sendmail hang on boot occurs. Any suggestions

[gjwalsh]

Hi there:

I am going to assume you have installed both rpmfusion-free-release-branched.noarch.rpm and rpmfusion-nonfree-release-branched.noarch.rpm and that you then ran yum update before doing a yum install of akmod-nvidia and xorg-x11-drv-nvidia-libs.

That accomplished, we then remove/disable the nouveau drivers:
mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-nouveau.img
dracut /boot/initramfs-$(uname -r).img $(uname -r)

Be patient with that last command ... it will take a minute or so.

And .... if it helps, we are running sendmail at the moment as well.

Hope that helps ....

George

[Magickman]

Hi there:

I am going to assume you have installed both rpmfusion-free-release-branched.noarch.rpm and rpmfusion-nonfree-release-branched.noarch.rpm and that you then ran yum update before doing a yum install of akmod-nvidia and xorg-x11-drv-nvidia-libs.

That accomplished, we then remove/disable the nouveau drivers:
mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-nouveau.img
dracut /boot/initramfs-$(uname -r).img $(uname -r)

Be patient with that last command ... it will take a minute or so.

And .... if it helps, we are running sendmail at the moment as well.

Hope that helps ....

George
You are absolutely correct in the Nvidia install method. I have had a few issues, screensaver quit one day, and one day suddenly I had two Ethernet connections, my hardware Ethernet took a powder. A new PCI card fixed that, and still today everything works like new.

I wonder....when Fedora 17 Final is Released, will I have to do a fresh install, or will the BETA version update to Final?

[gjwalsh]

Glad that helped ... I know a lot of frustration of my own, so I defend myself by refusing to deal with any digital gadget that begins with the letter 'i' and anything suggesting a scaled down computer. That gives me hours and hours of extra time to application development.

As for the final Fedora 17 release, that will be updated automatically for you, although you might want to check repositories being used after F17 final. I usually work with the 'final release' until the next beta comes out. Best way I know of to keep track of all the myriad undocumented changes from version to version. That keeps my development packages at cutting edge and the exercise is worth a couple of days of effort every 6 months.

My server is running cleanly and efficiently except for the standard messup with Alsa sound. They seem to get that one right every second release. F16 ran 'out-of-the-box'. F17 can't produce anything. You only have to compare alsa-info.txt for the 2 releases to see the differences. And that, of course, is with the identical hardware.

Ah well .... sound is trivial in my programming environment.

George

[sgage]

The way I've been doing nvidia drivers since 16 is:

install rpmfusion repos
yum install akmod-nvidia

That's it - akmod-nvidia brings everything else in as dependencies Also, if you update your kernel before an appropriate new kernel module is on the repo, it will compile a new one. It's worked very well for me.

[VernDog]

The way I've been doing nvidia drivers since 16 is:

install rpmfusion repos
yum install akmod-nvidia

That's it - akmod-nvidia brings everything else in as dependencies Also, if you update your kernel before an appropriate new kernel module is on the repo, it will compile a new one. It's worked very well for me.

That doesn't work:

sudo yum install rpmfusion repos
...
Loaded plugins: langpacks, presto, refresh-packagekit
fedora/metalink | 8.8 kB 00:00
fedora | 4.2 kB 00:00
fedora/primary_db | 14 MB 02:44
fedora/group_gz | 434 kB 00:04
google-chrome | 951 B 00:00
google-chrome/primary | 1.4 kB 00:00
updates/metalink | 18 kB 00:00
updates | 2.6 kB 00:00
updates/primary_db | 1.2 kB 00:00
google-chrome 3/3
No package rpmfusion available.
No package repos available.
Error: Nothing to do
$ sudo yum install akmod-nvidia
Loaded plugins: langpacks, presto, refresh-packagekit
No package akmod-nvidia available.
Error: Nothing to do

[sgage]

That doesn't work:

sudo yum install rpmfusion repos
...
Loaded plugins: langpacks, presto, refresh-packagekit
fedora/metalink | 8.8 kB 00:00
fedora | 4.2 kB 00:00
fedora/primary_db | 14 MB 02:44
fedora/group_gz | 434 kB 00:04
google-chrome | 951 B 00:00
google-chrome/primary | 1.4 kB 00:00
updates/metalink | 18 kB 00:00
updates | 2.6 kB 00:00
updates/primary_db | 1.2 kB 00:00
google-chrome 3/3
No package rpmfusion available.
No package repos available.
Error: Nothing to do
$ sudo yum install akmod-nvidia
Loaded plugins: langpacks, presto, refresh-packagekit
No package akmod-nvidia available.
Error: Nothing to do


Here's how you install the rpmfusion repos:

yum --nogpgcheck install http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm

[gjwalsh]

If your are dealing with a beta release, why would you choose to install rpmfusion-(free and nonfree)-release-stable over the branched releases???? Once F17 Final is released, you'd want to use the stable releases of fpmfusion.

[sgage]

If your are dealing with a beta release, why would you choose to install rpmfusion-(free and nonfree)-release-stable over the branched releases???? Once F17 Final is released, you'd want to use the stable releases of fpmfusion.

On the one hand, what you say makes sense. On the other hand, doing it the way I suggested yields the following:

[root@miracle ~]# yum repolist
Loaded plugins: langpacks, presto, refresh-packagekit
repo id repo name status
adobe-linux-i386 Adobe Systems Incorporated 17
fedora Fedora 17 - i386 21,724
livna rpm.livna.org for 17 - i386 5
rpmfusion-free RPM Fusion for Fedora 17 - Free 399
rpmfusion-free-updates RPM Fusion for Fedora 17 - Free - Updates 0
rpmfusion-nonfree RPM Fusion for Fedora 17 - Nonfree 168
rpmfusion-nonfree-updates RPM Fusion for Fedora 17 - Nonfree - Updates 0
updates Fedora 17 - i386 - Updates 0
repolist: 22,313

[gjwalsh]

Ignoring the difference in architecture between us, the only material difference shown by repolist are the test-updates present in mine and absent in yours. I have found including them not only works to avoid version conflicts but is also the procedure employed in the rpmfusion.org website itself.