Nvidia driver

nvidia-settings
Oh no, another Nvidia driver repository? Why?

This driver reflects my personal view for the way the driver should be packaged for Fedora and CentOS/RHEL. It’s somewhat different from ELRepo repositories for RHEL/CentOS and from RPMFusion packages for Fedora.

What’s different?

First of all the packaging is a lot simplified; more stuff is compiled from source, smaller packages and more options. This packages try to comply as maximum to the Fedora Packaging Guidelines; which means they have debuginfo packages, default Fedora’s GCC compile time options (where possible) and standard locations for binaries, data and docs.

Here is a list of all the “differences” from the various Nvidia driver packages that I was able to spot on the web.

Packaging

  • nvidia-settings, nvidia-persistenced, nvidia-xconfig and nvidia-modprobe are compiled from source.
  • All RPM filters except for GL and OpenCL libraries have been removed, so there is no weird dependency option in the SPEC file. RPM pulls in all correct requirements on its own. This is to avoid pulling in the Nvidia drivers instead of the Mesa libraries or in place of the new open source OpenCL support that’s in Fedora.
  • Simplified packaging with much simpler and readable SPEC file.
  • Dependency on libva-vdpau-driver. So in Totem, or any other libVA supported application you can benefit from VDPAU acceleration.
  • Sources are generated with a script and inserted individually in the various packages; so it can be easily reproduced just by changing the version and rerunning the script.
  • armv7hl support is included in Fedora 20+ packages.
  • nvidia-xconfig is not required on anything that uses the modular X.org directives, as it writes too much in the configuration file (keyboards, monitors, etc.) and the required entries should be written in separate configuration files under /etc/X11/xorg.conf.d. The package is still available as it’s required to speed up some configuration like multi-monitor setups with SLI Mosaic enabled from the command line, but not installed by default.
  • The NVIDIA OpenGL-based Framebuffer Capture (NvFBCOpenGL) libraries (NvFBC and NvIFR) are private APIs that are only available to NVIDIA approved partners for use in remote graphics scenarios (i.e. Steam In-Home Streaming hardware encoding); so they are packaged in another small package called nvidia-driver-NvFBCOpenGL.
  • The nvidia-settings package now builds the external libXNVCtrl.so library that can be used to control the graphic cards through the NV-CONTROL extension. This library updates the old and obsolete one in Fedora based on drivers version 165.
  • Starting from version 343.13, the nvidia-settings binary is compiled with GTK3 instead of GTK2 on Fedora and RHEL/CentOS 7+.

Versioning

  • ELRepo ships 32 bit compatibility libraries in a separate package with x86_64 as the architecture and “32bit” in the name. 32 bit libraries should be like in RPMFusion, with an i686 package installable in parallel with the x86_64 one. There are no other packages in the distribution that are built for x86_64, with “32bit” in their name that contain i686 binaries (!), so Nvidia drivers should not be an exception. So no separate “32bit.x86_64” package for 32 bit libraries also on CentOS/RHEL; just install nvidia-driver-libs.i686.
  • Versions are not hidden; all packages have the same driver version.
  • No alternatives system, only the latest version which integrates CUDA support is available. For older releases nouveau works great; and anything below a GeForce 8xxx it’s in my opinion too low end to play anything modern. And Quake 3 and Doom 3 work greatly with nouveau, so that’s not a case!
  • The CentOS/RHEL repository contains the “Long Lived Branch version” where less changes occur; while Fedora repositories contains the “Short Lived Branch version”. Beta CentOS/RHEL and Fedora’s rawhide repositories will contain the “Beta Branch version”

CUDA support

  • CUDA libraries/tools for the driver are split into subpackages. There’s no need to install all the CUDA libraries and tools on a system that has only one adapter and is used for occasional gaming or for simple office use. This can save ~100 MB worth of installed libraries. nvidia-persistenced falls in this category as it’s not neeeded on a normal laptop or gaming system.
  • Complete packaged CUDA stack has been added for all supported distributions, all the packages provide/require/obsolete the relevant packages in the Nvidia CUDA repository; so you can enable this repository along with the official Nvidia CUDA one (x86_64 systems only).
  • Includes the GPU Deployment kit to the repository. This is constructed with NVML (NVIDIA Management Library) included with the drivers plus headers, docs and samples from a separate tarball. The separate tarball is using a different version number than the drivers. This is packaged in the nvidia-driver-NVML and nvidia-driver-NVML-devel packages. Installing these, the gpu-deployment-kit dependency provided by the CUDA repositories is preserved.
  • Along with NVML, the nvidia-healthmon and nvidia-validation-suite package is provided to monitor TESLA GPU clusters (x86_64 systems only).
  • Included is also the NVENC (Nvidia Encoder) header, docs and code samples. Again, this uses a different version than the drivers.

