Arch Linux User Repository

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

Please don't flag this package out-of-date unless a new version has been released by NVIDIA.

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?

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.

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

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)

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

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

@jonathon Thank you

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.

@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)
...

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 ...