# NVIDIA-Driver-510.73.05 - Failed to build Modules

**URL:** <https://forums.rockylinux.org/t/nvidia-driver-510-73-05-failed-to-build-modules/6114>\
**Category:** Rocky Linux Help & Support\
**Created:** [May 20, 2022, 8:48pm UTC](https://forums.rockylinux.org/t/nvidia-driver-510-73-05-failed-to-build-modules/6114 "2022-05-20T20:48:56Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![ValorCat](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/valorcat/32/1953_2.png) [@ValorCat](https://forums.rockylinux.org/u/ValorCat)\
**Post date:** [May 20, 2022, 8:48pm UTC](https://forums.rockylinux.org/t/nvidia-driver-510-73-05-failed-to-build-modules/6114/1 "2022-05-20T20:48:56Z")

</div>

My current version 510.68.02 is working fine.

Trying to update to the latest proprietary NVIDIA drivers (The proper way) by building the .run file in “systemctl set-default multi-user.target” mode…

I know there is the precompiled cuda-rhel8.repo route, but I’ve had borked system on reboot issues from that…

Historically, I’ve found the most stable way to be to manually build in multi-user.target…

Maybe the new backported 8.6 kernel is the issue? I’m kind of afraid to try again until there is a newer driver…

Anyone else experiencing this? Can’t wait for open-sourced kmods to take effect!

---

<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:** [May 20, 2022, 9:32pm UTC](https://forums.rockylinux.org/t/nvidia-driver-510-73-05-failed-to-build-modules/6114/2 "2022-05-20T21:32:51Z")

</div>

I’ve always used “third way”:

```bash
dnf install elrepo-release
dnf install kmod-nvidia

```

---

<div class="post-metadata">

**Author:** ![ValorCat](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/valorcat/32/1953_2.png) [@ValorCat](https://forums.rockylinux.org/u/ValorCat)\
**Post date:** [May 20, 2022, 10:04pm UTC](https://forums.rockylinux.org/t/nvidia-driver-510-73-05-failed-to-build-modules/6114/3 "2022-05-20T22:04:19Z")

</div>

@jlehtone thank-you, that looks about the most concise way to do it!  
Any experience with Maya or Davinci Resolve?  
I know the rpmfusion repo version is hit-or-miss with CUDA stuff…

Is this elrepo-release/kmod-nvidia basically a pre-compiled version of the latest NVIDIA .run file?

Cheers!

---

<div class="post-metadata">

**Author:** ![ValorCat](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/valorcat/32/1953_2.png) [@ValorCat](https://forums.rockylinux.org/u/ValorCat)\
**Post date:** [May 20, 2022, 10:09pm UTC](https://forums.rockylinux.org/t/nvidia-driver-510-73-05-failed-to-build-modules/6114/4 "2022-05-20T22:09:05Z")

</div>

@jlehtone Actually, this is a very outdated version… I need absolute latest for Redshift Render

…Or is my rpmfusion repo overriding?

![image](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/2X/e/e62233ffc621d27959138df387c5b94e9c51e943.png)

---

<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:** [May 20, 2022, 10:55pm UTC](https://forums.rockylinux.org/t/nvidia-driver-510-73-05-failed-to-build-modules/6114/5 "2022-05-20T22:55:46Z")

</div>

Those are clearly packages from rpmfusion-nonfree-updates.

The NVidia .run file is just a tarball or whatever with a shell script. The package management has no idea what files it places, or worse replaces.

NVidia have their own yum-repository, where they have both the graphics driver and CUDA as RPM packages.  
RPMFusion (a yum-repository) has the graphics drivers as RPM packages.  
ELRepo (a yum-repository) has the graphics drivers as RPM packages.

RPM-files the package management can install/update/remove “cleanly”.

ELRepo’s additional twist is that their kernel modules work with all kernels of one point update. The others have you install or build the kernel module for each kernel.

Yes, ELRepo has currently only version 470.103.01-2.el8\_6 for EL8, while they have 510.68.02-1.el7\_9 for EL7. If you want latest and particularly if you need CUDA, then NVidia’s yum repo is the best bet.  
See [Installation Guide Linux :: CUDA Toolkit Documentation](https://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html)

The `elrepo-release` is an RPM package from Rocky’s ‘extras’ repository that provides files that define the ‘elrepo’ repository. You can see the files of RPM package with:

```bash
rpm -ql elrepo-release # if package is installed
rpm -qlp elrepo-release-8.2-1.el8.noarch.rpm # if you have that RPM-file
dnf rq -l elrepo-release # for package that is in repo, but is not installed

```

---

<div class="post-metadata">

**Author:** ![ValorCat](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/valorcat/32/1953_2.png) [@ValorCat](https://forums.rockylinux.org/u/ValorCat)\
**Post date:** [May 21, 2022, 6:55am UTC](https://forums.rockylinux.org/t/nvidia-driver-510-73-05-failed-to-build-modules/6114/6 "2022-05-21T06:55:15Z")

</div>

Anyone else fail to build kmods from the latest 510.73.05 NVIDIA update (from NVIDIA .run file)?

Ryzen 9 5900x + three 3080ti’s

---

<div class="post-metadata">

**Author:** ![gerry666uk](https://avatars.discourse-cdn.com/v4/letter/g/dbc845/32.png) [@gerry666uk](https://forums.rockylinux.org/u/gerry666uk)\
**Post date:** [May 21, 2022, 10:12am UTC](https://forums.rockylinux.org/t/nvidia-driver-510-73-05-failed-to-build-modules/6114/7 "2022-05-21T10:12:21Z")

</div>

> [@jlehtone](#):
>
> ELRepo’s additional twist is that their kernel modules work with all kernels of one point update.

I’m interested to know more about this. Are you saying they have signed kernel modules that work with multiple kernel versions?

---

<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:** [May 21, 2022, 10:41am UTC](https://forums.rockylinux.org/t/nvidia-driver-510-73-05-failed-to-build-modules/6114/8 "2022-05-21T10:41:54Z")

</div>

Yes. Normally when you compile a module, it works only with the kernel that you did build it for. RHEL kernels within one point update are so similar that if you strip the exect version requirement from the module, it will work with them all. For example, all 8.5’s kernels could have been used with one ELRepo module. The 8.6’s kernel is different and ELRepo has rebuilt the kmod-nvidia to match.

And yes, ELRepo has their own key to sign their modules with. One can import that key into UEFI and then one can have Secure Boot enabled.

---

<div class="post-metadata">

**Author:** ![gerry666uk](https://avatars.discourse-cdn.com/v4/letter/g/dbc845/32.png) [@gerry666uk](https://forums.rockylinux.org/u/gerry666uk)\
**Post date:** [May 21, 2022, 10:48am UTC](https://forums.rockylinux.org/t/nvidia-driver-510-73-05-failed-to-build-modules/6114/9 "2022-05-21T10:48:50Z")

</div>

Thanks, this is really interesting; do you how they strip the version; do they use something like an ‘elf’ editor on the final module.

---

<div class="post-metadata">

**Author:** ![brian](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/brian/32/5777_2.png) [@brian](https://forums.rockylinux.org/u/brian)\
**Post date:** [August 25, 2023, 3:49am UTC](https://forums.rockylinux.org/t/nvidia-driver-510-73-05-failed-to-build-modules/6114/10 "2023-08-25T03:49:06Z")

</div>


