CUDA 8, cuDNN, Nvidia drivers and GNOME Software metadata

GNOME software integration

The Nvidia driver repository has been updated with AppStream metadata. From Fedora 25 onward, you will be able to search for Nvidia, CUDA, GeForce or Quadro to make the driver, control panel and other programs appear in the Gnome Software window.

As far as I know, this should be enabled by default on Fedora 25.


Thanks to Richard Hughes for helping out with the metadata.

I require proper 16:10 aspect ratio pictures for both NSight and the Visual Profiler running on Fedora, so if you want to contribute just drop me an email or open an issue on the CUDA package on GitHub.

Changes to the Nvidia driver packaging

The Nvidia driver can now be installed without nvidia-settings (the control panel utility) as requested by Red Hat, in preparation for the Gnome software integration. This means the dependencies have been reversed, and that to install the driver and the control panel you need to install nvidia-settings or the driver and nvidia-settings:

dnf/yum -y install nvidia-settings kernel-devel

The libglvnd package has been updated to the latest snapshot and now features all the changes that have been introduced by Adam Jackson for the Mesa GLVND integration in Fedora 25. This means that while installing you will be prompted to install/upgrade smaller packages that contain a subset of the libglvnd libraries, this includes EGL support for the recently released beta drivers version 375.10. For anything lower than 375.10 (so Fedora 23-24 and CentOS/RHEL 6/7 at the moment of writing this) Nvidia’s last official note on EGL is:

“, while not a proper GLVND library, depends upon the GLVND infrastructure for proper functionality. Therefore, any driver package which aims to support NVIDIA EGL must provide the GLVND libraries […]”

So for now, in Fedora 23, 24 and CentOS/RHEL 6/7:

$ rpm -q --requires nvidia-driver-libs.x86_64 | grep libglvnd
libglvnd-gles(x86-64) >= 0.1.1
libglvnd-glx(x86-64) >= 0.1.1
libglvnd-opengl(x86-64) >= 0.1.1
$ rpm -q --conflicts nvidia-driver-libs.x86_64 | grep libglvnd
libglvnd-egl(x86-64) >= 0.1.1

And for Fedora 25:

$ rpm -q --requires nvidia-driver-libs.x86_64 | grep libglvnd
libglvnd-egl(x86-64) >= 0.2
libglvnd-gles(x86-64) >= 0.2
libglvnd-glx(x86-64) >= 0.2
libglvnd-opengl(x86-64) >= 0.2

Not a big deal. This accommodates the ongoing modularization in Mesa but still preserves the original EGL libraries from Nvidia. The upgrade should be transparent and you should not notice any difference except some smaller packages being installed.

vulkan_500px_june16Vulkan is now part of Fedora, so on supported Fedora releases, the Vulkan loader and libraries can be installed and you do not need to do anything to enable support in the drivers. CentOS and Red Hat Enterprise Linux do not have Vulkan yet. I’m not sure if it’s worth installing it by default along with the drivers, though.

Let’s assume you have a freshly installed Fedora 25 system with a recent Nvidia GPU and you want to:

  • Install the driver for gaming
  • Play Vulkan enabled games
  • Want to be comfortable with the control panel
  • Play 32 bit games on a 64 bit system
  • Play 32 bit Vulkan games on a 64 bit system
