@jonathon - Confirmed today that nvidia-390xx-dkms 390.143-4 builds correctly and installs without issue against: 5.13.1-arch1-1 as well as against my various 5.12.X kernels.
Cheers!
Git Clone URL: | https://aur.archlinux.org/nvidia-390xx-utils.git (read-only, click to copy) |
---|---|
Package Base: | nvidia-390xx-utils |
Description: | NVIDIA drivers utilities |
Upstream URL: | https://www.nvidia.com/ |
Licenses: | custom |
Conflicts: | nvidia-390xx-libgl, nvidia-libgl, nvidia-utils |
Provides: | nvidia-390xx-libgl, nvidia-libgl, nvidia-utils, opengl-driver, vulkan-driver |
Submitter: | svenstaro |
Maintainer: | jonathon (vnctdj) |
Last Packager: | vnctdj |
Votes: | 61 |
Popularity: | 2.16 |
First Submitted: | 2020-03-11 17:29 (UTC) |
Last Updated: | 2024-11-25 23:34 (UTC) |
« First ‹ Previous 1 .. 19 20 21 22 23 24 25 26 27 Next › Last »
@jonathon - Confirmed today that nvidia-390xx-dkms 390.143-4 builds correctly and installs without issue against: 5.13.1-arch1-1 as well as against my various 5.12.X kernels.
Cheers!
DKMS no longer builds on 5.13.0. Tried reinstalling DKMS and nvidia-390xx-dkms itself, no luck. Warnings and errors:
[...]
/var/lib/dkms/nvidia/390.143/build/nvidia/nv-mmap.c: In function ���nv_encode_caching���:
/var/lib/dkms/nvidia/390.143/build/nvidia/nv-mmap.c:255:16: warning: this statement may fall through [-Wimplicit-fallthrough=]
255 | if (NV_ALLOW_CACHING(memory_type))
| ^
/var/lib/dkms/nvidia/390.143/build/nvidia/nv-mmap.c:257:9: note: here
257 | default:
| ^~~~~~~
[...]
/var/lib/dkms/nvidia/390.143/build/nvidia-drm/nvidia-drm-crtc.c:188:23: error: initialization of ���int (*)(struct drm_plane *, struct drm_atomic_state *)��� from incompatible pointer type ���int (*)(struct drm_plane *, struct drm_plane_state *)��� [-Werror=incompatible-pointer-types]
188 | .atomic_check = nv_drm_plane_atomic_check,
| ^~~~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/nvidia/390.143/build/nvidia-drm/nvidia-drm-crtc.c:188:23: note: (near initialization for ���nv_plane_helper_funcs.atomic_check���)
/var/lib/dkms/nvidia/390.143/build/nvidia-drm/nvidia-drm-crtc.c:189:23: error: initialization of ���void (*)(struct drm_plane *, struct drm_atomic_state *)��� from incompatible pointer type ���void (*)(struct drm_plane *, struct drm_plane_state *)��� [-Werror=incompatible-pointer-types]
189 | .atomic_update = nv_drm_plane_atomic_update,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/nvidia/390.143/build/nvidia-drm/nvidia-drm-crtc.c:189:23: note: (near initialization for ���nv_plane_helper_funcs.atomic_update���)
/var/lib/dkms/nvidia/390.143/build/nvidia-drm/nvidia-drm-crtc.c:190:23: error: initialization of ���void (*)(struct drm_plane *, struct drm_atomic_state *)��� from incompatible pointer type ���void (*)(struct drm_plane *, struct drm_plane_state *)��� [-Werror=incompatible-pointer-types]
190 | .atomic_disable = nv_drm_plane_atomic_disable,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/nvidia/390.143/build/nvidia-drm/nvidia-drm-crtc.c:190:23: note: (near initialization for ���nv_plane_helper_funcs.atomic_disable���)
CC [M] /var/lib/dkms/nvidia/390.143/build/nvidia-drm/nvidia-drm-gem.o
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:272: /var/lib/dkms/nvidia/390.143/build/nvidia-drm/nvidia-drm-crtc.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile:1847: /var/lib/dkms/nvidia/390.143/build] Error 2
make[1]: Leaving directory '/usr/lib/modules/5.13.0-174-tkg-cacule/build'
make: *** [Makefile:81: modules] Error 2
I've been crossing XID errors with screen crashes.
Rolling back to 390.143-1 (+ Linux 5.12.13) is so far stable
Confirmed working on Jun. 9th, 2021
Linux Kernel 5.12.9 installed packages:
Nvidia Driver 390.143 installed packages:
Nvidia Driver 390.143 packages not tried:
Installation Notes:
Reboot & Enjoy! Please make sure you also report any bugs!
Thanks everyone, especially Nvidia team, package maintainer jonathon and anyone providing patches!
@stephenboston: That's because the three packages: nvidia-390xx-utils, opencl-nvidia-390xx, nvidia-390xx-dkms are all built from the same source and PKGBUILD file.
This page for nvidia 390 dkms is pointing to the repo for nvida 390 utils.
I don't think that's a packaging issue (e.g. https://github.com/OpenPIV/openpiv-python-gpu/issues/3). Maybe open a thread on the forum?
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)
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.