Arch Linux User Repository

@dbermond my kernel build does create a directory in /usr/lib/modules. That is not the issue. The issue is that when it's symlinked back to the source, there is no version file where this build script is looking with the following snippet:

local _kernver
    if [ -d "/usr/lib/modules/$(uname -r)" ]
    then
        _kernver="$(<"/usr/lib/modules/$(uname -r)/build/version")"
    else
        _kernver="$(find /usr/lib/modules -mindepth 1 -maxdepth 1 -type d | head -n1)"
        _kernver="$(<"/usr/lib/modules/${_kernver##*/}/build/version")"
fi

if i'm not mistaken, the version file at that location has been deprecated and is now at include/generated/uapi/linux/version.h. what I provided below would change the PKGBUILD to only look at module folders found in /usr/lib/modules without the need for a specific version file. With the latest update and a locally built 6.15.2, this was still necessary. Perhaps there's a better way to write it, but it's functional at this point with what's below.

@sonofevropa firstly, your build issue should be fixed by your custom kernel, and not in this package, as it should correctly provide a versioned directory for kernel modules. Secondly, your suggestion does not make sense, as the '_kernver' variable is not used in the build() function.

Every time I build this, it requires intervention to build against my locally built kernel, which with traditional compilation does not produce a version file. I'd like to propose a change to the package build:

local _kernver
    if [ -d "/usr/lib/modules/$(uname -r)" ]
    then
        _kernver="$(uname -r)"
    else
        _kernver="$(find /usr/lib/modules -mindepth 1 -maxdepth 1 -type d | head -n1)"
        _kernver=_kernver="${_kernver##*/}"
    fi

@nikdog I have just checked after deleting my local cached upstream sources, and the package is building perfectly fine. I cannot reproduce your issue.

Not sure why I'm getting this error. Would seem to be bad source files, but then everyone would have this problem.

 [ nvidia            ]  CC           _out/Linux_x86_64/g_nvid_string.c
_out/Linux_x86_64/g_nvid_string.c:1:25: warning: missing terminating " character
    1 | const char  NVRM_ID[] = "nvidia id: NVIDIA UNIX Open Kernel Module for x86_64  575.51.02  Release Build  (archlinux_builder@archlinux)  May 18 07:20:21.275 [notice] Tor 0.4.8.16 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.5.0, Zlib 1.3.1, Liblzma 5.8.1, Libzstd 1.5.7 and Glibc 2.41 as libc.
      |                         ^
_out/Linux_x86_64/g_nvid_string.c:1:25: error: missing terminating " character
    1 | const char  NVRM_ID[] = "nvidia id: NVIDIA UNIX Open Kernel Module for x86_64  575.51.02  Release Build  (archlinux_builder@archlinux)  May 18 07:20:21.275 [notice] Tor 0.4.8.16 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.5.0, Zlib 1.3.1, Liblzma 5.8.1, Libzstd 1.5.7 and Glibc 2.41 as libc.
      |                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_out/Linux_x86_64/g_nvid_string.c:2:1: error: ‘May’ undeclared here (not in a function)
    2 | May 18 07:20:21.275 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
      | ^~~
_out/Linux_x86_64/g_nvid_string.c:2:5: error: expected ‘,’ or ‘;’ before numeric constant
    2 | May 18 07:20:21.275 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
      |     ^~
_out/Linux_x86_64/g_nvid_string.c:2:37: warning: missing terminating ' character
    2 | May 18 07:20:21.275 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
      |                                     ^
_out/Linux_x86_64/g_nvid_string.c:2:37: error: missing terminating ' character
    2 | May 18 07:20:21.275 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
      |                                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_out/Linux_x86_64/g_nvid_string.c:3:48: warning: multi-character character constant [-Wmultichar]
    3 | May 18 07:20:21.275 [warn] Command-line option 'PDT' with no value. Failing.
      |                                                ^~~~~
_out/Linux_x86_64/g_nvid_string.c:4:69: warning: missing terminating " character
    4 | May 18 07:20:21.275 [err] Reading config failed--see warnings above.";
      |                                                                     ^
_out/Linux_x86_64/g_nvid_string.c:4:69: error: missing terminating " character
    4 | May 18 07:20:21.275 [err] Reading config failed--see warnings above.";
      |                                                                     ^~
make[1]: *** [Makefile:203: _out/Linux_x86_64/g_nvid_string.o] Error 1
make[1]: Leaving directory '/home/nikdog/.cache/yay/nvidia-open-beta/src/open-gpu-kernel-modules-575.51.02/src/nvidia'
make: *** [Makefile:34: src/nvidia/_out/Linux_x86_64/nv-kernel.o] Error 2
make: Leaving directory '/home/nikdog/.cache/yay/nvidia-open-beta/src/open-gpu-kernel-modules-575.51.02'
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: nvidia-open-beta-exit status 4

@@brianc Try to build the package in a clean chroot. Alternatively, use nvidia-open-beta-dkms.

@brianc Are you using the nvidia-open-beta or nvidia-open-beta-dkms package? the dkms package should automatically rebuild and install itself properly after a kernel update, so if you are not using that one, give it a try. Also, do you have the headers package for your specific kernel type installed?

@dbermond That's what I initially tried; but, it didn't work for me - and it's breaking again today with the -2 version of both this package and the linux package.

I'm looking at line 45 of the PKGBUILD and it checks for the presence of a directory matching the currently running kernel which shouldn't be there if the kernel has been updated; but, on my system, it's still there.

Its contents seem to be directly related to this package--a single directory called extramodules that contains the nvidia kernel modules:

❭ cd 6.14.4-arch1-1/extramodules
❭ ls
nvidia-drm.ko.zst  nvidia-modeset.ko.zst  nvidia-uvm.ko.zst
nvidia.ko.zst      nvidia-peermem.ko.zst

It looks like those are being left around for some reason on my system when the kernel is updated. I'm not sure why. But that's definitely the source of the build failing.

I suspect it's a similar issue to the one @Thorin_Wolf was reporting previously--remnants of an older kernel headers package left around tricking this PKGBUILD into thinking that was the version to build against.

I removed those old remnants and the build works as expected.

@brianc you can do a system upgrade with 'pacman -Syu' and rebuild this package immediately after, and then you reboot.

Build error on linux-tkg 6.14.4, https://pastebin.com/Di5suHTk, I'm using makepkg of course, also new kernel ver. linux 6.14.4.arch1-2 gives errors when rebuilding intramfs ERROR: module not found: 'nvidia' ERROR: module not found: 'nvidia_modeset' ERROR: module not found: 'nvidia_uvm' ERROR: module not found: 'nvidia_drm'