Arch Linux User Repository

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?

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.

The same issue. Downgrade to glibc-2.36-7 solve the problem with startx X server

Let's just say things look very grim. https://bbs.archlinux.org/viewtopic.php?pid=2083569

I think it's not a kernel, glibc update 2.36-7 => 2.37-2 cause errors in my case. I revert it and problem with X server go away.

upd: my kernel package linux-zen 6.1.9.zen1-2

@drankinatty I found the same issue here after the (default and lts) kernel update today.

This is odd. After update linux (6.1.9.arch1-1 -> 6.1.9.arch1-2) on 2/7, I can no longer connect to the X-server. This seems kernel/driver related as Intel graphics has no issue. startx fails. (could not connect to X server) No problem with prior kernel 6.1.9.arch1-1. Now X will not start on the normal kernel or LTS. Anybody else see anything similar? Exact startx error is "xinit: unable to connect to X server: Connection refused" (permission, dbus, pam ??) Xorg.0.log is quite happy as the nvidia module is found and loaded without any problem and X does appear to be fully starting before the "Connection Refused" error.

With linux 6.1.8.arch1-1 and linux-lts 5.15.90-1 installed pacman throws:

$ pacman -U nvidia-390xx-utils-390.157-1-x86_64.pkg.tar.xz
...
(2/3) Install DKMS modules
==> dkms install --no-depmod nvidia/390.157 -k 6.1.8-arch1-1
==> dkms install --no-depmod nvidia/390.157 -k 5.15.90-1-lts
==> depmod 6.1.8-arch1-1
==> depmod 5.15.90-1-lts
==> ERROR: Missing 4.15.5-1-ARCH kernel headers for module nvidia/390.157.

mkinitcpio builds successfully though.

I'm not sure if this is the right place to report issue with the driver, but since I updated my system in November 2022 my system segfaults every time I run windows manager. I was getting some help here: https://bbs.archlinux.org/viewtopic.php?id=281047 and here: https://bbs.archlinux.org/viewtopic.php?id=282801 (these two are the same thread, I thought the issue was solved after falling back to LTS kernel, but it did not help).

@bpetlert I cannot bring back brightness even using those kernel parameters. Don't know why acpi_backlight=video doesn't make /sys/class/backlight/acpi_video0 path.

@FiestaLake Yes, I have backlight problem too.

Kernel parameter acpi_backlight=vendor and recent kernel make /sys/class/backlight directory empty. Changing it to acpi_backlight=video solved problem for me. Another machine, I need to remove acpi_backlight parameter to fix this issue.

Is there anyone having problems with brightness with recent kernel?