After upgrading xorg-server
to v21.1.2 I can't resume my laptop from suspend.
On nouveau everything works fine.
Downgrading server to 21.1.1 resolves the problem so issue is related to nvidia-390xx driver and newest xorg-server
.
I'm wondering if anyone else has this problem?
Search Criteria
Package Details: opencl-nvidia-390xx 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: | 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.96 |
First Submitted: | 2020-03-11 17:29 (UTC) |
Last Updated: | 2025-01-24 07:30 (UTC) |
Dependencies (2)
- zlib (zlib-ng-compat-gitAUR, zlib-gitAUR, zlib-ng-compat)
- opencl-headers (opencl-headers-gitAUR) (optional) – headers necessary for OpenCL development
Required by (67)
- aftershotpro2 (requires opencl-nvidia) (optional)
- aftershotpro3 (requires opencl-nvidia) (optional)
- arrayfire-git (requires opencl-driver) (optional)
- bfgminer-git (requires opencl-driver) (optional)
- computecpp (requires opencl-driver)
- cpu-x-opencl (requires opencl-driver) (optional)
- cuda-10.0 (requires opencl-nvidia)
- 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)
- cuda-9.2 (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)
- Show 47 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
Latest Comments
« First ‹ Previous 1 .. 18 19 20 21 22 23 24 25 26 27 28 Next › Last »
duht commented on 2021-12-20 23:56 (UTC) (edited on 2021-12-21 00:00 (UTC) by duht)
duht commented on 2021-12-18 22:34 (UTC) (edited on 2021-12-18 22:38 (UTC) by duht)
@jonathon 30-nvidia-ignoreabi.conf
is not needed with 390.147
deliodc commented on 2021-11-17 20:21 (UTC)
Thanks a lot @Scarlet and @Juggrnaut
I was have the error message:
primus: fatal: Bumblebee daemon reported: error: [XORG] (EE) NVIDIA: Use the -ignoreABI option to override this check.
The solution for me was edit the file /etc/bumblebee/xorg.conf.nvidia like the recommendation of @Juggrnaut and add in the Section "Device" zone, the follow lines:
Section "Device"
...
BusID "PCI:01:00:0"
Option "AllowExternalGpus" "true" # If the GPU is external
...
EndSection
And at the end of the file, add the follow section like the recommendation of @Scarlet:
Section "ServerFlags"
Option "IgnoreABI" "1"
EndSection
jonathon commented on 2021-11-15 23:26 (UTC) (edited on 2021-11-15 23:26 (UTC) by jonathon)
Or, just update your copy of nvidia-390xx-utils
as it includes an override file.
DAC324 commented on 2021-11-15 13:49 (UTC) (edited on 2021-11-15 13:50 (UTC) by DAC324)
For all those with that Xorg ABI error and having no /etc/X11/xorg.conf
:
Search for a file called /etc/X11/xorg.conf.d/20-server_flags.conf
. If it does not exist yet, create it. Amend the file and paste the well-known contents there:
Section "ServerFlags"
Option "IgnoreABI" "1"
EndSection
Let's see if Nvidia indeed fixes that. According to https://bbs.archlinux.org/viewtopic.php?pid=2003589#p2003589, Nvidia stated it is supported and receives compat fixes until the end of 2022
.
Juggrnaut commented on 2021-11-13 17:40 (UTC) (edited on 2021-11-14 02:01 (UTC) by Juggrnaut)
After adding in "IgnoreABI" to "/etc/bumblebee/xorg.conf.nvidia" I now receive the following error and it doesn't load:
(WW) NVIDIA: The driver will continue to load, but may behave strangely.
(WW) NVIDIA: This driver was compiled against the X.Org server SDK from commit 4c00369024c9754e670fca37804711fef2980e2f and may not be compatible with the final version of this SDK.
UPDATE <SOLVED> I've figured out my issue and posting it in case anyone else runs into the same problem.
Prior to the recent updates, I never needed to modify the "/etc/bumblebee/xorg.conf.nvidia" file and it worked just fine OOTB. Now after the recent updates, I had to modify that file to now also include the BusID of the nvidia card. Details found here: https://wiki.archlinux.org/title/Bumblebee#Multiple_NVIDIA_Graphics_Cards_or_NVIDIA_Optimus
So after adding in the BusID (along with the "IgnoreABI" setting), it is working again.
CyrIng commented on 2021-11-10 23:21 (UTC)
Do you guys have a solution to avoid the XID errors which freeze desktop ?
JKMooney commented on 2021-11-10 22:07 (UTC)
Impressive, a patch put in place within a day....and here I was getting ready to just concede "end of life" for this old card ;)
jonathon commented on 2021-11-10 17:47 (UTC) (edited on 2021-11-10 17:47 (UTC) by jonathon)
I've included an override file with 390.144-3 as a stop-gap until Nvidia update the driver - while things might randomly break, at least Xorg will load...
hute37 commented on 2021-11-10 17:17 (UTC)
@Scarlet, work like a charm!. For lazy ones like me still using bumblebee
the xorg,conf is: /etc/bumblebee/xorg.conf.nvidia
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?