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

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: 57
Popularity: 0.74
First Submitted: 2020-03-11 17:29 (UTC)
Last Updated: 2024-07-20 22:27 (UTC)

Dependencies (2)

Required by (68)

Sources (15)

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

« First ‹ Previous 1 .. 18 19 20 21 22 23 24 25 Next › Last »

MartinDiehl commented on 2021-05-10 16:07 (UTC) (edited on 2021-05-10 16:08 (UTC) by MartinDiehl)

I have a problem with running an an MPI application (compiled on my computer)

--------------------------------------------------------------------------
An error occurred while trying to map in the address of a function.
  Function Name: cuIpcOpenMemHandle_v2
  Error string:  /usr/lib/libcuda.so.1: undefined symbol: cuIpcOpenMemHandle_v2
CUDA-aware support is disabled.
--------------------------------------------------------------------------

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Backtrace for this error:
#0  0x146a21675f7f in ???
#1  0x0 in ???

I assume it is related to the recent inclusion of (optional) CUDA support into openMPI (https://bugs.archlinux.org/task/68031).

On other computers, I simply get the message that CUDA support is disabled because libcuda.so is not found.

jonathon commented on 2021-04-29 10:20 (UTC)

@hute37: Not a package issue. Report to the paru maintainer.

hute37 commented on 2021-04-29 09:20 (UTC) (edited on 2021-04-29 09:20 (UTC) by hute37)

Conficts reported in latest update:

installing nvidia-390xx-utils (390.143-3) breaks dependency 'nvidia-390xx-utils=390.141' required by nvidia-390xx-dkms

running paru -Syyu, proposed the upgrade:


Aur (3) 
    nvidia-390xx-settings-390.143-2 (libxnvctrl-390xx nvidia-390xx-settings)  
    nvidia-390xx-utils-390.143-3 (nvidia-390xx-utils nvidia-390xx-dkms opencl-nvidia-390xx)

jonathon commented on 2021-04-06 11:14 (UTC)

Thank you, I've tracked down the original source for the patch and added it (with credit) to this package!

BlackIkeEagle commented on 2021-04-06 09:07 (UTC)

Manjaro has a working patch for building with the upcoming 5.12 kernel https://gitlab.manjaro.org/packages/extra/linux512-extramodules/nvidia-390xx/-/blob/master/kernel-5.12.patch

CyrIng commented on 2021-04-05 10:05 (UTC)

@jonathon Thank you

jonathon commented on 2021-04-01 18:07 (UTC)

That kind of looks like you're using mesa rather than nvidia? If you could use the linked forum thread to provide further details that would be easier than using the comments section here.

CyrIng commented on 2021-03-30 23:08 (UTC)

@jonathon Using nvidia-390xx-* plus kernel 5.11.10 and without vulkan-swrast:

systemd-coredump[....]: Process .... (chromium) of user .... dumped core.

                                              Stack trace of thread ....:
                                              #0  0x00007f... vkGetPhysicalDeviceProperties (libvulkan.so.1 + 0x32b30)
                                              #1  0x00007f... n/a (swrast_dri.so + 0xb7b124)
                                              #2  0x00007f... n/a (swrast_dri.so + 0xf99a5e)
                                              #3  0x00007f... n/a (swrast_dri.so + 0x15c067)
                                              #4  0x00007f... n/a (swrast_dri.so + 0x6e102e)
                                              #5  0x00007f... n/a (swrast_dri.so + 0x156801)
                                              #6  0x00007f... n/a (swrast_dri.so + 0x60a869)
                                              #7  0x00007f... n/a (libGLX_mesa.so.0 + 0x3bd12)
                                              #8  0x00007f... n/a (libGLX_mesa.so.0 + 0x356de)
                                              #9  0x00007f... n/a (libGLX_mesa.so.0 + 0x365f1)
...

jonathon commented on 2021-03-30 22:13 (UTC)

nvidia-utils (and nvidia-390xx-utils) provides vulkan-driver, which vulkan-swrast also provides. I wonder if this might be related to https://bugs.archlinux.org/task/65118 ...

« First ‹ Previous 1 .. 18 19 20 21 22 23 24 25 Next › Last »