Fedora 19 nVidia Drivers Install / Uninstall Guide - Comment Page: 3

Looking Fedora 22/21 nVidia Drivers Install Guide? [inttf_post_ad1] This is guide, howto install nVidia proprietary drivers on Fedora 19 "Schrödinger’s Cat" and disable Nouveau driver. This guide works with GeForce 6/7/8/9/200/300/400/500/600/700 series cards. Older GeForce series cards works with 304.xx nVidia drivers and newer 8/9/200/300/400/500/600/700 series cards works with 331.xx nVidia drivers. Fedora 19 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. 1. Before nVidia drivers installation 1.1 Check is your nVidia card...

129 comments on “Fedora 19 nVidia Drivers Install / Uninstall Guide - Comment Page: 3

1 2 3 4 5 6
    1. I’m having the same issue as Tupac only I used akmod instead of kmod.

      uname -a
      Linux RyanD620.localdomain 3.11.8-200.fc19.i686 #1 SMP Wed Nov 13 16:55:29 UTC 2013 i686 i686 i386 GNU/Linux

      rpm -qa kernel\* \*nvidia\* | sort -V

      lsmod |grep -e nouv -e nvidia

      modprobe nvidia
      modprobe: FATAL: Module nvidia not found.

      lspci | grep VGA
      01:00.0 VGA compatible controller: NVIDIA Corporation G72M [Quadro NVS 110M/GeForce Go 7300] (rev a1)

    2. Hmm…. I am apparently in driver purgatory…

      Mon Nov 18 21:31:51 CST 2013
      [email protected]:#> rmmod nouveau
      rmmod: ERROR: Module nouveau is not currently loaded

      Mon Nov 18 21:31:59 CST 2013
      [email protected]:#> modprobe nvidia
      modprobe: FATAL: Module nvidia not found.

    3. Muhahahaha… GOT IT…

      Mon Nov 18 22:09:17 CST 2013
      [email protected]:#> lsmod | grep nvidia
      nvidia 8545952 53
      drm 230162 2 nvidia
      i2c_core 28619 4 drm,i2c_i801,of_i2c,nvidia
      Mon Nov 18 22:09:31 CST 2013

      First make sure you have your latest Nvidia driver set from;

      You can use wget to grab it from the shell if your GUI is hosed by using
      “wget http://urldownload.blah

      If you are running the KDE-Spin, you will need to absolutely remove the boot information from the kernel boot parameters or this thing will consistently want to boot using that “other” driver.

      It is a witch!! Burn it!! (Thanks JR for the commands here for the Fedora 17 Release as this also works on FC19!)

      ## Backup old initramfs nouveau image ##
      mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-nouveau.img

      ## Create new initramfs image ##
      dracut /boot/initramfs-$(uname -r).img $(uname -r)

      Then after this is done, I rebooted into (Runlvl 3) using using the following;

      ->(Or just add a ” 3″ without quotes to the end of the line with vmlinux)

      Then it turns out that when running the Nvidia install script, it will complain about the “kernel-devel” package.

      So I did a “yum install kernel-devel”

      That and it also complained about the kernel source code (What a whiner.. Complain why don’t ya…)

      So I did the following;
      yumdownloader –source kernel

      Then as if it was not enough of a pain, I then had to give it the path to the kernel “includes”.

      So I ran it with the following;
      ./NVIDIA-Linux-x86-319.72.run –kernel-source-path /usr/src/kernels/3.11.8-200.fc19.i686

      It then seemed to compile just fine and I got dropped back to my shell. I then gave it a reboot command and I got the Nvidia Splash screen! Hooray!!.. She then booted up just fine running the correct driver!

      But now why do I have the old crusty boot screen…???… Hmm… Guess I will leave that for another nights project.. Anyways, good luck to all of you and thanks for the help JR with all of your “if-not-true-then-false” sites as I was able to finally glue this laptop back together.

    4. Well… That was bitter sweet…. It was working for a short time and I was able to play Portal and Half Life on my older than dirt laptop but then I lost my desktop effects after running a “yum update” and upon doing further checking I was able to find the following;

      Nov 19 06:01:47 Poseidon kernel: [ 32.282281] nvidia: module license ‘NVIDIA’ taints kernel.
      Nov 19 06:01:47 Poseidon kernel: [ 32.282284] Disabling lock debugging due to kernel taint
      Nov 19 06:01:47 Poseidon kernel: [ 32.293717] nvidia: module verification failed: signature and/or required key missing – tainting kernel
      Nov 19 06:01:47 Poseidon kernel: [ 32.300162] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
      Nov 19 06:01:47 Poseidon kernel: [ 32.300613] [drm] Initialized nvidia-drm 0.0.0 20130102 for 0000:01:00.0 on minor 0
      Nov 19 06:01:47 Poseidon kernel: [ 32.300622] NVRM: loading NVIDIA UNIX x86 Kernel Module 319.72 Wed Oct 30 16:52:15 PDT 2013

      I am really starting to think that the newer Nvidia drivers and Linux are really not playing nice together. This is kind of sad if this is the case as OpenGL was the cornerstone of the Nvidia world in Linux for a long time. I am not sure how they could have botched that one up. I am going to do some additional research but it seems that the kernel does not like the driver for some reason.

      • Hi Benand1985,

        Did you get kernel update when you update your system?

    5. Disregard my previous post (that’s still waiting to be moderated). I solved my issue. In my case I hadn’t installed kernel-devel so akmod couldn’t do it’s thing. Once I installed kernel-devel and rebooted everything worked fine.

    6. Hey JR,

      Really appreciate your guides and the help you’ve given me in the past.

      I have the drivers working on my Fedora 19 box running KDE. But I can’t get openGL to work. I’m not sure if you might have some ideas or maybe I just need to get a new video card. I am using an older card.

      glxinfo gives an error (“X Error of failed request: BadWindow (invalid Window parameter)”

      I am running the nvidia driver and everything looks great – but certain software that uses certain openGL stuff will cause the system to completely lock up. For instance I can’t run Amarok with the analyzer plugin running. I can’t run Kivy stuff, the emulator for the Android SDK, and so on.

      Here is some of the output you usually ask people for.

      lsmod |grep -e nouv -e nvidia
      nvidia 10622789 23
      drm 278576 2 nvidia
      i2c_core 34242 4 drm,i2c_i801,nvidia,videodev

      lspci | grep VGA
      01:00.0 VGA compatible controller: NVIDIA Corporation G86 [GeForce 8300 GS] (rev a1)

      uname -a
      Linux jr-acerdesk.eeaoa.net 3.11.8-200.fc19.x86_64 #1 SMP Wed Nov 13 16:29:59 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

      rpm -qa kernel\* \*nvidia\* | sort -V

      I appreciate any suggestions if you have time to look at this. And again – really appreciate the guides. I use a lot of them.

      • Hi JR Peck,

        First, all your outputs look good, so nvidia driver is successfully installed.

        Do you use custom xorg.conf?

        Could you also post /var/log/Xorg.0.log to http://pastebin.com ?

    7. I am running Fedora 19 with kernel 3.11.8-200 (x86_64 version). I have a G84 (GeForce 8600GT) (rev a1) NVIDIA graphic card. So, I installed akmod-nvidia and xorg-x11-drv-nvidia-libs, following the instructions shown in this thread. I got the NVIDIA “moving bar” splash screen during the bootup but the system failed at the KDE login. Question #1:
      Do the nvidia drivers work fine with 3.11.8 linux kernel on fedora 19?
      I uninstalled the nvidia drivers according to the instructions here but I still had the NVIDIA splash “moving bar” screen. KDE came up but it was without the nouveau driver and the resolution was 1024×768 max. I reinstalled nouveau but to no avail. Finally, I found that in /boot/grub2/grub.cfg, the linux line had been modified with some comments appearing to blacklist nouveau. After removing everything following “rhgb quiet” on that line the system worked fine with the nouveau driver. [I recommend to backup /boot/grub2/grub.cfg before installing the nvidia driver, just in case]. Those additional instructions found in the linux line did not show up in /etc/default/grub. Question #2: Does the installation modify /boot/grub2/config directly and not /etc/default/grub?

    8. ERRATA: Question #2 is: Does the installation modify /boot/grub2/grub.cfg directly and not /etc/default/grub?

    9. I am having the problem with the nouveau modules loaded so Nvidia drivers are failing to load. But I am using UEFI boot to boot the latest kernel directly. So how do I prevent the nouveau modules from loading?

    10. Hello JR,

      Sorry for the delay, I have had a lot of things going on as of late which have pooled my attention. In turn, with family, thanksgiving and Bitcoin I have had my hands tied. However, you are correct, after running a “yum update” on the system it seems that the newer kernel was downloaded and installed from what I could tell and it seems that with the current Nvidia drivers, there are known issues with the current Fedora kernel. I have been looking for a good way to work around the problem but I have been coming up short for what I can do. It is kind of sad if you think about it as I would have thought there would be better Q/A on the Nvidia side before releasing something with a possible kernel conflict.

      Anyways, any input you could provide would be awesome.

      • Hello Benand,

        And sorry for delay too, I have also been very busy now…

        If there is some problems with current kernel, then easiest work around is use latest working kernel, until problems are fixed. If your computer is behind nat (normally desktops are) or you are not running any public services, then even missing kernel security fixes/patches shouldn’t be big problem.

        Please let me know, if you get it working or if you have more problems. :)

    11. Yeah… I am going to get it to the point where it was working and I will add the following into my yum.conf to prevent the kernel updates;

      exclude=php* kernel*

      I guess I will have to wait for Nvidia to get their stuff fixed. It seems that there has been a lot of driver updates and changes causing issues pending the release of the new Steambox. It seems that AMD(ATI) and Nvidia have been going crazy trying to compete for the hardware composition of the new system. It is just unfortunate is it seems that not testing things is starting to reflect negatively for the Linux community.

    12. Hi,
      I just installed fedora 19 on my laptop (Dell, windows 7), the reason being to use a test version of VMD package. However, I am getting some erros and it looks like it has to do with the graphics card.
      Following is the information about my graphics card:
      lspci |grep -i VGA
      00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
      01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 525M] (rev a1)

      can some one help me?


    13. I won’t get into why, but, I was having trouble with nvidia drivers, so, i UnInstalled according to directions.

      Nouveau was not reenabled. i did the lsmod | grep -e nouv -e nvidia and got nothing.

      So, reboot, same thing. then i did a modprobe nouveau and I see it loaded after the lsmod command again.

      reboot, nothing.

      modprobe nouveau
      then startx, nothing

      i am desperate.

      i cannot figure out why the latest kernel update and nvidia updates hosed my system.

      i thought going back to nouvea would be trivial but it’s not.


    14. when i try to use the akmod nvidia driver i get the whitescreen. lookinhg at the /var/log/messages i see that dkms_autoinstaller has an error.

      i just wanta system that works. nvidia isnt working and i cant seem to get back to nouveau

    15. This gonna break ur system if u have latest 3.11.10 kernel…my fed box won;t boot after the installation…it says[failed]Failed to start GNOME Display Manager

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.