Arch Linux User Repository

@Menelkir Thanks for reply, I scrubbed my caches and found some CFLAGS/CXXFLAGS and unset them and then reinstalled kernel+headers and nvidia-470xx-dkms but unfortunately I'm still getting the same error:

...
==> dkms install --no-depmod nvidia/470.161.03 -k 6.2.7-zen1-1-zen
Error! Bad return status for module build on kernel: 6.2.7-zen1-1-zen (x86_64)
Consult /var/lib/dkms/nvidia/470.161.03/build/make.log for more information.
==> WARNING: `dkms install --no-depmod nvidia/470.161.03 -k 6.2.7-zen1-1-zen' exited 10
❯ less /var/lib/dkms/nvidia/470.161.03/build/make.log
KMS make.log for nvidia-470.161.03 for kernel 6.2.7-zen1-1-zen (x86_64)
...
/var/lib/dkms/nvidia/470.161.03/build/nvidia/nv-acpi.c:84:19: error: initialization of ‘void (*)(struct acpi_device *)’ from incompatible pointer type ‘int (*)(struct acpi_device *, int)’ [-Werror=incompatible-pointer-types]
   84 |         .remove = nv_acpi_remove_two_args,
      |                   ^~~~~~~~~~~~~~~~~~~~~~~

I will try removing then reinstalling involved packages as a last effort and see if this will change anything. If not I'm out of ideas and stay on lts kernel for now I guess.

edit: removing before reinstalling didn't change anything

edit: I just got 6.2.8-zen1-1-zen kernel and nvidia-470xx-dkms from chaotic-aur to work. But this aur package still fails to build the module for me. I'm getting a different error, but now for the lts kernel as well. So the problem is most likely on my side. Might be mixing aur with chaotic-aur packages or just something about my very old arch installation. Since chatotic-aur does the trick for me I won't investigate further. Thanks for hearing me out and looking into it @Menelkir.

@aparthy I use zen too, I just removed and reinstalled the package (after cleaning up any sort of cache) and it builds and installs without any issue. Do you have custom CFLAGS? I've noticed you're forcing the dkms autoinstall, is there something preventing you from just installing this package? Dkms should trigger and install the modules by default just fine.

❯ less /var/lib/dkms/nvidia/470.161.03/build/make.log
DKMS make.log for nvidia-470.161.03 for kernel 6.2.6-zen1-1-zen (x86_64)
Sa 18. Mär 21:18:26 CET 2023
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: gcc (GCC) 12.2.1 20230201
  You are using:           cc (GCC) 12.2.1 20230201
...
/var/lib/dkms/nvidia/470.161.03/build/nvidia/nv-acpi.c:84:19: error: initializatio
n of ‘void (*)(struct acpi_device *)’ from incompatible pointer type ‘int (*)(stru
ct acpi_device *, int)’ [-Werror=incompatible-pointer-types]
   84 |         .remove = nv_acpi_remove_two_args,
      |                   ^~~~~~~~~~~~~~~~~~~~~~~

I don't know if there's a proper way to make it right, because there's many kernels and also many linux-headers. Holding linux-headers as dependency will force to install the main linux-headers even if a person only uses linux-headers-lts or linux-headers-zen.

I had to run pacman -S linux-headers so that I don't get any missing kernel headers errors.

Shouldn't linux-headers be added to the dependencies?

Any ideas?

Error! Bad return status for module build on kernel: 6.2.1-arch1-1 (x86_64) Consult /var/lib/dkms/nvidia/470.161.03/build/make.log for more information.

cat /var/lib/dkms/nvidia/470.161.03/build/make.log

warning: the compiler differs from the one used to build the kernel

The kernel was built by: gcc (GCC) 12.2.1 20230201 You are using: cc (GCC) 12.2.1 20230201

My Solution (for the moment)

• downgrade to Kernel 6.1.12-arch1-1

• install the driver via this git-repo: https://github.com/Frogging-Family/nvidia-all

Now i'm back on track :-)

@Menelkir seems i found problem. its my vfio setup broken in 6.* kernel. after remove vfio modules from mkinitcpio.conf, regenerate initram, and adjust xorg.conf(second gpu now visible to nvidia driver). tty console start work normal.

It seems the system is having issues to load the module. You can try loading by hand before Xorg starts (or using some other ways) or add to your initrd (which doesn't hurt but it'll increase your initrd size).