@drankinatty Do you consider the optimal action plan to be: 1) include the kernel-6.14.patch and 2) remove the kernel-6.13.patch (as it is no longer needed) ?
Search Criteria
Package Details: nvidia-390xx-utils 390.157-14
Package Actions
Git Clone URL: | https://aur.archlinux.org/nvidia-390xx-utils.git (read-only, click to copy) |
---|---|
Package Base: | nvidia-390xx-utils |
Description: | NVIDIA drivers utilities |
Upstream URL: | https://www.nvidia.com/ |
Licenses: | custom |
Conflicts: | nvidia-390xx-libgl, nvidia-libgl, nvidia-utils |
Provides: | nvidia-390xx-libgl, nvidia-libgl, nvidia-utils, opengl-driver, vulkan-driver |
Submitter: | svenstaro |
Maintainer: | jonathon (vnctdj) |
Last Packager: | vnctdj |
Votes: | 61 |
Popularity: | 1.24 |
First Submitted: | 2020-03-11 17:29 (UTC) |
Last Updated: | 2025-01-24 07:30 (UTC) |
Dependencies (6)
- egl-wayland (egl-wayland-gitAUR)
- libglvnd (libglvnd-gitAUR)
- xorg-server (xorg-server-gitAUR, xorg-server-bug865-issue1578AUR, xorg-server-bug865AUR)
- nvidia-390xx-settingsAUR (optional) – configuration tool
- opencl-nvidia-390xxAUR (optional) – OpenCL support
- xorg-server-devel (xorg-server-devel-gitAUR) (optional) – nvidia-xconfig
Required by (320)
- adaptivecpp (requires nvidia-utils)
- adaptivecpp-git (requires nvidia-utils)
- agisoft-metashape (requires nvidia-utils) (optional)
- agisoft-metashape-pro (requires nvidia-utils) (optional)
- airshipper (requires vulkan-driver) (optional)
- alchemy-viewer-git (requires nvidia-utils) (optional)
- alchemy-viewer-git (requires nvidia-libgl) (optional)
- aquamarine-git (requires opengl-driver)
- ares-emu (requires vulkan-driver)
- ares-emu-avx-git (requires vulkan-driver)
- ares-emu-git (requires vulkan-driver)
- armorpaint (requires opengl-driver)
- arrayfire-git (requires nvidia-utils) (optional)
- aurorafw-git (requires opengl-driver)
- auto-gpufreq-git (requires nvidia-utils)
- autokey-git (requires nvidia-utils) (optional)
- blackmagic-raw-sdk (requires nvidia-utils) (optional)
- btop-git (requires nvidia-utils) (optional)
- btop-gpu-git (requires nvidia-utils) (optional)
- ccdc-mercury (requires opengl-driver)
- Show 300 more...
Sources (17)
- gcc-14.patch
- https://us.download.nvidia.com/XFree86/Linux-x86_64/390.157/NVIDIA-Linux-x86_64-390.157.run
- kernel-4.16+-memory-encryption.patch
- kernel-6.10.patch
- kernel-6.12.patch
- kernel-6.13.patch
- kernel-6.2.patch
- kernel-6.3.patch
- kernel-6.4.patch
- kernel-6.5.patch
- kernel-6.6.patch
- kernel-6.8.patch
- nvidia-390xx-utils.sysusers
- nvidia-390xx.rules
- nvidia-drm-outputclass.conf
- systemd-homed-override.conf
- systemd-suspend-override.conf
canolucas commented on 2025-03-22 20:16 (UTC)
drankinatty commented on 2025-03-17 21:03 (UTC) (edited on 2025-03-17 21:52 (UTC) by drankinatty)
The 6.14 kernel is soon to arrive. Thankfully there is only a minor patch to nvidia-drm-drv.c
required. The kernel-6.14.patch can be grabbed if you want to test it early. The patch is reworked for correct line offsets from @joanbm
joanbm/nvidia-470xx-fix-linux-6.14.patch
It's short enough to include here:
diff -ruNb a/kernel/nvidia-drm/nvidia-drm-drv.c b/kernel/nvidia-drm/nvidia-drm-drv.c
--- a/kernel/nvidia-drm/nvidia-drm-drv.c 2025-01-17 18:43:37.516640859 -0600
+++ b/kernel/nvidia-drm/nvidia-drm-drv.c 2025-03-17 15:30:32.466599940 -0500
@@ -759,7 +759,10 @@
.name = "nvidia-drm",
.desc = "NVIDIA DRM driver",
+#if LINUX_VERSION_CODE < KERNEL_VERSION(6, 14, 0)
+ // Rel. commit. "drm: remove driver date from struct drm_driver and all drivers" (Jani Nikula, 4 Dec 2024)
.date = "20160202",
+#endif
#if defined(NV_DRM_DRIVER_HAS_DEVICE_LIST)
.device_list = LIST_HEAD_INIT(nv_drm_driver.device_list),
(note: offsets in this patch take into consideration the application of all prior patches that also patch nvidia-drm-drv.c
. The kernel patches for 6.2, 6.4, 6.6, 6.8 and 6.12 also patch this file. Just add this as the next patch in your PKGBUILD
after the application of all other kernel patches)
@lu9dce - do you get any errors in the journal, or xsession-errors or Xorg.0.log? Is there any error for the browser? I've not run into that issue before and will need your help to understand what you are seeing. Also, do you use wayland or x11? If wayland, that wasn't even around when the 390 driver came out, which could explain it.
batot commented on 2025-03-17 20:48 (UTC) (edited on 2025-03-17 21:40 (UTC) by batot)
$ sudo dkms status
nvidia/390.157, 6.12.19-1-lts, x86_64: installed
Great job bro.
If you need my help i can join helping testing nvidia-390xx...
lu9dce commented on 2025-03-07 13:07 (UTC)
This driver compiles and installs but does not activate 3D support Neither browsers nor software that requires OpenGL work
The module is loaded but programs cannot access 3D
I have been testing this with the LTS kernel I have been using kernel 6.1.0 for a month now.. because the driver works on Debian so I decided to use a kernel that is more similar to the one that Debian 12 has
If changing the kernel works, I don't see that it is a problem with Mesa or the current OpenGL
I had previously mentioned this topic here
drankinatty commented on 2025-03-01 23:59 (UTC)
Looks like the kernel in may have fixed what was patched for with the 6.13 patch to the kbuild files. I just removed the patch from openSUSE Tumbleweed for 6.13.5 and the build proceeded fine. I'll update in a bit. If you experience a build failure with 6.13.5, try removing the kernel-6.13.patch.
air-g4p commented on 2025-01-24 14:14 (UTC) (edited on 2025-01-24 14:15 (UTC) by air-g4p)
@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
vnctdj commented on 2025-01-24 07:37 (UTC)
Use this forum thread for discussion: https://bbs.archlinux.org/viewtopic.php?pid=1946926
vnctdj commented on 2025-01-24 07:36 (UTC) (edited on 2025-01-24 07:37 (UTC) by vnctdj)
Package updated!
Thanks again @drankinatty :)
As a reminder, there's no need to flag the package as out-of-date... (see pinned comment)
drankinatty commented on 2025-01-23 23:29 (UTC) (edited on 2025-01-24 00:01 (UTC) by drankinatty)
@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)
air-g4p commented on 2025-01-23 05:53 (UTC) (edited on 2025-01-24 13:48 (UTC) by air-g4p)
@drankinatty - Just a heads up: the linux and -zen kernels were released today, 23 Jan, both at version 6.13.
Cheers
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-headers
should 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
linux
is not an installed kernel?