CUDA 9.0, cuDNN 7.0 and Wayland support in Fedora 27

The Nvidia repository now contains packages for Fedora 27. This is with the release candidate of CUDA 9, and it contains also cuDNN at version 7.0, which is the only version supported with CUDA 9 at the moment of writing.

The updated cuDNN 7.0 library has been added also to the other branches, this means it will be automatically upgraded from version 6.0 to 7.0. If you still need one of the previous versions, just remove it and install one of the compatibility packages:

# dnf list cuda-cudnn*
Installed Packages
cuda-cudnn.x86_64                   1:7-1.fc26         @fedora-nvidia
Available Packages
cuda-cudnn-devel.x86_64             1:7-1.fc26         fedora-nvidia 
cuda-cudnn5.1.x86_64                1:5.1-2.fc26       fedora-nvidia 
cuda-cudnn5.1-devel.x86_64          1:5.1-2.fc26       fedora-nvidia 
cuda-cudnn6.0.x86_64                1:6.0-1.fc26       fedora-nvidia 
cuda-cudnn6.0-devel.x86_64          1:6.0-1.fc26       fedora-nvidia

CUDA 9 supports GCC 6.x and CLANG 3.9, so when it will be officially released, it will cover Fedora 25 and RHEL/CentOS compilers. With Fedora 27, there will be the usual need for a GCC compatibility package (like the compat-gcc53 package currently in the repository) as GCC is at version 7 and CLANG is at version 4.0.

I will try to provide a compat-gcc64 for Fedora 27+ at the time of the official CUDA 9 release.

Regarding the drivers, on Fedora 27 where Mutter 3.25+ is available, the modesetting part of the Nvidia drivers has been enabled by default, this means that at the login you can just select “GNOME” to run Gnome on Wayland. Please note that X 3D programs running on XWayland might not work properly.

13 thoughts to “CUDA 9.0, cuDNN 7.0 and Wayland support in Fedora 27”

  1. A fresh install of fedora 27 beta and the akmod-nvidia package leaves the following in /var/cache/akmods/akmods.log:

    2017/11/02 21:57:05 akmods: Checking kmods exist for 4.13.10-300.fc27.x86_64
    2017/11/02 21:57:05 akmods: Files needed for building modules against kernel
    2017/11/02 21:57:05 akmods: 4.13.10-300.fc27.x86_64 could not be found as the following
    2017/11/02 21:57:05 akmods: directories are missing:
    2017/11/02 21:57:05 akmods: /usr/src/kernels/4.13.10-300.fc27.x86_64/
    2017/11/02 21:57:05 akmods: /usr/lib/modules/4.13.10-300.fc27.x86_64/build/
    2017/11/02 21:57:05 akmods: Is the correct kernel-devel package installed?

    I discovered that the kernel-devel package for the 4.13.10 kernel version is NOT installed, only the 4.10.9 version is installed.

    I solved this by downloading the right package at the following URL and install it manually:

    https://koji.fedoraproject.org/koji/buildinfo?buildID=991436

    After a reboot the akmods.log file reads:

    2017/11/02 22:09:30 akmods: Checking kmods exist for 4.13.10-300.fc27.x86_64
    2017/11/02 22:09:30 akmods: Building and installing nvidia-kmod
    2017/11/02 22:09:30 akmods: Building RPM using the command ‘/sbin/akmodsbuild –target x86_64 –kernels 4.13.10-300.fc27.x86_64 /usr/src/akmods/nvidia-kmod.latest’
    2017/11/02 22:11:18 akmods: Installing newly built rpms
    2017/11/02 22:11:18 akmods: DNF detected
    2017/11/02 22:11:24 akmods: Successful.

  2. Hello Slaanesh,

    there seems to be an issue with the fedora-multimedia updates for f26 from 2017-10-23:
    “gstreamer1-plugins-bad-1:1.12.3-2.fc26.x86_64” needs “libQt5Core.so.5(Qt_5.9)(64bit)”, which cannot be resolved, probably because f26 is still on qt 5.7. What can I do to resolve this? Thanks a lot.

  3. Unfortunately, it seems I can only run Wayland under llvmpipe. X still seems to be working fine, but I can’t get Wayland to use nVidia. I’ve tried disabling selinux at one point, but it didn’t seem to change anything.

    Am I wrong in thinking it should just work under 27? Should I be able to simply install the driver and have it work, or is there another step required?

  4. Just upgrade to Fedora 27 beta with neweast nvidia driver from the repo here, I (seems also) encounter the problem that GDM just crashed that only an Logout button showed for me, while it goes fine if nouveau is driving the display. It’s interesting that, after several tries, I found the GDM could be launched if SELinux is disabled.
    By the way, still, my session type is X11 rather than wayland, with nvidia-drm.modeset=1.

    1. It seems to be an SELinux issue, this should temporarily fix it:

      ausearch -c 'gnome-session-c' --raw | audit2allow -M mygnomesession.c
      semodule -X 300 -i mygnomesession.c.pp

      This is what is in audit.log:

      allow xdm_t xserver_misc_device_t:chr_file map;
  5. On my side, i have some issues with F27 beta after the upgrade… I can’t launch GDM without an error message “Oh no something has gone wrong”. I am obliged to do alt + F2 and run a startx for everything to work. Under nouveau everything works. I have blocked wayland in the gdm configuration. i had no problems with the negativo drivers under F26.

  6. apparently it’s not just me (it came out in other comments as well) but your beautiful work/repos aren’t usable in some parts of the world, DNF shuts itself complaining for low downloading speeds (below 5Kb/s). Never had any problems with other repos. Such a pity. Any idea? thanks for yiur work PS may I suggest you to start a survey on the issue?

Leave a Reply