$ sudo dnf install nvidia-settings kernel-devel dkms-nvidia vulkan.i686 nvidia-driver-libs.i686
Last metadata expiration check: 0:33:49 ago on Mon Oct 24 14:14:30 2016.
Dependencies resolved.
 Package            Arch   Version                             Repository       Size
 dkms-nvidia        x86_64 2:375.10-1.fc25                     fedora-nvidia   6.4 M
 libglvnd           i686   1:0.2.999-4.20161025git28867bb.fc25 fedora-nvidia   103 k
 libglvnd           x86_64 1:0.2.999-4.20161025git28867bb.fc25 fedora-nvidia   105 k
 libglvnd-egl       i686   1:0.2.999-4.20161025git28867bb.fc25 fedora-nvidia    44 k
 libglvnd-egl       x86_64 1:0.2.999-4.20161025git28867bb.fc25 fedora-nvidia    42 k
 libglvnd-gles      i686   1:0.2.999-4.20161025git28867bb.fc25 fedora-nvidia    29 k
 libglvnd-gles      x86_64 1:0.2.999-4.20161025git28867bb.fc25 fedora-nvidia    28 k
 libglvnd-glx       i686   1:0.2.999-4.20161025git28867bb.fc25 fedora-nvidia   114 k
 libglvnd-glx       x86_64 1:0.2.999-4.20161025git28867bb.fc25 fedora-nvidia   110 k
 libglvnd-opengl    i686   1:0.2.999-4.20161025git28867bb.fc25 fedora-nvidia    39 k
 libglvnd-opengl    x86_64 1:0.2.999-4.20161025git28867bb.fc25 fedora-nvidia    38 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:375.10-3.fc25                     fedora-nvidia   3.1 M
 nvidia-driver-NVML x86_64 2:375.10-3.fc25                     fedora-nvidia   397 k
 nvidia-driver-libs i686   2:375.10-3.fc25                     fedora-nvidia    15 M
 nvidia-driver-libs x86_64 2:375.10-3.fc25                     fedora-nvidia    14 M
 nvidia-libXNVCtrl  x86_64 2:375.10-1.fc25                     fedora-nvidia    26 k
 nvidia-settings    x86_64 2:375.10-1.fc25                     fedora-nvidia   935 k
 vulkan             i686                     updates-testing 1.5 M
 vulkan-filesystem  noarch                     updates-testing 8.0 k

Transaction Summary
Install  21 Packages

Total download size: 42 M
Installed size: 178 M
Is this ok [y/N]:

Note that the requirement on kernel-devel is still required as otherwise the package kernel-debug-devel is pulled in automatically in place of the normal non-debug package. There is bug opened on dnf/libsolv for this.

Changes to CUDA packaging

The CUDA packages hosted on the Nvidia repository are split into multiple subpackages, based on the library. For each library, you have the corresponding devel subpackage with the headers, the unversioned library symlink and the static library. Here, they were divided in one libs, one big extra-libs, one static and one devel subpackage for everything. Since I’m planning to enable CUDA/NVCUVID encoding/decoding in FFmpeg (I’m actually waiting to the dynamic loader patches to land in the 3.2 branch before enabling that) there should be a way to install just what is required by those functions and not the whole CUDA toolkit set of libraries.

So now, all the libraries are split into subpackages, much like in the original Nvidia CUDA repository. This allows you to install and build software relying on specific components without the need to install all the CUDA toolkit just to satisfy a library dependency. With the new packaging organization, the original cuda-devel and cuda-extra-libs will pull in all the specific subpackages giving you the same situation you are accustomed to. Also, for the same reason, static libraries have been included in each respective devel subpackage.

Example, just with the basic tools:

$ sudo dnf install cuda
Last metadata expiration check: 0:00:20 ago on Sun Oct 23 13:11:01 2016.
Dependencies resolved.
 Package           Arch         Version               Repository           Size
 cuda              x86_64       1:8.0.44-4.fc24       fedora-nvidia        95 M
 cuda-cufft        x86_64       1:8.0.44-4.fc24       fedora-nvidia        97 M
 cuda-curand       x86_64       1:8.0.44-4.fc24       fedora-nvidia        38 M
 cuda-libs         x86_64       1:8.0.44-4.fc24       fedora-nvidia       6.4 M

Transaction Summary
Install  4 Packages

Total size: 236 M
Installed size: 469 M
Is this ok [y/N]:

The basic tools along with all the libraries (note that the NVML headers are included):

