Since we are in need of a long-term maintainer, and since @vnctd did such a good job handling the patches for glibc-2.37 and the 6.2 kernel patch, I would nominate @vnctd as the new maintainer -- if he will do it.
I fumbled around getting the package to build without the patch to the point of drm failure, but then would have been stuck until I could find an existing patch for it. I know C and understood the errors
nv-acpi.c:77:19: error: initialization of XXX from incompatible pointer type YYY
77 | .remove = nv_acpi_remove_two_args,
and
nvidia-drm-drv.c:244:21: error: ‘struct drm_mode_config’ has no member named ‘fb_base’
244 | dev->mode_config.fb_base = 0;
However, it would likely have taken me a bit more time to arrive at a full solution -- so I'm not the guy. Anyone else have a 2nd or other thoughts?
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.