# Rocky 9.6 + Nvidia Drivers issue

**URL:** <https://forums.rockylinux.org/t/rocky-9-6-nvidia-drivers-issue/18706>\
**Category:** Rocky Linux Help & Support\
**Created:** [June 8, 2025, 10:54am UTC](https://forums.rockylinux.org/t/rocky-9-6-nvidia-drivers-issue/18706 "2025-06-08T10:54:13Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![tunaboy](https://avatars.discourse-cdn.com/v4/letter/t/22d042/32.png) [@tunaboy](https://forums.rockylinux.org/u/tunaboy)\
**Post date:** [June 8, 2025, 10:54am UTC](https://forums.rockylinux.org/t/rocky-9-6-nvidia-drivers-issue/18706/1 "2025-06-08T10:54:13Z")

</div>

Folks,

Maybe I’m a special case, but I have two RL9 systems and neither is able to use the nvidia/cuda drivers with the new 9.6 kernel. This may well be expected behavior, as I see the nvidia driver that I’m using is from a build in mid-May, and I’m trying to get it to work with the 9.6 kernels that were build June 2(?).

I’ve given up for the moment, and went back to the previous kernel with both:  
kernel-5.14.0-503.40.1.el9\_5.x86\_64

but I’m wondering if there is a trick that will make the nvidia graphics drivers and cuda work with the kernel:  
kernel-5.14.0-570.18.1.el9\_6.x86\_64

If we should just wait for NVIDIA to catch up, I won’t spend more of my time trying to get these to work.

Cheers,  
Mike

---

<div class="post-metadata">

**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\
**Post date:** [June 8, 2025, 3:08pm UTC](https://forums.rockylinux.org/t/rocky-9-6-nvidia-drivers-issue/18706/2 "2025-06-08T15:08:52Z")

</div>

NVidia has three sets of RPMs in their repo:

- Proprietary driver that depends on `dkms` to build module for new kernel
- Open source driver that depends on `dkms` to build module for new kernel
- Prebuilt kernel modules for some kernel versions

Both package sets that use dkms should install fine on el9\_6.

---

<div class="post-metadata">

**Author:** ![Sheldon](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/sheldon/32/5467_2.png) [@Sheldon](https://forums.rockylinux.org/u/Sheldon)\
**Post date:** [June 8, 2025, 4:40pm UTC](https://forums.rockylinux.org/t/rocky-9-6-nvidia-drivers-issue/18706/3 "2025-06-08T16:40:33Z")

</div>

Where are you finding your nvidia drivers?

I don’t know if this helps, but I am able to use cuda with the 9.6 kernel.

```auto
5.14.0-570.18.1

nvidia-driver-cuda.x86_64 3:575.57.08-1.el9 @cuda-rhel9-x86_64
nvidia-driver-cuda-libs.x86_64 3:575.57.08-1.el9 @cuda-rhel9-x86_64
dnf-plugin-nvidia.noarch 2.2-2.el9 @cuda-rhel9-x86_64
kmod-nvidia-latest-dkms.x86_64 3:575.57.08-1.el9 @cuda-rhel9-x86_64
libnvidia-cfg.x86_64 3:575.57.08-1.el9 @cuda-rhel9-x86_64
libnvidia-fbc.x86_64 3:575.57.08-1.el9 @cuda-rhel9-x86_64
libnvidia-gpucomp.x86_64 3:575.57.08-1.el9 @cuda-rhel9-x86_64
libnvidia-ml.x86_64 3:575.57.08-1.el9 @cuda-rhel9-x86_64
nvidia-driver.x86_64 3:575.57.08-1.el9 @cuda-rhel9-x86_64
nvidia-driver-libs.x86_64 3:575.57.08-1.el9 @cuda-rhel9-x86_64
nvidia-kmod-common.noarch 3:575.57.08-1.el9 @cuda-rhel9-x86_64
nvidia-libXNVCtrl.x86_64 3:575.57.08-1.el9 @cuda-rhel9-x86_64
nvidia-libXNVCtrl-devel.x86_64 3:575.57.08-1.el9 @cuda-rhel9-x86_64
nvidia-modprobe.x86_64 3:575.57.08-1.el9 @cuda-rhel9-x86_64
nvidia-persistenced.x86_64 3:575.57.08-1.el9 @cuda-rhel9-x86_64
nvidia-settings.x86_64 3:575.57.08-1.el9 @cuda-rhel9-x86_64
nvidia-xconfig.x86_64 3:575.57.08-1.el9 @cuda-rhel9-x86_64
xorg-x11-nvidia.x86_64 3:575.57.08-1.el9 @cuda-rhel9-x86_64

```

---

<div class="post-metadata">

**Author:** ![tunaboy](https://avatars.discourse-cdn.com/v4/letter/t/22d042/32.png) [@tunaboy](https://forums.rockylinux.org/u/tunaboy)\
**Post date:** [June 9, 2025, 7:50am UTC](https://forums.rockylinux.org/t/rocky-9-6-nvidia-drivers-issue/18706/4 "2025-06-09T07:50:43Z")

</div>

Hey [jlehtone](https://forums.rockylinux.org/u/jlehtone) and [Sheldon](https://forums.rockylinux.org/u/Sheldon),

I’m using the open source version of the driver, which I’ve been using for well over a year now, installed (from guidance given by nvidia-driver-assistant) with the command:

> dnf -y module install nvidia-driver:open-dkms

These continue to work fine with the previous kernel, but X will not start with the 9.6 kernel. It’s not an installation problem, per se. The new kernel boots, but the nvidia loadable kernel modules do not load with the 9.6 kernel. If I reboot with the 9.6 kernel, then (logging in from a different machine) check to see if the proprietary modules loaded, they did not. On the 9.5 kernels, if I issue the command

> # lsmod | grep nvidia

I see a host of nvidia modules loaded:

> nvidia\_uvm 4087808 0  
> nvidia\_drm 151552 17  
> nvidia\_modeset 1732608 63 nvidia\_drm  
> nvidia 11579392 729 nvidia\_uvm,nvidia\_modeset  
> drm\_kms\_helper 274432 2 nvidia\_drm  
> drm 782336 21 drm\_kms\_helper,nvidia,nvidia\_drm  
> video 73728 2 asus\_wmi,nvidia\_modeset

On the 9.6 kernel, none of these are loaded.

I’ve rebooted into the 9.6 kernel, and removed and reinstalled the nvidia drivers, and still no joy. X will not start, and I suspect there will be no cuda occuring either.

Sheldon, your listing did help, at least to confirm I am using the same rpm packages except for one. This might be what the issue is. That package difference is the kmod-nvidia\* package. You’re using “latest”, and I’m using “open”.

Mine:

> kmod-nvidia-open-dkms.noarch 3:575.57.08-1.el9 @cuda-rhel9-x86\_64

Yours:

> kmod-nvidia-latest-dkms.x86\_64 3:575.57.08-1.el9 @cuda-rhel9-x86\_64

I have found the page in the nvidia site that shows how to switch between the two, and I got the switch completed. I’m about to reboot with the “latest-dkms” as the choice, and hopefully that will do the trick. If it does I’ll let you know…

Thanks much!  
Mike

EDIT: rebooted, and still no joy, but I could boot with the latest-dkms nvidia driver installed on that system with the 9.5 kernels. I may have muffed something in my thrashes, but I now believe that others are not finding a problem getting the system to work with the nviida drivers under the 9.6 kernels.

Thanks much for the help. I’ll try to run this to ground and share with the community. Cheers all…

---

<div class="post-metadata">

**Author:** ![robbott](https://avatars.discourse-cdn.com/v4/letter/r/57b2e6/32.png) [@robbott](https://forums.rockylinux.org/u/robbott)\
**Post date:** [June 9, 2025, 2:34pm UTC](https://forums.rockylinux.org/t/rocky-9-6-nvidia-drivers-issue/18706/5 "2025-06-09T14:34:07Z")

</div>

Hi,

not sure if this is the reason why in Rocky / RHEL 10 the “dnf module” was removed, but almost after every upgrade I have to reinstall the nvidia drivers so I know the commands by heart. I had some problems with epel-multimedia, hence I disable it for the update. Ignore it if you haven’t installed epel.multimedia. If you get a “transaction error”, just remove all the packages listed and reinstall them later, if needed.

In my experience 97% of the problems on a workstation come from nvidia. Don’t fight it! Embrace it!

```bash
sudo dnf config-manager --set-enabled crb
sudo dnf -y config-manager --add-repo https://developer.download.nvidia.com/compute/cuda/repos/rhel9/x86_64/cuda-rhel9.repo
sudo dnf config-manager --set-disabled epel-multimedia
sudo dnf -y remove cuda-toolkit
sudo dnf -y remove cuda\*
sudo dnf -y remove nvidia-driver
sudo dnf -y remove nvidia\*
sudo dnf -y module reset nvidia-driver
sudo dnf -y upgrade
# reboot after the upgrade so open-dkms get build with the new kernel and kernel-headers.
sudo reboot
sudo dnf -y module install nvidia-driver:open-dkms
# reboot to get your screen back
sudo reboot
sudo dnf config-manager --set-enabled epel-multimedia
sudo dnf -y upgrade

```

---

<div class="post-metadata">

**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\
**Post date:** [June 9, 2025, 5:16pm UTC](https://forums.rockylinux.org/t/rocky-9-6-nvidia-drivers-issue/18706/6 "2025-06-09T17:16:16Z")

</div>

> [@tunaboy](#):
>
> That package difference is the kmod-nvidia\* package. You’re using “latest”, and I’m using “open”.

The “latest” is proprietary, the “open” is open. The proprietary does not work with Blackwell (e.g. RTX 5xxx cards.) The open does not work with cards older than Turing. If open driver did work previously, then you have recent enough card for it.

* * *

What kernel packages do you have?

```auto
dnf rq --installonly

```

What NVidia kernel modules you have?

```auto
find /lib/modules -type f -name "nvidia*.ko.xz"

```

You can tell the system to go to text mode in boot with:

```auto
systemctl set-default multi-user.target

```

(and revert to "start GUI on boot with `systemctl set-default graphical.target`)

If you have nvidia modules in the el9\_6 kernel’s dirs, then I would boot to text mode and ask:

```auto
modinfo nvidia
modprobe nvidia

```

If there are no nvidia modules for the new kernel, then the question is why dkms did fail to build them?

* * *

I have the “open” 575.57.08 on one AlmaLinux 9.6 and 570 on multiple. The Rocky’s kernel should be at least as good as AlmaLinux kernel (but probably even more compatible with RHEL kernel).

* * *

> [@robbott](#):
>
> the reason why in Rocky / RHEL 10 the “dnf module” was removed

The DNF modules are a nice idea, but implementation was far from great. Red Hat went totally overboard with modules in RHEL 8, managed to tone done for RHEL 9, and by development of RHEL 10 concluded that modules is more trouble than benefit.

---

<div class="post-metadata">

**Author:** ![tunaboy](https://avatars.discourse-cdn.com/v4/letter/t/22d042/32.png) [@tunaboy](https://forums.rockylinux.org/u/tunaboy)\
**Post date:** [June 9, 2025, 10:13pm UTC](https://forums.rockylinux.org/t/rocky-9-6-nvidia-drivers-issue/18706/7 "2025-06-09T22:13:46Z")

</div>

> [@jlehtone](#):
>
> What kernel packages do you have?  
> `dnf rq --installonly`

kernel-0:5.14.0-503.38.1.el9\_5.x86\_64  
kernel-0:5.14.0-503.40.1.el9\_5.x86\_64  
kernel-0:5.14.0-570.18.1.el9\_6.x86\_64  
kernel-core-0:5.14.0-503.38.1.el9\_5.x86\_64  
kernel-core-0:5.14.0-503.40.1.el9\_5.x86\_64  
kernel-core-0:5.14.0-570.18.1.el9\_6.x86\_64  
kernel-devel-0:5.14.0-503.38.1.el9\_5.x86\_64  
kernel-devel-0:5.14.0-503.40.1.el9\_5.x86\_64  
kernel-devel-0:5.14.0-570.18.1.el9\_6.x86\_64  
kernel-modules-0:5.14.0-503.38.1.el9\_5.x86\_64  
kernel-modules-0:5.14.0-503.40.1.el9\_5.x86\_64  
kernel-modules-0:5.14.0-570.18.1.el9\_6.x86\_64  
kernel-modules-core-0:5.14.0-503.38.1.el9\_5.x86\_64  
kernel-modules-core-0:5.14.0-503.40.1.el9\_5.x86\_64  
kernel-modules-core-0:5.14.0-570.18.1.el9\_6.x86\_64  
kernel-modules-extra-0:5.14.0-503.38.1.el9\_5.x86\_64  
kernel-modules-extra-0:5.14.0-503.40.1.el9\_5.x86\_64  
kernel-modules-extra-0:5.14.0-570.18.1.el9\_6.x86\_64

> [@jlehtone](#):
>
> What NVidia kernel modules you have?
> 
> ```auto
> find /lib/modules -type f -name "nvidia*.ko.xz"
> 
> ```

/lib/modules/5.14.0-427.16.1.el9\_4.x86\_64/extra/nvidia.ko.xz  
/lib/modules/5.14.0-427.16.1.el9\_4.x86\_64/extra/nvidia-modeset.ko.xz  
/lib/modules/5.14.0-427.16.1.el9\_4.x86\_64/extra/nvidia-drm.ko.xz  
/lib/modules/5.14.0-427.16.1.el9\_4.x86\_64/extra/nvidia-uvm.ko.xz  
/lib/modules/5.14.0-427.16.1.el9\_4.x86\_64/extra/nvidia-peermem.ko.xz  
/lib/modules/5.14.0-427.18.1.el9\_4.x86\_64/extra/nvidia.ko.xz  
/lib/modules/5.14.0-427.18.1.el9\_4.x86\_64/extra/nvidia-modeset.ko.xz  
/lib/modules/5.14.0-427.18.1.el9\_4.x86\_64/extra/nvidia-drm.ko.xz  
/lib/modules/5.14.0-427.18.1.el9\_4.x86\_64/extra/nvidia-uvm.ko.xz  
/lib/modules/5.14.0-427.18.1.el9\_4.x86\_64/extra/nvidia-peermem.ko.xz  
/lib/modules/5.14.0-427.22.1.el9\_4.x86\_64/extra/nvidia.ko.xz  
/lib/modules/5.14.0-427.22.1.el9\_4.x86\_64/extra/nvidia-modeset.ko.xz  
/lib/modules/5.14.0-427.22.1.el9\_4.x86\_64/extra/nvidia-drm.ko.xz  
/lib/modules/5.14.0-427.22.1.el9\_4.x86\_64/extra/nvidia-uvm.ko.xz  
/lib/modules/5.14.0-427.22.1.el9\_4.x86\_64/extra/nvidia-peermem.ko.xz  
/lib/modules/5.14.0-427.24.1.el9\_4.x86\_64/extra/nvidia.ko.xz  
/lib/modules/5.14.0-427.24.1.el9\_4.x86\_64/extra/nvidia-modeset.ko.xz  
/lib/modules/5.14.0-427.24.1.el9\_4.x86\_64/extra/nvidia-drm.ko.xz  
/lib/modules/5.14.0-427.24.1.el9\_4.x86\_64/extra/nvidia-uvm.ko.xz  
/lib/modules/5.14.0-427.24.1.el9\_4.x86\_64/extra/nvidia-peermem.ko.xz  
/lib/modules/5.14.0-427.28.1.el9\_4.x86\_64/extra/nvidia-fs.ko.xz  
/lib/modules/5.14.0-427.31.1.el9\_4.x86\_64/extra/nvidia.ko.xz  
/lib/modules/5.14.0-427.31.1.el9\_4.x86\_64/extra/nvidia-modeset.ko.xz  
/lib/modules/5.14.0-427.31.1.el9\_4.x86\_64/extra/nvidia-drm.ko.xz  
/lib/modules/5.14.0-427.31.1.el9\_4.x86\_64/extra/nvidia-uvm.ko.xz  
/lib/modules/5.14.0-427.31.1.el9\_4.x86\_64/extra/nvidia-peermem.ko.xz  
/lib/modules/5.14.0-503.38.1.el9\_5.x86\_64/kernel/drivers/platform/x86/nvidia-wmi-ec-backlight.ko.xz  
/lib/modules/5.14.0-503.40.1.el9\_5.x86\_64/kernel/drivers/platform/x86/nvidia-wmi-ec-backlight.ko.xz  
/lib/modules/5.14.0-503.40.1.el9\_5.x86\_64/extra/nvidia.ko.xz  
/lib/modules/5.14.0-503.40.1.el9\_5.x86\_64/extra/nvidia-modeset.ko.xz  
/lib/modules/5.14.0-503.40.1.el9\_5.x86\_64/extra/nvidia-drm.ko.xz  
/lib/modules/5.14.0-503.40.1.el9\_5.x86\_64/extra/nvidia-uvm.ko.xz  
/lib/modules/5.14.0-503.40.1.el9\_5.x86\_64/extra/nvidia-peermem.ko.xz  
/lib/modules/5.14.0-570.18.1.el9\_6.x86\_64/kernel/drivers/platform/x86/nvidia-wmi-ec-backlight.ko.xz

And booted to the 9.6 kernel, no nvidia modules were loaded. I then did the delete them all/reinstall them all step I use:

> dnf module remove --all nvidia-driver  
> dnf module install nvidia-driver:latest-dkms

… and voila, the drivers appeared.

I’d tried this (in my version of this, where I rebooted into the running, but essentially text mode kernel from another machine). I would then just reboot w/o doing any checks like the “modinfo nvidia” or my “lsmod | grep nvidia”, and it never rebooted with a running graphical mode.

This was with the open version of the driver, but this success was with the proprietary (“latest”) version of the drivers. I am about to try this with the system that is still the open version, but I will then lose this window. I am going to do this more clean boot into “multi-user.target”, and see if it works. If it does, then it has nothing to do with “latest” vs “open”…

More on the flipside. But got one system up!

Much, much thanks!

Mike

---

<div class="post-metadata">

**Author:** ![tunaboy](https://avatars.discourse-cdn.com/v4/letter/t/22d042/32.png) [@tunaboy](https://forums.rockylinux.org/u/tunaboy)\
**Post date:** [June 9, 2025, 10:39pm UTC](https://forums.rockylinux.org/t/rocky-9-6-nvidia-drivers-issue/18706/8 "2025-06-09T22:39:23Z")

</div>

And did the same twostep, but with the “open” variant. And it is running just fine. I have not yet rebooted, but I suspect it will work w/o issue given it switched runlevels w/o issue.

I am wondering if I did not do this flush and re-install a few times unsuccessfully in the booted 9.6 kernel, but I have to admit that’s a possibility.

Confused, but happy to have the systems back and running under the newest kernel, with the nvidia driver running. These are two different peices of hardware, and neither worked until did the flush/reinstall step while running in textmode (runlevel 3/multi-user.target). I thought I did the equivalent, but something changed between the two. Also don’t understand why neither system didn’t just work with the new kernel.

Regardless: Much,much thanks.  
Systems working great now.

Mike

---

<div class="post-metadata">

**Author:** ![tunaboy](https://avatars.discourse-cdn.com/v4/letter/t/22d042/32.png) [@tunaboy](https://forums.rockylinux.org/u/tunaboy)\
**Post date:** [June 9, 2025, 10:57pm UTC](https://forums.rockylinux.org/t/rocky-9-6-nvidia-drivers-issue/18706/9 "2025-06-09T22:57:53Z")

</div>

![](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/2X/a/a683f19f82199a4c97605a4041a5b02763dc3339.png "robbott") Robbott, you have a much more involved flush and re-install script. Mine is just:

```
dnf module remove --all nvidia-driver
dnf module install nvidia-driver:latest-dkms

```

or, for the open driver

```
dnf module remove --all nvidia-driver
dnf module install nvidia-driver:open-dkms

```

Really good to have these in a script, just for repeatability. I did have to add the reset when I switched from “open” to “latest”, so I suspect your version is more complete than mine.

Much thanks for your help in this. I’m still baffled by what happened for me to require all my gyrations. My money now would me doing something something wrong as I was booting both of these after having them non-running last week…

Cheers,  
Mike

---

<div class="post-metadata">

**Author:** ![tunaboy](https://avatars.discourse-cdn.com/v4/letter/t/22d042/32.png) [@tunaboy](https://forums.rockylinux.org/u/tunaboy)\
**Post date:** [June 13, 2025, 6:36am UTC](https://forums.rockylinux.org/t/rocky-9-6-nvidia-drivers-issue/18706/10 "2025-06-13T06:36:40Z")

</div>

And now, I am adding additional details, as they re-appeared. On one of the machines I had an issue when the next kernel level arrived. After much fooling around, on this newer machine, neither open or “latest” nvidia drivers will work.

On the earlier kernels, the drivers did work just fine (both types). So I now have two machines, and one had no problem upgrading through the entire chain of the kernels I’ve seen:

> kernel-5.14.0-570.18.1.el9\_6.x86\_64  
> kernel-5.14.0-570.19.1.el9\_6.x86\_64  
> kernel-5.14.0-570.21.1.el9\_6.x86\_64

and the second (more recent motherboard) I could only get to work through

> kernel-5.14.0-570.18.1.el9\_6.x86\_64  
> kernel-5.14.0-570.19.1.el9\_6.x86\_64

That machine is now happily running on kernel-5.14.0-570.21.1.el9\_6.x86\_64, using the nouveau driver, with the cuda rpms still installed. Haven’t tried to play with the cuda bit. Likely will just wait for the next kernel level.

I can share more details about differences between the machine that’s currently fine, and the one that’s not, but not sure if anyone cares. But I do suspect others might run into the same issue right now.

Much thanks for the help.  
Cheers!  
Mike

---

<div class="post-metadata">

**Author:** ![tunaboy](https://avatars.discourse-cdn.com/v4/letter/t/22d042/32.png) [@tunaboy](https://forums.rockylinux.org/u/tunaboy)\
**Post date:** [July 2, 2025, 7:28am UTC](https://forums.rockylinux.org/t/rocky-9-6-nvidia-drivers-issue/18706/11 "2025-07-02T07:28:52Z")

</div>

Just got the machine that was having issues back to health (open driver, with the latest kernel: 5.14.0-570.23.1.el9\_6.x86\_64. The one thing I had to do was to add one additional step and that was to add:

> dnf install nvidia-fs

after removing, resetting, and re-installing the nvidia drivers. Not sure if I could have gotten it working on an earlier kernel version if I’d tried this earlier, but I finally had time to get this working again tonight, and it’s completely back and functional. I need to verify I actually need that package, but the system is up and working again.

Putting this out there, in case anyone else had an issue like this.

Cheers!  
Mike

---

<div class="post-metadata">

**Author:** ![kcb](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/kcb/32/658_2.png) [@kcb](https://forums.rockylinux.org/u/kcb)\
**Post date:** [July 15, 2025, 5:52pm UTC](https://forums.rockylinux.org/t/rocky-9-6-nvidia-drivers-issue/18706/12 "2025-07-15T17:52:34Z")

</div>

Interesting. Any idea what the nvidia-fs provides that was missing before and now fixes this?

I have the same issue, but never had time to debug/repair. (ffor the short-term just booted a previous working kernel… ugh). A system with a big ol GPU in it that blew up when I installed the latest kernel. (Rocky linux in my case).

When I have time I am going to try to get my drivers fixed/working using your simple recipe noted a few posts ago.

Any preference to the “open” vs “proprietary” drivers? Just wondering which one I MIGHT have more success with…

---

<div class="post-metadata">

**Author:** ![kcb](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/kcb/32/658_2.png) [@kcb](https://forums.rockylinux.org/u/kcb)\
**Post date:** [August 4, 2025, 7:40pm UTC](https://forums.rockylinux.org/t/rocky-9-6-nvidia-drivers-issue/18706/13 "2025-08-04T19:40:29Z")

</div>

OK, so I have been battling this for weeks. Finally got some downtime scheduled to play again. has the magic sauce.Before any fixes, when I tried normal system updates (including the kernel), I got this nastiness:

```auto
Autoinstall of module nvidia/550.54.14 for kernel 5.14.0-570.18.1.el9_6.x86_64 (x86_64)Building module(s)…(bad exit status: 2)Failed command:‘make’ -j32 NV_EXCLUDE_BUILD_MODULES=‘’ KERNEL_UNAME=5.14.0-570.18.1.el9_6.x86_64 modules

```

```auto
Error! Bad return status for module build on kernel: 5.14.0-570.18.1.el9_6.x86_64 (x86_64)Consult /var/lib/dkms/nvidia/550.54.14/build/make.log for more information.

```

```auto
Autoinstall on 5.14.0-570.18.1.el9_6.x86_64 failed for module(s) nvidia(10).

```

```auto
Error! One or more modules failed to install during autoinstall.Refer to previous errors for more information.warning: %posttrans(kernel-core-5.14.0-570.18.1.el9_6.x86_64) scriptlet failed, exit status 11

```

```auto
So, on a whim I tried installing “nvidia-fs” first. Here by the way is what it installed:========================================================================================================================Package Architecture Version Repository Size

```

```auto
Installing:nvidia-fs x86_64 2.26.6-1 cuda-rhel9 7.3 kInstalling dependencies:kmod-nvidia-open-dkms noarch 3:580.65.06-1.el9 cuda-rhel9 16 Mlibnvidia-cfg x86_64 3:580.65.06-1.el9 cuda-rhel9 152 klibnvidia-gpucomp x86_64 3:580.65.06-1.el9 cuda-rhel9 19 Mlibnvidia-ml x86_64 3:580.65.06-1.el9 cuda-rhel9 666 knvidia-driver-cuda x86_64 3:580.65.06-1.el9 cuda-rhel9 511 knvidia-driver-cuda-libs x86_64 3:580.65.06-1.el9 cuda-rhel9 59 Mnvidia-fs-dkms x86_64 2.26.6-1 cuda-rhel9 84 knvidia-kmod-common noarch 3:580.65.06-1.el9 cuda-rhel9 72 Mnvidia-modprobe x86_64 3:580.65.06-1.el9 cuda-rhel9 29 knvidia-persistenced x86_64 3:580.65.06-1.el9 cuda-rhel9 33 kopencl-filesystem noarch 1.0-15.el9 CTSI_Rocky9_rocky9_appstream 7.4 k

```

And then I finally tied RE-installing the kernel stuff. SUCCESS!

So there’s something inside the nvidia-fs and/or dependencies that APPEARS to solve this.

---

<div class="post-metadata">

**Author:** ![fredex](https://avatars.discourse-cdn.com/v4/letter/f/cab0a1/32.png) [@fredex](https://forums.rockylinux.org/u/fredex)\
**Post date:** [August 9, 2025, 6:18pm UTC](https://forums.rockylinux.org/t/rocky-9-6-nvidia-drivers-issue/18706/14 "2025-08-09T18:18:06Z")

</div>

what is “nvidia-fs” ? I don’t have it on my system (Rocky 9.6) and according to dnf it is neither available, nor installed.

---

<div class="post-metadata">

**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\
**Post date:** [August 9, 2025, 8:56pm UTC](https://forums.rockylinux.org/t/rocky-9-6-nvidia-drivers-issue/18706/15 "2025-08-09T20:56:21Z")

</div>

It is one part of the “GPUDirect Storage” (see [1. Overview Guide — GPUDirect Storage Overview Guide](https://docs.nvidia.com/gpudirect-storage/overview-guide/index.html) ) and pulled in by one of the `nvidia-gds` packages: [CUDA Installation Guide for Linux — Installation Guide for Linux 13.0 documentation](https://docs.nvidia.com/cuda/cuda-installation-guide-linux/#common-instructions)

It might be that it requires the open flavor of NVidia driver.