Nvidia rocky 10 guide

Rocky Linux Help & Support
1

hey everyone, is there any guides on install nvidida on 10?? or is it the same as 9 - used to foloow this because of safe boot. - How to Install NVIDIA Driver and CUDA on Rocky 9.1 - #10 by timppu

2

I have not seen something written for 10. On 8 and 9, modules were the preferred way to go, and I have done a lot of NVIDIA installs using modules. Modules were a horrible experiment in the Enterprise environment, imo! With 10, if you type ā€œdnf module list --allā€ you will not see any modules - yeah! So I tried using the installer. The first step is to disable the nouveau driver. On my NVIDIA system, this also removes sound. When I put the NVIDIA drivers on, sound was still listed as dummy. I did not research more as the driver is not critical for me, but I will personally wait for guidance from NVIDIA before I try again.

3

There seems to be clear agreement on that. Red Hat introduced Software Collections (SCL) for RHEL 7 (and RHEL 6). On RHEL 8 they made everything a module (ā€œapplication streamā€), hoping to replace SCL. They saw issues when RHEL 8 was in use, but kept some for RHEL 9. In RHEL 10 they chose to have no modules.

There have been many packagers of NVidia drivers for EL distros:

  • NVidia has the .run file, which bypasses package management. This is the oldest and available for most major versions. However, ā€œsource installsā€ that mess up package management are not nice
  • NVidia has driver as RPM too as they now distribute CUDA as packages. Alas, it lags a bit behind; they have now repo for ā€˜rhel10ā€™, but no content yet
  • ELRepo builds kernel modules that RHEL does not provide. Solid, when they get it rolling. (Not yet for el10)
  • RPM Fusion builds too. They seem to have ā€˜575.64-1.el10ā€™ packages now
  • negativo17 Nvidia driver, CUDA tools and libraries ā€“ negativo17.org seems to have NVidia packages for el9 and el10
  • AlmaLinux 10 offers kernel module as extra, but uses negativoā€™s packages for the rest of the driver

I do prefer ELRepo and NVidiaā€™s CUDA repo, but they are not yet possible for el10.

Most packaged drivers do that on install.

With most package sources one simply installs packages. NVidia has guide for their offerings; they even mention Rocky.

1 Like
4

I generally found using modules to be a lot better than SCL, but I guess it can be a personal preference. Maybe with EL8 they went overboard and had too many of them. With EL9 it seemed quite a good balance, and generally never had any issues with it personally. For me was far worse with SCL.

5

They are solutions for slightly different problems.

The SCL, like Environment Modules, is about how to have more than one version installed simultaneously. User has to state which version to use (today).

The DNF modules, application streams, are about installing one version. One could have separate repo for each version; modules allows packages to be in same repo.

6

ā€˜modularā€™ RPMā€™s are what made EL 8.x an abominationā€¦
ā€˜Iā€™ gave up on it 1 week after attempting to install/use itā€¦
Skipped over to ā€˜9.xā€™ which at least allowed you to just ignore themā€¦
Someone figured out what they were by 10.x and got rid of themā€¦
May they burn on the scrap heap of bad codeā€¦
Just my opinionā€¦

7

would this work you think for 10??? ive always used it for 9 no problemsā€¦ its from anotehr post

I actually found instructions that seem to be working, without having to disable Secure Boot:

https://www.reddit.com/r/RockyLinux/comments/woqgij/rocky_9_nvidia_drivers_secure_boot_success/

I changed the instructions a bit, e.g. the non-working ā€œsudo echo >ā€ commands in the original instructions:

sudo dnf install epel-release 
sudo dnf upgrade
sudo reboot

After the reboot:

sudo dnf config-manager --add-repo http://developer.download.nvidia.com/compute/cuda/repos/rhel9/$(uname -i)/cuda-rhel9.repo
sudo dnf install kernel-headers-$(uname -r) kernel-devel-$(uname -r) tar bzip2 make automake gcc gcc-c++ pciutils elfutils-libelf-devel libglvnd-opengl libglvnd-glx libglvnd-devel acpid pkgconfig dkms
sudo dnf module install nvidia-driver:latest-dkms
echo "blacklist nouveau" | sudo tee /etc/modprobe.d/blacklist-nouveau.conf
echo 'omit_drivers+=" nouveau "' | sudo tee /etc/dracut.conf.d/blacklist-nouveau.conf
sudo dracut --regenerate-all --force
sudo depmod -a

The mokutil command will prompt for you to make up a password, which will be used during reboot

sudo mokutil --import /var/lib/dkms/mok.pub
sudo reboot

After the reboot, your system should ask you if you want to enroll a key or something like that, say yes and it asks for the password you gave in the mokutil command.

Later on, check that the nvidia drivers are installed:

nvidia-smi

If you dual boot windows, a windows-driven firmware update may reset the TPM chip (?). Anyway, any time this happens youā€™ll need to re-run ā€˜mokutil --import /var/lib/dkms/mok.pubā€™
8

That has already more steps than one needs. You can look at 1. Introduction ā€” NVIDIA Driver Installation Guide r580 documentation for shorter list (for Rocky 9, among all the text).

Alas, the https://developer.download.nvidia.com/compute/cuda/repos/rhel9/$(uname -i)/
is for Rocky 9, not for Rocky 10.
One has to wait until NVidia builds packages for rhel10 and puts them into
https://developer.download.nvidia.com/compute/cuda/repos/rhel10/ (or something),
before one can use this ā€œCUDA repo methodā€ with el10.