Kernel modules

  • Multiple choice of kernel module packages; akmod (RPMFusion) for Fedora and binary kmod (Kernel ABI whitelists) for CentOS/RHEL. In addition to this, on both distributions dkms packages are available. This way all cases and personal preferences are covered for both distributions.
  • Starting of drivers version 331.17, the kernel module packages contain the main Nvidia kernel module (nvidia.ko) but also the Unified Memory kernel module and support for multiple kernel modules as specified by the Nvidia documentation. These are optional and can be configured manually for CUDA enabled systems that need to address a specific GPU or to share memory between the CPU and GPU in CUDA programs.
  • When building instantiated kernel modules (up to 352.xx); both akmod and dkms packages can be configured to build the additional modules instead of the single one, so you can still choose your preferred method.
  • Starting from Nvidia driver version 334.16, the Nvidia DDX driver for X can also rely on the nvidia-modprobe command in the system to create devices and set permissions, so the new optional package has been added.
  • The nvidia module has a soft dependency on the nvidia-uvm module, making sure the module is loaded when installing the nvidia-driver-cuda package, but making sure that these modules are not included in the initrd (thing that would happen with systemd configuration (module-s-load.d). UDev rules make sure the module has proper permissions.
  • On Fedora, the kernel modules are compressed with XZ, like all the other kernel modules.

Default configuration

  • Dracut options are depending on the distribution; so no more “vga=normal is an obsolete option” at boot. Each distribution gets its own specific GRUB options for booting.
  • 96 DPI is written in the default xorg.conf config file. Why? Gnome 3 by defaults hard-codes a 96×96 DPI resolution, most of the free drivers do (intel, nouveau, etc.) as the EDID is almost never reliable (please see the excellent Adam’s Jackson post where he explains this). As an example, if you install the Nvidia drivers on a RHEL/CentOS 6 laptop where you used to have nouveau installed (96 DPI hardcoded), the fonts gets 90% of the time supersize and ugly as Gnome 2 and the Nvidia driver do not hard-code 96 DPI like Gnome 3.
  • Make X.org NVIDIA Files section to be loaded latest in case there are other packages providing a custom Files section.
  • Starting from Fedora 21, all driver X.org configuration can be managed by simply adding/removing X.org configuration snippets in /etc/X11/xorg.conf.d.
  • Use new OutputClass directive on Fedora 21 X.org server 1.16 (and later) to load the driver and do not rely on an edited /etc/X11/xorg.conf file. This also removes editing of the xorg.conf file from the package scriptlets.
  • Add the IgnoreABI directive by default on Fedora rawhide builds.

Kernel modesetting and Wayland support

Kernel mode setting on the nvidia-drm module has been disabled by default for various reasons. First of all, Wayland support in the drivers require a patched Wayland which has been refused upstream, and then the driver itself does not expose an FB driver for the console, so you won’t see any difference in the terminal output, you will still be limited to VGA.

There is a proposal for sorting everything out at XDC 2016 for hardware vendors that require to expose extensions for the drivers.

The Wayland libraries are still included in the Fedora builds, as all the dependencies are there but they are not used. On CentOS/RHEL 7 pacakges, they are not included as this would result in missing dependencies.

Distribution and Nvidia driver version support

Here is a rundown of Nvidia supported drivers and options split by distribution. Basically, CentOS/RHEL will always get a Long Lived branch release if possible, Fedora always a Short Lived branch release, and unreleased distributions will always get a Beta driver.

Operating systemel6 / el7f23 / f24f25
Driver branchLong LivedShort Lived
Long Lived
Beta
Short Lived
Long Lived
Driver version367.35367.35367.35
NVENC6.0.16.0.16.0.1
NVML352.79352.79352.79
Architectures:

i686
x86_64
YesYesYes
Basic nvidia driver:

nvidia-driver
nvidia-driver-libs
nvidia-libXNVCtrl
YesYesYes
CUDA libraries and tools:

nvidia-driver-cuda
nvidia-driver-cuda-libs
nvidia-driver-NVML
nvidia-persistenced
YesYesYes
OpenGL Framebuffer Capture:

nvidia-driver-NvFBCOpenGL
YesYesYes
Nvidia tools:

nvidia-healthmon (x86_64)
nvidia-validation-suite (x86_64)
nvidia-modprobe
nvidia-settings
nvidia-xconfig
YesYesYes
Binary kernel
modules (kABI):

kmod-nvidia
YesNoNo
DKMS kernel
modules:

dkms-nvidia
YesYesYes
aKMOD kernel
modules:

akmod-nvidia
NoYesYes
32 bit compatibility on x86_64:

nvidia-libXNVCtrl
nvidia-driver-libs
nvidia-driver-cuda-libs
nvidia-driver-NVML
YesYesYes
Development

nvidia-driver-NVML-devel
nvidia-driver-devel
nvenc
nvenc-samples
libvdpau-devel
YesYesYes
GLVND libraries

libglvnd (compat)
libglvnd-server-module
libglvnd-devel
NoYesYes
VDPAU libraries

libvdpau
1.1.11.1.11.1.1

Along with the CUDA tools and libraries:

Operating systemel6 / el7f21 / f22 / f23
CUDA branch/version7.5.187.5.18
Basic CUDA libraries/tools:

cuda
cuda-libs
cuda-extra-libs
YesYes
CUDA development:

cuda-cli-tools
cuda-devel
cuda-docs (noarch)
YesYes
Java GUI programs:

cuda-nsight
cuda-nvvp
YesYes
Static libraries

cuda-static
YesYes
Samples

cuda-samples
YesYes

Sample installation on an office laptop

Here is an example on my Fedora laptop at work:

# dnf install nvidia-driver dkms-nvidia
Dependencies resolved.
================================================================================
 Package               Arch      Version                 Repository        Size
================================================================================
Installing:
 dkms-nvidia           x86_64    2:367.27-1.fc24         fedora-nvidia    6.1 M
 libglvnd              i686      0.1.0-3.8277115.fc24    fedora-nvidia    209 k
 libglvnd              x86_64    0.1.0-3.8277115.fc24    fedora-nvidia    206 k
 libva-vdpau-driver    x86_64    0.7.4-14.fc24           fedora            61 k
 libvdpau              i686      1.1.1-3.fc24            fedora            35 k
 nvidia-driver         x86_64    2:367.27-1.fc24         fedora-nvidia    3.1 M
 nvidia-driver-libs    i686      2:367.27-1.fc24         fedora-nvidia     16 M
 nvidia-driver-libs    x86_64    2:367.27-1.fc24         fedora-nvidia     14 M
 nvidia-libXNVCtrl     x86_64    2:367.27-1.fc24         fedora-nvidia     25 k
 nvidia-settings       x86_64    2:367.27-1.fc24         fedora-nvidia    939 k
 
Transaction Summary
================================================================================
Install  10 Packages
 
Total download size: 40 M
Installed size: 174 M
Is this ok [y/N]:

As you can see, this system has dkms enabled kernel module and libraries for running 32 bit applications. The amount of data to download for the drivers is really small compared to packages that contain CUDA libraries and tools. And no nvidia-persistenced or multiple kernel modules.

All packages have Epoch set to 2; so they should never be upgraded on your system when you enable this repository along the RPMFusion or ELRepo ones.

Repository installation

To install the repository on a supported Fedora distribution, run as root the following command:

dnf config-manager --add-repo=http://negativo17.org/repos/fedora-nvidia.repo

To install the repository on CentOS/RHEL:

yum-config-manager --add-repo=http://negativo17.org/repos/epel-nvidia.repo

Package installation

If you are booting the system in UEFI mode; as a prerequisite to installing any external module (not built into the kernel package), you have to disable UEFI Secure Boot in the system configuration. All modules contained in the kernel package are signed with keys that are generated during build and deleted when packaging. If you want to preserve Secure Boot, you need to sign the modules yourself and import the keys into your hardware module. Doing so is out of scope here; if you need a decent guide just follow Red Hat’s guide for signing kernel modules.

First of all remove all the Nvidia drivers you might have on your sistem due to RPMFusion, ELRepo, or the Nvidia CUDA repository. The packages should already take care of this for you, as they should be completely compatible; but better be safe than sorry. This is usually accomplished with the following root command:

yum -y remove \*nvidia\*

Then, to install the nvidia-driver packages in Fedora or CentOS/RHEL, perform the following command:

yum -y install nvidia-driver

Specific driver installations

For both Fedora and CentOS/RHEL distributions it’s possible to install additional packages and / or variant of the basic kernel modules. This paragraph contains some examples.

Make sure you have the RPMFusion repository enabled if you plan to use AKMOD kernel modules:

yum -y install nvidia-driver akmod-nvidia kernel-devel

Requirement on kernel-devel is required as otherwise the package kernel-debug-devel is pulled in automatically in place of the normal non-debug package.

To install in CentOS/RHEL with the binary kABI (Kernel ABI whitelist) module:

yum -y install nvidia-driver kmod-nvidia

To add 32 bit libraries on a 64 bit system (for games or applications like Steam):

yum -y install nvidia-driver-libs.i686

To use the Nvidia driver with the DKMS enabled kernel module (on CentOS/RHEL it requires the EPEL repository being enabled):

yum -y install nvidia-driver dkms-nvidia

CUDA installations

To install just a runtime CUDA support (required for running CUDA enabled programs):

yum -y install cuda nvidia-driver-cuda

To install packages required for enabling CUDA development:

yum -y install cuda-devel

or, if you need also NVML / GPU Deployment kit libraries:

yum -y install cuda-devel nvidia-driver-NVML-devel

Enabling multiple (instantiated) kernel modules (up to driver 352.xx)

Version 325 and newer of the drivers support multiple kernel modules for driving multiple GPUs in a single system. According to the documentation; this helps when separate GPUs are intended to process independent workloads in a single system.

Multiple kernel modules are supported on the DKMS and aKMOD variant of the kernel packages. Binary kMOD packages are not generated for RHEL/CentOS as the required kernel symbols are not inserted in the package at build time and would result in a ~100 mb download of kernel modules even if the system is used for normal desktop usage.

aKMOD support

To enable building your aKMOD package with support for multiple kernel modules, as root create the /etc/rpm/macros.nvidia file with the following contents:

echo "%_nv_build_module_instances 8" > /etc/rpm/macros.nvidia

By changing the number in the macro, you can have your desired number of multiple kernel modules (up to 8). This is taken from the default RPMFusion package behaviour for the exception that the original nvidia.ko and nvidia-uvm.ko modules are not built due to compatibility with the multiple kernel modules variant.

To rebuild the kernel module package, remove the current kmod-nvidia-kernel_version package and rebuild it with the following root command:

akmods --force

To revert to the single kernel module just remove the /etc/rpm/macros.nvidia file.

DKMS support

Enabling your DKMS setup to build multiple kernel modules requires you to create the /etc/dkms/nvidia.conf configuration file that contains overrides for the default DKMS configuration recipe. As root, perform the following command using the driver version as appropriate:

cp /usr/src/nvidia-<version>/dkms-nvidia-multi.conf /etc/dkms/nvidia.conf

By editing the file, you can have your desired number of multiple kernel modules (up to default of 8). To reduce the number of modules, just remove the extra lines; the file is pretty self explanatory. The file takes care of not building the nvidia.ko and nvidia-uvm.ko modules; due to compatibility with the multiple kernel modules variant.

To rebuild the kernel modules, rebuild them with the following root command:

dkms install -k <kernel_version> -m nvidia -v <version> --verbose

To revert to the single kernel module just remove the /etc/dkms/nvidia.conf file.

Bugs

Just open an issue to the specific package on Github.

485 thoughts on “Nvidia driver

    1. I personally think Bumblebee is a hack. I support the official Nvidia implementation (i.e. X.org configuration) or the fully open Prime solution.

    1. akmods already requires the latest kernel-devel package; there’s nothing to be installed separately. You can check by running rpm -q --requires akmods.

  1. I’m probably missing something obvious but will this support Optimus cards and allow switching / powering off and using external monitors?

    1. It’s written in the page, if you use the OpenSource (intel and nouveau) drivers and kernel 3.12+, dynamic power on/off of the cards works out of the box. The card of course will not power off if you’re using the external monitor.

  2. I have this weird situation (that I’ll admit I haven’t fully debugged yet) With the nvidia package from nvidia.com everything works.

    After installing your drivers (and reinstall xorg and various other things) I can log in if I init 3, startx. But the gdm menu either doesn’t come up or when it does logging in as a user gets a bunch of white boxes or full white screen. Any ideas where to start looking?

    1. We ran into the same problem at work–
      sudo vim /etc/gdm/custom.conf
      and uncomment the #WaylandEnable=false line
      This was part of the fix for us.

      1. Actually on Fedora 22, the login screen/session work like follows:

        – If using the OSS drivers, GDM is launched on wayland
        – After login, the Xwayland servers for compatibility are launched as user processes

        If disabling Wayland:

        – If using the OSS drivers, GDM is launched as user “gdm” and not “root”
        – Desktop session is run on another X process start as the user who logged in and not “root”

        If using binary drivers:

        – The system detects it and both GDM and user sessions have X running as “root”

        So actually it should not be needed to explicitly disabling wayland in GDM.

  3. i’m using an old quadro nvs card to drive four displays via xinerama (no twinview at all). i’m using the rpmfusion driver setup. lately i’ve run into a bizarre problem where the display locks (while displaying vibrating patterns) and then often triggers a crash/reboot. the logs are devoid of anything interesting or useful. i’m interested in trying your setup. is it safe and easy to switch back & forth between rpmfusion and your setup? will my xorg.conf file get clobbered/rewritten?

    1. Hello, it’s easy to switch back and forth using akmod, just backup your xorg.conf file:

      cp /etc/X11/xorg.conf /etc/X11/xorg.conf.working
      yum -y remove \*nvidia\*
      yum -y install nvidia-driver
      cp -f /etc/X11/xorg.conf.working /etc/X11/xorg.conf

      But if your problem is due to the binary driver; unless you change the driver itself there will probably be no benefit. If the versions I’m hosting are the same as RPMFusion ones, then you will have the same problems for sure.

  4. So where’s the libcudart.so.5.5 for 64-bit.

    I keep getting:
    error while loading shared libraries: libcudart.so.5.5: wrong ELF class: ELFCLASS32

    1. That’s part of CUDA 5.5, which I’m not packaging. It seems you’re loading the 32 bit libcudart.so.5.5 in your 64 bit environment.

      1. Thought it was a negativo17 repo problem because it happened when I did yum update…

        But something about this started to sound familiar so I went back through my notes. Managed to find that I had this problem before and found my fix: (so I’m good now)

        sudo ln -sf libcuda.so.340.24 /usr/lib64/nvidia/libcuda.so
        sudo ln -sf libcuda.so.340.24 /usr/lib/nvidia/libcuda.so
        
        sudo rsync -arv /usr/local/cuda-5.5/lib64/* /usr/lib64/nvidia/
        sudo rsync -arv /usr/local/cuda-5.5/lib/* /usr/lib/nvidia/
        
        sudo ldconfig
        1. First of all, this has nothing to do with libcudart libraries error you were referring to. Second, this is all wrong as you’re duplicating libraries all over, including linking x86_64 in i686 folders.

          To find the library you are requiring type the following command:

          # yum provides \*libcuda.so

          This will tell you that it’s in the nvidia-driver-devel package; so assuming you are on an x86_64 system, the only thing you need to do to have the library on the system is to do the following:

          # yum install nvidia-driver-devel nvidia-driver-devel.i686

          Second step is to make sure your system can find the CUDA libraries. Copying the libraries you require somewhere else is totally wrong. You actually need to make your system find the CUDA ones instead.

          Copy the two /etc/ld.so.conf.d/nvidia-lib*.conf files as /etc/ld.so.conf.d/cuda-lib*.conf and replace the contents with your cuda paths.

          Afterwards, rerun ldconfig to rebuild the library cache. Running ldconfig -p | grep library.so will tell you where the system is getting its libraries.

  5. I just installed driver 343.22 on F20 and system fails to boot on graphic mode. I have a 9800 GT, and driver 343.22 release notes state that “removed support for G8x, G9x […] Ongoing support for new Linux kernels and X servers, as well as fixes for critical bugs, will be included in 340.* legacy releases through the end of 2019.”
    Probably a dumb question, but does the G9x above includes the 9800GT? If so, which driver should I download? It seems that there’s no 340-legacy packages yet.

    1. Replying to myself: yep, 9800 GT has been officially labeled legacy with the release of 343.x driver series (full list of cards here). So, I guess I’ll just have to revert back to nouveau until 340xx legacy drivers are available… :-/

      Any ETA?

      1. I’m creating a separate repository for the 340 branch as yours it’s not the first request I receive. Will post it on the blog once it’s ready.

        Please note that today’s games do not run well on old hardware such as the 9800GT, and if you don’t play games and don’t need full hardware acceleration the nouveau driver is more than fine.

        1. The repository has been created. Just grab the appropriate *340.repo file and put it in place in /etc/yum.repos.d.
          To sync you can use the yum distro-sync command.

          Example for Fedora when using aKMOD packages:

          yum-config-manager --disable fedora-nvidia
          yum-config-manager --add-repo=http://negativo17.org/repos/fedora-nvidia-340.repo
          yum remove kmod-nvidia\*
          yum distro-sync \*nvidia\*
          reboot
          1. Wow, that was fast! =) I just installed, and it is working flawlessly. I’m back in the game 😉

            Thank you so much for such awesome support =))

  6. Thks for the info, and for providing support for legacy cards. I will probably upgrade my graphics card in the near future but, in the meantime, being able to use NVidia drivers would be great. I am currently running Nouveau as a workaround, and overall it indeed works fine, but aside from the worse performance, it also has some issues (sometimes it freezes after login on GNOME, Google Sheets doesn’t redraw sometimes on Google Chrome etc.).

  7. So… updated and now I’m getting:

    NVRM: The NVIDIA GeForce 210 GPU installed in this system is
    NVRM: supported through the NVIDIA 340.xx Legacy drivers. Please
    NVRM: visit http://www.nvidia.com/object/unix.html for more
    NVRM: information. The 343.22 NVIDIA driver will ignore
    NVRM: this GPU. Continuing probe…

    Any way to downgrade?

  8. There is a bug in the nvidia-persistenced package. It tries to start /usr/bin/nvidia-persistenced, but the daemon is installed to /usr/sbin/nvidia-persistenced.

    Another question, do you have the “nvcc” program packaged? It normally comes with the cuda installation from nvidia, but I cannot find it with a yum provides search.

    1. Thanks for spotting the mistake, I’m updating all nvidia-persistenced packages now.

      Regarding CUDA binaries; I have packaged the latest CUDA libraries and binaries (6.5.19) and I’m looking for someone to test them before publishing them along with the rest of the Nvidia packages. Are you interested to test them and give some feedback?

  9. For anyone who runs into the same problems I did, trying to run ccminer using this driver package: make sure to install nvidia-driver-devel/nvidia-driver-cuda-libs and nvidia-modprobe, these are not normally brought along with the driver installation. I’m using a cuda toolkit 6.5 installation separate from RPMs as I’m not sure how to compile ccminer with the packaged nvidia-driver-cuda. (I also installed nvidia-driver-cuda for the nvidia-smi binary.) But I am just glad to have an up to date packaging of the driver.

    1. Actually to get all headers required for compiling software against the Nvidia driver libraries you should just install the nvidia-driver-devel package; this will pull in almost all of the original Nvidia tarball:

      $ rpm -q --requires nvidia-driver-devel | grep ^nvidia
      nvidia-driver-NVML(x86-32) = 2:343.22-1.fc21
      nvidia-driver-NvFBCOpenGL(x86-32) = 2:343.22-1.fc21
      nvidia-driver-cuda-libs(x86-32) = 2:343.22-1.fc21
      nvidia-driver-libs(x86-32) = 2:343.22-1.fc21

      The package nvidia-modprobe should not actually be needed anymore (I’m offering it for compatibility reasons) as the main driver gets loaded automatically and the UVM extra module is loaded through an UDEV rule:

      $ rpm -ql nvidia-driver-cuda  | grep uvm
      /usr/lib/udev/rules.d/60-nvidia-uvm.rules

      What is exactly that your setup was missing that needed you to install the nvidia-modprobe package?

      Thanks.

  10. I couldn’t compile ccminer without nvcc so I didn’t try (and it is the only cuda application I use), but sure I can help test when I get some time. Without nvidia-modprobe, ccminer would not run saying that it could not query the number of CUDA devices; I looked up the error and saw calls to nvidia-modprobe so I tried installing it and then it worked. Do you have my email, or IRC?

    1. I have your email, thanks. Will send you the link with the packages (hopefully tomorrow) after reviewing them.

      Many thanks!

      1. I found that nvidia-modprobe is essential for getting libgpuarray installed (which is used for the computation package Theano, for instance) – so there’s some functionality in there that people are relying on…

        1. Can you provide some info/link? On the drivers, it is needed only if the character devices are not available when the driver is initializing.

  11. Hi,
    first of all thanks for packaging the new nvidia driver for fedora!
    Runs fine here on a F20 installation but there is one thing i miss…

    Kernel-RT support.
    The RPM-Fusion driver worked well with akmods enabled to build for the ccrma-kernel but this here is different. Don’t know if nvidia changed something or maybe its the packaging?
    Trying to –force the build give me this errror:
    *** Failed PREEMPT_RT sanity check. Bailing out! ***
    Any Ideas? Things i can try?

    Thanks!

    1. Hello, the kernel module is compiled with IGNORE_PREEMPT_RT_PRESENCE=1. Which driver version are you using? Can you check that this is passed during the build in the logs?

      Also, where is the RT enabled kernel on planetccma? I can’t find it.

        1. Hi,
          i changed the spec file and rebuild the akmod with success. yay!
          Don’t know where you added the option but this way it worked for me:

          for kernel_version in %{?kernel_versions}; do
          %if !0%{?_nv_build_module_instances}
              pushd _kmod_build_${kernel_version%%___*}/
                  make %{?_smp_mflags} \
                      IGNORE_XEN_PRESENCE=1 \
                       IGNORE_PREEMPT_RT_PRESENCE=1 \
                      SYSSRC="${kernel_version##*___}" \
                      module
              popd
              pushd _kmod_build_${kernel_version%%___*}/uvm
                  make %{?_smp_mflags} \
                      IGNORE_XEN_PRESENCE=1 \
                       IGNORE_PREEMPT_RT_PRESENCE=1 \
                      SYSSRC="${kernel_version##*___}" \
                      module
              popd
          %else
              pushd _kmod_build_${kernel_version%%___*}/
                  make \
                      IGNORE_XEN_PRESENCE=1 \
                       IGNORE_PREEMPT_RT_PRESENCE=1 \
                      SYSSRC="${kernel_version##*___}" \
                      NV_BUILD_MODULE_INSTANCES=%{?_nv_build_module_instances} \
                      module
              popd
          %endif

          best regards

  12. Hi,

    Great that you’ve built the 346 beta drivers for fc21, but the 343 packages seem to be gone. Example :-

    yum list *nvidia*
    
    Loaded plugins: langpacks
    Available Packages
    akmod-nvidia.x86_64                                           2:343.22-2.fc21                        fedora-nvidia

    But the install says :-

    No Presto metadata available for fedora-nvidia
    akmod-nvidia-343.22-2.fc21.x86 FAILED                                          
    http://negativo17.org/repos/nvidia/fedora-21/x86_64/akmod-nvidia-343.22-2.fc21.x86_64.rpm: [Errno 14] HTTP Error 404 - Not Found

    I’ll try installing the 346 rpm manually for now

    1. You simply had the old metadata on your computer and I had already uploaded the new packages and metadata on the site. Next time, just delete your yum cache; there’s no need to do anything manual:

      yum clean all
      yum update
  13. I could not build the kernel module for Fedora 21. It says missing auto.conf and autoconf.h somewhere in the middle of the akmod log. My kernel is 3.17.3-300.fc21.x86_64

    Is there a way to fix that or is it possible for you to provide the rpm for the kernel module?

    1. You’re missing the kernel-devel package that matches your system. Follow the instructions on the page and rebuild the modules (akmods --force) or reboot.

      1. I do have the matching kernel-devel
        kernel-devel-3.17.3-300.fc21.x86_64

        I have been using akmods –force successfully with the packages from rpmfusion before. Suddenly it stops working. Not sure if it is the nvidia part or the fedora part that breaks.

          1. I still could not get it compiled with akmods. It turns out not missing those files, but something else that I could not figure out. If you could kindly help, the log is available at

            Click here to see the log

            At the start of the error , it says

            In file included from /tmp/akmodsbuild.w3LHxRAw/BUILD/nvidia-kmod-346.16-x86_64/_kmod_build_3.17.4-300.fc21.x86_64/nv-linux.h:107:0,
            from /tmp/akmodsbuild.w3LHxRAw/BUILD/nvidia-kmod-346.16-x86_64/_kmod_build_3.17.4-300.fc21.x86_64/nvlink-linux.h:14,
            from /tmp/akmodsbuild.w3LHxRAw/BUILD/nvidia-kmod-346.16-x86_64/_kmod_build_3.17.4-300.fc21.x86_64/nvlink.c:13:
            /tmp/akmodsbuild.w3LHxRAw/BUILD/nvidia-kmod-346.16-x86_64/_kmod_build_3.17.4-300.fc21.x86_64/nvlink.c: In function 'nvlink_init':
            include/linux/pci.h:1122:45: error: 'KBUILD_MODNAME' undeclared (first use in this function)
            __pci_register_driver(driver, THIS_MODULE, KBUILD_MODNAME)

  14. Hi, nice packaging.

    Any chance you could also provide ‘legacy’ drivers? Just noticed my card is no longer supported by the latest drivers, only by the 340.xx series…

  15. hello..
    want to try this primarilly in order to use gpu rendering in cycles, cuda being a prerequisit..
    a question pops, excuse my ignorance.. new to .rpm/ yum..
    taken that rpmfusion needs to be added/ enabled, for akmod to work, how do i point to the wanted drivers?? as in, not the rpmfusion ones??
    thanks..

  16. Hello, I have a problem with the new Fedora 21. With the 340 driver, I got stuck on gnome-shell start, just after GDM login.
    Gnome shell hangs with 90+ CPU load and I can’t go beyond a grey screen.

    1. Ok, I fixed it. For anyone having same problem, just remove the ‘gnome-shell-extension-background-logo’ package
      sudo yum remove gnome-shell-extension-background-logo

  17. Hello negativo17. First of all I wanna say thank you for your work. I came here to ask you – how about nvidia driver installation key? I use Fedora 21 with enabled Ultra Fast and Secure Boot UEFI options and I need import key which should be in /usr/share/nvidia/ folder by mokutil. The problem is i cant find him in /usr/share/nvidia after installation driver from your repository. I have to manually download nvidia driver from nvidia’s website, then manually install it and in the installation process choose option to generate key. After that i have to import that key with sudo mokutil --import /usr/share/nvidia/nvidianvidia-modsign*.der then restart computer and add key using Shim UEFI Keys Manager. Where nvidia driver from your repository put the key? Or maybe driver from you repositories doesn’t generate key during the installation process? Please reply me on my email or in the comment below. I’ve marked option “Notify me the new posts”.

    1. Hello, thanks for the information.

      No I haven’t tried doing what you describe. Usually I disable UEFI Secure Boot if using the Nvidia Drivers. I will include required files and instructions on the page.
      How do you “add key using Shim UEFI Keys Manager”? Can you provide the commands?

  18. Hi,

    I just installed F21, and for some reason nvidia driver is not working, gnome just shows that vague error page saying that “something wrong happened”. I have a GTX 750 Ti that was working just fine on F20. Any tips on how to understand what’s wrong?
    I followed the instructions to the letter, the only thing I had to workaround was the installation of kmodtool, I had to disable gpg checking because for some reason rpmfusion is providing the F20 package instead of F21.

    To make matters worse, nouveau is not working, and either I fix this or I’ll have to go back to F20…

    1. Nevermind… I just rebooted today and it just worked 🙂 One of my last attempts to fix the problem probably did it, I guess I was just one reboot away from success 😉

  19. Dude!
    Thanks so much for your comprehensive and clearly worded instructions, and indeed your repos themselves. New Fedora 21 installation this weekend, beating my head against a wall with Nvidia drivers, no 340xx series drivers available in Fusion, 304xx broken and uninstallable. Your 340 repo really came to the rescue.

    Keep up the good work!

  20. Thanks for the great repo!

    I’ve recently switched from Ubuntu to Fedora 21 and I did not want to install RPMFusion just for the Nvidia drivers for my 660ti, so I was surely happy when I found this alternative – I like the clean documentation and you seem to know what you are doing.

    Keep the good work up!

  21. Hi there. Thanks for your great work with the 340xx series driver. It made my laptop usable on Fedora 21, after I’d bashed my head against RPMFusion’s version for hours.

    I was wondering if you’d be willing to apply this patch to the 340xx driver series, or if it was even possible to do given Fedora’s kernel. I have the same issue laid out in the bug where resume-from-suspend causes graphical corruption every time. It’s not too annoying, since I can just “Alt+F2 -> r” and reload GNOME but it’s still undesired behaviour.

    https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1210077

    Or, if you know any way of getting rid of this corruption through a grub/driver setting, that’d be great too!

    Thanks a bunch.

    1. I will rebuild and update when I come back on the 8th of January, I’m currently travelling through Indochina without connectivity. Thanks for letting me know.

    2. Nice! I’ve been suffering with graphical corruption after suspend as well, I thought it could be related to the fact that 346.22 is marked as beta on Nvidia site, but I tried 343.36 from RPMFusion and the problem was still there. Hopefully this patch will fix this problem 😉

    3. Hello, the patch you are pointing to is already included since the 331.67 release. Probably the problem you are experiencing is related to something else.

  22. Hi!

    Just installed:
    dkms-nvidia-346.22.1.fc21.x86_64.rpm
    nvidia-driver-346.22.1.fc21.x86_64.rpm
    nvidia-driver-libs-346.22.1.fc21.x86_64.rpm
    nvidia-libXNVCtrl-346.22.1.fc21.x86_64.rpm
    nvidia-settings-346.22.1.fc21.x86_64.rpm
    nvidia-xconfig-346.22.1.fc21.x86_64.rpm
    from your repository.

    How to configure Fedora to use nvidia driver, since after installation I do not see xorg.conf configuration file in the /etc/X11 folder?

    1. Since Fedora 21 (and CentOS/RHEL 6.6 with newer Xorg) there is no need for an Xorg.conf file. The configuration is using the new “OutputClass” directive (/etc/X11/xorg.conf.d/99-nvidia-driver.conf). Please look at the driver page as I’ve described it there.

  23. Hi there!

    Since I updated with fedup from F20 to F21 my nvidia drivers were missed somewhere in the universe (GeForce 9400M card, so 340xx).

    I followed your guide and I have propietary drivers again. Really you finished one of my worst headaches since long.

    Keep the good work!

  24. Fedora 340 repo is great, works fantastic and it saved me from trouble when I upgraded F20 to F21. You should add a note on blog post that it exists so people would find it easily.

    Thanks for all of this 🙂

  25. how to install 340 ??

    I installed repo “nvidia-repo”
    this command “yum -y install nvidia-driver” install by me driver 346 and this vs dont work.

    please what is theyum command to install 340 vs
    thx

    1. Hello, yes, there is a mistake. The package is only available for Fedora and internal RHEL builds. I’m updating all driver releases/builds with the fix. Please give a few hours for the upload. Thanks for spotting!

  26. Hello..
    First of all thanks for the tutorial and for maintaining the repo..
    Maybe you can help me because I’ve been searching for days for a solution. I have a GTX 650 and since I installed the nvidia driver I simply cannot get graphical boot. I have managed to get grub to the resolution of 2560×1080 bott as soon as fedora starts to boot I get back to an ugly resolution with no graphical boot..
    when I boot the live media I have graphical boot but I guess that’s because it is using the nouveau driver.
    here is my /etc/default/grub:

    GRUB_TIMEOUT=5
    GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
    GRUB_DEFAULT=saved
    GRUB_DISABLE_SUBMENU=true
    GRUB_CMDLINE_LINUX="rd.lvm.lv=fedora_hal-terminal/root rd.lvm.lv=fedora_hal-terminal/swap rhgb quiet rdblacklist=nouveau nomodeset"
    GRUB_DISABLE_RECOVERY="true"
    GRUB_THEME=/boot/grub2/themes/DarkFedora/theme.txt
    GRUB_GFXPAYLOAD_LINUX="keep"
    GRUB_VIDEO_BACKEND="vbe"
    GRUB_FONT_PATH="/boot/grub2/themes/DarkFedora/Droid-Sans.pf2"
    GRUB_GFXMODE="2560x1080x32"
    GRUB_BACKGROUND="/boot/grub2/background.png"

    1. Hello,

      you cannot have graphical boot with the nvidia driver enabled and the PC in bios mode. The nvidia driver expects only vga to be present on the console, otherwise it will throw an error. It can work with vesa on the console, but it’s not supported and you will still get the notice.

      What is supported, is UEFI graphical boot. The system will use efifb for the console and the nvidia driver for the DDX.

      See the table at the end of this article:

      http://negativo17.org/complex-setup-with-nvidia-optimus-nouveau-prime-on-fedora-20/

  27. Hi!

    Can not go forward with nVidia drivers installation. Can you prepare step by step installation instruction?
    I still get the “Oh no! Something has gone wrong.” information.
    There is a lot of information from people who successfully installed nVidia drivers but there is no complete how-to.
    Following steps described here-in or even somwhere else still leads to problem with driver installation.
    I believe that step by step instruction will help people like me to enjoy full features of nVidia drivers under Linux.
    I have installed:
    nvidia-driver-cuda-libs-346.22-2.fc21.x86_64
    nvidia-driver-cuda-libs-346.22-2.fc21.i686
    opencl-filesystem-1.0-2.fc21.noarch
    nvidia-libXNVCtlr-346.22-1.fc21.x86_64
    nvidia-settings-346.22-1.fc21.x86_64
    nvidia-driver-libs-346.22-2.fc21.x84_64
    nvidia-driver-libs-346.22-2.fc21.i686
    dkms-nvidia-346.22-1.fc21.x86_64
    nvidia-driver-346.22-2.fc21.x86_64
    nvidia-driver-cuda-346.22-2.fc21.x86_64
    nvidia-persistenced-346.22-1.fc21.x86_64
    nvidia-xonfig-346.22-1.fc21.x86_64

    I run nvidia-xconfig and as an output I got warning that the X configuration file cannot be locate/open and the xorg-server was not found in the pkg-config search path, however xorg.conf file was created.
    No sucess after reboot.

    1. Hi,

      Don’t know if it will help but, in my case, installation on F21 always went wrong, but simply rebooting after the GNOME error message “fixed” the problem.

      HTH,

      André

    2. The detailed instructions are printed above, there’s not much to add. Just check that your module is built and loaded.

      You can remove all of these:

      nvidia-driver-cuda-libs-346.22-2.fc21.x86_64
      nvidia-driver-cuda-libs-346.22-2.fc21.i686
      opencl-filesystem-1.0-2.fc21.noarch
      nvidia-driver-cuda-346.22-2.fc21.x86_64
      nvidia-persistenced-346.22-1.fc21.x86_64

      You will not need them if you don’t need to run CUDA enabled programs.

      1. I run dkms install -k 3.17.8-300.fc21.x86_64 -m nvidia -v 346.22 –verbose. Drives has been compiled successfully, but after reboot I am still in the same place.
        What I am missing to sucessfully enable nvidia drives?

        1. I have founf in the Xorg.0.log file that the glx module is loaded but it generates errors.
          Module glx )libglx.so) is loaded from /usr/lib64/xorg/modules/extensions folder instead of /usr/lib64/nvidia/xorg folder.
          Probably this is the root cause of my problem. Can you help me to solve this problem? Is it a simple way to fix it?

          1. Hi!

            Found the problem – xorg.conf created in /etc/X11 folder after run nvida-xconfig command made X server impossible to start. After xorg.conf removal and following reboot I can enjoy X server running on nvidia derivers.

            On the other hand. Do I need to reinstall (dkms install etc. …) drivers either if new driver version will appear (now I have 346.22, and new one 346.35 is available) and new kernel version will appear?
            Another question is about snippets in xorg.conf.d folder. Can you post some examples for monitor video card, mouse, keyboard etc. configurations?
            What about snippets order (question in terms of labeling Identifiers) – is it relevant or not?

          2. If you are running Fedora 21, there should be no /etc/X11/xorg.conf, so please delete it and start from scratch if you want to override the default configuration. Remember that unless you are doing something specific, you don’t need to edit xorg.conf directly. Keyboard and mouse sections are particularly useless.

            When updating, the packages will take care of everything, you don’t need to perform any action.

  28. Thanks very much for the hard work. Got my legacy card working with the 340 driver and akmods –force. Finally understand the differences in the different Nvidia drivers.

  29. Hi.

    Some applications in Fedora segfaults with libGL implementation of latest nVidia driver (from this repository). Please see [1] for details. The problem is something I don’t really understand much.

    Do you experience same issue with nVidia driver from this repository?

    Do you experience same issue with nVidia driver from RPMFusion?

    Try to install and run nomacs. It should segfault.

    Thank you.

    [1] https://bugzilla.redhat.com/show_bug.cgi?id=1181085

    1. Sorry but so far I’ve not experienced this. Driver wise, these packages and RPMFusion ones should exhibit the same problems. The driver are shipped in binary format, the difference is only on packaging and on the accompanying tools (nvidia-{settings,xconfig,modprobe,persistenced}.

  30. Hi

    Thank you very much for your great work. Really very helpful.

    I have a fresh Korora 21 Beta 64Bit (remix from Fedora kororaproject.org) installed on UEFI.

    I installed “yum install nvidia-driver akmod-nvidia kernel-devel”.

    Bootings with secure boot enabled produce always a “oh no something went wrong – log out” on GDM. No log-in possible. Access only by console with Ctrl-Alt-F2.

    Disabling secure boot in UEFI for bootings does the trick. Now GDM allows log-in and driver Nvidia 346.35 runs fine.

    Behaviour is reproducible constantly.

    So no secure boot on UEFI possible.

    Please investigate.

    Greetings from cantone San Gallo to Lugano.

    Rgds
    AW

    1. Hello,

      yes, drivers do not work with Secure Boot enabled. There are two ways to resolve this:

      – Rebuild the kernel modules always with the same key, and enroll the key in your system’s key database. I can’t do this for you, as I would need to send you the private key and thus rendering Secure Boot useless.

      – I could ship you a prebuilt binary and the public key only to enroll it, but you could not regenerate the rpm and would require me to sync binary updates along with the official kernel packages; which is almost impossible.

      Unfortunately there is no easy way for this, so my suggestion is not to use the binary drivers if you need Secure Boot enabled. Please see this link with instructions from Redhat:

      https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7-Beta/html/System_Administrators_Guide/sect-signing-kernel-modules-for-secure-boot.html

      And this article that also covers UEFI Secure Boot:

      http://negativo17.org/complex-setup-with-nvidia-optimus-nouveau-prime-on-fedora-20/

  31. Oh oh now I did it. I was working on my conky background layout. I wanted to show the actual clock speed of my 780 Ghz Edition on it. I needed nvidia-smi to show that information. Fedora reported your missing this package, please install (I believe it was) nvidia-cuda. I did and my conky script worked awesome until I rebooted. Fedora 21 would just stop when the blue bars where moving. I went ahead and switch to terminal 2. I removed /*nvidia/* and reinstalled the driver from start again. Now it loads and it crashes at the Gnome start up with a grey screen.

    Can anyone give me some guidance and what I can do to repair and what should I have installed to get the nvidia-smi tool?

    Thanks for any help. Did not sleep very well last night thinking how to fix this today.

    1. Assuming you are using Fedora 21 (you have not specified) you can start by deleting /etc/X11/xorg.conf and rebooting. This should start X with the default settings and load the appropriate driver depending on the new DRM class (see above comments).

      Then, if it does not start anyway look in the logs, module status, etc.

    1. Hmm now that you say that, I think that was packaged i installed originally. While working on the conky script, I let Fedora 21 run some updates. One of them was a new kernel, I believe it moved to 3.18. something. I wonder if that’s what cause all my issues instead of me installing the nvidia-driver-cuda. Thank you so much slaanesh and will keep you posted once I get home from work tonight and let you know what I discover. I really do appreciate everything you do for the Fedora Community.

  32. I’m using Fedora 21 x86_64 with kernel 3.18.3-201 and nvidia 346.35 in my notebook. To be able to use external monitor using HDMI, I followed the standard xorg.conf available in the Internet. But I could only use the external monitor, the notebook monitor is undetected.

    xorg.conf

    Section "ServerLayout"
    Identifier "layout"
    Screen 0 "nvidia"
    Inactive "intel"
    EndSection

    Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "01:00:0"
    Option "ConstrainCursor" "no"
    EndSection

    Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration"
    EndSection

    Section "Device"
    Identifier "intel"
    Driver "modesetting"
    EndSection

    Section "Screen"
    Identifier "intel"
    Device "intel"
    EndSection

    Output of xrandr:

    Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
    HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 1600mm x 900mm
    800x600 60.32 +
    1920x1080 (0x27f) 148.500MHz
    h: width 1920 start 2448 end 2492 total 2640 skew 0 clock 56.25KHz
    v: height 1080 start 1084 end 1089 total 1125 clock 50.00Hz

    Is there a way to enable the notebook screen? Previously before 346, I have LVDS-1 shown and was able to use both the internal and external monitors.

  33. Don’t know if this is important but wanted to report it all the same:

    mplayer: /lib64/nvidia/libOpenCL.so.1: no version information available (required by /lib64/libavutil.so.54)
    MPlayer SVN-r37363-4.9.2 (C) 2000-2015 MPlayer Team
    
    yum provides /lib64/nvidia/libOpenCL.so.1
    2:nvidia-driver-cuda-libs-346.35-3.fc21.x86_64 : Libraries for nvidia-driver-cuda
    Repo        : @negativo17-nvidia
    Matched from:
    Filename    : /lib64/nvidia/libOpenCL.so.1
    1. Thanks, will look into it. ffmpeg is compiled with OpenCL support in the RPMFusion packages.
      Are you using OpenCL for encoding?

  34. Hi there! I want to play CS:GO in my CentOS 7 with NVIDIA Drivers and I can’t install nvidia-driver-libs.i686 because of a missing dependency ( libvdpau(x86-32) ). I have been seeking for a solution but I didnt find it!

    Any idea? Thanks!

  35. Well, slaanesh, I could be no less than thankful to you for posting about nvidia x fedora issues, so common to so many users. But unfortunately your instructions did not solve my problem, which was simply to install the latest nvidia driver. I have tried many of the available solutions without success. My laptop worked with the bumblebee, as per installation instructions in fedora site, but, as you say, bumblebee is a hack. So I returned to the noveau driver, despite all shortcomings. At least I can have my laptop working! Running fedora 21, however, I am still stuck with the bug of two displays and video instabilities already described elsewhere. I have to turn off display 2 every time I log in. Better this than nothing.

  36. Hi,
    many thanks for your great work. Yuor procedure it’s the only one that makes me able to install nvidia driver on my laptop. Anyway after all the installations yuo’ve suggested i’m unable to set my video resolution properly. it’s blocked and setted in a bad value. how could i change it please?
    Thank you so much.

    1. Maybe you have a broken EDID. Try to read X.org man pages (man xorg.conf) and Nvidia documentation (in /usr/share/doc/nvidia-driver) on how to override it.

  37. Hey thanks for the repositories mate! Would you have any idea when the driver will be available for fc22/kernel 4.0*?

  38. Hello,

    I have tried to install your nvidia drivers today – unfortunately, it was a bit a bumpy ride and is not working fully.

    First of all I’ve removed RPMFusion packaged, then I have installed nvidia-driver and dkms-nvida via yum from your repository.

    1. After boot nvidia module is not enabled and system boots into 1024×768 resolution. Installing nvidia-xconfig and running it fixes the resolution issue, but…
    2. compiz does not work – how do I enable compiz?

    Many thanks,
    Marek

    1. You need to be more specific, this is totally vague.

      Which distribution are you running? Fedora 21? Have you then removed akmod after switching to dkms? What do the Xorg, dkms log say when you have a 1024×768 resolution? Does the kernel module compile and load cleanly? Have you removed/reset your xorg configuration (there should be no /etc/X11/xorg.conf file if you are running Fedora 21+).

      Which desktop environment are you running? Compiz can’t run everywhere. Have you checked that you can run it?

      1. Hi!
        Thanks for reply!

        Yes, I am running Fedora 21 with MATE-Desktop.
        Yes, I’ve used compiz with MATE-Desktop with no issues with akmod drivers 🙂
        Yes, I did remove akmods before installing dkms drivers.
        Yes, there was no default xorg.conf file – akmods seemed to work without it with no issues.
        Yes, modules did compile cleanly though dkms was complaining about missing dkms.conf.

        To fix the low resolution had to install nvidia-xconfig module from your repository and run it – it created an xorg.conf with bunch of settings. Only:
        Section “Device”
        Identifier “Videocard0”
        Driver “nvidia”
        EndSection
        seemed to be required for nvidia driver to load.
        To enable compiz/OpenGL had to add the following lines in order to get OpenGL load correctly:
        Section “Files”
        ModulePath “/usr/lib64/nvidia/xorg”
        ModulePath “/usr/lib64/xorg/modules”
        EndSection

        Sadly, after making everything work, totem would not play videos at all – I would only see the white screen. The reason I wanted to use your drivers was to get the native video rendering on my 2560×1440 screen… so had to revert back to akmods. After revert vidoes still don’t play in Totem, though VLC works fine.
        Will have time to play more with your drivers at weekend.

        Many thanks for your reply and comments!

        1. All the settings you have added to /etc/X11/xorg.conf are already inside the packages in the following files:

          /etc/X11/xorg.conf.d/99-nvidia-modules.conf
          /etc/X11/xorg.conf.d/99-nvidia-driver.conf

          1. I don’t recall seeing 99-nvidia-*.conf files there after installing your drivers… as I said – I’ll give it another go on the weekend. Thanks!

  39. Hey– Thanks for this project. I LOVE your repos!

    I discovered that after installing or upgrading (kernel along with new nvidia driver) a line in Grub2 is still loading nouveau or, at least, passing arguments to it. Right after that statement is a blacklisting of nouveau. I always boot into the “Ooops! Something went wrong.” every time I boot. When I removed the nouveau line from Grub and ran grub2-mkconfig and rebooted, the log-in screen came right up along with by secondary monitor. I’d thought I’d share that here. BTW, I’m always running the latest stable Fedora (21 at the moment).

    Thanks again!
    Matt Hutchinson

    1. Fedora 21 running on a Lenovo W540 installed in a docking station.

      I am running into the same “Oh no! Something has gone wrong!” issue after installing the nvidia driver and akmod packages given here. The only way I was able to recover was to switch to a tty console, and uninstall all of the nvidia code.

      I will try again and remove the nvidia switches (except the blacklist one) from the boot line.

      1. Just tried again, this time removing nouveau.modeset=0 from /boot/grub2/grub.cfg, but it didn’t make any difference. I still get “Oh no! …”

        1. I also have to ctl-alt F2, log in as root and run the nv modprobe command (can’t remember it off the top of my head).

  40. Hi! Whether it is possible install driver version 340xx? My graphics card – NVidia 200, so never version of the driver does not work …

  41. Hi!
    Thanks for the repos. Everything is working great! However, I have a questions. I’m sorry if it’s very “newbie” for all of you, but I figure that other might have the same question.

    All I did to install the driver was:
    – Install repo
    – Remove othe nvidia drivers
    – And: yum -y install nvidia-driver cuda

    I thought that I would need the akmod module to make sure that the driver do not breatk after kernel update. But I did not install it, did 2 kernel update after that and everything is working great still.

    So, my question: On a standard Fedora installation,
    – Why would I install akmod modules?
    – Why would I install dkms driver?

    Thank you!

    1. If you have installed nvidia-driver and did not specify akmod or dkms, you will get akmod by default on Fedora. Do you need cuda?

      1. ok, got it. Thanks for the reply.
        You are right. I probably don’t have any programs using cuda… Handbrake maybe? Probably not. I installed it, I figured that it would not do much harm to have it installed…

  42. Thanks! I install 340 drivers from your repository, and a few days everything was fine, but then (possibly after Yum partial update, but without kernel!) was again loaded driver novieau and disappeared 3-D effects… How to disable novieau and check the installation?..

  43. Usually in my Korora I can log-in as user xy and then switch to a log-in for a second user (or more) simultaneously without logging out user xy. I can have two or more users logged-in the same time and jumping from one user to another without logging out a user.

    This is not possible with my Korora 21 (Fedora 21) with recent nvidia drivers installed out of repo http://negativo17.org/repos/fedora-nvidia.repo

    As soon as trying to log-in a second user I get a “OOPS something went wrong” (from Gnome) on console 2 (Ctrl-Alt-F2) and the already logged-in user on console 1 is logged-out automatically.

    May be this due to problems with graphic drivers and/or Xorg.

    Here is what happens.

    What is wrong?

    Rgds
    AW

    1. If you look at the log, you can see that there are numerous errors (EE). Are you sure you have only the bundled /etc/X11/xorg.conf.d/*nvidia* files?

      1. ls -all /etc/X11/xorg.conf.d
        insgesamt 20
        drwxr-xr-x. 2 root root 4096 13. Mär 09:44 .
        drwxr-xr-x. 6 root root 4096 30. Jan 08:42 ..
        -rw-r–r–. 1 root root 232 22. Jan 11:30 00-keyboard.conf
        -rw-r–r–. 1 root root 106 5. Aug 2014 99-nvidia-driver.conf
        -rw-r–r–. 1 root root 227 25. Feb 15:10 99-nvidia-modules.conf

        Look also at this http://fpaste.org/205473/14278221/raw/

        Nothing else found.

        I have now

        uname –all
        Linux xyz 3.19.1-201.fc21.x86_64 #1 SMP Wed Mar 18 04:29:24 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

        But also with older kernels these problems were existing.

        Rgds
        AW

          1. It is not, on Fedora 22+ the driver is loaded through the drm class (file /etc/X11/xorg.conf.d/99-nvidia-driver.conf). I don’t ship the file you’re mentioning in my packages, so don’t know where you got it.

  44. Thanks so much for the ease your packaging provides.

    As of F20 (running F21 now) the proprietary driver stopped responding to adjustments to backlight brightness and remains stuck at, I’m guessing, around 90%.

    I’m running a GT218M [NVS 3100M] (from your fedora-nvidia-340 repo).

    I’m curious if you have any thoughts on this.

    Thanks.

  45. Nevermind. It occurred to me shortly after sending that that I’ve dealt with this before. It’s a Thinkpad-specific issued.

    The solution which used to work is to add a .conf to /etc/X11/xorg.conf.d, specifically with the content:

    Section “Device”
    Option “RegistryDwords” “EnableBrightnessControl=1”
    EndSection

    Unfortunately it now hangs at (something like) “waiting for Plymouth boot screen to quit” which it never does and therefore never fully gets to runlevel 5.

    I’ll keep experimenting. Thanks

  46. OK. From novieau loading helps
    yum remove xorg-x11-drv-nouveau
    &
    rdblacklist=nouveau nouveau.modeset=0 in GRUB_CMDLINE_LINUX.

    But I have another problem with the drivers: now brightness is not regulated оn mу classic Thinkpad T410…
    Usual tricks like «acpi_backlight=vendor» in GRUB_CMDLINE_LINUX does not help… Does anyone how to solve it?..

    4.- Blacklist nouveau

    1. sudo dnf -y install beesu
    2. beesu gedit /etc/default/grub

    1. I found a solution to our problem (no backlight control on Thinkpads).

      I created an xorg conf file in /etc/X11/xorg.conf.d with the following contents and named it

      22-thinkpad_T510_bright.conf

      Section "Device"
      Identifier "Thinkpad Brightness Control"
      Option "RegistryDwords" "EnableBrightnessControl=1"
      EndSection

      This didn’t work previously because I had neglected to add the Identifier line. Hope this helps.

    2. Removing the nouveau driver is not required, as it’s not loaded. Adding the parameters through GRUB_CMDLINE_LINUX is required only if you regenerate the Grub config file through grub2-mkconfig. Otherwise what you did is not needed, the driver package adds the required parameters through grubby:

      $ rpm -q --scripts nvidia-driver
      postinstall scriptlet (using /bin/sh):
      if [ "$1" -eq "1" ]; then
        ISGRUB1=""
        if [[ -f /boot/grub/grub.conf && ! -f /boot/grub2/grub2.cfg ]]; then
            ISGRUB1="--grub"
        fi
        /sbin/grubby $ISGRUB1 --update-kernel=ALL --args='nouveau.modeset=0 rd.driver.blacklist=nouveau nomodeset gfxpayload=vga=normal' &>/dev/null
      fi || :
      preuninstall scriptlet (using /bin/sh):
      if [ "$1" -eq "0" ]; then
        ISGRUB1=""
        if [[ -f /boot/grub/grub.conf && ! -f /boot/grub2/grub2.cfg ]]; then
            ISGRUB1="--grub"
        fi
        /sbin/grubby $ISGRUB1 --update-kernel=ALL --remove-args='nouveau.modeset=0 rd.driver.blacklist=nouveau nomodeset gfxpayload=vga=normal' &>/dev/null
      fi ||:
  47. I just wanted to say thanks — I’m on Fedora 21 (3.19.3), GNOME 3.14.2; I went from a manually installed driver (346.47 from the nvidia website; gtx970) to your repo, and not only does the shell consume significantly less vram, but has become a *lot* more responsive.

    I’m not technical enough to tell whether your packaging is the cause; but the change followed up on installing it, and I’m really happy for it. Thanks!

  48. Hello Negativo,

    Thank you for your useful repos! There is any chance to start a repo for 340xx driver in fedora 22? I have a Dell precision 4500 with quadro 880m and the latest driver doesn’t work 🙁
    In rpmfusion there is 304xx but doesn’t work with the fedora’s xorg version!

    Currently I am using nouveau.

    Thank you!

  49. Thank you very much!

    Unfortunately, I got the following errors 🙁

    [ 64.201] (EE) Failed to load module “nouveau” (module does not exist, 0)
    [ 64.201] (EE) Failed to load module “nv” (module does not exist, 0)
    [ 64.204] (EE) open /dev/dri/card0: No such file or directory
    [ 64.205] (EE) open /dev/fb0: No such file or directory
    [ 64.206] (EE) Screen 0 deleted because of no matching config section.
    [ 64.904] (EE) AIGLX: reverting to software rendering
    [ 64.925] (EE) AIGLX error: dlopen of /usr/lib64/dri/swrast_dri.so failed (/usr/lib64/dri/swrast_dri.so: undefined symbol: _glapi_tls_Dispatch)
    [ 64.925] (EE) GLX: could not load software renderer

    1. Yes, it was an issue on 346.47 and fixed in 346.52. I have reapplied it to the 340.xx series (a new version is coming out, btw). Uploading now.

  50. Hello,

    Thank you for such a contribution to Fedora community. I’ve tried to add your repo without success:

    sudo yum-config-manager –add-repo=http://negativo17.org/repos/fedora-nvidia.repo
    > YumRepo Error: All mirror URLs are not using ftp, http[s] or file.

    sudo dnf –enablerepo=http://negativo17.org/repos/fedora-nvidia.repo
    > Error: Unknown repo: ‘http://negativo17.org/repos/fedora-nvidia.repo’

    What’s wrong here?

  51. For update,

    Solved this problem with the right command for dnf in Fedora 22 and good internet connection:
    sudo dnf config-manager –add-repo=http://negativo17.org
    /repos/fedora-nvidia.repo

    We will see how it works.

    Thank you.

  52. FYI,

    “dnf install kernel-devel” will fix “something wrong happened” when booting Fedora 22, and possibly older Fedora too. Now things works!

    Thank you for your contribution.

    1. Hello, installation of the kernel-devel package is in the instructions for the aKMOD variant. aKMOD pulls in kernel-debug-devel, this is why I added it to the instructions. DKMS, on the other hand, already pulls in kernel-devel.

  53. Hi,

    I’m unable to get the proprietary drivers working under Fedora 22:

    $ Linux notebook 4.0.0-1.fc22.x86_64 #1 SMP Mon Apr 13 10:03:33 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

    This is a notebook with a Geforce 560M card.

    After installing with ‘# yum -y install nvidia-driver’, the system reboots to the infamous “Oh no! Something has gone wrong … Please log out and try again” screen, instead of a functional GDM. Nouveau, on the other hand, works perfectly.

    Can you help me further debug this? Thank you.

  54. Following Infinite’s comment above (manually installing the kernel-devel package) seems to have fixed the issue.

  55. Hello and thank you for the work!

    I’m trying to add your repo to a fresh Fedora22 install without success. I’ve tried both “yum-config-manager –add-repo=http://negativo17.org/repos/fedora-nvidia.repo” and “sudo dnf config-manager –add-repo=http://negativo17.org/repos/fedora-nvidia.repo” but i get the error: “Error: No matching repo to modify: –add-repo=http://negativo17.org/repos/fedora-nvidia.repo”. would you possibly have a hint for me on what i’m doing wrong and how to get your repo& driver on my system please?

    1. By a quick look to the comment you are not using a double dash (–) to the add-repo parameter:

      yum-config-manager --add-repo=http://negativo17.org/repos/fedora-nvidia.repo

      You can still copy the repository file in /etc/yum.repos.d manually, though.

  56. I’m having trouble building graphics programs like blender, and it appears to be due to do something about the nvidia-340 branch. Even though NVidia doesn’t recommend any other options for my card (Quadro FX 1800) other than the 340 branch, is it safe for me to use the 346 drivers and libraries (including CUDA and OpenCL) on my desktop (Dell Precision T7500 w/Fedora 21)?

  57. A quick question about Blender —

    When using nvidia’s installer, I’m able to use the graphics card as a ‘compute device’ for the Cycles Renderer (User Preferences/System/Compute Device/CUDA) — on your package, however, I don’t see the graphics card listed at all. This holds for the stable release, as well as the daily builds from blender.org.

    I’ve installed (all from the @fedora-nvidia repo)
    akmod-nvidia.x86_64
    kmod-nvidia.x86_64
    kmod-nvidia-3.19.5-200.fc21.x86_64.x86_64
    nvidia-driver.x86_64
    nvidia-driver-NVML.x86_64
    nvidia-driver-NvFBCOpenGL.x86_64
    nvidia-driver-cuda.x86_64
    nvidia-driver-cuda-libs.x86_64
    nvidia-driver-devel.x86_64
    nvidia-driver-libs.i686
    nvidia-driver-libs.x86_64
    nvidia-libXNVCtrl.x86_64
    nvidia-persistenced.x86_64
    nvidia-settings.x86_64
    cuda.x86_64
    cuda-cli-tools.x86_64
    cuda-devel.x86_64
    cuda-extra-libs.x86_64
    cuda-libs.x86_64

    What do you think I might be missing?

  58. The problem I mentioned in the post above was resolved with today’s update to the 2:349.16-2 versions. Thanks!

        1. Hello, I’m literally swamped with apartment move and daily work. I will be rebuilding everything during the weekend, expect it next week.

  59. Hi, thanks for maintaining this and keeping up with us.

    I haven’t been able to get BOINC to find my GPU. I got it working last year with the RPMFusion drivers and the CUDA package from NVIDIA (I think it was 5.5 back then). I’ve got most of this repository installed. Anynthing I should look for?

      1. I couldn’t find it exactly in their docs. I know it ran with Cuda 5.5, and I think (don’t remember clearly) with 6.0. I’ve got a GTX650TiBOOST, if it’s relevant. Should still be supported.

        I just installed ccminer from your repository, to see if I could get anything working. When I ran “ccminer –benchmark” I got:
        [2015-05-02 02:49:15] GPU monitoring is not available.
        [2015-05-02 02:49:15] 1 miner thread started, using 'x11' algorithm.
        [2015-05-02 02:49:15] GPU #0: quark_blake512_cpu_init invalid device symbol
        [2015-05-02 02:49:16] GPU #0: aes_cpu_init invalid device symbol
        [2015-05-02 02:49:17] GPU #0: aes_cpu_init invalid device symbol
        [2015-05-02 02:49:18] GPU #0: x11_simd512_cpu_init invalid texture reference
        [2015-05-02 02:49:19] GPU #0: quark_blake512_cpu_init invalid device symbol
        [2015-05-02 02:49:20] GPU #0: aes_cpu_init invalid device symbol
        [2015-05-02 02:49:21] GPU #0: aes_cpu_init invalid device symbol
        [2015-05-02 02:49:22] GPU #0: x11_simd512_cpu_init invalid texture reference
        [2015-05-02 02:49:23] GPU #0: GeForce GTX 650 Ti BOOST, 0.00 H/s
        [2015-05-02 02:49:23] Total: 0.00 H/s
        [2015-05-02 02:49:23] GPU #0: quark_blake512_cpu_init invalid device symbol
        [2015-05-02 02:49:24] GPU #0: aes_cpu_init invalid device symbol
        [2015-05-02 02:49:25] GPU #0: aes_cpu_init invalid device symbol
        [2015-05-02 02:49:26] GPU #0: x11_simd512_cpu_init out of memory
        [2015-05-02 02:49:27] GPU #0: GeForce GTX 650 Ti BOOST, 0.00 H/s
        [2015-05-02 02:49:27] Total: 0.00 H/s
        [2015-05-02 02:49:27] GPU #0: quark_blake512_cpu_init invalid device symbol
        ...

        1. Mmmh. This is not what’s happening here:

          [2015-05-03 11:14:20] GPU monitoring is not available.
          [2015-05-03 11:14:20] 1 miner thread started, using 'x11' algorithm.
          [2015-05-03 11:14:30] GPU #0: GeForce GTX 860M, 2474.76 kH/s
          [2015-05-03 11:14:30] Total: 2474.76 kH/s

  60. Is there a problem with akmod-nvidia for F22?
    At the moment the newest driver in your repo is 2:352.09-1.fc22. There is no corresponding akmod-nvidia package. Thus nvidia-driver wants to pull in dkms-nvidia.

  61. thanks for the work

    i got a problem , i did use akmod-nvidia with f22 and i got a problem with the X server , it didn’t load the path /usr/lib64/nvidia/xorg which is present in
    /etc/X11/xorg.conf.d/99-nvidia-modules.conf

    log of the failed X server
    #/var/log/Xorg.0.log
    [ 2866.166] Build ID: xorg-x11-server 1.17.1-12.fc22
    [ 2866.167] (==) Using config file: “/etc/X11/xorg.conf”
    [ 2866.167] (==) Using config directory: “/etc/X11/xorg.conf.d”
    [ 2866.167] (==) Using system config directory “/usr/share/X11/xorg.conf.d”
    [ 2866.167] (==) ModulePath set to “/usr/lib64/xorg/modules”
    [ 2866.178] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
    [ 2866.190] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
    [ 2866.195] (II) Loading /usr/lib64/xorg/modules/libfb.so
    [ 2866.196] (II) Loading /usr/lib64/xorg/modules/libwfb.so
    [ 2866.578] (II) Loading /usr/lib64/xorg/modules/input/libinput_drv.so

    so i did create a symlink
    ln -s /usr/lib64/nvidia/xorg/libglx.so /usr/lib64/xorg/modules/extensions/libglx.so
    and now it works

    am i the only one which got this bug ?

    1. It is loading fine on my system. I have other problems relating to the X 1.16+ server always loading glamor, but not that one you’re mentioning.

  62. i think the repo for fc21 is broken , there a mix between drivers version 349 and 352 , and it broke for me with the new kernel 4.0.4 ( akmod failed to build with 346 )

      1. Hello,

        I have Fedora 22 x64 with GTX 760Ti. By default is your repo suggesting to install beta driver? Why not stable? Can you please help me ho to install stable?

        1. Hello, not at the moment. You can just rebuild the source RPMS for 349.xx.

          Normally I have beta drivers available only for the unreleased Fedora versions, but this time the schedule did not match with Nvidia, and I had the beta driver in before the Fedora release.

  63. I have an issue with Fedora 22 KDE Spin. Installed fresh system from ISO. I added negativo17 repo. Nvidia driver works ok. System boot up, however KDE doesn’t start properly. I have one krunner error and 3 plasma errors and and the end plasma doesn’t start. With nouveau driver all is OK. Is there anybody how had the same issue?

    1. I had this issue until I realized my card needed the 340 driver. I had installed fedora-nvidia rather than the needed fedora-nvidia-340.repo. I disabled the fedora-nvidia repo , added the -340.repo, removed then installed per the instructions and it worked.

      1. Glad you fixed it. To go from one version to the other, you could just replace the .repo file and just do a dnf distro-sync or dnf downgrade command.

  64. I realized that when adding a repos with dnf config-manager, the files do not have read rights for group and other. So a dnf search would fail for that repos.
    Workaround: execute “chmod +r /etc/yum.repos.d/fedora-nvidia.repo” as root (or via sudo)

  65. Thank You so much for your efforts! I was able to install the drivers for my GT200GL Quadro FX3800 using the fedora-nvidia-340.repo on my HP Z800 Fedora 22 KDE. I was running Fedora 21 with the nvidia drivers successfully until a yum update broke it. The Download from Nvidia’s site no longer runs and there is some patch on the developer site I did not understand how to compile/implement. Until I found your site, I was stuck. Unable to revert back to the Nouveau drivers due to a lack of concise instructions.

  66. i get the ‘oh no something went wrong’ after installing nvidia-driver on F22. I already had kernel-devel installed, and im using kernel 4.0.4-303. I tried using the dkms-nvidia instead but same error. has something changed with latest kernel?

  67. i did kmods –force to try re-building for kernel 4.0.4-303 but get this error:

    [root@frodo andrew]# akmods --force
    Checking kmods exist for 4.0.4-303.fc22.x86_64 [ OK ]
    Building and installing nvidia-kmod [FAILED]
    Building rpms failed; see /var/cache/akmods/nvidia/352.09-1-for-4.0.4-303.fc22.x86_64.failed.log for details

    Hint: Some kmods were ignored or failed to build or install.
    You can try to rebuild and install them by by calling
    '/usr/sbin/akmods --force' as root.

    1. Do you have the kernel-devel package for 4.0.4-303.fc22.x86_64 installed?

      You can check with:

      rpm -qa kernel\* | sort

        1. we turn off Optimus in BIOS, and select discreet graphics rather than Nvidia. There may be other options, but this seems to work best for us.

    2. More specifically, the error I see in /var/cache/akmods/nvidia/352.09-1-for-4.0.4-303.fc22.x86_64.failed.log is:

      install: cannot stat '_kmod_build_4.0.4-303.fc22.x86_64/uvm/nvidia*.ko': No such file or directory

      1. sorry, full error here which gives more insight:

        + install -p -m 0755 '_kmod_build_4.0.4-303.fc22.x86_64/uvm/nvidia*.ko' /tmp/akmodsbuild.SKeKT5hh/BUILDROOT/nvidia-kmod-352.09-1.fc22.x86_64//usr/lib/modules//4.0.4-303.fc22.x86_64//extra/nvidia//
        install: cannot stat '_kmod_build_4.0.4-303.fc22.x86_64/uvm/nvidia*.ko': No such file or directory
        error: Bad exit status from /var/tmp/rpm-tmp.2G7CfH (%install)

  68. For Fedora 22, a file from the cuda-devel package (/usr/share/man/man3/deprecated.3.gz) conflicts with a file from the qwt5-qt4-devel package.

    Just thought you should know.

    Cheers
    Stu

  69. I have same error as finite9, fresh install. No optimus, kernel-devel package installed for that specific kernel.

  70. Hello,

    I have installed Fedora 22 (fresh install) and then tried to install nvidia drivers from your repository. As reported before – nvidia driver is not loaded after reboot and resolution drops to 1024×768 maximum… the only thing I did was:

    dnf config-manager –add-repo=http://negativo17.org/repos/fedora-nvidia.repo

    then:

    yum -y install nvidia-driver

    What do I need do to actually get the driver working?

    Many thanks,
    Marek

    1. from the log file:

      # cat /var/log/Xorg.0.log| grep -i glx
      [ 6.045] (II) “glx” will be loaded by default.
      [ 6.045] (II) LoadModule: “glx”
      [ 6.046] (II) Loading /usr/lib64/nvidia/xorg/libglx.so
      [ 6.221] (II) Module glx: vendor=”NVIDIA Corporation”
      [ 6.222] (II) NVIDIA GLX Module 352.21 Tue Jun 9 21:22:54 PDT 2015
      [ 6.898] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)

        1. Looks like I have right version installed:

          $ rpm -qa kernel\* | sort
          kernel-4.0.4-301.fc22.x86_64
          kernel-4.0.4-303.fc22.x86_64
          kernel-core-4.0.4-301.fc22.x86_64
          kernel-core-4.0.4-303.fc22.x86_64
          kernel-devel-4.0.4-303.fc22.x86_64
          kernel-headers-4.0.4-303.fc22.x86_64
          kernel-modules-4.0.4-301.fc22.x86_64
          kernel-modules-4.0.4-303.fc22.x86_64
          kernel-modules-extra-4.0.4-301.fc22.x86_64
          kernel-modules-extra-4.0.4-303.fc22.x86_64
          kernel-tools-libs-4.0.4-303.fc22.x86_64

          and I can see the module is being built:
          # find / | grep nvidia.ko
          /var/lib/dkms/nvidia/352.21/4.0.4-303.fc22.x86_64/x86_64/module/nvidia.ko

  71. First of all, if you have an Optimus laptop, there’s no out of the box support.

    If it is not, do you have an /etc/X11/xorg.conf file? You should not have one. From the line in your log it is not loading the module from the appropriate folder, and the thing is in the /etc/X11/xorg.conf.d/99-nvidia*.conf files.

    1. It’s a desktop computer with a nVidia GeForce GTX 650 graphics card, rpm fusion drivers work with no issues out of the box.

      There was no /etc/X11/xorg.conf file after installation (and reboot), there were two /etc/X11/xorg.conf.d/99-nvidia*.conf files. Everything as expected from the standard installation.

      1. @slaanesh any idea why nvidia would fail on my desktop?

        The nvidia drivers from rpmfusion works great… but I cannot make yours to work 🙁

  72. Hello, thank you for building these and offering them to the public – it’s greatly appreciated.

    For the latest Fedora 22 kernel (4.0.5-300) I had to run “/usr/sbin/akmods –force” to get the nvidia.ko to build as it did not do this automatically like in the past.

    I’m not sure if this is something specific to kernel-4.0.5+ but this was not needed for prior 4.0.4* kernels. Hoping this helps someone.

    FWIW I’m using a Geforce GTX 560 with the latest 352-series drivers.

    Thanks again for providing these to the public.

    1. I’m sorry but it’s not happening here (GTX 560ti x2 in SLI on same kernel). If the new driver comes along with the new kernel-devel package (i.e. when updating all together), the module will get built at next boot.

  73. I was able to install the drivers for my GT200GL Quadro FX3800 using the fedora-nvidia-340.repo on my HP Z800 Fedora 22 KDE dual screens and it was running OK until I did a dnf upgrade to load 322 updates. This loaded new kernel-4.0.5-300.fc22.x86_64 and kernel-devel-4.0.5-300.fc22.x86_64. I yum removed and yum -y install nvidia-driver but the window sessions would not come up. After unloading I get only a single lo resolution screen. Any suggestions? Thanks!

      1. I believe the fedora-nvidia-340.repo is the legacy drivers as I had them working just fine, but I think they only work with the kernel prior to kernel-4.0.5-300.fc22.x86_64. Does the fedora-nvidia-340.repo have to be somehow updated in order to work with the new kernel?

  74. Hi there, great tutorial you’ve got here. Unfortunately, I still can’t use my nvidia gpu. Info: Running fedora 22 dual boot with win7, all non uefi, Asus k55 laptop, i7 with a gtx 850M. There’s no way to change between gpus in BIOS. Kernel 4.0.5-300.fc2.x86_64

    Here’s what’s happening, with the nouveau drivers, the battery life sucks, running cs go in fedora is ridiculous, and, this happens very often, the noveau drivers give me a ton of errors at startup, so I have to turn off my laptop 2, 3 times before it fully boots. This is why I want to try different drivers, in this case, the Nvidia ones.

    I’ve tried the bumblebee 2 times, and both times I had to reinstall fedora, I wasn’t able (probably because I’m ignorant) to undo what was done. But this time, with your tutorial, everything went fine when installing, I managed to run nvidia settings, had to install nvidia-xconfig, also ran that without any problem. when I rebooted my laptop, i couldn’t boot anymore.. I’m stuck in “A Start job is running for Wait for Plymouth Boot Screen to Quit (45s / no limit).

    From here, i’m able to enter the console, remove the nvidia drivers, but still can’t boot.

    If you could give me some help, I would appreciate it, because I’m not going to give up. I like these puzzles, but I’ve spent a good amount of time in this.. Oh, And I only started to mess with a linux os about 2 weeks ago, so go easy on me please 🙂

  75. I’m running Fedora 22. I have a GT240 card, and am using the 340 branch. I also had to manually run
    /usr/sbin/akmods –kernels 4.0.5-300.fc22.x86_64

    Until now I have had to keep rebooting into the older 4.0.4 kernel, because the modules for 4.0.5 did not build.

    Thank you sadsfae for the tip!!!

  76. Does anybody else has problem with totem that crashes after installing the drivers on F22 ?

    (totem:2936): Gdk-ERROR **: The program ‘totem’ received an X Window System error.
    This probably reflects a bug in the program.
    The error was ‘BadMatch (invalid parameter attributes)’.
    (Details: serial 393 error_code 8 request_code 153 (GLX) minor_code 31)
    (Note to programmers: normally, X errors are reported asynchronously;
    that is, you will receive the error a while after causing it.
    To debug your program, run it with the GDK_SYNCHRONIZE environment
    variable to change this behavior. You can then get a meaningful
    backtrace from your debugger if you break on the gdk_x_error() function.)

  77. oh dear… as of 4.0.7-300.fc22.x86_64 “which updated automatically” this stopped working for me..

    i have redone all the above with no success…
    i get plasma crashing on me “no menus etc..”

    and no second diaplay despite rebuilding the modules…

    dell inspiron 17 7000 series “Optimus” type…

    08:00.0 3D controller: NVIDIA Corporation Device 1344 (rev ff) (prog-if ff)
    !!! Unknown header type 7f
    Kernel modules: nouveau, nvidia

      1. sorry i did notice that and decided to start from scratch…

        to that end i have done the following:
        yum -y remove \*nvidia\*
        and
        yum -y install nvidia-driver

        Kernel params in grub = rd.driver.blacklist=nouveau nomodeset

        this should give me a clean starting point….

        1. I now have both displays working.

          However when I login plasma crashes and I get screen scrolling rapidly on the laptop almost to a blur.

          Lspci -vv shows kernel driver in use nvidia
          Kernel modules: nouveau, nvidia

          Not sure where it’s getting nouveau from as I can’t find any reference to it.

          I should mention that I’m not too clued up on this sort of issue. It’s just always worked for me.

  78. You have saved me! could not get graphics working properly on my new HP Zbook 17 G2. Your repo worked perfectly!

  79. Hi,

    After playing a bit with optimus/bumblebee I’ve found I really don’t need this and it is more pain than gain 🙂 So, I’ve removed everything installed by this, and moved back to negativo’s repo. Unfortunately my cinnamon/gnome crashes maybe due to some version conflict.

    I have messages like this
    glxgears
    Error: couldn't get an RGB, Double-buffered visual

    glxinfo64
    name of display: :0.0
    Error: couldn't find RGB GLX visual or fbconfig

    less /var/log/Xorg.0.log | grep gl
    [ 92.159] (WW) "glamoregl" will not be loaded unless you've specified it to be loaded elsewhere.
    [ 92.159] (II) "glx" will be loaded by default.
    [ 92.159] (II) LoadModule: "glx"
    [ 92.159] (II) Loading /usr/lib64/nvidia/xorg/libglx.so
    [ 92.159] (EE) Failed to load /usr/lib64/nvidia/xorg/libglx.so: libnvidia-tls.so.352.30: cannot open shared object file: No such file or directory
    [ 92.159] (II) UnloadModule: "glx"
    [ 92.159] (II) Unloading glx
    [ 92.159] (EE) Failed to load module "glx" (loader failed, 7)

    dnf list installed |grep nvidia
    akmod-nvidia.x86_64 2:352.30-1.fc22 @System
    kmod-nvidia-4.1.4-200.fc22.x86_64.x86_64
    nvidia-driver.x86_64 2:352.30-2.fc22 @System
    nvidia-libXNVCtrl.x86_64 2:352.30-1.fc22 @System
    nvidia-settings.x86_64 2:352.30-1.fc22 @System

    my system is 4.1.4-200.fc22.x86_64

    Any idea?

    Thanks

    1. Seems, it is solved by
      dnf --best install nvidia-driver-libs-2\:352.30-2.fc22

      ldd ./libglx.so
      linux-vdso.so.1 (0x00007ffc741e8000)
      libnvidia-tls.so.352.30 => /lib64/libnvidia-tls.so.352.30 (0x00007f2e5733f000)
      libnvidia-glcore.so.352.30 => /lib64/libnvidia-glcore.so.352.30 (0x00007f2e548ac000)
      libc.so.6 => /lib64/libc.so.6 (0x00007f2e544ec000)
      libdl.so.2 => /lib64/libdl.so.2 (0x00007f2e542e8000)
      libm.so.6 => /lib64/libm.so.6 (0x00007f2e53fe0000)
      /lib64/ld-linux-x86-64.so.2 (0x00005556b0291000)

      1. nvidia-driver-libs it’s a dependency of nvidia-driver, this means you have forced installation of the main package ignoring the rest as it is normally automatically pulled in.

        Also, don’t forget to install nvidia-driver-libs.i686 if you want to play Steam games 🙂

        1. Now, everything is installed from negativo repo, and there is no major error in my logs, however it seems glx extensions is missing/not working… do you have any idea how to fix it?

          1. Usually it’s an all in one, either you have OpenGL/GLX Nvidia libraries loaded or not. You can not have “some glx extensions”. What extensions are you referring to?

        2. Hi, I just installed Fedora22 64bit on my desktop PC with Nvidia GTX480.

          I updated all packages before attempting to install your nvidia driver like this:
          dnf remove \*nvidia\*
          dnf install nvidia-driver

          GDM crashed at boot, and journalctl showed that there was no 3D acceleration available.
          I tried ‘akmods –force’ and it showed that the module was OK.

          ‘nvidia-driver-libs’ were not installed however, after installing them manually, GDM went fine.

          Thank you for your work!

          Regards,
          Sladi

          1. Hello, yes, unfortunately with the latest library reorganization I accidentally deleted the nvidia-driver-libs requirement in nvidia-driver. It is fixed now and the libraries are installed automatically.

  80. So, finally I’ve removed the proprietary driver and installed again nouveau… it seems this has basic support for optimus (at least I can use digital output of my docking which was not working with intel only config), so if it will be stable enough I’ll stay with open source again 🙂

  81. You install instructions are missing key information for novice user like me or dozen others. You say to install driver install only “nvidia-driver” package, but that will not work. What about adding “nvidia-driver-libs”? How many users were left with broken computer unable to boot?

    1. The instructions are correct, it’s that with the latest library reorganization I accidentally deleted the nvidia-driver-libs requirement in nvidia-driver. It is fixed now and the libraries are installed automatically (as it was last week).

        1. You can use both DKMS or aKMOD, your choice. By default the first one providing nvidia-kmod gets pulled in, so in alphabetical order is akmod-nvidia then dkms-nvidia in Fedora, and binary kmod-nvidia and dkms-nvidia on CentOS/RHEL. Please read the repository page for instructions.

          1. Hmm i quite don´t understand, even if i have Googled for differences between KMOD, AKMOD and DKMS. I guess i was dumbed down by Ubuntu 🙂 where i didn´t needed to choose anything and nvidia driver was one-click install in Additional Drivers GUI. So i have installed “nvidia-driver”, “nvidia-driver-libs” both 32/64 bit for Steam and now which kernel module you recommend to install for future so my system will boot after kernel update, KMOD or DKMS?

          2. If you have installed nvidia-driver, then you already have some module, as it’s automatic. That’s the point, you should not worry about it if you don’t know the differences. Try this to see what’s installed:

            $ rpm -qa \*nvidia\* | sort

  82. Hi, the newest update fails to find all files I guess. GDM crashed, only 2D acceleration was enabled and I got this error:

    (II) LoadModule: “glx”
    (II) Loading /usr/lib64/nvidia/xorg/libglx.so
    (EE) Failed to load /usr/lib64/nvidia/xorg/libglx.so: libnvidia-tls.so.352.30: cannot open shared object …

    I tried simply symlinking and it seems to work now:
    ln -s /usr/lib64/libnvidia-tls.so.352.30 /usr/lib64/nvidia/xorg/

    1. There is something wrong with your system, that is absolutely not needed. Libraries are loaded through ldconfig, and if your system would not be able to find libraries in /usr/lib64 it would not boot at all. Or you have screwed your permissions in /usr/lib64/libnvidia* or you have some other issue, because permissions are correct inside the package.

      $ rpm -qpvl nvidia-driver-libs-352.30-3.fc22.x86_64.rpm | grep tls
      -rwxr-xr-x 1 root root 12912 Jul 22 03:25 /usr/lib64/libnvidia-tls.so.352.30

      Your problem is not related to the packages.

      1. I think it happened because I tried to install both the driver and the 32bit libs at once. This happened on a new system again, and when I installed just the driver first, it worked fine.

  83. Hi, Thanks for the repo.

    I am just having one issue, I am trying to make my monitor layout stay after reboot.

    I created a .conf file under /etc/X11/xorg.conf.d/

    with the following:

    Section “Monitor”
    # HorizSync source: edid, VertRefresh source: edid
    Identifier “Monitor0”
    VendorName “Unknown”
    ModelName “DELL 2208WFP”
    HorizSync 30.0 – 83.0
    VertRefresh 56.0 – 76.0
    Option “DPMS”
    EndSection

    Section “Screen”
    Identifier “Screen0”
    Device “Device0”
    Monitor “Monitor0”
    DefaultDepth 24
    Option “Stereo” “0”
    Option “nvidiaXineramaInfoOrder” “DFP-0”
    Option “metamodes” “DVI-D-0: nvidia-auto-select +2970+480, DVI-I-1: nvidia-auto-select +1050+480, HDMI-0: nvidia-auto-select +0+0 {rotation=left}”
    Option “SLI” “Off”
    Option “MultiGPU” “Off”
    Option “BaseMosaic” “off”
    SubSection “Display”
    Depth 24
    EndSubSection
    EndSection

    but still no luck. Am I doing something wrong?.. still new to fedora and linux.

    Thanks.

  84. Any chance of rolling back to the last driver version? gnome-shell keeps crashing when GDM tries to start up with nvidia-driver-355.11-1.fc23.x86_64 on Fedora 22 and Fedora 23 with a GeForce GTX 780 Ti. I checked the repo URL to see if I could roll back manually but I don’t see previous versions.

    [ 229.817576] traps: gnome-shell[5128] trap int3 ip:7f12a32668eb sp:7ffecc8db420 error:0
    [ 233.605400] traps: gnome-shell[5165] trap int3 ip:7fdcf08c28eb sp:7fff89b1b500 error:0
    [ 237.459072] traps: gnome-shell[5202] trap int3 ip:7fc7ee1878eb sp:7ffe00da84b0 error:0
    [ 241.272302] traps: gnome-shell[5239] trap int3 ip:7efc51e528eb sp:7ffd321776e0 error:0
    [ 245.121385] traps: gnome-shell[5277] trap int3 ip:7f97499cc8eb sp:7ffdd0b43650 error:0

    on Fedora 22 and Fedora 23.

    1. There is no previous version, but this does not seem to be related to the drivers. Do you have any additional X.org configuration apart from the one provided by the drivers?

      1. No additional X.org configuration other than what nvidia-driver provides.

        I was able to get more out of journalctl andit seems that it can’t find the drm kms device with the new driver. It was working fine with the previous driver.

        Sep 24 15:48:31 desktop systemd[1]: Started User Manager for UID 42.
        Sep 24 15:48:31 desktop gnome-session[2431]: (gnome-shell:2437): mutter-ERROR **: could not find drm kms device
        Sep 24 15:48:31 desktop kernel: traps: gnome-shell[2437] trap int3 ip:7f54c24fa8eb sp:7fffff26dd20 error:0
        Sep 24 15:48:38 desktop systemd-coredump[2441]: Process 2437 (gnome-shell) of user 42 dumped core.

        Stack trace of thread 2437:
        #0 0x00007f54c24fa8eb g_logv (libglib-2.0.so.0)
        #1 0x00007f54c24faa5f g_log (libglib-2.0.so.0)
        #2 0x00007f54c622b9bb meta_launcher_new (libmutter.so.0)
        #3 0x00007f54c62269e8 meta_backend_native_init (libmutter.so.0)
        #4 0x00007f54c2816b09 g_type_create_instance (libgobject-2.0.so.0)
        #5 0x00007f54c27f7ebb g_object_new_internal (libgobject-2.0.so.0)
        #6 0x00007f54c27f97d1 g_object_newv (libgobject-2.0.so.0)
        #7 0x00007f54c27fa104 g_object_new (libgobject-2.0.so.0)
        #8 0x00007f54c61b9846 meta_clutter_init (libmutter.so.0)
        #9 0x00007f54c61ec782 meta_init (libmutter.so.0)
        #10 0x00007f54cb6a843a main (gnome-shell)
        #11 0x00007f54c0916580 __libc_start_main (libc.so.6)
        #12 0x00007f54cb6a8849 _start (gnome-shell)

        Stack trace of thread 2439:
        #0 0x00007f54c09ed11d poll (libc.so.6)
        #1 0x00007f54c24f423c g_main_context_iterate.isra.29 (libglib-2.0.so.0)
        #2 0x00007f54c24f434c g_main_context_iteration (libglib-2.0.so.0)
        #3 0x00007f54c24f4389 glib_worker_main (libglib-2.0.so.0)
        #4 0x00007f54c251ab25 g_thread_proxy (libglib-2.0.so.0)
        #5 0x00007f54c0cbe60a start_thread (libpthread.so.0)
        #6 0x00007f54c09f8bbd __clone (libc.so.6)

        Stack trace of thread 2440:
        #0 0x00007f54c09ed11d poll (libc.so.6)
        #1 0x00007f54c24f423c g_main_context_iterate.isra.29 (libglib-2.0.so.0)
        #2 0x00007f54c24f45c2 g_main_loop_run (libglib-2.0.so.0)
        #3 0x00007f54c39a54a6 gdbus_shared_thread_func (libgio-2.0.so.0)
        #4 0x00007f54c251ab25 g_thread_proxy (libglib-2.0.so.0)
        #5 0x00007f54c0cbe60a start_thread (libpthread.so.0)
        #6 0x00007f54c09f8bbd __clone (libc.so.6)

        Sep 24 15:48:38 desktop gnome-session[2431]: Unrecoverable failure in required component gnome-shell-wayland.desktop
        Sep 24 15:48:38 desktop systemd-logind[1405]: Removed session c6.
        Sep 24 15:48:38 desktop /usr/libexec/gdm-wayland-session[2427]: Activating service name=’org.gtk.vfs.Daemon’
        Sep 24 15:48:38 desktop /usr/libexec/gdm-wayland-session[2427]: Successfully activated service ‘org.gtk.vfs.Daemon’
        Sep 24 15:48:38 desktop /usr/libexec/gdm-wayland-session[2427]: Activating service name=’ca.desrt.dconf’
        Sep 24 15:48:38 desktop gnome-session[2431]: gnome-session[2431]: WARNING: Application ‘gnome-shell-wayland.desktop’ killed by signal 5
        Sep 24 15:48:38 desktop org.gtk.vfs.Daemon[2429]: A connection to the bus can’t be made
        Sep 24 15:48:38 desktop systemd[1]: Stopping User Manager for UID 42…

  85. getting warnings in Xorg.0.log on fedora 23 about the ABI.

    warning: this version of xorg has ABI 22 but the driver requires ABI 20. driver will continue to load but will behave strangely.

    this is with 355.11

    1. Nvidia drivers do not support (yet) X.org server version 1.18. See /etc/X11/xorg.conf.d/99-nvidia-ignoreabi.conf on your system.

  86. First, I really love what you have done with the nvidia driver. I have one request for RHEL6: nvidia-driver-352.41-1.el6.
    It’s putting blacklist-nouveau.conf in /usr/lib/modprobe.d/ instead of /etc/modprobe.d/ On RHEL6, dracut isn’t using that file. If I copy it to /etc/modprobe.d/ dracut works as expected.

      1. Fantastic. I should mention that nvidia-uvm.conf in the nvidia-driver-cuda package has the same problem.
        I also found the binary driver installs libGL.so and libEGL.so. Maya2016 doesn’t run without them, so if we could get those links added to nvidia-driver-libs, that would be awesome. Last issue is that nvidia-settings only gets installed if I install nvidia-driver-cuda. If I want nvidia-smi, but not the cuda driver (or nvidia-uvm kernel module) I am unable to do that. Could nvidia-smi be moved to nvidia-driver instead of nvidia-driver-cuda? I apologize for all this at once, but if all these issues were resolved, I’d be a super happy camper.

  87. Hi,
    im asking you to make some legacy repo for fedora 23 nvidia drivers since my card is not in supported list for 355 .
    Ive made changes in you 340 repo file and installed the one from fc22 but it gave the same result, perhaps i did something wrong.
    this is what it show
    “Oh no! Something has gone wrong. A problem has occurred and the system can’t recover. Please log out and try again.”

  88. However I tried I could not make Nvidia drivers work on Fedora 23 beta. (including RPMFusion, which crashes the system completely and the only way it can be fixed is using `chroot` on system drive and externally removing installed packages)

    With Negativo, after `dnf` installation, kmod-x.xxx.xxx package is automatically installed. (can see this in `dnf history`). When I install `nvidia-driver`, `akmod-nvidia` is pulled from the RPMFusion repo.

    After reboot things seem to work but when I login to Gnome it hangs a bit and then returns with a crash to login page over again.

    I tried manually disabling `nouveau` manually in grub.cfg and blocklisting it in modprobe but nothings seems to work.

    Any advice please?

    P.S. Thank you very much for your work!

  89. Hi.

    I’m trying to install you driver, but it look like the kernel module is trying to compile for the 4.0.2 kernel instead of the 4.2.2 kernel, making the xserver crash.

  90. Hello,
    I installed the Nvidia drivers but Firefox keep crashing now. It seems to work if I uninstall them.
    I’m new to Fedora. I used this command to install the drivers:
    $ sudo dnf install nvidia-driver akmod-nvidia kernel-devel nvidia-driver-libs.i686
    I have found this bug report but I don’t know if it’s related: https://bugzilla.redhat.com/show_bug.cgi?id=1219068
    What can I do ?

      1. The Firefox devs say that I need to remove libva-vdpau-driver and closed the bug.

        I said to them that I disagree because you shouldn’t have to remove softwares to make an other soft work. Plus, I use VDPAU in MPV so I don’t want to remove it. And even if I try to remove libva-vdpau-driver the whole Nvidia driver will be removed.

        If you agree with me don’t hesitate to say it to them:
        https://bugzilla.mozilla.org/show_bug.cgi?id=1192900

        1. Ok I had an explanation and it’s not Firefox that crash but :
          “It is gstreamer itself that is crashing because one of its plugin, designed by Intel to work with their VAAPI adapter happen to call another piece of software that is using libva-vdpau which itself is crashing. Someone thought it would be a good idea to make a nvidia card appear like an intel one.”

          And he said “I’m not sure what distribution you are using, but I don’t see libva-vdpau-driver being a dependency for the vdpau drivers. It’s should be the other way round. If libva-vdpau-driver is a dependency for the nvidia drivers, you should report that bug to the packager.”

          So maybe we should avoid to have libva-vdpau-driver as a dependency of the Nvidia driver ?

          https://bugzilla.mozilla.org/show_bug.cgi?id=1192900#c13

          1. That’s interesting. If I remove that package as a dependency, would mean that out of the box you would not be able to use VAAPI acceleration for programs that use that (instead of VDPAU) with Nvidia drivers.
            As a side note, whether this is good or bad, the component using VAAPI should not crash.

            It’s not crashing for me, btw. Can you tell me which distribution are you using and point me to the site that is making your Firefox crash?

            Thanks.

  91. I’m on Fedora 22 x64. It’s my first install of Fedora and I test it because I want to switch to it. I was on Xubuntu before, and I have to say that I tried many different Nvidia drivers installation.

    Before knowing your repo I tried the Nvidia driver work from the RMP-Fusion repo (sudo dnf install akmod-nvidia “kernel-devel-uname-r == $(uname -r)”) but I couldn’t make it work (black screen at boot or something like that).

    After that I tried the Nvidia driver from your repo. After many test (RPM-Fusion, Your Repo, Nouveau drivers) the only working way to install the Nvidia driver is now “sudo dnf install nvidia-driver”.

    I don’t know why but this don’t work anymore (“sudo dnf install nvidia-driver akmod-nvidia kernel-devel nvidia-driver-libs.i686”) (black screen at boot or something like that).

    All that to say that I made a lot of test but I don’t think it infer with the crash.

    So, I agree that VAAPI should not crash, but if there is a bug it’s safer to remove the dependency, at least for now.

    The crash happen on Youtube with the HTML5 player if I seek in the video or if I switch to fullscreen.

    1. Just to be clear the first time I tried your drivers the installation with this command (“sudo dnf install nvidia-driver akmod-nvidia kernel-devel nvidia-driver-libs.i686”) works perfectly. No problem with your Nvidia drivers 😉

  92. I’m on Fedora 22. The driver is working fine and has been for months, but I recently tried to open nvidia-settings and got this series of error messages (and no nvidia-settings):

    » nvidia-settings

    ERROR: The requested operation is not available on target device

    ERROR: The requested operation is not available on target device

    ERROR: The requested operation is not available on target device

    ERROR: The requested operation is not available on target device

    ERROR: The requested operation is not available on target device

    nvidia-settings: libXNVCtrlAttributes/NvCtrlAttributesNvml.c:1616: NvCtrlNvmlGetValidAttributeValues: Assertion `ret2 == NvCtrlAttributeNotAvailable’ failed.
    [1] 5825 abort (core dumped) nvidia-settings

      1. It’s a GTX 660. Nvidia-settings used to work fine with this same card. I have an extra .nvidia-settings-rc at a different location that is used by a script that calls “nvidia-settings –config=$that_other_path -l”. The script still works, and that file was last modified (with the working GUI) on October 24, 2014. I don’t edit my .nvidia-settings-rc manually, so unless there’s some circumstance where it gets automatically modified without the settings being changed in the GUI, the last time it worked was Aug 16 of this year, the last modified time of my .nvidia-settings-rc at the default location.

        It still crashes with “nvidia-settings –no-config”. Nvidia-smi does not have any problems.

      2. I seem to have the same problem:

        % nvidia-settings
        nvidia-settings: libXNVCtrlAttributes/NvCtrlAttributesNvml.c:1616: NvCtrlNvmlGetValidAttributeValues: Assertion `ret2 == NvCtrlAttributeNotAvailable’ failed.
        zsh: abort (core dumped) nvidia-settings

        Fedora 23, NVIDIA driver 358.16, Xorg 1.18.0, two GTX 970 cards. It used to work with Fedora 22 and RPM Fusion packaged drivers.

          1. It’s ok… but it still doesn’t work. It looks like NVML_AVAILABLE=0 is needed, not NVML_AVAILABLE=1. 😉

  93. Seems on F23 im hitting a snag as 355 exists on the repos but nvidia-settings-358 🙁

    1✗ ~/src $ sudo dnf install nvidia-driver –allowerasing
    Last metadata expiration check performed 0:15:03 ago on Tue Oct 27 09:15:52 2015.
    Error: nothing provides nvidia-settings = 2:355.11 needed by nvidia-driver-2:355.11-3.fc23.x86_64

  94. Cannot make it work on asus with 740m.
    Get error
    (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found), but i see nvidia in lsmod.
    Any ideas?

      1. Fedora 22
        kernel 4.2.3
        As for config – I haven’t changed anything – stanard 99-nvidia-modules.conf and 99-nvidia-driver.conf. Xorg logs show only these errors:
        (EE) Failed to load module “nv” (module does not exist, 0)
        (EE) [drm] KMS not enabled
        (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
        Latest driver version, installed today (355.11)
        Yes, multicard, with Intel. Maybe its impossible with asus and optimus?

  95. My nouveau drivers came back with the dnf upgrade from F22 to F23, which prevented X11 from starting. I removed them with “dnf erase xorg-x11-drv-nouveau”.

    1. There is no need to remove them, they are not loaded when installing the drivers. Keep in mind though that Video Driver ABI = 20 (X.org 1.18) is not supported by the Nvidia drivers yet.

  96. Error: Transaction check error:
    file /usr/share/man/man3/deprecated.3.gz from install of cuda-devel-1:7.0.28-1.fc23.x86_64 conflicts with file from package qwt5-qt4-devel-5.2.2-28.fc23.x86_64

    just thought you should know

  97. Legacy drivers 340.xx don’t appear to exist for FC23 yet.

    causing me a bit of a problem as i’m using a somewhat older GPU on one of my systems.

    1. I’m currently travelling, I will update them through the weekend along with the latest packaging enhancements from the 358.x branch.
      Don’t expect anything spectacular, as there is no support for X.org 1.18 nor kernel 4.2 in the legacy drivers, I don’t even know if it works.

      1. You’d think it would be the kernel & X.org’s job to make that work given these are LEGACY drivers, but still somewhat recent enough to expect users to exist, and unlikely to be updated by the manufacturers specifically for linux requirements.

      2. still getting messages about missing repodata/repomd.xml

        Will you put an update posting on the site when you do push this?

  98. Tried installing on fedora 23, but after rebooting, cinnamon keeps crashing. Any idea why this is or how I can fix it?

    All I did was installing nvidia-drive akmod-nvidia and kernel-devel and then reboot, is there anything else I should have done?

  99. Hi there,

    Thanks for providing the driver for F23, however I have a few issues with it.
    First, the gdm login screen shows up with only a grey background, but I can:
    – either hit enter, and my password, then I get logged
    – either alt+ctl+f2, and then back to alt+ctl+f1, then it shows the usual gdm login icns, but nothing can get clicked. I can however hit Enter + type my login, and get through to my gnome session.

    Then, the gnome session lasts only for a few moments. For instance starting firefox of google chrome will crash the session.

    Would you like some logs or more details ?

      1. Thanks for the hint! It does sort out the login screen issue, but the gnome session still crashes after a few random minutes

        1. I’ve run into a similar issue after login the gnome session starts to load, apparently crashes, then returns to the login screen.

  100. Heya,

    Installed driver :

    dnf -y install nvidia-driver akmod-nvidia kernel-devel nvidia-driver-libs.i686

    … rebooted but had to create xorg .conf

    I get this error with games from wine :

    err:winediag:X11DRV_WineGL_InitOpenglInfo Unable to activate OpenGL context, most likely your 32-bit OpenGL drivers haven’t been installed correctly

    Can you help ?

  101. Hi!!

    First of all thanks for your work!

    Also: are there any plans for updating the 340xx repo to fedora 23? Or have you stopped maintaining the legacy driver?

    Thanks!

  102. I had some problems with nvidia-driver-351.11-4 and kernel-4.2.6-200 using dkms on fedora 22.

    First a “dnf update” said it could not find an updated driver on the mirror. I had to uninstall dkms-nvidia and nvidia-driver and install again for dnf to be happy.

    Second the kernel module for 4.2.6 was not built when the new driver packages were installed. GNOME presented the “Oops something bad has happened…” error. I had to uninstall kernel-4.2.5 and reboot for the module to be built and GNOME to run correctly.

    I have been through a few kernel updates without this happening so it seems it might have been a result of recent packaging changes?

    My install is fedora 22 Workstation x86_64 and the negativo17/fedora-nvidia repository is the only non-fedora repository I have on the system.

    1. This can happen when installing the driver and update the kernel at the same time. The new module is built and THEN the new kernel is installed for which a module is not built. Was that the case?
      I might need to look if I can add to the DKMS driver the trigger script that is in the aKMOD variant.

      1. That seems a likely cause of the problem. I will take your assessment as being correct.

        A fix would be nice but at least I was able to get things working so it is not a big problem.

      2. Same problem here: kernel 4.2.6 installed, system rebooted, Gnome error. By looking at the “modinfo nvidia” output, the module is in place but it has the wrong vermagic (for the 4.2.5 kernel). I suspect that DKMS skipped the rebuilding and just installed the already built module for the old kernel.

  103. Any ETA for 352.63 on F23? I don’t mean to rush anything, just trying to schedule when I will upgrade to F23 (decided to wait until proper support for Xorg 1.18 was out).

    As always, thank you so much for all your work on these repos! =)

    1. They will not end up in Fedora 23, but they are already in the repositories for RedHat/CentOS 6/7. Please see the table in the Nvidia driver page.

      1. Sorry, didn’t realize they were not meant for F23. I just saw 358.16 is out, and you’re already working on them. Cool! =)

        1. Actually the source tarballs for nvidia-{xconfig,modprobe,settings,persistenced} have not been pushed to the FTP nor to the Github repositories yet. 352.64 is also missing from Github, but at least is available from the FTP.

          1. They appear to have been now, not in the Github however. I think we’re all pretty excited since 358.16 is a significant update. Looking forward to the next push to the repo.

  104. Im, find now ver. driver Linux x64 (AMD64/EM64T) Display Driver NVIDIA Certified 358.16
    Added support for X.Org xserver ABI 20 (xorg-server 1.18).

  105. When installing to we have to specify which driver we want? Confused on how to get negativo nvidia driver package up and running. Tried in once, but reboot came back with “something went wrong”

  106. I can’t log into Fedora 23 without changing hitting ctrl+alt+F2 once after putting my login/password in at GDM. This is after the latest 358.16 release (and with SELinux still set to permissive).

    Also having a fair few crashes in Steam with the Nvidia 358.16 driver. Simple things like adding a game to a category cause it to exit. I can’t seem to run any unity based games (such as Shadowrun, Satellite Reign, etc). They just exit before loading.

    Using the 355 driver was fine, so I think perhaps the 358 driver is the issue. Any chance we can get the 355 driver in the Fedora 23 repository? At least until the fixes are through for the 358 series.

    Alternatively – if someone has a workaround for these issues, I’d love to hear about it.

    1. Driver 355 has been superseded by 358 (it is the new short lived version) and there is no support for X.org 1.18 nor for the SELinux policy workaround in it.

    2. Hi,

      as for the gdm login issue I know how to handle this. There seems to be a bug with gdm and wayland on some systems. I had the same issue on my workstation. Laptop seems fine though.

      Alt + F2 and log in with your credentials. As root, edit /etc/gdm/custom.conf and uncomment #WaylandEnabled=false. That disables wayland for the login and runs now on X.

      Good luck and report back if this did solve the issue.

      1. Actually this should be the case if you are using binary drivers; X.org will switch to “normal” mode, run as root and GDM etc. are not started under Wayland.

  107. I’m having issues getting the drivers to work on Fedora 23 Cinnamon Spin. All the packages install correctly, but on reboot Cinnamon crashes and goes into fallback mode. When trying to run glxgears I get the following error:
    Xlib: extension “GLX” missing on display “:0”.
    Error: couldn’t get an RGB, Double-buffered visual

    My laptop is an ASUS N550JV, so is an optimus with a 750m. Any ideas or suggestions would be greatly appreciated.

      1. Thanks for the reply. I’ve just moved over from Ubuntu and using that I was able to get the drivers to work out-of-the-box on my laptop so didn’t realise the full implications of running optimus. Fortunately, I’ve managed to get things working using bumblebee for now so am happy.

        Cheers.

  108. Regarding the libva-vdpau-driver dependency, I consistently get crashes in Firefox with the crash reports consistently pointing to libvdpau_nvidia.so.358.16 as the culprit. Here are the facts:

    1) I don’t have an intel CPU or AMD graphics card.
    2) Most people point to either Flash or HTML5 being the cause of the crash, however, I seem to crash even if Flash is disabled.
    3) I’ve disabled hardware acceleration in flash.
    4) Using RPM Fusion makes no difference. I can definitely say that lib-vdpau-driver is responsible for the crashes.

    Now it seems like people keep throwing bad advice around, from removing Gstreamer to removing Libva. As far as I can see, it has nothing to do with Gstreamer. I can run Chromium with lib-vdpau-driver installed fine as well as VLC. It’s only Firefox that crashes.

    Judging from the trail of zombie bug reports and the massive amount of spam in said bug reports from clueless users, it doesn’t look like this will be fixed anytime soon.

    Therefore, I respectfully ask that you remove the dependency and let us decide whether or not to install the lib-vdpau-driver. Thank you.

  109. I tried installing nvidia-driver through your repo on Fedora 23, but after rebooting I end up getting a black screen.
    How can I fix this?

  110. Most happily I’ve received my new thinkpad but am having issues with using the proprietary driver. Mostly because I don’t really understand how to deal with dual GPUs. I’m running a new installation of fc23.

    lspci output:

    00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09)
    08:00.0 3D controller: NVIDIA Corporation GM108GLM [Quadro K620M] (rev a2)

    I understand that the proprietary driver should “provide intelligent powering down and up of the discrete nVidia card” but I can’t figure out how to get kmod-nvidia to replace nouveau. Any suggestions would be greatly appreciated.

    And thank you for your work.

      1. It appears that the kernel is unaware of the fact that I have a discrete GPU. Or maybe the kernel knows but the DM doesn’t. Not sure what’s happening. lsmod | grep i915 says:

        i915 1110016 9
        i2c_algo_bit 16384 2 i915,nouveau
        drm_kms_helper 118784 2 i915,nouveau
        drm 335872 12 ttm,i915,drm_kms_helper,nouveau
        video 36864 3 i915,thinkpad_acpi,nouveau

        So the module is loaded but output from xrandr –listproviders says:

        Providers: number : 1
        Provider 0: id: 0x49 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 4 outputs: 6 associated providers: 0 name:Intel

        I placed “video=VGA-2:d” in the kernel command line but nothing happened. Could it be that lspci returns a “3D controller” for the chipset instead of “VGA controller?”

        Additionally, there doesn’t exist a /sys/kernel/debug/vgaswitcheroo/switch file.

        I’m about to try only using the nvidia GPU standalone per your instructions but I’m pretty befuddled. Any thoughts are appreciated.

        1. The fact that is listed as a 3d controller it probably means that simply it has no outputs attached to it.

          The fact that you’re not seeing the vgaswitcheroo folder means the arbiter module is not loaded (vgaarb). Don’t know why, that is built in the kernel, so maybe your system is not recognized properly. At this point, without a mechanism to turn on/off the cards properly, you’re welcome to try using the nvidia driver directly configured with Output Sink.

          Make sure that you do not have additional spurious kernel parameters around.

          1. Thank you.
            dmesg | grep vgaarb says:

            [ 0.140863] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=mem,locks=none
            [ 0.140866] vgaarb: loaded
            [ 0.140867] vgaarb: setting as boot device: PCI:0000:00:02.0
            [ 0.140868] vgaarb: bridge control possible 0000:00:02.0
            [ 1.327250] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=mem

            so vgaarb is there but, as you say, the system isn’t properly recognized. Perhaps I’ll look at compiling a kernel with a patch for recognizing a “3d Controller” I think I read about somewhere, if I can find it. And still probably try out the nvidia driver standalone.

            Also, I noticed that there was an xorg conf file, 10-disable_prime.conf which I imagine is there for the same reason. I rendered it unusable but, since it’s clearly a lower level issue, nothing happened, naturally.

            Thanks for you thoughts and comments.

          2. Oh yeah. I installed bumblebee and this does show up in dmesg:

            [ 3.861785] bbswitch: Found integrated VGA device 0000:00:02.0: \_SB_.PCI0.VID_
            [ 3.861790] bbswitch: Found discrete VGA device 0000:08:00.0: \_SB_.PCI0.PEG_.VID_

  111. Hello i am using your nvidia repo in my fedora 23 installation. I am using the akmod kernel module. Everytime when a kernel update shows up if i install it my computer boots but i see an error that is saying “failed to load kernel module bla bla” but it boots. whats this? for example this happened when i updated my kernel to the latest 4.2.6.301

        1. The first: /var/log/Xorg.0.log (or some old logs).
          The second: /var/cache/akmods/akmods.log
          For kernel packages, at least:
          $uname -r
          and
          $rpm -qa kernel

          Try out a terminal.

  112. Hi, thank you for this repository. I’m using it for installing nvidia drivers without problem. But now I’m trying to install cuda-devel and I encountered following problem with nvcc when trying to compile some pyCuda tests.

    nvcc --cubin -arch sm_52 -I/usr/lib64/python2.7/site-packages/pycuda-2015.1.3-py2.7-linux-x86_64.egg/pycuda/cuda kernel.cu]
    nvcc fatal : Path to libdevice library not specified

    Most solutions for this problem I found with google are updating nvcc.profile, but I can’t find it with where is.

    1. Ignore my previous post. Today it is working without problems. I don’t know what happened, maybe new version of gcc solved this problem.

      1. Actually it’s working just because you freshly logged in your system.
        Cuda base package includes an environment profile that is sourced when you start a new login shell:

        # cat /etc/profile.d/cuda.sh
        [ -x /usr/bin/nvcc ] && export NVVMIR_LIBRARY_DIR=/usr/share/cuda
        [ -x /usr/libexec/cuda/open64/bin/nvopencc ] && export PATH=$PATH:/usr/libexec/cuda/open64/bin
        [ -d /usr/include/cuda ] && export CUDA_INC_PATH=/usr/include/cuda

        Without it, you get the error you posted.

  113. If anyone has been having trouble with modules being built by DKMS with the wrong module magic, for example, after upgrading the kernel, it seems there’s an error in the DKMS make command. It causes modules to be built for the running kernel regardless of the target kernel chosen, and then fail to load at your next boot.

    To fix it temporarily you can create a file at /etc/dkms/nvidia.conf with the following content (delimited by the dashes, but don’t actually include them)

    MAKE[0]="'make' -j2 module SYSSRC=${kernel_source_dir} IGNORE_XEN_PRESENCE=1 IGNORE_PREEMPT_RT_PRESENCE=1"

    It ensures the builds always use the correct kernel sources.

    1. Thanks for spotting it! I’ve added the parameter to the dkms.conf file that is bundled with the dkms-nvidia package.
      That was present before Nvidia removed the instantiated module builds from their makefile and I probably removed that by accident when rewriting it for the new build system.

  114. Hi,

    First of all I would like to thank you for this repository. It’s really great!
    I’m on Fedora 22 with one Nvidia GTX 770 and until now it was working perfectly. But yesterday I updated my system which in particular updated the kernel from 4.1.6 to 4.2.8 and gcc from 5.1.1 to 5.3.1. And now the system doesn’t start anymore.
    When I update the kernel and reboot, the kernel fails to load the modules but that’s normal. I need to sign the nvidia and nvidia-uvm because of the BIOS secure boot. This always solved the problem before but this time it seems to not be enough.

    uname -r: 4.2.8-200.fc22.x86_64
    journalctl -b Xorg.0.log and akmods.log can be found here:
    https://gist.github.com/anonymous/e2600e4e6c07d44d55f2

    It seems it is not able to find nvidia-uvm but the module is there and signed correctly. With modinfo I can see they are in /lib/modules/4.2.8-200.fc.22.x86_64/extra/nvidia/nvidia(-uvm).ko

    Also there is a complain about Wayland and GDM in the logs attached and I saw in an earlier post that it should be fixed.

    What should I do? If you need other information I’m happy to share anything you need.

    Thanks a lot in advance!

      1. I just found the solution by chance. There is apparently a new module called nvidia-modeset. Since I only signed nvidia and nvidia-uvm but not this one it was not able to load it. Somehow it was not mentioned in the log. Is this something new?

        Thank you anyway. So happy to see my screen again 😀

          1. I am running Fedora 22. But I jumped from 355.11 to 358.16 when I updated my system. So that’s why. Thank you again!

  115. Has anyone got this to work with RHEL/Centos 7.2 yet? The packages work well on my machine with kernel 3.10.0-229.20 but no matter what I do they fail on 3.10.0-327.4.4 with:

    NVIDIA: Failed to initialize the NVIDIA kernel module.

  116. I have updated to Fedora 23 from 22. Since completing the update instead of gdm loading I get the “oh no! something has gone wrong” message. I’ve tried the wayland uncomment in gdm custom.conf mentioned above. I am using a GTX650 on a desktop running kernel 4.3. Any suggestions as to what I can do beyond removing and reinstalling the nvidia drivers.

  117. Hi, I have lenovo w550s laptop with f23 and i can’t get nvidia drivers to work. i tried all kinds of installation methods: official drivers 352|358|361, bumblebee, negativo17 and can’t get the drivers to work. i installed cuda and it works fine but cuda executables give errors.

    “`
    > lspci |grep -E “VGA|3D”
    00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09)
    08:00.0 3D controller: NVIDIA Corporation GM108GLM [Quadro K620M] (rev a2)
    15:09:41seer~/Downloads
    > uname -a
    Linux seer 4.3.3-301.fc23.x86_64 #1 SMP Fri Jan 15 14:03:17 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
    15:09:47seer~/Downloads
    > rpm -qa | grep -E ‘nvidia|bumblebee|bbswitch|primus|VirtualGL’
    nvidia-settings-358.16-2.fc23.x86_64
    nvidia-driver-cuda-libs-358.16-1.fc23.x86_64
    nvidia-validation-suite-352.55-1.fc23.x86_64
    bumblebee-nonfree-unmanaged-release-1.2-1.noarch
    akmod-nvidia-358.16-1.fc23.x86_64
    nvidia-driver-NvFBCOpenGL-358.16-1.fc23.x86_64
    nvidia-xconfig-358.16-1.fc23.x86_64
    nvidia-driver-358.16-1.fc23.x86_64
    nvidia-texture-tools-devel-2.0.8-11.fc23.x86_64
    kmod-nvidia-358.16-1.fc23.x86_64
    nvidia-libXNVCtrl-358.16-2.fc23.x86_64
    nvidia-persistenced-358.16-1.fc23.x86_64
    nvidia-driver-NVML-devel-352.55-1.fc23.x86_64
    nvidia-healthmon-352.55-1.fc23.x86_64
    dkms-nvidia-358.16-2.fc23.x86_64
    nvidia-driver-libs-358.16-1.fc23.x86_64
    nvidia-driver-devel-358.16-1.fc23.x86_64
    VirtualGL-2.4-5.fc23.x86_64
    nvidia-libXNVCtrl-devel-358.16-2.fc23.x86_64
    kmod-nvidia-4.3.3-301.fc23.x86_64-358.16-1.fc23.x86_64
    nvidia-driver-cuda-358.16-1.fc23.x86_64
    nvidia-texture-tools-2.0.8-11.fc23.x86_64
    nvidia-driver-libs-358.16-1.fc23.i686
    nvidia-driver-NVML-358.16-1.fc23.x86_64
    nvidia-modprobe-358.16-1.fc23.x86_64
    15:09:55seer~/Downloads
    > sudo dnf repolist
    Last metadata expiration check performed 0:46:07 ago on Fri Jan 22 14:24:02 2016.
    repo id repo name status
    *fedora Fedora 23 – x86_64 46,074
    fedora-nvidia negativo17 – Nvidia 49
    google-chrome google-chrome 3
    rpmfusion-free RPM Fusion for Fedora 23 – Free 692
    rpmfusion-free-updates-testing RPM Fusion for Fedora 23 – Free – Test Updates 236
    rpmfusion-nonfree RPM Fusion for Fedora 23 – Nonfree 206
    rpmfusion-nonfree-updates-testing RPM Fusion for Fedora 23 – Nonfree – Test Updates 77
    *updates Fedora 23 – x86_64 – Updates 14,647

    > sudo nvidia-smi
    modprobe: ERROR: could not insert ‘nvidia’: Unknown symbol in module, or unknown parameter (see dmesg)
    NVIDIA-SMI has failed because it couldn’t communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.

    “`

    I will appreciate any kind of guidance. Thank you.
    and thank you for creating this project.

  118. I’m on Fedora 23 and got a 404 when I tried to install runtime CUDA support as per the instructions:

    $ sudo dnf install -y cuda nvidia-driver-cuda

    [MIRROR] nvidia-driver-cuda-358.16-1.fc23.x86_64.rpm: Status code: 404 for http://negativo17.org/repos/nvidia/fedora-23/x86_64/nvidia-driver-cuda-358.16-1.fc23.x86_64.rpm
    [FAILED] nvidia-driver-cuda-358.16-1.fc23.x86_64.rpm: No more mirrors to try – All mirrors were already tried without success

    The second time I tried it, dnf couldn’t find the package!

    $ sudo dnf install nvidia-driver-cuda
    Last metadata expiration check performed 0:14:09 ago on Tue Jan 26 23:34:32 2016.
    No package nvidia-driver-cuda available.
    Error: Unable to find a match.

    Any ideas on why I cannot install the nvidia-driver-cuda?

  119. I installed Fedora 23. Updated it, add your repo and then installed nvidia-driver but now i get

    “Oh! Something has gone wrong”

    When trying to boot up GNOME. What might be?

    I have a ASUS 970, Intel Core i5 2500K, 16 Gigs of RAM and a ASUS P8Z68-V PRO.

    Thanks.

  120. First off, everything has been working great, I really like this repository and prefer it to the packaged binary that NVIDIA distributes.

    I recently moved from Fedora 22 to Fedora 23, and now whenever I log in my NVIDIA settings are ignored. I’ve successfully added a section to my /etc/X11/xorg.conf.d which I generated with sudo nvidia-settings, so when I get the actual login screen on first boot both monitors are on in the proper layout. When I log into my user account the main monitor turns OFF and I am with just the second monitor enabled. I can open nvidia-settings again and fix them, but if I alt-f2 -> r -> enter and restart my gnome session the monitor settings immediately jump back to just one monitor.

    1. If anyone else is experiencing a similar problem, it has nothing to do with the NVIDIA drivers. You just need to delete ~/.config/monitors.xml and the problem should go away. Alt-F2 -> r -> enter to reset gnome session and verify.

  121. Think there’s a problem with the latest nvidia-driver-libs.

    old install:
    # tree /lib*/nvidia
    /lib64/nvidia
    ├── [ 260 May 20 2014] alternate-install-present
    ├── [ 16 Nov 18 13:23] libEGL.so.1 -> libEGL.so.340.96
    ├── [ 965K Nov 9 2:05] libEGL.so.340.96
    ├── [ 22 Nov 18 13:23] libGLESv1_CM.so.1 -> libGLESv1_CM.so.340.96
    ├── [ 47K Nov 9 2:05] libGLESv1_CM.so.340.96
    ├── [ 19 Nov 18 13:23] libGLESv2.so.2 -> libGLESv2.so.340.96
    ├── [ 61K Nov 9 2:05] libGLESv2.so.340.96
    ├── [ 15 Nov 18 13:23] libGL.so.1 -> libGL.so.340.96
    ├── [ 1.2M Nov 9 1:05] libGL.so.340.96
    ├── [ 18 Nov 18 13:23] libOpenCL.so.1 -> libOpenCL.so.1.0.0
    ├── [ 21K Nov 9 1:20] libOpenCL.so.1.0.0
    └── [ 4.0K Jan 25 0:58] xorg
    └── [ 13M Nov 9 1:09] libglx.so
    /lib/nvidia
    ├── [ 16 Nov 18 13:21] libEGL.so.1 -> libEGL.so.340.96
    ├── [ 647K Nov 9 2:12] libEGL.so.340.96
    ├── [ 22 Nov 18 13:21] libGLESv1_CM.so.1 -> libGLESv1_CM.so.340.96
    ├── [ 42K Nov 9 2:11] libGLESv1_CM.so.340.96
    ├── [ 19 Nov 18 13:21] libGLESv2.so.2 -> libGLESv2.so.340.96
    ├── [ 58K Nov 9 2:11] libGLESv2.so.340.96
    ├── [ 15 Nov 18 13:21] libGL.so.1 -> libGL.so.340.96
    ├── [ 1.0M Nov 9 1:11] libGL.so.340.96
    ├── [ 18 Nov 18 13:21] libOpenCL.so.1 -> libOpenCL.so.1.0.0
    └── [ 21K Nov 9 1:25] libOpenCL.so.1.0.0

    Latest:
    # tree /lib*/nvidia
    /lib64/nvidia
    ├── [ 260 May 20 2014] alternate-install-present
    ├── [ 18K Feb 3 18:09] libEGL.so.1
    ├── [ 18 Feb 9 17:46] libOpenCL.so.1 -> libOpenCL.so.1.0.0
    ├── [ 26K Feb 3 18:15] libOpenCL.so.1.0.0
    └── [ 4.0K Feb 15 20:52] xorg
    └── [ 12M Feb 3 18:14] libglx.so
    /lib/nvidia
    ├── [ 14K Feb 3 18:12] libEGL.so.1
    ├── [ 18 Feb 9 17:42] libOpenCL.so.1 -> libOpenCL.so.1.0.0
    └── [ 26K Feb 3 18:18] libOpenCL.so.1.0.0

    Appears we’re missing a pile of files all of a sudden.

    1. Actually you should do rpm -ql libglvnd nvidia-driver-libs, and not check the nvidia folder. The Nvidia labeled folder contains only the overrides to equally named system libraries; most of the libraries now have unique names.

      The libglvnd package is a placeholder that has been put in place until the base OS catches up (Mesa, etc.), so for now it’s still overriding the base libraries.

      If you want more details:
      https://devtalk.nvidia.com/default/topic/915640/unix-graphics-announcements-and-news/multiple-glx-client-libraries-in-the-nvidia-linux-driver-installer-package/

      Last question, are the packages working for you? They should pull in the libglvnd packages as a dependency.

  122. Hello, I am sorry, but I encountered a problem with your version of the 361.28 driver. After install the driver from your repo, some of the Steam games began to crash. Dota 2 crashed with error “Missing basic OpenGL v1.0 -> v2.0 required OpenGL functionality.”, other Valve games CS, HL2… ended with message “Could not find required OpenGL entry point ‘glGetError’! Either your video card is unsupported or your OpenGL driver needs to be updated.}}”. 32Bit libs where of-course installed.
    I followed workarounds described in wiki.archlinux.org/index.php/Steam. I also tried to deflect libs from Steam runtime-libs (via. /etc/ld.so.conf.d/steam.conf ldconfig….) all without any success.
    After uninstall the your driver and install it from default run file downloaded from nvidia.com all games began to work properly.
    I am using F23 x64, KDE, GTX960, dualmonitor.

    1. Unfortunately yes, this is due to some executables accessing non OpenGL ABI compliant stuff in the libGL.so.1 library, which are not exposed by libglvnd. I’ve reverted to the non-glvnd libGL.so.1 library as per Nvidia installer’s default:

      https://devtalk.nvidia.com/default/topic/915640/unix-graphics-announcements-and-news/multiple-glx-client-libraries-in-the-nvidia-linux-driver-installer-package/

      The latest nvidia-driver* packages should fix the issue.

    1. You would need a separate repo then. 355.00.28 is older than 361.28. It will be included by default in 364.x or whatever.
      As with previous OpenGL releases, Nvidia adds the feature to some older driver so not everyone will jump on it.

  123. Hi,

    It seems on cuda-samples package there are hardcoded paths that make all compilations fail:

    For example, in:
    /usr/share/doc/cuda-samples/5_Simulations/smokeParticles

    make yields:

    “/home/slaanesh/rpmbuild/SOURCES/cuda/cuda-7.5.18-x86_64″/bin/nvcc -ccbin g++ -I../../common/inc -m64 -gencode arch=compute_20,code=sm_20 -gencode arch=compute_30,code=sm_30 -gencode arch=compute_35,code=sm_35 -gencode arch=compute_37,code=sm_37 -gencode arch=compute_50,code=sm_50 -gencode arch=compute_52,code=sm_52 -gencode arch=compute_52,code=compute_52 -o GLSLProgram.o -c GLSLProgram.cpp
    /bin/sh: /home/slaanesh/rpmbuild/SOURCES/cuda/cuda-7.5.18-x86_64/bin/nvcc: El fitxer o directori no existeix
    Makefile:243: recipe for target ‘GLSLProgram.o’ failed

    The hardcoded path is on CUDA_PATH variable, at the beggining of the Makefile:
    # Location of the CUDA Toolkit
    CUDA_PATH ?= “/home/slaanesh/rpmbuild/SOURCES/cuda/cuda-7.5.18-x86_64”

    1. Thanks for notifying, there was a mistake in the makeself files from Nvidia were extracted. To tell the truth I never tried building the samples, only external programs.
      If you need to fix them immediately, you can just call the Makefiles like this:

      CUDA_PATH=/usr make

      Fixed packages are building; they will be uploaded in a few minutes.

      1. Thanks for the hotfix and the kick fix, already built stuff wuth CUDA. I was checking the samples cause I was having issues with Tensorflow and wanted to check if everything was OK.

  124. Hello! Thanks for the repo. I’m using Fedora 23, MATE spin. After hours installing and reinstalling these packages and those on rpmfusion, I finally have the nvidia driver working. The solution for me was embarrassingly simple: enter BIOS, disable ‘fast boot’ and ‘UEFI secure boot’. Now I can play Portal 2, wahey.

    Slaanesh, please could you add “disable UEFI secure boot” to instructions above? It wasn’t obvious to me. As I understand, secure boot requires kernel modules be signed, which isn’t the case for the modules in this repo or any home baked with akmod.

    Here’s what else I learnt:

    1. You really don’t need an xorg.conf . Creating one with nvidia-xconfig will only mean X crashes if the driver isn’t available, rather than fallback to low resolution.
    2. As explained above, to play 32 bit games (as on Steam), you need to install the nvidia-driver-libs.i686 package . Otherwise you’ll see an error “OpenGL GLX context is not using direct rendering, which may cause performance problems.” You can test 32-bit direct rendering with the command `glxinfo32 | grep “direct rendering”`
    3. glxgears and glmark2 are useful benchmarks. My glmark2 score increased hundredfold from 140 to 14000 after installing driver.

    Debugging guide I would have found useful:

    1. Delete rhgb (graphical boot) from grub.cfg
    2. Check lsmod lists nvidia module
    3. Which logs to check if it doesn’t.

    Thanks again.

    1. Thanks for the suggestion, the information has been added to the installation section, with also a link for signing your own modules.

    1. Updated the Fedora 24 repository. Remember that 364.12 is beta. Wayland support is not finished, specific Nvidia patches have been rejected upstream and KMS does not work properly on every hardware.

        1. Haven’t tested it yet… Unfortunately I don’t have an Optimus laptop anymore. Judgning from the Nvidia notes on their forum not much has changed for Optimus laptops.

      1. Hi!

        As rpmfusion doesn’t provide FC24 packages for akmods and kmodtool, I had to build both packages from SRPMs. However, installing nvidia-driver and akmod-nvidia always resulted in installing kmod-nvidia, too.

        Right now, booting into gdm doesn’t work, as I’m stuck on the Fedora Plymouth logo. Removing kmod-nvidia and rebuilding akmod-nvidia also doesn’t seem to help.

        Is installing the dkms-nvidia RPM instead of the akmod-nvidia RPM in your repo an option? I couldn’t test it because right now there seems to be some version conflict (dkms-nvidia-364.12 vs nvidia-driver-364.15).

        GPU is NVIDIA GTX 970.

  125. Hello! I’m having problem with installing nvidia-driver. First I uninstalled everything with:
    dnf remove *nvidia*

    Then installed with:
    dnf install nvidia-driver

    After installation I got this error:
    systemd-modules-load[219]: Failed to find module ‘nvidia-uvm’

    So I uninstalled kmod-nvidia* and akmod-nvidia* and installed akmod-nvidia again. Then build it again with akmods –force.

    And now I see this in lsmod|grep nvidia.
    nvidia_modeset 741376 7
    nvidia_uvm 561152 0
    nvidia 10014720 141 nvidia_modeset,nvidia_uvm
    drm 335872 6 nvidia

    But I’m still getting error mentioned above. Can anybody help me?

      1. Situation is getting weirder. After uninstalling everything nvidia driver related I’m still getting this error
        systemd-modules-load[219]: Failed to find module ‘nvidia-uvm’
        When I try to install nvidia-driver again. I’m ending with blinking boot screen. This is part of the Xorg.0.log:

        [ 58.838] (II) LoadModule: “nvidia”
        [ 58.838] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
        [ 58.838] (II) Module nvidia: vendor=”NVIDIA Corporation”
        [ 58.838] compiled for 4.0.2, module version = 1.0.0
        [ 58.838] Module class: X.Org Video Driver

        And later on there is this in log:
        [ 58.839] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
        [ 58.839] (EE) NVIDIA: system’s kernel log for additional error messages and
        [ 58.839] (EE) NVIDIA: consult the NVIDIA README for details.

        1. Ok, I don’t know what happened. But the driver is working again.
          This is what I did:
          rm -rf /lib/modules/$(uname -r)/extra

          At this location I found nvidia.ko, nvidia-uvm.ko and nvidia-modeset.ko.

          Then I edited /lib/modules/$(uname -r)/modules.dep and deleted lines with above kernel objects

          After this I installed nvidia driver again from your repository and everything looks good.

          Maybe this will help someone in future.

          1. I’ve got the same problem from kernel 4.4.6-301 onward. I don’t know what’s going on. Does it mean it can’t use Kernel Modesetting with this version?

  126. fedora 23 with NVS 5400M
    dnf complain
    /sbin/ldconfig: /usr/lib64/nvidia/libEGL.so.1 is not symbolic link

    lrwxrwxrwx. 1 root root     16  1 avril 09:04 libEGL.so -> libEGL.so.346.46
    -rwxr-xr-x. 1 root root  14368 23 mars  01:24 libEGL.so.1
    -rwxr-xr-x. 1 root root 952704 18 févr.  2015 libEGL.so.346.46

    must be changed??

    1. Nvidia drivers override base Mesa EGL libraries, even with GLVND:

      $ ldconfig -p | grep EGL
              libEGL_nvidia.so.0 (libc6,x86-64) => /lib64/libEGL_nvidia.so.0
              libEGL_nvidia.so.0 (libc6) => /lib/libEGL_nvidia.so.0
              libEGL.so.1 (libc6,x86-64) => /usr/lib64/nvidia/libEGL.so.1
              libEGL.so.1 (libc6,x86-64) => /lib64/libEGL.so.1
              libEGL.so.1 (libc6) => /usr/lib/nvidia/libEGL.so.1
              libEGL.so.1 (libc6) => /lib/libEGL.so.1

      And in both Mesa and Nvidia cases, the EGL library is always a symlink, don’t know where you got that library from. ldconfig is complaining that you have a library with the SONAME it should create a link for as a physical file.

      Fedora 23 has drivers 361.42 in the repos, not 346.46, and the links/libraries are fine, so you are asking for help on your setup which has nothing to do with what I ship.

  127. With stable 364.19 being released this week, are you considering updates Fedora 23 to the 364.19 driver version?

  128. akmod-nvidia-2:364.15-1.fc24.x86_64
    dkms-nvidia-2:364.12-1.fc24.x86_64

    Please update dkms-nvidia to match. It’s currently unusable because no other 364.12 dependencies exist. Thanks!

  129. I recently found an issue with an updated tool in Fedora that seems to only happen with the nvidia driver, not with the nouveau driver.

    I am not playing any video games these days so it might be time to consider switching over to nouveau. Just posting this to see if there are any thoughts on this.

    I am using:
    nvidia-driver-340.96-1.fc23.x86_64

    My card:
    NVIDIA Corporation GT200 [GeForce GTX 260] (rev a1)

    I don’t have a pressing issue with the nvidia driver but the bug is with the new version of liveusb-creator which gives a segmentation fault. The Fedora devs don’t want to know about it since I am using the nvidia driver.

    Current reason for not switching to nouveau is that I can’t get the two GPU temperatures to show up when using it. I have a mostly default (tho I use Xfce) install on an old hard drive that I did the nouveau testing with.

    P.S. I don’t actually need the liveusb-creator since I can just use `dd` to create a bootable USB when needed.

  130. Thanks for updating Fedora 23 to the 364.19 driver (works great). I was hoping to get vulkan support with the 364.19 driver, but maybe vulkan needs to packaged up separately first.

  131. Are there plans to build the legacy 340 for Fedora 24? I do a daily use of an old notebook that still works great and it is running now F22.

  132. Nvidia driver 364.19 hangs my Fedora 23 installation. I’m using a fairly standard GTX-650 card and this keeps happening to me every once in a while. Some Nvidia drivers work like a charm, adapting perfectly to kernel updates, and then… boom! The frowning booting face. It keeps me on the edge because I never know when I’m going to lose my main working computer.

  133. Thanks for your wonderful nvidia repo in the first place!

    I found a little config oddity with the nvidia-driver-cuda-36x.xx-x.fc23.x86_64 RPMs. Both 361.42 and 364.19 are affected.

    You install
    /usr/lib/modules-load.d/nvidia-uvm.conf
    containing
    nvidia-uvm
    which itself depends on the central “nvidia” kernel module.

    Unfortunately this file gets included in initramfs.img.

    So systemd tries to load this very early from the initramfs. But it seems dracut is missing the information that it should include it there because systemd fails to load nvidia-uvm toggling away from the plymouth bootscreen and presenting the red [failed] message.

    Adding nvidia and nvidia-uvm to dracut.conf (or manually by calling dracut –add) fixes it.

    Don’t know how to handle that without including the huge nvidia.ko in the initramfs.

    The module gets loaded later anyway and everything works fine. But I don’t like “failed” messages in the boot sequence;-)

    1. That’s really interesting, thanks for spotting. I will exclude all nvidia modules from initramfs.img (/usr/lib/dracut/dracut.conf.d/99-nvidia.conf).

      Thanks for notifying!

  134. dnf install libglvnd-server-module.x86_64

    nothing provides libglvnd(x86-64) = 0.0.0-19.af2aeb0.fc23 needed by libglvnd-server-module-0.0.0-19.af2aeb0.fc23.x86_64

    1. The server extensions has been superseded by a GLX extension. Since libglvnd 0.1.x and Nvidia drivers 364.x there is no more support for it.

  135. it’s working
    nvidia 10199040 106 nvidia_modeset,nvidia_uvm
    4.5.5-300.fc24.x86_64
    364.19-1.fc24

  136. Hi!
    There seems to be an error in package dkms-nvidia-364.19-1.fc23.x86_64.rpm. Module nvidia-uvm.ko is not being built, so opencl dependent programs fail to use opencl. It seems that in a file dkms.conf strings BUILT_MODULE_NAME and DEST_MODULE_LOCATION for “nvidia-uvm” and “nvidia-drm” have the same [number] field:

    BUILT_MODULE_NAME[2]="nvidia-uvm"
    DEST_MODULE_LOCATION[2]="/extra"

    BUILT_MODULE_NAME[2]="nvidia-drm"
    DEST_MODULE_LOCATION[2]="/extra"

    If [2] is changed to [3] for the “nvidia-drm”, all modules are built and installed without errors.

  137. I have just installed the kmod-nvidia packages into Fedora 23 and have now encountered a graphical boot issue. On a normal boot after selecting the grub boot menu entry the boot process would display a graphical boot Fedora logo for the length of the boot process. With your kmod drivers installed instead of the logo I get 3 different coloured thick lines overlaying each other at the bottom of the screen progressing across the screen to indicate boot progress. I have tried to play around with the GRUB_GFXPAYLOAD_LINUX option in /etc/default/grub but nothing I set makes any difference. I have made sure that after every change I update grub.cfg and update the mbr, but it always functions as if GRUB_GFXPAYLOAD_LINUX=text is set.
    Do you have any idea what in your drivers would be causing this or what I need to set in /etc/default/grub to get the standard Fedora Graphical Boot Screen back again?

    1. I think you have some leftover from other installations, as I don’t disable the graphical boot up on installation. Check that you have only the lines listed in the scripts section of the nvidia-driver package:

      $ rpm -q --scripts nvidia-driver
      postinstall scriptlet (using /bin/sh):
      if [ "$1" -eq "1" ]; then
        /usr/sbin/grubby --update-kernel=ALL --args='nouveau.modeset=0 rd.driver.blacklist=nouveau nomodeset gfxpayload=vga=normal' &>/dev/null
        sed -i -e 's/GRUB_CMDLINE_LINUX="/GRUB_CMDLINE_LINUX="nouveau.modeset=0 rd.driver.blacklist=nouveau nomodeset gfxpayload=vga=normal /g' /etc/default/grub
      fi || :
      preuninstall scriptlet (using /bin/sh):
      if [ "$1" -eq "0" ]; then
        /usr/sbin/grubby --update-kernel=ALL --remove-args='nouveau.modeset=0 rd.driver.blacklist=nouveau nomodeset gfxpayload=vga=normal' &>/dev/null
        sed -i -e 's/nouveau.modeset=0 rd.driver.blacklist=nouveau nomodeset gfxpayload=vga=normal //g' /etc/default/grub
      fi ||:
  138. I have run the rpm command and I only have the statements you have listed, which I am not surprised at as this is the first time I have ever installed these drivers. I didn’t know they existed until now.
    Is the GRUB_CMDLINE_LINUX statement in your script replacing the existing statement or inserting into the existing statement, as I have extra parameters on that statement that are not in your script.
    I had a similar problem when attempting to use the akmod drivers from rpmfusion which was resolved by using GRUB_GFXPAYLOAD_LINUX=keep, which seems to be ignored immediately upon using your drivers. It also doesn’t matter what I specify for this parameter the boot is always the same.
    It seems to me that from your script you are using grubby to generate grub.cfg and to update the mbr, is that correct, because if so it seems to me that you have the updating of /etc/defaul/grub and the execution of grubby in the wrong order in the script. Also I use grub2-mkconfig and grub2-install to create grub.cfg and to update the mbr, could that be causing an issue with your drivers?

    1. Hello, sorry for the late reply.

      The settings used in Grubby and /etc/default/grub are totally independent. Grubby uses its own command line parameters and is used to modify the existing grub configuration file, while the latter is only used when you run grub2-mkconfig to overwrite completely the file.

      In fact at the beginning I was not even shipping the settings in /etc/default/grub.

      The parameters to GRUB_CMDLINE_LINUX are added, the whole variable is never replaced as people could have different settings like you.

  139. Has anyone got this to work in fedora 24 (beta)?

    When I am trying to install nvidia-driver, it pulls in kernel-debug-devel 4.5.5-300.fc24, but the installed kernel is 4.5.6-300.fc24.x86_64.

    Also when I try to install kernel-devel it is version 4.5.5-300.fc24.

    When I go ahead and install anyway, I get the “Ooops, something went wrong” screen.

    1. There is something wrong with the dependencies in the packages installed. To have the modules built you require matching kernel and kernel-devel packages.

      1. Ok, yes. I will wait for the official f24 release and if the problem persists take it to askfedora. But it should work on f24 (provided I get the correct packages installed), correct?

        1. Just happened here as well. The fedora-rpos package for Fedora 24 has been updated, disabling the updates testing repository. This lead to some packages installed which are not yet available in the released updates.

          Just run a dnf distro-sync or dnf --enablerepo=updates-testing update and you should be good to go.

  140. Hi,
    I updated to 364.19-2 but it doesn’t boot anymore. It seems there are some remaining 364.19-1 packages. In journalctl it complains that the nvidia module could not be inserted by modprobe. With modinfo the only things that works is modinfo -n nvidia but modinfo nvidia also throws an error.
    Do you know what is going on?
    What would be the command to rollback to 364.19-1 for all the installed packages from your repo?
    Thanks

  141. Hi,
    I did a dnf update which install a new version of nvidia-driver but my system doesn’t work anymore and journalctl complains that the module nvidia could not be inserted. Weirdly enough the module has been built because I can see the file but modinfo nvidia throws an error after the first line (which shows the filepath). I check and it seems some version of packages are inconsistent 19-1 versus 19-2. Could this be the problem? Here is the list and I marked with an asterisk the affected packages:

    nvidia-driver.x86_64 2:364.19-2.fc22
    nvidia-driver-NVML.x86_64 2:364.19-2.fc22
    *nvidia-driver-NVML-devel.x86_64 1:352.79-1.fc22
    nvidia-driver-NvFBCOpenGL.x86_64 2:364.19-2.fc22
    nvidia-driver-cuda.x86_64 2:364.19-2.fc22
    nvidia-driver-cuda-libs.x86_64 2:364.19-2.fc22
    nvidia-driver-devel.x86_64 2:364.19-2.fc22
    nvidia-driver-libs.x86_64 2:364.19-2.fc22
    *nvidia-healthmon.x86_64 1:352.79-1.fc22
    *nvidia-libXNVCtrl.x86_64 2:364.19-1.fc22
    *nvidia-libXNVCtrl-devel.x86_64 2:364.19-1.fc22
    *nvidia-modprobe.x86_64 2:364.19-1.fc22
    *nvidia-persistenced.x86_64 2:364.19-1.fc22
    *nvidia-settings.x86_64 2:364.19-1.fc22
    *nvidia-validation-suite.x86_64 1:352.79-1.fc22
    *nvidia-xconfig.x86_64 2:364.19-1.fc22

    Thank you for your help

    1. I think I found what the problem was. The modules are now compressed .ko.xz and my script that call sign-file to sign the modules for the secure boot was actually signing the compressed module which would make it unreadable. Unstead you need to uncompress the module by calling unxz then sign the .ko file and then compress it again by calling xy.

      (ps: I sent my initial post twice because I thought it failed but it was simply awaiting moderation, and I was on a different computer so I would not see it, sorry for this)

      1. Thanks for letting me know. Would you mind sharing your script? Maybe I can create or provide some hook (and then instructions) for an easier signing of the modules once installed. Also, I’m about to trigger another update where I changed a bit the signing part.

    2. I don’t see the kmod/akmod/dkms packages there… btw, the important part is satisfied by the dependencies; so unless you got a dependency error, you can be sure that the packages you have installed are correct.

      As written in the table here: https://github.com/negativo17/nvidia-driver
      you can see that versions for some components are different.

  142. On fedora 22 the nvidia samples do not build anymore (also tried on fedora 23 with the same result):

    make
    make[1]: Entering directory '/usr/share/doc/cuda-samples/0_Simple/simpleTemplates'
    /usr/bin/nvcc -ccbin g++ -I../../common/inc  -m64    -gencode arch=compute_20,code=sm_20 -gencode arch=compute_30,code=sm_30 -gencode arch=compute_35,code=sm_35 -gencode arch=compute_37,code=sm_37 -gencode arch=compute_50,code=sm_50 -gencode arch=compute_52,code=sm_52 -gencode arch=compute_52,code=compute_52 -o simpleTemplates.o -c simpleTemplates.cu
    cc1plus: fatal error: cuda_runtime.h: No such file or directory
    compilation terminated.
    Makefile:229: recipe for target 'simpleTemplates.o' failed
    make[1]: *** [simpleTemplates.o] Error 1
    make[1]: Leaving directory '/usr/share/doc/cuda-samples/0_Simple/simpleTemplates'
    Makefile:52: recipe for target '0_Simple/simpleTemplates/Makefile.ph_build' failed
    make: *** [0_Simple/simpleTemplates/Makefile.ph_build] Error 2

    I could build gromacs using cuda but not the samples.
    Thanks

    1. There’s a missing “-I /usr/include/cuda” somewhere, the cuda_runtime.h header is not in /usr/include folder or you will have headers everywhere. Will check if I can patch samples directly.

      Thanks for reporting.

  143. Your host is extremely slow. Have you considered using copr for this?

    All in all, amazing work. This repo has made my life running linux on Mac Pro much much simpler.

    1. Would love to, but can not. Copr and official Fedora tools (Koji, etc.) can not be used for things that are in the list of forbidden items. So Nvidia drivers, cdrtools, all multimedia stuff, etc. They can’t serve but also can’t be used for building packages, so it’s a no go.

      Mirrors are welcome though 🙂

      1. I wouldn’t be able to help with a mirror, but I would be happy to donate some $$$ to help you boost your capacity, if this is possible. It would be a small token of gratitude for all the effort you put into providing these packages. Have you considered something like this? Maybe others would jump in as well, and with small amounts from a lot of people, we could do something nice.

        1. Thank you very much. That would be great. Actually in the main page there should be a button to donate through Paypal and a QR code for donating Bitcoins.
          If that is not the case… well, then I have a problem with WordPress 🙂

          1. The button is there, don’t worry =) I must say I haven’t paid attention to it before, though. Anyway, I will stand by my offer and make a donation. After all, life on Fedora + Nvidia is *much* simpler thanks to your efforts.

            BTW negativo17.org/site/ returns a 404.

  144. Having an issue getting the system to boot after installing the drivers on a fresh Fedora build. Only commands I ran after install were:

    dnf update
    reboot
    rpm -i rpmfusion-free-release-23.noarch.rpm
    rpm -i rpmfusion-nonfree-release-23.noarch.rpm
    dnf config-manager --add-repo=http://negativo17.org/repos/fedora-nvidia.repo
    dnf install nvidia-driver
    reboot

    After rebooting, the system hangs for a few seconds at “Starting switch root” and then crashes with the unrecoverable error screen. Uninstalling the drivers and re-enabling nouveau doesn’t seem to work either for some reason – getting the same crash. Any ideas on what’s wrong or how to fix this? Thanks.

    1. In the instructions I wrote there’s written to install kernel-devel as well, but I don’t see it in your commands.
      I think it’s the usual problem with kernel-debug-devel providing kernel-devel, so you don’t have the correct headers installed. That’s a known bug in Fedora open since forever.

  145. Hi,
    I still cannot get the Fedora 23 graphical boot logo after selecting the kernel to boot from, instead I get 3 different coloured horizontal bars at the bottom of the screen overlaying each other, that progress across the screen, to indicate boot progress. Playing around with GRUB_GFXPAYLOAD_LINUX doesn’t seem to impact this in any way. Is there something else I need to look at to resolve why this is happening with your drivers?

    1. Just further to this. To try and test things out I uninstalled all the nvidia related packages that were installed except the nouveau xorg driver package. This broke xorg as the system was no longer able to start it, apparently because it could no longer find any screens.
      To work around this I booted with the rescue entry in grub, which booted with the graphical Fedora logo, which booted to a console login, but did not enable the network so I couldn’t run a dnf install to reinstall your nvidia drivers. To fix this issue I booted into another linux distro I have installed and manually downloaded the rpms to a directory on my Fedora root partition and did a manual install of all the ones that didn’t have dependency issues that could be resolved from the rescue environment.
      Having gotten the packages installed, which included kmod-nvidia and akmod-nvidia packages, when I booted into each of the existing kernels, the boot process did an akmod-nvidia build process, but could not start xorg until I did a subsequent reboot off that kernel, why was xorg not able to use the akmod built driver immediately?
      Having gotten the drivers back in and usable, the boot process has reverted back to not displaying the graphical boot logo that is displayed from the rescue boot, why is this the case?
      Also after getting the drivers reinstalled I ran a system update which installed a newer kernel. When I booted into the new kernel the akmod build did not take place, hence that process was able to use the kmod-nvidia driver, so why couldn’t the kernels that were already installed when I reinstalled the nvidia drivers able to use the kmod driver?

  146. Hi,

    Thanks for the driver. Is it possible add in the nvidia.icd into /etc/OpenCL/vendors when installed to list the GPU as a OpenCL device?

    1. Hello, it is already done, you need to install the nvidia-driver-cuda package:

      $ sudo dnf provides /etc/OpenCL/vendors/nvidia.icd 
      nvidia-driver-cuda-2:367.27-1.fc24.x86_64 : CUDA integration for nvidia-driver
      Repo        : fedora-nvidia

      It will also load the unified video memory module, etc…

      1. Thanks for the quick reply! I somehow got into a state where I had the nvidia-opencl libraries but no .icd. It seems that those OpenCL libraries are loaded in with nvidia-driver-cuda-libs. I’ll keep that in mind for the future.

        Would it be better off moved it to an opencl package?

  147. Hello, thank you for the Nvidia drivers but I have a problem. I’m on Fedora 24, I installed the RPMFusion free and non-free repos. I installed “kernel-devel”, your repo and the drivers “$ sudo dnf config-manager –add-repo=”http://negativo17.org/repos/fedora-nvidia.repo” && sudo dnf install kernel-devel nvidia-driver dkms-nvidia nvidia-driver-libs.i686″. After a reboot that worked well but only for 5mn. After a few minutes the screen swicth to the tty ! I could go back to Gnome but the screen was corrupted and slow.

    I removed the drivers “sudo dnf remove \*nvidia\*” and I couldn’t boot anymore (black screen).

    I hope you can help me. Thanks !

    1. I reinstall Fedora 24 and tried with “dnf install nvidia-driver akmod-nvidia kernel-devel” and it’s the same. After a few minutes the screen swicth to the tty ! The one where there is some boot infos.

      1. For the nvidia drivers removing that produce a black screen it seems to be related to libglvnd that is not removed.

          1. Yeah, I thought about it, but eventually this package would be replaced by an official one and there are plans to use it also on AMD Catalyst drivers, so I can’t make it require Nvidia drivers. Maybe I can add some weak requriments in the RPM package like the CUDA driver part for FFMPeg libraries?

          2. I don’t know how you can deal with this package but I know that if someone remove the nvidia driver he should not have a black screen 😀 It took me some time to find it was the culprit.

            If a weak requirement in the RPM package can avoid the black screen it’s ok. Maybe a little note should be add where you explain how to remove the driver to avoid more people having a black screen in the mean time ?

      2. If you added RPMFusion, then those commands would install the RPMFusion version of the nvidia driver. AFAIK, the F24 repo for negativo17 still has some problems. It does not work with akmod-nvidia, and dkms-nvidia doesn’t actually install anything.

        1. I’m using Fedora 24 like a lot of other people here, and it both works with akmods and DKMS packages.
          Did you follow the guide? Did you make sure that kernel-devel is installed and and not kernel-debug-devel as described in the instructions?

          There is only an issue after about 5-10 minutes where the screen will disappear and show the boot log, and you have to Ctrl+Alt+F2 to get back to the desktop. It’s not related to the Nvidia driver, it’s a bug in Gnome Shell which fix has not yet been ported to Fedora 24 packages:

          https://github.com/GNOME/gnome-shell/commit/5226d8b0864fa894f180b8584e837aaf565578b2
          https://bugzilla.gnome.org/show_bug.cgi?id=764898
          https://bugzilla.redhat.com/show_bug.cgi?id=1350184

  148. Hey,

    I am using Fedora 24 and your nvidia driver. I have an issue after about 5-10 minutes where the screen will disappear and show the boot log. If I then Ctrl+Alt+F2 I get back to the desktop and from there on in am good. I was using a 660 but yesterday got the 960 and both do exactly the same …

    Any help ?

    Thanks

  149. I have installed the 340 driver in fedora 24 MATE and I get a “failed to query glx server vendor” in the nvidia server settings. And of course i have no 3d acceleration.
    This is a great advance since the nvidia blob could not make a graphical start.
    Any ideas?

    Thanks very much for your help.

  150. After installing nvidia driver on my Fedora 24 installation, computer crashes with this message: “Wećome to emergency mode! …”

  151. Hello I installed a fresh Fedora 24 on a laptop with a Core I7 that has an integrated Intel graphics. And the laptop has a geforce 850m as well. So I enabled your repos and installed the drivers. It seems that nouveau is disabled automatically after installing nvidia drivers from your repo wich is great, I think. The nvidia modules are loaded and the display manager shows as normally. But when I try to log in, black screen and then it switchs back to the display manager. Any clues??

  152. Following my upgrade to Fedora 24 I have issued the command dnf repoquery –unsatisfied as recommended on site https://fedoraproject.org/wiki/DNF_system_upgrade to see if there are any old packages that should be removed because they would not be working properly anyway, and received the following messages which to me make no sense, unless I am completely misinterpreting the message.

    The kernel mentioned in the first message is the last of the Fedora 23 kernels that is still installed after the upgrade to F24, while the kernel listed in the 2nd message is the kernel installed by a sudo dnf upgrade issued the day after the upgrade to F24. Hence the bottom line is both kernels mentioned in the messages are installed, so why is dnf reporting that it can’t find them?

    package kmod-nvidia-4.5.7-200.fc23.x86_64-2:367.27-1.fc24.x86_64 requires kernel-uname-r = 4.5.7-200.fc23.x86_64, but none of the providers can be installed
    package kernel-4.6.3-300.fc24.x86_64 requires kernel-core-uname-r = 4.6.3-300.fc24.x86_64, but none of the providers can be installed

    1. I got an X11 oops after upgrading my Fedora 23 system to Fedora 24. The nvidia driver wouldn’t load and it turned out that /lib/modules/4.6.3-300.fc24.x86_64/modules.dep wasn’t updated for the extra/nvidia drivers. I booted the Fedora 23 4.5 kernel, removed the kmod-nvidia-4.6.3-300.fc24.x86_64-367.27-1.fc24.x86_64 rpm and rebuild with akmods –kernels 4.6.3-300.fc24.x86_64. My next boot of the Fedora 24 kernel 4.6.3 worked fine. I don’t know why the modules.dep file wasn’t update properly. Thanks for all your work on creating the nvidia rpm packages.

  153. Hi,
    In my case you’re driver is the only working on a fresh install of F24 with 1080 cards…
    I tried RPMfusion / UnitedRPMs, with them i got the grey screen saying “oops something got wrong ….”

    Maybe someone can reply to that:
    1. How is that possible ?
    2. Can i stay with your drivers with a 90% chance they’ll don’t break (this is on production machines)
    3. I saw maybe I need to install the akamods but I don’t get a thing : with the “classic” non akmod driver if the kernel is updated do I get into trouble each times ?

    1. Hello, good to hear that they work for you. For the answers:

      1. I don’t know, I don’t even know how they are packaged anymore
      2. Yes, they have been available for quite a few years now and if you look at the page there’s even the kind of version (long lived, short lived, beta) version that is supported on each distribution
      3. DKMS and akmods are just two variants of the same thing. It just happens that I’m also the Fedora/EPEL mantainer of DKMS, but that’s it. Feel free what you think is right for you.

  154. There appears to be some problem between mesa-libGLES and libglvnd on libGLESv2.so.2()(64bit). I haven’t yet installed the nvidia driver yet on my desktop, but I did enable the nvidia repo (as well as the multimedia repo) and did an update which upgrades gstreamer1-plugins-bad. This pulls in libglvnd rather than mesa-libGLES (as my laptop did) which breaks nouveau and leads to an oops screen. It complains about missing symbol _glapi_check_multithread. The goal is install the nvidia driver, but seems this strange intermediate state causes some problems. Just want to make you and others aware of this problem enabling the nvidia repo and the multimedia repo but not yet having the nvidia driver installed. To fix the problem I installed mesa-libGLES then removed libglvnd. Maybe this could be an explicit requires so it somehow prefers the mesa-libGLES package?

    1. Hello, yes there is some cause/effect thing in place. First of all, gstreamer1-plugins-bad requires libGL and libEGL to be present:

      # rpm -q --requires gstreamer1-plugins-bad | egrep "libGL|libEGL"
      libEGL.so.1()(64bit)
      libGL.so.1()(64bit)
      libGLESv2.so.2()(64bit)

      These in turn are offered by both mesa-libGL and mesa-libEGL. But if you have Nvidia driver repository enabled, they are provided by libglvnd; at least until Fedora base components will provide a libglvnd compatible mesa libGL. Those will take precedence, as if you have the Nvidia driver repository enabled this means you are actually asking for the driver. So, if you don’t need the driver, do not enable the repository for it.

      Otherwise, if you now want everything (Nvidia driver + CUDA + 32 bit GL support), just do a:

      dnf -y install kernel-devel dkms-nvidia nvidia-driver-cuda nvidia-driver-libs.i686

      and you should be good to go. Something similar to the GL thing is the libcuda.so.1 loading in FFMpeg:

      # rpm -q --whatrecommends nvidia-driver-cuda-libs
      ffmpeg-libs-3.1.1-1.fc24.x86_64

      If you have the Nvidia repository enabled, then FFMpeg pulls in the “recommended” packages, otherwise it just skips them. So if you have the Nvidia driver repository enabled but you don’t want to use it, you will end up with unwanted components.

      Separate all these things is not easy, especially that now FFmpeg 3.1.1 can dynamic link CUDA libraries for the NPP acceleration (I haven’t enabled that yet). I might change it when merging all repositories together into 1. I will make an update on the repository page with the above details.

Leave a Reply