$ sudo dnf install cuda-devel
Last metadata expiration check: 0:10:00 ago on Sun Oct 23 13:11:01 2016.
Dependencies resolved.
 Package                 Arch       Version             Repository         Size
 cuda                    x86_64     1:8.0.44-4.fc24     fedora-nvidia      95 M
 cuda-cublas             x86_64     1:8.0.44-4.fc24     fedora-nvidia      21 M
 cuda-cublas-devel       x86_64     1:8.0.44-4.fc24     fedora-nvidia      38 M
 cuda-cudart             x86_64     1:8.0.44-4.fc24     fedora-nvidia     131 k
 cuda-cudart-devel       x86_64     1:8.0.44-4.fc24     fedora-nvidia     659 k
 cuda-cufft              x86_64     1:8.0.44-4.fc24     fedora-nvidia      97 M
 cuda-cufft-devel        x86_64     1:8.0.44-4.fc24     fedora-nvidia      73 M
 cuda-cupti              x86_64     1:8.0.44-4.fc24     fedora-nvidia     1.2 M
 cuda-cupti-devel        x86_64     1:8.0.44-4.fc24     fedora-nvidia     213 k
 cuda-curand             x86_64     1:8.0.44-4.fc24     fedora-nvidia      38 M
 cuda-curand-devel       x86_64     1:8.0.44-4.fc24     fedora-nvidia      60 M
 cuda-cusolver           x86_64     1:8.0.44-4.fc24     fedora-nvidia      23 M
 cuda-cusolver-devel     x86_64     1:8.0.44-4.fc24     fedora-nvidia     4.1 M
 cuda-cusparse           x86_64     1:8.0.44-4.fc24     fedora-nvidia      23 M
 cuda-cusparse-devel     x86_64     1:8.0.44-4.fc24     fedora-nvidia      23 M
 cuda-devel              x86_64     1:8.0.44-4.fc24     fedora-nvidia     1.6 M
 cuda-libs               x86_64     1:8.0.44-4.fc24     fedora-nvidia     6.4 M
 cuda-npp                x86_64     1:8.0.44-4.fc24     fedora-nvidia      91 M
 cuda-npp-devel          x86_64     1:8.0.44-4.fc24     fedora-nvidia      47 M
 cuda-nvgraph            x86_64     1:8.0.44-4.fc24     fedora-nvidia     4.6 M
 cuda-nvgraph-devel      x86_64     1:8.0.44-4.fc24     fedora-nvidia      12 k
 cuda-nvml-devel         x86_64     1:8.0.44-4.fc24     fedora-nvidia      41 k
 cuda-nvrtc              x86_64     1:8.0.44-4.fc24     fedora-nvidia     6.6 M
 cuda-nvrtc-devel        x86_64     1:8.0.44-4.fc24     fedora-nvidia      16 k

Transaction Summary
Install  24 Packages

Total size: 655 M
Installed size: 1.4 G
Is this ok [y/N]:

