Fedora 17 nVidia Drivers Install Guide (disable nouveau driver) - Comment Page: 2

Looking Fedora 22/21 nVidia Drivers Install Guide? [inttf_post_ad1] This is guide, howto install nVidia proprietary drivers on Fedora 17 "Beefy Miracle" and disable Nouveau driver. This guide works with GeForce 6/7/8/9/200/300 series cards. Fedora 17 nVidia driver installation is not much different from previous Fedora versions. I have tested this guide with a couple computers, so let me know, if you have some problems. Before nVidia drivers installation Check is your nVidia card supported lspci |grep -i VGA ## Example output ## 01:00.0 VGA compatible controller: nVidia Corporation GT218 [GeForce G210] (rev a2) List of Supported NVIDIA GPU Products, your...

194 comments on “Fedora 17 nVidia Drivers Install Guide (disable nouveau driver) - Comment Page: 2

1 2 3 4 6
    1. Great tutorial,
      Worked like a charm new to Fedora also so learning as I go.

      GFX Card: nVidia 9600gt

      Thanks
      Eme

      Reply
    2. Hi,

      I have an Asus N55SF with GeForce GT 555M and I can’t boot into Fedora now. Is there a way to revert these changes? Total noob here btw.

      Reply
      • Hi Random,

        If I check Asus N55 SF, it looks like your computer have NVIDIA Optimus Technology?

        Did you check before installation section? This guide will not work with NVIDIA Optimus Technology.

        If your used nouveua then you can check this revert from nVidia drivers back to nouveau drivers guide. I think that, this should also work, if you used Intel drivers.

        Reply
        • Thanks for the reply.

          Yes, I knew my computer used optimus technology, but I still tried this guide: http://forums.fedoraforum.org/showthread.php?t=280750

          It didn’t work and now it seems my entire Fedora system is messed up, hehe… Although not the end of the world, it stings a bit since I’ve fixed up a few things. I did notice rc-local.service failing, but I can’t imagine that having much to do with it since that is something I’ve already set up from before (and it wouldn’t surprise me if it has failed all the time ever since it was set up, lol).

          A run-down:
          I boot Fedora and am met with “repair filesystem” saying “An error occurred during the file system check”

          It’s a lot of text and looks mostly like gibberish too me.

          I write “exit” and processes starting are listed (rc-local fails) before it gets stuck starting and stopping Mail Transport Client and Agent over and over. Right before that happens there’s an error “[ 74.781969]EXT4-fs error (device dm-2): ext4_mb_generate_buddy:741:group 2, 31244 clusters in bitmap, 65338 in gd”

          When pressing ctrl-alt-delete there’s this error: “Failed to start Plymouth reboot screen” coupled with a few “Bug” “Bad rss-counter state”

          There are more errors here and there and different things happened on earlier boots after following the linked guide…

          Give it to me straight, doc… I have to format and start over, don’t I? :P

          Reply
          • I’ve gained ground, although not much. I tried fsck -y on all linux partitions (which I found by using “blkid”).

            After that I logged in as root through recovery and did the following a few times:
            rm -f /var/lib/rpm/_db*
            rpm -rebuilddb
            yum clean all

            After that I followed the commands you listed to revert back to nouveau drivers, but strangly enough “yum list installed |grep nvidia” didn’t list anything. At any rate I followed through.

            Now the boot stops at starting display manager.

            I feel hope.

            Reply
            • Correction: boot stops right after Started Display Manager (without fail).

              Reply
              • In my desperation I have corrupted the recovery mode… I’m preparing a DVD to attempt and rescue my Fedora system somehow.

                I did the following to ruin it:
                mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-nvidia-broken.img
                dracut /boot/initramfs-$(uname -r)-nouveau.img

                I forgot to end it with $(uname -r)

                Through my live USB I am able to reach the boot partition, only to marvel helplessly on my mistake (I don’t have permission to change anything).

                I need some serious help.

                Reply
                • By now it should be clear that I have no idea what I’m doing xD

                  I did however manage to fix what I did through the recovery DVD I made.

                  Now all that remains are these problems:
                  -On boot it hangs right after [Ok] Started Control Manager
                  -StartX in recovery mode yields error (1), No Screens Found, Nvidia module not found.

                  Reply
                  • I got everything back for seemingly no reason whatsoever by doing the following:

                    I installed akmod-nvidia drivers again and rebooted. Then I proceeded with this:
                    yum remove akmod-nvidia*
                    yum remove xorg-x11-drv-nvidia*
                    rm /etc/x11/xorg*
                    rm /etc/modprobe.d/blacklist-nouveau.conf
                    reboot

                    Now it works. I have no idea why.

                    At least I learned a lot of commands on the terminal…

                    Reply
                    • Hi again Random,

                      I have been while away from computer, but I’m very happy that you got it working again. Actually my recommendation would have been re-installation, because it very hard to solve this styles problems when you can’t access to computer. :) But now it’s not needed… :)

                      So next good Linux lesson might be try Bumblebee with your NVIDIA Optimus, here is Bumblebee installation instruction. If you get it working it would be very nice, if you could write some instructions for other users (to If !1 0 forums) how you did it on Fedora 17. ;)

                      Reply
    3. Brilliant. Worked right away on a Dell Latitude 6420, with a Nvidia NVS 4200M.
      Thanks!

      Reply
    4. I cannot have both intel onboard and Nvidia GeForce 8400GS enabled. Under Fedora14 I have got multiseat using both cards. Thogh F17 is automatic multiseat but neither nouveau nor Nvidia proprietary driver allow me to use both cards.
      Any help?

      Reply
      • Hi masoud,

        Do you have NVIDIA Optimus Technology? Or do you have totally separated cards?

        Reply
    5. Hey JR,
      nice guide, I’m having a problem, on F16 with official nvidia drivers I had the boot screen with text and on a “good” resolution (not sure if 1024×768 or my native resolution 1366×768, I don’t remember). But unfortunately I can’t find how I did it, and I want to do it on fedora 17, the text thing is solved, I only need to set the resolution screen.
      Tks

      Reply
    6. I was trying to install the dev drivers from the Cuda Downloads Nvidia page, and ended up here when trying to figure out why things won’t work. I have blacklisted nouveau as prescribed and cut the new ramfs, but I am not sure if it took. When I reboot and do lsmod|grep nouveau I get some output. How do I know if I successfully disabled nouveau?

      Quadro NVS 4200M

      Reply
      • Hi Derrick,

        Could you post full output of following commands:

        
        lsmod |grep nouveau
        
        lsmod |grep nvidia
        
        Reply
        • lsmod |grep nouveau would give me output.

          I finally got things to work. I think the key was doing an ‘rmmod nouveau’ before doing the ‘dracut’ of the new ram disk. For good measure I added kernel parameters ‘nomodeset rdblacklist=nouveau nouveau.modeset=0’ also, for icing on the cake I added ‘blacklist nouveau’ to /etc/modprobe.d/blacklist

          I believe the direcitons above should be amended to tell you to do ‘rmmod nouveau’ before the ‘dracut’

          Reply
    7. Thanks, worked perfect. I’m a new user with Fedora 17 and Nvidia 8600 GT.

      Reply
    8. Thank you very much for the walk through.

      Instructions worked for;
      DK315 1 CARD (CIRCUIT)…, GRAPHICS…, 128, 7300, LOW ENCRYPTION…, MRMGA10
      DK315 – NVidia GeForce 7300 LE, 128MB, VGA DVI & TV Outs, MRMGA10 for Dell Computers

      Perhaps you can answer a simple (I hope) question???
      I have a Dell JX145 1 PROCESSOR…, 6600, 2.4, 4M, CORE DUO-CONROE…, BURN 2…
      I thought this was a 32-bit system but in the log it reads;
      – Build Operating System: x86-07 2.6.32-220.17.1.el6.x86_64
      – Current Operating System: Linux localhost.localdomain 3.4.4-5.fc17.i686 #1 SMP Thu Jul 5 20:17:29 UTC 2012 i686

      Is this a 32-bit system, versital 32 and 64-bit, or is this an issue?

      Best regards,

      NB

      Reply
    9. The kmod version worked with a GTX 670 while akmod failed to start X. Thanks, Blender is happy again.

      Reply
    10. I’m having trouble trying to use an external display after following your instructions. The nvidia drivers appears to be installed properly, however, under the display settings I only show an “Unknown” display and do not have the option to mirror as I did with the nouveau driver. Any help is appreciated.

      Reply
      • Hi Adam,

        You can try configure X with nvidia-settings:

        
        yum install nvidia-settings
        
        nvidia-settings
        

        Then check “X Server Display Configuration”.

        If this doesn’t recognize your monitors then another way is do configuration manually.

        Reply
        • Nvidia settings did the trick.

          Thanks so much.

          Reply
          • Excellent! You are very welcome! :)

            Reply
    11. so i did as you described and it works when i set my bios to discrete, but if i do optimus it won’t start xserver. it just hangs showing me the services [on] after plymouth

      any fix?

      Reply
    12. Had it working with kernel 3.4.4-5, but when upgrading to 3.4.5-2 and 3.4.6-2 I get error of no screens found.

      I attempted to dracut the 3.4.6, but no luck. Is this a current issue or am I experiencing another problem?

      Reply
      • Hi Sambo,

        Are you using akmod or kmod?

        Reply
        • Thanks for the reply. akmod.

          Reply
          • Okay, could you post output of following commands:

            
            rpm -qa \*kmod\* \*nvidia\* kernel\* |sort
            
            uname -a
            
            Reply
            • rpm -qa \*kmod\* \*nvidia\* kernel\* |sort
              akmod-nvidia-295.59-1.fc17.x86_64
              akmods-0.4.0-4.fc17.noarch
              kernel-3.4.4-5.fc17.x86_64
              kernel-3.4.5-2.fc17.x86_64
              kernel-3.4.6-2.fc17.x86_64
              kernel-devel-3.4.4-5.fc17.x86_64
              kernel-devel-3.4.5-2.fc17.x86_64
              kernel-devel-3.4.6-2.fc17.x86_64
              kernel-headers-3.4.6-2.fc17.x86_64
              kernel-tools-3.4.6-2.fc17.x86_64
              kmod-7-2.fc17.x86_64
              kmod-libs-7-2.fc17.i686
              kmod-libs-7-2.fc17.x86_64
              kmod-nvidia-3.4.4-5.fc17.x86_64-295.59-1.fc17.4.x86_64
              kmodtool-1-20.fc17.noarch
              nvidia-settings-1.0-18.fc17.x86_64
              nvidia-xconfig-1.0-16.fc17.x86_64
              xorg-x11-drv-nvidia-295.59-1.fc17.x86_64
              xorg-x11-drv-nvidia-libs-295.59-1.fc17.x86_64

              uname -a
              Linux xxxxx.xxxxx 3.4.6-2.fc17.x86_64 #1 SMP Thu Jul 19 22:54:16 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

              Reply
              • Some reason you have only kmod-nvidia build for 3.4.4-5 kernel, so you can try to build it for 3.4.6-2 kernel with following command (as root):

                
                /etc/rc.d/init.d/akmods start
                /etc/rc.d/init.d/akmods --kernel $(uname -r)
                

                Then reboot.

                Do you get any errors? If it’s not working then post please output of following commands:

                
                rpm -qa \*nvidia\* kernel\* |sort
                
                uname -a
                
                Reply
                • Thanks so much for you help. I did not have a script in the init.d directory for akmods. /sbin/akmods was able to build for the current kernel and appears to be working perfectly.

                  Is there some typical alternative that works as a service that I have not set up?

                  Reply
    13. I too have issues. The install compeletes without error. Upon reboot, the screen is corrupted, the mouse is responding poorly, mouse clicks take tens of seconds to respond, the screen lags FAR behind what is being typed on the kepboard. Top and system monitor say that nothing else is consuming significant processor cycles (heck only FireFox is running to get this typed!!

      Reply
      • Hi Robert,

        Could you post output of following commands:

        
        rpm -qa \*nvidia\* kernel\* |sort
        
        lspci | grep -i vga
        
        lsmod |grep -e nvidia -e nouveau
        
        uname -a
        
        grep EE /var/log/Xorg.0.log
        
        Reply
    14. The issue was NOT the Nvidia drivers, not Fedora. The card, a GTX480 was DYING a slow death. After replacing with a GTX560 all is well

      Reply
      • Okay, sounds very good, if you got this problem solved. Is this GTX480 card working normally without nVidia drivers?

        Reply
1 2 3 4 6

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Close