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

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: 4

1 2 3 4 5 6
    1. Doesn’t work on my desktop with nv-GTX-550Ti, stops at a black screen with a line of “cannot open font file ” any ideas plz?

        • Did what you said, still no luck, same black screen….

          • Okay, then try fix from this bug report.

            First backup your grub.cfg:

            cp /boot/grub2/grub.cfg /boot/grub2/grub.cfg.bak

            Just manually change True to latarcyrheb-sun16 every place it is used as a font name in the following 2 files:


            Then run following command (run following command also if you already have latarcyrheb-sun16 in files):

            grub2-mkconfig -o /boot/grub2/grub.cfg

            Then reboot again and check is it working then?

    2. Help! I have an PAE-kernel and did all things described above, but it does not work. This is what I got after doing so:

      [[email protected] /]# lspci |grep -i VGA
      01:00.0 VGA compatible controller: nVidia Corporation GT218 [GeForce 210] (rev a2)
      [[email protected] /]# fbset -i

      mode “640×480-73”
      # D: 30.720 MHz, H: 36.923 kHz, V: 73.260 Hz
      geometry 640 480 640 480 32
      timings 32552 80 32 16 4 80 4
      rgba 8/16,8/8,8/0,8/24

      Frame buffer device information:
      Name : VESA VGA
      Address : 0xf1000000
      Size : 1245184
      Type : PACKED PIXELS
      Visual : TRUECOLOR
      XPanStep : 0
      YPanStep : 0
      YWrapStep : 0
      LineLength : 2560
      Accelerator : No
      [[email protected] /]# lsmod |grep nouveau
      [[email protected] /]# lsmod |grep nvidia
      nvidia 10227390 0
      i2c_core 28305 2 i2c_i801,nvidia
      [[email protected] /]#

    3. Also, my boot screen and tty2-7 text is HUGE. Seems to be running at a lower res in a small portion at the center of the monitor.

    4. is there a possibility to switch between the two drivers? (including a reboot)

      • Hi Mario,

        It’s possible to switch between Nouveau and nVidia drivers. Do you use custom /etc/X11/xorg.conf?

        • I do not use a custom xorg.conf and I don’t know how to.
          I know I could change driver in the xorg.conf from nvidia to nouveau. But that has lead to many things for me, but not to a working x server ;-)

          • Hi Mario,

            Okay, first you have to revert back to nouveau initramfs:

            mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-nvidia.img
            mv /boot/initramfs-$(uname -r)-nouveau.img /boot/initramfs-$(uname -r).img

            Then backup following config files:

            mv /etc/X11/xorg.conf.d/00-nvidia.conf /etc/X11/xorg.conf.d/00-nvidia.conf.bak
            mv /etc/modprobe.d/blacklist-nouveau.conf /etc/modprobe.d/blacklist-nouveau.conf.bak

            Then make sure that you don’t have nouveau.modeset=0 and rdblacklist=nouveau on /boot/grub/grub.cfg file.

            And if you want back to nvidia then restore nvidia initramfs, configs and grub line.

    5. It would be nice to use nouveau KMS and later change to nvidia. But I dont know if its possible

    6. I followed your instructions to a T for installing the latest nvidia drivers. It was a awhile since I did it before on my laptop, so I wanted tested method for my server. It Failed.

      Something about Plymouth start failed to quit, yada yada. I read the comments and found the backout method. Did that. That failed too. Bad color blocks on screen, drv – channel 1 failed, channel 2 failed . . .yada yada.

      I went back and did the install structions again. Well, this time it worked. Go figure.

      The plus is my monitor is a 1900 x 1024 but was only getting 1280×1024 with default noveau. now i have full resolution with evga geforce nvidia 560 and Dell ST24 LED Monitor.

      Thanks !!

    7. I followed the guide, but I found the nvidia drivers messed up my display for bootup, shutdown, and virtual terminal screens. I kept using it for a few weeks anyways, but now I’ve tried going back to the original drivers.

      After following the guide posted earlier in this thread, I’ve been able to uninstall the nvidia drivers and boot using the initramfs I had backed up, using the same kernel version (3.5.3-1.fc17.i686). But now I’m not sure how to get back to the newer kernel version (3.5.4-2.fc17.i686), since the initramfs I have for it now causes the system to run very slow in addition to the issues I had with the nvidia drivers.

      I’ve checked to make sure the nvidia files are removed and that nouveau isn’t blacklisted, since those things were mentioned in this thread. I’ve recreated the initramfs using dracut, but it doesn’t change anything. Any ideas? Thanks!

      • Hi Baudzilla,

        How did you recreated initramfs after nVidia driver uninstall and did you checked that you recreated 3.5.4-2.fc17.i686 kernel initramfs?

        • I renamed the nvidia versions of the initramfs, appending “-nvidia-broken” to the name. Then I recreated the files using “dracut /boot/initramfs-$(uname -r).img $(uname -r)” while running in the 3.5.4-2.fc17.i686 kernel, and also tried recreating it while running the kernel version that was working by specifying the version explicitly “dracut /boot/initramfs-3.5.4-2.fc17.i686.img 3.5.4-2.fc17.i686”. Both attempts produced the same result.

          • Then it sounds good. Could you also post error(s) what you get when you try boot using newer 3.5.4-2.fc17.i686 kernel?

            And could you post output of following commands when you boot with 3.5.4-2.fc17.i686 kernel:

            lsmod |grep -e nouv -e nvidia
            rpm -qa \*nvidia\*
            • I don’t see anything recent under the Automatic Bug Reporting tool. Here’s the output of those commands.

              [[email protected] ~]$ lsmod |grep -e nouv -e nvidia
              nouveau 814795 0
              mxm_wmi 12727 1 nouveau
              wmi 18273 2 mxm_wmi,nouveau
              video 18504 1 nouveau
              i2c_algo_bit 13065 1 nouveau
              ttm 62705 1 nouveau
              drm_kms_helper 30925 1 nouveau
              drm 215938 3 ttm,drm_kms_helper,nouveau
              i2c_core 28305 5 drm,drm_kms_helper,i2c_algo_bit,nouveau,i2c_nforce2
              [[email protected] ~]$ rpm -qa \*nvidia\*
              [[email protected] ~]$

              Thanks for your help, JR =)

              • Looks good, no nVidia (packages or modules) and nouveau is loaded.

                So only problem now is that your system is slow?

                Could you check your graphics card temperatures? Are they high?

                yum install lm_sensors
                ## Then run sensors command ##
                • The system runs very slow and in a lower resolution. It doesn’t seem to recognize my monitor and System Settings > Displays shows “Unknown”. As a result, it doesn’t recognize my monitor’s native resolution, so I can’t even select that. Additionally, I have the same problems that happened from installing the nVidia drivers, which is that the startup, shutdown, and virtual terminal screens look messed up. More specifically, text appears as blobs and startup shows a messed up looking progress bar at the bottom of the screen. Still, here’s the result of the sensor reading:
                  [[email protected] ~]# sensors
                  Adapter: Virtual device
                  temp1: +40.0°C (crit = +75.0°C)

                  Adapter: ACPI interface
                  Vcore Voltage: +1.39 V (min = +1.45 V, max = +1.75 V)
                  +3.3 Voltage: +3.31 V (min = +3.00 V, max = +3.60 V)
                  +5.0 Voltage: +5.05 V (min = +4.50 V, max = +5.50 V)
                  +12.0 Voltage: +11.90 V (min = +11.20 V, max = +13.20 V)
                  CPU FAN Speed: 1814 RPM (min = 0 RPM, max = 1800 RPM)
                  CHASSIS FAN Speed: 1061 RPM (min = 0 RPM, max = 1800 RPM)
                  CHIPSET FAN Speed: 0 RPM (min = 0 RPM, max = 1800 RPM)
                  CPU Temperature: +35.0°C (high = +90.0°C, crit = +125.0°C)
                  MB Temperature: +31.0°C (high = +70.0°C, crit = +125.0°C)

                  Adapter: PCI adapter
                  Core0 Temp: +35.0°C

                  [[email protected] ~]# Disregard the chipset fan speed as it was replaced with a heat sink years ago.

                  • Looks good too. Did nouveua drivers worked earlier with older kernel? Or is it even working normally now with older kernel?

                    Could you also post output of following command:

                    lspci |grep -i VGA
                    • The nouveau drivers worked and still do work with the older kernel, but ONLY using the initramfs that I had backed up from when I installed the nVidia drivers. I just tried rebuilding the initramfs file for the older kernel using dracut, and that caused it to have the same problems. Restoring the old initramfs reversed the issue again. It seems like dracut is creating bad files. Maybe the info it uses to build the initramfs is bad?

                      I ran the command you gave me under the newer and older kernels and both produced the same result:
                      01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600 GT] (rev a2)

                      • This sounds really strange. Could you post output of following commands example to (http://pastebin.org):

                        cat /etc/X11/xorg.conf
                        cat /etc/X11/xorg.conf.d/00-nvidia.conf
                        cat /etc/modprobe.d/blacklist-nouveau.conf
                        cat /etc/grub2.cfg
                        cat /etc/default/grub
      • Thanks, looks good too.

        What happens if you boot newer 3.5.5-2.fc17 or 3.5.6-1.fc17 kernel?

        • Both of those kernels do the same thing as the others. Now, I can’t remember if I rebuilt the initramfs before rebooting after I uninstalled the nVidia drivers. Could booting off the old initramfs file have corrupted my system?

          • I don’t believe that booting off the old initramfs file have corrupted your system.

            Let’s check more log files to find out that what is problem, could you post output of following commands (after boot) with working system and broken system (to http://pastebin.com):

            cat /var/log/Xorg.0.log
            tail -n 600 /var/log/messages
            • I’ve posted the logs twice, but my posts keep disappearing and I don’t know why.

              • Hi Baudzilla,

                And sorry, your earlier comment was some reason marked as spam. So thanks for the log files and there is very likely the reason causing this problem.

                First question is, do you have any updates if you run simply?

                yum update

                You have following error on broken log file:
                (EE) [drm] failed to open device

                Could you post output of following command:

                for filename in $(ls /etc/modprobe.d/*); do echo $filename;cat $filename; echo;done
                • Yum says no packages marked for update.
                  Here’s the output of that command:
                  # Listing a module here prevents the hotplug scripts from loading it.
                  # Usually that'd be so that some other driver will bind it instead,
                  # no matter which driver happens to get probed first. Sometimes user
                  # mode tools can also control driver binding.
                  # Syntax: see modprobe.conf(5).

                  # watchdog drivers
                  blacklist i8xx_tco

                  # framebuffer drivers
                  blacklist aty128fb
                  blacklist atyfb
                  blacklist radeonfb
                  blacklist i810fb
                  blacklist cirrusfb
                  blacklist intelfb
                  blacklist kyrofb
                  blacklist i2c-matroxfb
                  blacklist hgafb
                  blacklist nvidiafb
                  blacklist rivafb
                  blacklist savagefb
                  blacklist sstfb
                  blacklist neofb
                  blacklist tridentfb
                  blacklist tdfxfb
                  blacklist virgefb
                  blacklist vga16fb
                  blacklist viafb

                  # ISDN - see bugs 154799, 159068
                  blacklist hisax
                  blacklist hisax_fcpcipnp

                  # sound drivers
                  blacklist snd-pcsp

                  # I/O dynamic configuration support for s390x (bz #563228)
                  blacklist chsc_sch

                  # generated by nvidia-installer
                  blacklist nouveau
                  options nouveau modeset=0

                  options b43 nohwcrypt=1 qos=0

                  # Makes the stock fbdev driver work with the kernel driver
                  options udlfb fb_defio=y

                  • Thanks!

                    Run following command:

                    rm /etc/modprobe.d/nvidia-installer-disable-nouveau.conf

                    Then run dracut again with your latest kernel and reboot your system using latest kernel, is it working then?

                    • Yep, that fixed it. Thanks so much for your help! Any idea why that file was named slightly different than what we were searching for?

                      • Excellent! You are very welcome!

                        Do you have ever run nVidia original installer NVIDIA-Linux-x86-xxx.xx.xx.run file? Based on some information it will do the /etc/modprobe.d/nvidia-installer-disable-nouveau.conf file.

    8. Thanks! worked great in my nvidia 7300 LE (1A), the only difference was the name of this package: xorg-x11-drv-nvidia-libs

    9. JR, I probably did run that file. Before I followed this guide, I had tried unsuccessfully to install the driver using the download from the nVidia website. I wasn’t aware it had done anything at all though, since the installer would just fail.

      • Okay, this /etc/modprobe.d/nvidia-installer-disable-nouveau.conf file is likely created by nVidia installer (even the installation failed), because I can’t see this file on RPMFusion packages.

    10. Thank you for the guidance at installing nvidias drivers. It worked perfectly.

    11. Hi!
      One question; after installing the NVIDIA drivers, the animations seem to be slower. Also, it lags a lot when I open the Activities panel. With Nouveau, it doesn’t happen, although installing NVIDIA driver fixed some other problems.
      Is it normal? I have a NVIDIA 9300M GS, and I actually have Fedora 17 with Nouveau because I’m scared to slow my system again with NVIDIA.

      • Hi Joska,

        Nope, it is not normal.

        Normally it should work without problems. I have heard some problems with nVidia drivers and Gnome Shell with earlier nVidia 2XX.XX drivers and nVidia has fixed some Gnome Shell related bugs earlier (based on nVidia Linux driver changelog).

        But based on this information it’s little bit hard to say why you have these types of problems. Did you tested any other desktop than Gnome 3.x?

        • Thank You very much.

    12. Thank you ! This guide worked like a charm. I moved to ubuntu because i had problems with video drivers on Fedora, but now i’m back on Fedora and with this guide i have no more problems with my videocard.

      Thanks again!

    13. Thanks worked a treat on fedora 15 here, however. I spent some time with xev, xbindkeys & xbindkeys configuration ;

      “amixer -c 2 set Speaker 1%+”
      m:0x0 + c:123
      “amixer -c 2 set Speaker 1%-”
      m:0x0 + c:122

      now xev does not show these responses on my usb device, Is there a way to enable this again, as it seems xbind was lost with nouveau?

      • Take that as fedora 17

    14. Worked like a charm for me. With later kernels (really anything from 3.4.X and beyond) I was having laptop suspend/resume problems. With the 3.6.2 kernels the kernel was functioning find but the video system was not and I think it was due to inability of nouveau driver to perform modeset on waking up.

      So going over to nvidia driver fixed all that. The only thing I found was that I had to add

      Option “RegistryDwords” “EnableBrightnessControl=1”

      to /etc/X11/xorg.conf

      in order for brightness control to function properly with nvidia driver.

1 2 3 4 5 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.