I checked and 6.16.1
has the same error. I have a laptop with an external monitor connected via HDMI, and Xorg is launched via startx
. Disconnecting the monitor doesn't help. maybe running via startx
means that the error doesn't occur for everyone? 6.16.0 works normally like all previous kernel versions. What changed in 6.16.1 that suddenly stopped working? Does anyone have any ideas?
Search Criteria
Package Details: opencl-nvidia-390xx 390.157-17
Package Actions
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: | 61 |
Popularity: | 0.147067 |
First Submitted: | 2020-03-11 17:29 (UTC) |
Last Updated: | 2025-06-12 22:18 (UTC) |
Dependencies (2)
- zlib (zlib-gitAUR, zlib-ng-compat-gitAUR, zlib-ng-compat)
- opencl-headers (opencl-headers-gitAUR) (optional) – headers necessary for OpenCL development
Required by (66)
- aftershotpro3 (requires opencl-nvidia) (optional)
- arrayfire-git (requires opencl-driver) (optional)
- bfgminer-git (requires opencl-driver) (optional)
- computecpp (requires opencl-driver)
- cpu-x-git (requires opencl-driver) (optional)
- crark (requires opencl-driver) (optional)
- cuda-10.2 (requires opencl-nvidia)
- cuda-11.1 (requires opencl-nvidia)
- cuda-11.7 (requires opencl-nvidia)
- cuda-8.0 (requires opencl-nvidia)
- cuda-9.0 (requires opencl-nvidia)
- cuda11.1 (requires opencl-nvidia)
- cuda11.4 (requires opencl-nvidia)
- cuda11.4-versioned (requires opencl-nvidia)
- cuda12.0 (requires opencl-nvidia)
- cuda12.0-versioned (requires opencl-nvidia)
- cytoscape (requires opencl-driver) (optional)
- davinci-resolve (requires opencl-driver)
- davinci-resolve-beta (requires opencl-driver)
- davinci-resolve-portable (requires opencl-driver)
- Show 46 more...
Sources (20)
- gcc-14.patch
- gcc-15.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.14.patch
- kernel-6.15.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
duht commented on 2025-08-23 10:56 (UTC)
aldolat commented on 2025-08-23 06:46 (UTC) (edited on 2025-08-23 07:11 (UTC) by aldolat)
No problem here upgrading from linux-6.16.1.arch1-1
to linux-6.16.2-arch1-1
.
duht commented on 2025-08-22 23:53 (UTC)
I have exactly the same problem as @Irving-1291 with kernel 6.16.2-zen1-1
. I haven't tested 6.16.1
. 6.16.0
works fine. Does anyone have any ideas on how to solve this?
Irving-1291 commented on 2025-08-21 01:56 (UTC)
After updating to linux 6.16.1.arch1-1
Xorg stopped working.
~/.local/share/xorg/Xorg.0.log
says that:
(EE) NVIDIA(GPU-0): Failed to acquire modesetting permission.
(EE) NVIDIA(0): Failing initialization of X screen 0
(II) UnloadModule: "nvidia"
(II) UnloadSubModule: "wfb"
(EE) Screen(s) found, but none have a usable configuration.
(EE)
Fatal server error:
(EE) no screens found
if I roll back to an older kernel, everything works just fine
drankinatty commented on 2025-08-14 20:56 (UTC)
Confirmed 6.16.0 - no patches required. All good here on update.
drankinatty commented on 2025-08-08 00:53 (UTC) (edited on 2025-08-08 01:41 (UTC) by drankinatty)
That is indeed good news. So long as what you have in your virtual machine was triggering the build of the 390xx driver with the 6.16 kernel, then you did it the right way. With this package installed and then installing the 6.16 kernel, there isn't any reason a build in virtualbox would be any different than a build on hardware. (I'll take that as a good sign 6.16 will be one that doesn't need patching for -- thankfully :)
aldolat commented on 2025-08-07 06:14 (UTC) (edited on 2025-08-07 18:14 (UTC) by aldolat)
I'm not sure if this is the correct way to test compatibility, so feel free to correct me if I'm wrong. Here's what I did:
In a VirtualBox machine, I enabled the testing repositories (core-testing
and extra-testing
) and upgraded the system, including the kernel to version 6.16.0-arch1-1
. Then I rebooted the virtual machine, cloned this AUR repository, and ran makepkg -s
.
The package compiled successfully without any errors.
drankinatty commented on 2025-08-06 05:52 (UTC) (edited on 2025-08-06 05:55 (UTC) by drankinatty)
The kernel 6.16 just entered the Testing repo. Anybody have a chance to check if a patch is needed? I haven't had time to look yet. I'll start snooping around. No patch listed at joanbm's gist site -- maybe we will get lucky and none will be needed (rare, but has occurred).
killajoe commented on 2025-06-24 14:25 (UTC)
Checksum changed for the run file
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?