The nvidia-driver-NVML-devel package, which was including the NVML header (for has now been made obsolete by the new headers, which are now part of CUDA 8. So the cuda-nvml-devel package will take care of that. Again, this is the same as in the Nvidia repository. Everything that was requiring the NVML header now refers to that package instead of the previous one. I will leave it for a few releases like that and then I will remove the Obsolete/Provides tags from the various SPEC files.

The header is also required for building the latest nvidia-settings from the 375.10 source, this has been taken into account making the CUDA package buildable on i686 but generating only the cuda-nvml-devel subpackage.

Extra stuff

In addition to the libraries bundled in the CUDA toolkit, also the cuDNN library for distributed neural networks is included in the repository.

As usual, you are welcome to open bugs / request stuff / comment on the GitHub repositories.

48 thoughts to “CUDA 8, cuDNN, Nvidia drivers and GNOME Software metadata”

  1. Hi. The package libva-vdpau-driver is no longer present. Thus the dependency has failed for nvidia-driver-410.73-4.el7.x86_64. Can you help me to locate this missing library? Thank you!

    Error: Package: 3:nvidia-driver-410.73-4.el7.x86_64 (epel-nvidia)
    Requires: libva-vdpau-driver(x86-64)

  2. For RHEL7, it looks like the nvidia.ko module in kmod-nvidia is not compatible with the latest kernel (3.10.0-514.10.2).

  3. I have a T430 notebook with a nvidia nvs 5400m gpu (optimus) and would like to use the 375.26 driver from this repo, but it doesn’t show up in software and if i install it via dnf i don’t get the login screen. Fedora 25 just shows the warring that something went wrong. I think the gpu should be supported by the driver because nvidia direct me to 375.26 if i download the driver from their site. Any idea on this problem?

    1. Did you configure your system for Optimus? That does not work yet out of the box (will probably be in time for Fedora 26):
      Did you configure your system appropriately for Optimus?

      Not in Fedora 25 yet:
      – EGLStreams support for Mutter (Wayland on binary drivers)
      – GLVND enabled Mesa (no overriding of GL libraries)
      – Extended OutputClass for device options is included already in X server 1.19.0-3, I’m making tests now but I will not probably push anything in the repositories before christmas: (last 3 commits)

      1. I haven’t configured anything for optimus. Thought i could just replace nouveau with the nvidia driver, and nouveau works fine so far. Except wayland, but i think that is as you said okay because F25 doesn’t support that for now and automatically fallback to X.
        Do i get this right, i just have to configure my xorg.conf the right way and i should work?

  4. So I was really hopeful that this repo would help me eliminate our cuda woes… but when I use it to install Nvidia 375 driver and CUDA 8.0, I’m getting the following issues with NVML when running code: (The driver version “375.20” does not contain a supported version of NVML. )

        1. After installation, ran nvidia-healthmon and get the following:

          # nvidia-healthmon

          Using config file path: /etc/nvidia-healthmon/nvidia-healthmon.conf

          Loading Config: SUCCESS
          Global Tests
          Black-Listed Modules: SKIPPED
          Black-Listed Drivers: SUCCESS
          Load NVML: SUCCESS
          NVML Sanity
          The driver version “375.20” does not contain a supported version of NVML.
          Result: CRITICAL ERROR
          Global Test Results: 5 success, 1 errors, 0 warnings, 4 did not run

          System Results: 5 success, 1 errors, 0 warnings, 4 did not run
          One or more tests didn’t run.
          One or more tests failed.

          1. Ok, nvidia-healthmon is a binary only application provided by Nvidia and statically linked to libnvidia-ml, and was included in the Gpu Deployment Kit (NVML header) 352.79. This has been obsoleted by CUDA 8, which now includes the NVML header. The old Gpu Deployment Kit is not supported anymore. I left the packages there as I did not know what to do exactly with them, but now that 375.20 is a long lived release I should probably remove them.

            To test something using NVML you should compile something with recent headers, for example one of the CUDA samples (package cuda-samples).

  5. Hi, I have a problem with nvidia-settings on fedora 24. It’s the first time I try nvidia-drivers from this repository.
    When I try start nvidia-settings this happens:
    nvidia-settings: libXNVCtrlAttributes/NvCtrlAttributesNvml.c:1690: NvCtrlNvmlGetValidAttributeValues: Assertion `ret2 == NvCtrlAttributeNotAvailable’ failed.

    I installed nvidia-driver* nvidia-persistenced nvidia-settings nvidia-xconfig (and some other packages for cuda). All is working fine except nvidia-settings.

    It is a known problem or am I missing something?

    1. I had the same issue on Fedora 25, I downloaded the source for nvidia-settings and compiled a working version. I needed it to change the LED’s on my video cards, and the bundled nvidia-settings binary didn’t expose the GPULogoBrightness attribute for some reason. The one I built from src did, you can find the src for nvidia-settings here: and my built 375.20 Fedora 25 nvidia-settings binary here:

      1. It does work fine for my cards on both Fedora and RHEL 7, but I don’t have any that have any adjustable led.

        Do you have the NVML library (nvidia-driver-NVML) installed? That is dynamically loaded at runtime by nvidia-settings. Can you try without having it installed?

        1. I noticed that it works fine without nvidia-driver-NVML but unfortunately I need nvidia-driver-cuda, so it can’t be uninstalled.

          375.20 is out now, so i’ll check if with it the problem is resolved

          1. I was hit by the same error while I was messing with “coolbits”. Apparently not all attributes are “supported”, especially for coolbits >= 8. Fan speed control works just fine. I added those missing attributes somewhere in NvCtrlAttributesNvml.c
            + case NV_CTRL_GPU_NVCLOCK_OFFSET:
            and recompiled nvidia-settings. I am not really sure whether it is a proper solution, but at least nvidia-settings does not crash anymore.

    2. It does work fine for my cards on both Fedora and RHEL 7, but I don’t have any that have any adjustable led.

      Do you have the NVML library (nvidia-driver-NVML) installed? That is dynamically loaded at runtime by nvidia-settings. Can you try without having it installed?

  6. Could you please help me with cuda setup on F24 with NVidia 340xx drivers (GTX260)?
    I have the following packages installed:

    rpm -qa | grep cuda

    rpm -qa | grep nvidia

    How do I verify that cuda is working?
    If I try installing cuda-devel I get nvidia-driver-NVML 2:375.20-1.fc24 dependency.
    Is cuda supported on 340.xx?

  7. Having installed all the cuda rpms, I am unable to build the samples. nvcc returns this error: nvcc fatal : Path to libdevice library not specified. A “find / -name “libdevice* finds nothing except the pdf and the html folder for the libdevice-users-guide. What rpm would normally have these files? Have not figured out yet where my screw-up is.

    1. Sorry for the late reply:

      $ nvcc --help | grep -A3 libdevice-directory
      --libdevice-directory           (-ldir)                           
              Specify the directory that contains the libdevice library files when option
              '--dont-use-profile' is used.  Libdevice library files are located in the
              'nvvm/libdevice' directory in the CUDA toolkit.
      $ rpm -ql cuda | grep libdevice
      1. Thank you Slaanesh! A “dnf reinstall cuda” did the trick. Not sure what happened prior. OK, I can’t resist quoting Lord of the Rings: “A Wizard is never late…”

    1. Would love to, but I don’t have any hardware nor enough systems to cross-check everything (various Fedora releases and various RHEL/CentOS releases available).

  8. With Fedora 25 and your driver I get the “incompatible ABI” message. Anything you can do about that? Or anything I’m doing wrong?

    1. There’s no Nvidia driver that supports X server version 1.19, that’s part of their policy of not supporting unreleased kernels and X servers. They’re pretty fast in adding support once they are released, though. And most of the time it just works with IgnoreABI.

      I’ve pushed an updated that enables the flag also on Fedora 25.

      1. Thanks for that. Indeed I have by now tried using that flag, but X just segfaults. So I guess I’ll have to wait for to do their final release.

  9. It’s been a while that I am having issues with the kernel/nvidia drivers. After these changes I have more dependency problems. Is there anything I can do to resolve this on my end?

    Packages skipped because of dependency problems:
    kernel-3.10.0-327.36.3.el7.x86_64 from updates
    kmod-20-8.el7_2.x86_64 from updates
    2:kmod-nvidia-367.57-1.el7.x86_64 from epel-nvidia
    1:libglvnd-gles-0.2.999-4.20161025git28867bb.el7.i686 from epel-nvidia
    1:libglvnd-gles-0.2.999-4.20161025git28867bb.el7.x86_64 from epel-nvidia
    1:libglvnd-glx-0.2.999-4.20161025git28867bb.el7.i686 from epel-nvidia
    1:libglvnd-glx-0.2.999-4.20161025git28867bb.el7.x86_64 from epel-nvidia
    1:libglvnd-opengl-0.2.999-4.20161025git28867bb.el7.i686 from epel-nvidia
    1:libglvnd-opengl-0.2.999-4.20161025git28867bb.el7.x86_64 from epel-nvidia
    2:nvidia-driver-367.57-4.el7.x86_64 from epel-nvidia
    2:nvidia-driver-libs-367.57-4.el7.i686 from epel-nvidia
    2:nvidia-driver-libs-367.57-4.el7.x86_64 from epel-nvidia
    2:nvidia-libXNVCtrl-367.57-1.el7.x86_64 from epel-nvidia
    2:nvidia-settings-367.57-1.el7.x86_64 from epel-nvidia


    1. There’s something weird with the kmod package. It has the same files inside but somehow it does not provide anymore /sbin/depmod PRIOR to installation, but once installed, everything is fine. Can you do one of the following?

      yum --exclude=kmod update

      and then update kmod.

      After that, you can update kmod through rpm or yum. I will rework kmodtool to look for other dependencies instead of /sbin/depmod once I’m back from holiday (wednesday).

      1. I did that and at least I can now use the system again (GNOME wasn’t even logging in due to an error) but the kmod package is refusing to update. Trying to update gives me this:

        Resolving Dependencies
        –> Running transaction check
        —> Package kmod.x86_64 0:20-5.el7 will be updated
        —> Package kmod.x86_64 0:20-8.el7_2 will be an update
        –> Processing Dependency: /sbin/depmod for package: 2:kmod-nvidia-367.57-1.el7.x86_64

        Packages skipped because of dependency problems:
        kmod-20-8.el7_2.x86_64 from updates

        Trying to remove it will remove so many dependencies…

        1. I’ve pushed an update to the kmod-nvidia package that takes into account the changes that have been put into kmod. So instead of searching for /sbin/depmod, which is available once installed but not available in the yum metadata for the same kmod package, it looks for module-init-tools which is an explicit provision in kmod.

           Package            Arch   Version                            Repository   Size
           nvidia-driver      x86_64 2:367.57-4.el7                     epel-nvidia 3.1 M
           kmod               x86_64 20-8.el7_2                         updates     114 k
          Installing for dependencies:
           kmod-nvidia        x86_64 2:367.57-2.el7                     epel-nvidia  11 M
           libglvnd           x86_64 1:0.2.999-4.20161025git28867bb.el7 epel-nvidia 101 k
           libglvnd-gles      x86_64 1:0.2.999-4.20161025git28867bb.el7 epel-nvidia  27 k
           libglvnd-glx       x86_64 1:0.2.999-4.20161025git28867bb.el7 epel-nvidia 120 k
           libglvnd-opengl    x86_64 1:0.2.999-4.20161025git28867bb.el7 epel-nvidia  40 k
           nvidia-driver-libs x86_64 2:367.57-4.el7                     epel-nvidia  14 M
           nvidia-libXNVCtrl  x86_64 2:367.57-1.el7                     epel-nvidia  22 k
           nvidia-settings    x86_64 2:367.57-1.el7                     epel-nvidia 938 k
          Transaction Summary
          Install  1 Package (+8 Dependent packages)
          Upgrade  1 Package
          Total download size: 29 M
          1. Wonderful! I can finally have all packages working.

            PS: No need to apologize! It should be me thanking for your work (so here it is… thanks!!)

          2. I have recently observed this when trying to update my Centos 7:

            Skipped (dependency problems):
            nvidia-driver x86_64 2:375.26-4.el7 epel-HandBrake 3.1 M
            nvidia-driver-libs i686 2:375.26-4.el7 epel-HandBrake 15 M
            nvidia-driver-libs x86_64 2:375.26-4.el7 epel-HandBrake 14 M

            Should I exclude epel-HandBrake?

            With the new repos, if I wanted to have all your repos and nvidia, for a new installation, which should I chose? I don’t know if any of the ones I’m using are “legacy” and should be disabled…


          3. Hello, can you paste here the last part of the output of your update command with the --best parameter? This should work without issues.
            Something like:

            dnf --best update

          4. You did not specify what distribution you were using. Please paste the extra output from the yum command.

          5. This is the output I get:

            Resolving Dependencies
            –> Running transaction check
            —> Package nvidia-driver.x86_64 2:375.20-2.el7 will be updated
            –> Processing Dependency: nvidia-driver = 2:375.20 for package: 2:kmod-nvidia-375.20-2.el7.x86_64
            —> Package nvidia-driver.x86_64 2:375.26-1.el7 will be updated
            —> Package nvidia-driver.x86_64 2:375.26-4.el7 will be an update
            —> Package nvidia-driver-libs.i686 2:375.26-1.el7 will be updated
            —> Package nvidia-driver-libs.x86_64 2:375.26-1.el7 will be updated
            —> Package nvidia-driver-libs.i686 2:375.26-4.el7 will be an update
            —> Package nvidia-driver-libs.x86_64 2:375.26-4.el7 will be an update
            –> Finished Dependency Resolution
            Error: Package: 2:kmod-nvidia-375.20-2.el7.x86_64 (@epel-nvidia)
            Requires: nvidia-driver = 2:375.20
            Removing: 2:nvidia-driver-375.20-2.el7.x86_64 (@epel-HandBrake)
            nvidia-driver = 2:375.20-2.el7
            Updated By: 2:nvidia-driver-375.26-4.el7.x86_64 (epel-HandBrake)
            nvidia-driver = 2:375.26-4.el7
            Removing: 2:nvidia-driver-375.26-1.el7.x86_64 (installed)
            nvidia-driver = 2:375.26-1.el7
            Updated By: 2:nvidia-driver-375.26-4.el7.x86_64 (epel-HandBrake)
            nvidia-driver = 2:375.26-4.el7
            Available: 2:nvidia-driver-340.101-1.el7.x86_64 (epel-nvidia-340)
            nvidia-driver = 2:340.101-1.el7
            You could try using –skip-broken to work around the problem
            ** Found 9 pre-existing rpmdb problem(s), ‘yum check’ output follows:
            ipa-client-4.4.0-14.el7.centos.4.x86_64 has installed conflicts freeipa-client: ipa-client-4.4.0-14.el7.centos.4.x86_64
            ipa-client-common-4.4.0-14.el7.centos.4.noarch has installed conflicts freeipa-client-common: ipa-client-common-4.4.0-14.el7.centos.4.noarch
            ipa-common-4.4.0-14.el7.centos.4.noarch has installed conflicts freeipa-common: ipa-common-4.4.0-14.el7.centos.4.noarch
            ipa-python-compat-4.4.0-14.el7.centos.4.noarch has installed conflicts freeipa-python-compat: ipa-python-compat-4.4.0-14.el7.centos.4.noarch
            2:kmod-nvidia-375.26-1.el7.x86_64 is a duplicate with 2:kmod-nvidia-375.20-2.el7.x86_64
            libmad-0.15.1b-19.el7.x86_64 is a duplicate with libmad-0.15.1b-18.el7.x86_64
            2:nvidia-driver-375.20-2.el7.x86_64 has missing requires of nvidia-driver-libs(x86-64) = (‘2’, ‘375.20’, None)
            2:nvidia-driver-375.26-1.el7.x86_64 is a duplicate with 2:nvidia-driver-375.20-2.el7.x86_64
            2:nvidia-libXNVCtrl-375.26-1.el7.x86_64 is a duplicate with 2:nvidia-libXNVCtrl-375.20-1.el7.x86_64

            Thanks for looking into this!

          6. You have a problem in your rpm database, a broken (interrupted) yum transaction. This has nothing to do with the Nvidia packages.
            Just use yum-complete-transaction and/or package-cleanup --cleandupes. Look on Google for documentation.

          7. Thanks, it did work! I tried to complete the transaction before posting, but it did not work. On the other hand, your other suggestion to cleandupes resolved my rpm database issues.

Leave a Reply