If you did not migrate your account yet, visit https://idp-portal-info.suse.com/
- 1 Situation
- 2 Procedure
- 3 Uninstalling the NVIDIA drivers
- 4 Troubleshooting
- 5 See also
Installing the official NVIDIA drivers using ZYpp (YaST or Zypper) is desired.
For information regarding NVIDIA's official linux .run file see "the hard way".
Installing with YaST or Zypper requires root privileges.
Add the Nvidia Repository
The NVIDIA drivers can not be included with openSUSE because of their license. Conveniently, NVIDIA has an openSUSE repository that can be added and downloaded from.
- Open YaST, then click Software Repositories.
- Click Add (in the bottom left), then select Community Repositories.
- Select NVIDIA Graphics Drivers, then click OK.
# zypper addrepo --refresh 'https://download.nvidia.com/opensuse/leap/$releasever' NVIDIA
# zypper addrepo --refresh https://download.nvidia.com/opensuse/tumbleweed NVIDIA
Get the hardware information
In a terminal:
# lspci | grep VGA # lscpu | grep Arch
# hwinfo --gfxcard | grep Model # hwinfo --arch
This information is also available in the Display subsection at YaST Hardware Information.
One way to determine the appropriate driver is to input your hardware information into Nvidia's driver search engine. Alternatively, YaST Software or the following commands can be used to check the available packages:
# zypper se x11-video-nvidiaG0* S | Name | Summary | Type --+---------------------+---------------------------------------------------------+-------- | x11-video-nvidiaG04 | NVIDIA graphics driver for GeForce 400 series and newer | package | x11-video-nvidiaG05 | NVIDIA graphics driver for GeForce 600 series and newer | package
# zypper se -s x11-video-nvidiaG0* S | Name | Type | Version | Arch | Repository --+---------------------+---------+-------------+--------+----------- | x11-video-nvidiaG04 | package | 390.116-5.1 | x86_64 | NVIDIA | x11-video-nvidiaG04 | package | 390.116-5.1 | i586 | NVIDIA | x11-video-nvidiaG05 | package | 418.56-9.1 | x86_64 | NVIDIA
To take advantage of OpenGL acceleration you must install an additional package, choosing the one that corresponds to the driver:
# zypper se nvidia-glG0* S | Name | Summary | Type ---+--------------+-------------------------------------------------+-------- | nvidia-glG04 | NVIDIA OpenGL libraries for OpenGL acceleration | package | nvidia-glG05 | NVIDIA OpenGL libraries for OpenGL acceleration | package
- Go to the YaST Control Center and click Software Management.
- View > Repositories > NVIDIA
- Choose the appropriate driver, e.g. x11-video-nvidiaG04 or x11-video-nvidiaG05
- Optionally choose the corresponding OpenGL acceleration libraries; nvidia-glG04 or nvidia-glG05.
- Press Accept.
- Restart your computer.
# zypper in <x11-video-nvidiaG04 or x11-video-nvidiaG05> # zypper in <nvidia-glG04 or nvidia-glG05>
Restart your computer.
Kernels in Tumbleweed and Leap 15.2 or higher will, by default, refuse to load any unsigned kernel modules on machines with secure boot enabled.
During the NVIDIA driver installation on a secureboot system a MOK keypair is being created and the kernel modules been signed with the created private key. The created certificate (public key) remains on the storage below /var/lib/nvidia-pubkeys, but it also needs to be imported to the list of to be enrolled MOK pubkeys.
After the first reboot this certificate can easily be enrolled to the MOK database. The EFI tool for this (mokutil) is automatically started: inside the tool select "Enroll MOK", then "Continue", then "Yes". Use your root password (US keyboard layout!) when prompted for a password. The certificate is now added to the MOK database and is considered trusted, which will allow kernel modules with matching signatures to load. To finish, select "Reboot".
In case you miss the timeout for certificate enrollment after first reboot, you can easily import again the certificate by running the following command:
# mokutil --import /var/lib/nvidia-pubkeys/MOK-nvidia-gfxG0<X>-<driver_version>-<kernel_flavor>.der --root-pw
Then reboot the machine and enroll the certificate as described before.
As a last resource, in case you are having problems with secure boot, you can, at your own risk, disable validation for kernel modules:
# mokutil --disable-validation
During a driver update the old and no longer being used public key is being registered to be deleted from the MOK data base. So in addition to the "Enroll MOK" menu entry a "Delete MOK" entry will appear in the EFI tool once you reboot the machine. In order to finally remove it from the MOK data base, select "Delete MOK", then "Continue", then "Yes". Again use your root password (US keyboard layout!) when prompted for a password. You can show the certificate/description of the public key when selecting "View Key X" in order not to delete the wrong key. Press any key to continue from there.
Uninstalling the NVIDIA drivers
- Start YaST, go to: Software -> Software Management
- Change the 'Filter' to filter by software repositories
- Select the respective NVIDIA repository
- Mark any installed package from this repository for deletion and press 'Accept'. You may be prompted for conflicts, please ignore any conflicts and chose to break dependencies.
- Now in YaST select: Software -> Software Repositories
- Chose the respective NVIDIA repository and mark it 'disabled' - don't delete it as it will return enabled the next time the repositories are synced with the server.
Uninstalling the proprietary drivers will restore the previous X configuration file
/etc/X11/xorg.conf if one existed. If the hardware has changed in the mean time it may be necessary to manually edit this file.
# zypper rm <x11-video-nvidiaG04 or x11-video-nvidiaG05>
If that doesn't delete all the packages you can find the other names with
# zypper se -ir NVIDIA
# zypper lr # zypper se -ir <the repo number>
Also, the installer for the NVIDIA driver might have added nouveau to the blacklist; to be able to run the modesetting DDX driver or nouveau DDX driver again make sure there are no files containing the words
blacklist nouveau at /etc/modprobe.d/, as the installer might fail to remove these.
After uninstalling the packages, you might need to run:
- If your computer freezes before the login screen after installing the propietary drivers and you are using GDM (usually the case if you are using GNOME), try adding WaylandEnable=false in /etc/gdm/custom.conf.
- You can verify the driver was actually loaded by running
lsmod | grep nvidiain the terminal. The output should be like:
nvidia_drm 57344 2 nvidia_modeset 1187840 3 nvidia_drm nvidia_uvm 1110016 0 nvidia 19771392 81 nvidia_uvm,nvidia_modeset drm_kms_helper 229376 2 nvidia_drm,i915 drm 544768 13 drm_kms_helper,nvidia_drm,i915
The numbers in the middle column do not need to be the same. If the driver is loaded the problem relies elsewhere, since that means it was installed successfully.
- As stated before in this guide, if you are using secure boot make sure you accept the MOK, else the module won't load. One way to know see if secure boot could be blocking the module is looking at the output of
dmesgand search for warnings like the following:
Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7 modprobe: ERROR: could not insert 'nvidia': Required key not available
Users on hardware configurations with NVIDIA Optimus (usually the case on laptops) are advised to read SDB: NVIDIA SUSE Prime. Offloading to the dedicated GPU is possible using the instructions at PRIME Render Offload
Developers and users involved in High Performance Computing applications may want to install CUDA libraries. Additional instructions are provided at the CUDA Toolkit Documentation and download links at NVIDIA Developer