Package Details: opencl-nvidia-390xx 390.157-13

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: 1.87
First Submitted: 2020-03-11 17:29 (UTC)
Last Updated: 2024-11-25 23:34 (UTC)

Dependencies (2)

Required by (66)

Sources (16)

Pinned Comments

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?

jonathon commented on 2020-10-19 12:41 (UTC) (edited on 2021-05-11 14:18 (UTC) by jonathon)

PACKAGE NEEDS LONG TERM MAINTAINER

I have adopted the 390xx packages to keep them secure. I do not run any 390xx hardware so will not notice any breakages and cannot test any changes.

Until such time as someone else steps up to maintain these packages - ideally someone who actually has 390xx hardware - I have to rely on you to tell me what changes are needed.

Don't expect a response if you post only "this doesn't work", and do not email me to complain about the package not working!

Use this forum thread for discussion: https://bbs.archlinux.org/viewtopic.php?pid=1946926

A binary package is also available in my kernel-lts unofficial user repository.

Latest Comments

1 2 3 4 5 6 .. 27 Next › Last »

sfranchi commented on 2024-12-22 19:40 (UTC)

After the latest kernel update and after a successful build of the latest version 390xx-dkms package, my external monitor is no longer properly recognized. It does show up, but only as a basic CGA in a 640-400 resolution, instead of being seen as the Dell 1900x1280 that it is. This had never happened to me before. Anyone has any insights?

duht commented on 2024-12-10 20:59 (UTC)

@Foxos thank you so much. Your method worked for me too. A strange thing: when I deleted /etc/X11/xorg.conf.d/10-nvidia-drm-outputclass.conf now, everything still works as it should. I don't know if its due to latest minor kernel update, but it seems this solution is no longer needed.

yayowd commented on 2024-12-05 11:13 (UTC)

@Foxos After configuring according to your method, when using the nvidia-drm.modeset=1 parameter, the xorg starts normally. Thank you very much.

Foxos commented on 2024-12-01 18:51 (UTC) (edited on 2024-12-01 18:56 (UTC) by Foxos)

@duht I faced same problem and fixed it by following steps at NVIDIA/Troubleshooting:

copy /usr/share/X11/xorg.conf.d/10-nvidia-drm-outputclass.conf to /etc/X11/xorg.conf.d/10-nvidia-drm-outputclass.conf, and then edit /etc/X11/xorg.conf.d/10-nvidia-drm-outputclass.conf and add the line Option "PrimaryGPU" "yes"

duht commented on 2024-11-29 13:00 (UTC) (edited on 2024-11-29 13:07 (UTC) by duht)

After upgrade startx fails with

(EE) NVIDIA(GPU-0): Failed to acquire modesetting permission.
(EE) NVIDIA(0): Failing initialization of X screen 0
(EE) Screen(s) found, but none have a usable configuration.
(EE) 
(EE) no screens found(EE)

I use nvidia-drm.modeset=1 parameter, deleting or regenerating via nvidia-xconfig xorg configuration file doesn't help. Downgrading to 6.11 solves problem.

Any ideas??

drankinatty commented on 2024-11-29 07:00 (UTC)

@yayowd, I'm glad you got it working. Removal of the Nvidia drm output polling ability and having to rely on the kernel kms drm will cause issues in some cases. I'm still reading on this. The wiki has basic information, and information on Forcing modes and EDID. The 390, 470, 535 and 560 drivers are have differing support for kms and the change in drm will affect each in slightly different ways. What that means is it may take a driver by driver implementation of kernel drm to replace (if possible) what was lost with the latest kernel changes.

yayowd commented on 2024-11-27 10:55 (UTC)

After I updated the system and upgraded the kernel to 6.12, the xface desktop failed to start. I have not used the "nvidia-drm.modeset=1" parameter and the xserver configuration file.

First I noticed the error message in "dmesg | grep -i nvidia": nvidia: module verification failed: signature and/or required key missing - tainting kernel. I searched and found that it should not affect the use.

I added "nvidia-drm.modeset=1" to the kernel command line parameters, but it still failed to start. I checked the error "NVIDIA(GPU-0): Failed to acquire modesetting permission" in "cat .local/share/xorg/Xorg.0.log | grep -i nvidia". I searched and added in /etc/X11/xorg.conf: Option "UseDisplayDevice" "none" The error is gone, but the screen resolution is only 800x600.

I removed "nvidia-drm.modeset=1", deleted the xserver configuration file and reinstalled the nvidia driver, but the desktop still could not start. I used "nvidia-xcofig" to regenerate the xserver configuration file. The desktop could start, but there was no mouse pointer, the window could not be resized or dragged, the alacritty terminal could not be started, and the system shortcut keys could not be used. In Xorg.0.log, I saw the error "NVIDIA(0): Failed to initialize the GLX module". So, I added the following to /etc/X11/xorg.conf: Section "Files" ModulePath "/usr/lib/nvidia/xorg" ModulePath "/usr/lib/xorg/modules" EndSection After that, it resumed normal use.

air-g4p commented on 2024-11-27 08:22 (UTC) (edited on 2024-11-27 08:22 (UTC) by air-g4p)

@vnctdj, @drankinatty and @canolucas,

Thanks for your much appreciated 6.12 efforts. Builds, installs and operates correctly against 6.12.1-arch1-1.

Cheers

drankinatty commented on 2024-11-26 10:39 (UTC)

@JuliusTZM, I suspect that is a direct result of the removal of .output_poll_changed = nv_drm_output_poll_changed from the nvidia drm driver file. There were efforts to incorporate kernel drm with the addition of the functions you see in the patch, but it is likely to have differing capabilities. Let us know if setting the kernel parameter nvidia-drm.modeset=1 doesn't fix the issue. So far I've not noticed any difference -- but HDMI to SmartTV may be something not as well supported by kernel drm?

Foxos commented on 2024-11-25 23:42 (UTC)

After this 6.12.patch, setting nvidia-drm.modeset=1 is a must.

1 2 3 4 5 6 .. 27 Next › Last »