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

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: 62
Popularity: 0.180118
First Submitted: 2020-03-11 17:29 (UTC)
Last Updated: 2025-10-11 08:48 (UTC)

Dependencies (2)

Required by (67)

Sources (21)

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?

Latest Comments

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

duht commented on 2025-12-05 11:32 (UTC) (edited on 2025-12-05 11:36 (UTC) by duht)

@vnctdj, sorry for the late reply. My laptop has Intel graphics disabled in the BIOS and there's no way to run it. It only runs on Nvidia graphics, so the Arch Wiki on Nvidia Optimus is useless to me. As for xinit, I've been using it from the start, and Xorg stopped starting when Archlinux abandoned the "drivers/firmware: skip simpledrm if nvidia-drm.modeset=1 is set" patch for its kernel. I compiled my own kernel with xanmod patches and added the above patch, and everything works as before. As a plus, after using modprobed-db, the Linux kernel now takes up 10 times less disk space than the standard one. As a minus, I have to compile it myself. When I have time to play around, I'll install lightdm and see if it works with the standard kernel.

drankinatty commented on 2025-12-03 06:31 (UTC)

Well, that is some welcome news! Thank you @aldolat for the testing and report. Three out of the last seven kernels, no patching required - I like that.

aldolat commented on 2025-12-02 18:38 (UTC)

It looks like we're lucky this time! On my VirtualBox machine (which I use for testing), I upgraded to kernel 6.18 and didn't encounter any errors with the nvidia 390.157 package. Can anyone else confirm?

drankinatty commented on 2025-12-02 03:03 (UTC)

Well, this is either really good news, or not so good news. The 6.18 kernel just hit the testing repo and there is no 6.18 patch on Joan's page for the 470 driver. Hopefully this means there will be no patch required for 6.18? Has anybody tested with the 6.18 kernel yet?

vnctdj commented on 2025-11-10 23:38 (UTC)

@duht I also use startx to launch Xorg and doesn't use any display manager as I use i3. I don't use Bumblebee or any similar tool. I simply followed https://wiki.archlinux.org/title/NVIDIA_Optimus#Use_NVIDIA_graphics_only and https://wiki.archlinux.org/title/Xinit . I hope it helps as that's what works on my laptop.

yars068 commented on 2025-11-06 23:08 (UTC) (edited on 2025-11-06 23:09 (UTC) by yars068)

I attach a debug messages from driver, maybe this will be helpful.

yars068 commented on 2025-11-06 19:06 (UTC)

@canolucas, how should I set up my machine, given that it's an Optimus laptop with a Fermi chip? Currently I still use Bumblebee. What packages I should have installed?

duht commented on 2025-10-19 20:08 (UTC)

Thank you @drankinatty for your help, but adding nosimplefb=1 to kernel command line doesn't change anything. I already had nvidia-drm.modeset=1 set- without it, the system wouldn't boot properly. If you have any other ideas, I'd be happy to test them.

drankinatty commented on 2025-10-18 23:31 (UTC)

@duht I have had the exact reports from openSUSE on startx no longer working:

I do get them to build since uninstalling kernel and all nvidia added packages, then reinstalling same. only startx now fail and not previously. and I use startx frequently to run additional graphical desktops.

I did not get specifics, but in follow-on there was reference to blacklisting fbdev and making sure wayland wasn't involved (you now get stray pieces of wayland installed as dependencies). I can't find that post at the moment to quote.

What are you using for a command-line to boot, e.g. what is shown by cat /proc/cmdline? I seem to recall nosimplefb=1 and nvidia-drm.modeset=1 being needed now. I have those on openSUSE (but haven't tried startx), on Arch I don't have either, but boot to graphical-target with lightdm. Worth seeing if they make any difference.

duht commented on 2025-10-18 09:45 (UTC) (edited on 2025-10-18 09:49 (UTC) by duht)

Does anyone else still use startx to launch Xorg? I'm using kernel 6.17 and I still get the same error that started with 6.16.1.

(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

I've tried everything, various kernel parameters, deleted xorg.conf, and even installed a different desktop environment to see if it would start.

The only thing I can think of that explains why this problem occurs for me and not for most others is that I don't have any DM, I just run Xorg with startx.

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