| Git Clone URL: | https://aur.archlinux.org/nvidia-390xx-utils.git (read-only, click to copy) |
|---|---|
| Package Base: | nvidia-390xx-utils |
| Description: | OpenCL implemention for NVIDIA |
| Upstream URL: | https://www.nvidia.com/ |
| Licenses: | custom |
| Conflicts: | opencl-nvidia |
| Provides: | opencl-driver, opencl-nvidia |
| Submitter: | svenstaro |
| Maintainer: | jonathon (vnctdj) |
| Last Packager: | vnctdj |
| Votes: | 60 |
| Popularity: | 0.98 |
| First Submitted: | 2020-03-11 17:29 (UTC) |
| Last Updated: | 2025-01-24 07:30 (UTC) |
@drankinatty - thank you for your research and patching efforts!
On my end, both the pre-patched and patched PKGBUILD compiled and installed correctly against:
==> dkms install --no-depmod nvidia/390.157 -k 6.12.10-hardened1-1-hardened ==> dkms install --no-depmod nvidia/390.157 -k 6.13.0-arch1-1
Cheers
Use this forum thread for discussion: https://bbs.archlinux.org/viewtopic.php?pid=1946926
Package updated!
Thanks again @drankinatty :)
As a reminder, there's no need to flag the package as out-of-date... (see pinned comment)
@vnctdj and @air-g4p, Just updated to 6.13 on openSUSE Tumbleweed with the same Nvidia 390xx patch. Works like a champ. You can push the update.
Also note: the existing drivers for the 6.12 kernel should still build and work with 6.13. The patch is an update to how the Kbuild (make) files will use absolute symlink paths going forward to avoid problems depending on what the working directory is when the symlinks are generated. There weren't any changes to the kernel internals being addressed by the driver patches this time. Since the driver builds fine using the current relative paths and the makefile recipes, that shouldn't break just because of the 6.13 kernel update. (but I've not tested that)
@drankinatty - Just a heads up: the linux and -zen kernels were released today, 23 Jan, both at version 6.13.
Cheers
@vnctdj Will do. As soon as 6.13 is released, I'll let you know. I've already built and patched and 6.12.10 update went fine with the change from relative to absolute paths in the two Kbuild makefiles, so I don't expect any surprises when 6.13 is released. I still have to dig into why the change, but I suspect it is aimed at fixing some of the kms drm corner-cases that appeared after 6.12 removed the nvidia-drm from the kernel.
Note to all after the 6.12 drm changes I needed to add nvidia-drm.modeset=1 to my kernel command-line. Desktop was fine without it, but anything that relied on /sys/class/drm/card0... being present would fail as the links for card0, etc... were not created without it. (btop would fail to start, etc..)
@drankinatty Thanks for your early work! I've prepared the package update on my PC, I'll push the commit once you confirm the patch is working.
The changes for 6.13 simply effect the nvidia.Kbuild and nvidia-modesetting.Kbuild make files. It's just a change between using relative symlinks and absolute paths for them. (don't know why). The nvidia-470xx-fix-linux-6.13.patch patch from the 470 driver can be used directly. There is a max of a 2-line offset between the lines in the Kbuild files.
I did go ahead and create a Nvidia 390xx Linux 6.13 patch that corrects the 2-line offset and I've built with it under 6.12.9 which builds fine, but haven't testes on 6.13 yet. We will just have to wait for it to appear.
@drankinatty - thanks for the 6.13 heads up. Please let us know when you think the patch is ready - and I will help test it. Cheers
Linux 6.13 should be released next week and it does appear a patch will be required. The nvidia-470xx-fix-linux-6.13.patch (Joan Bruguera) can likely be adapted and I'll work through it this weekend.
Pinned Comments
vnctdj commented on 2025-01-24 07:37 (UTC)
Use this forum thread for discussion: https://bbs.archlinux.org/viewtopic.php?pid=1946926
jonathon commented on 2022-05-26 09:46 (UTC)
Please don't flag this package out-of-date unless a new version has been released by NVIDIA.
jonathon commented on 2021-12-26 22:44 (UTC) (edited on 2021-12-26 22:44 (UTC) by jonathon)
The DKMS package guidelines are explicit that
linux-headersshould not be a dependency of any DKMS package.As a concrete example of why including that as a hard dependency is a bad idea, what happens when
linuxis not an installed kernel?