Package Details: nvidia-390xx-dkms 390.157-13

Git Clone URL: https://aur.archlinux.org/nvidia-390xx-utils.git (read-only, click to copy)
Package Base: nvidia-390xx-utils
Description: NVIDIA drivers - module sources
Upstream URL: https://www.nvidia.com/
Licenses: custom
Provides: NVIDIA-MODULE
Submitter: svenstaro
Maintainer: jonathon (vnctdj)
Last Packager: vnctdj
Votes: 61
Popularity: 1.20
First Submitted: 2020-03-11 17:29 (UTC)
Last Updated: 2024-11-25 23:34 (UTC)

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.

Latest Comments

1 2 3 4 5 6 .. 28 Next › Last »

drankinatty commented on 2025-01-20 04:01 (UTC)

@vnctdj Will do. As soon as 6.13 is released, I'll let you know. I've already built and patched and 6.12.10 update went fine with the change from relative to absolute paths in the two Kbuild makefiles, so I don't expect any surprises when 6.13 is released. I still have to dig into why the change, but I suspect it is aimed at fixing some of the kms drm corner-cases that appeared after 6.12 removed the nvidia-drm from the kernel.

Note to all after the 6.12 drm changes I needed to add nvidia-drm.modeset=1 to my kernel command-line. Desktop was fine without it, but anything that relied on /sys/class/drm/card0... being present would fail as the links for card0, etc... were not created without it. (btop would fail to start, etc..)

vnctdj commented on 2025-01-19 22:57 (UTC)

@drankinatty Thanks for your early work! I've prepared the package update on my PC, I'll push the commit once you confirm the patch is working.

drankinatty commented on 2025-01-17 16:29 (UTC)

The changes for 6.13 simply effect the nvidia.Kbuild and nvidia-modesetting.Kbuild make files. It's just a change between using relative symlinks and absolute paths for them. (don't know why). The nvidia-470xx-fix-linux-6.13.patch patch from the 470 driver can be used directly. There is a max of a 2-line offset between the lines in the Kbuild files.

I did go ahead and create a Nvidia 390xx Linux 6.13 patch that corrects the 2-line offset and I've built with it under 6.12.9 which builds fine, but haven't testes on 6.13 yet. We will just have to wait for it to appear.

air-g4p commented on 2025-01-15 07:16 (UTC)

@drankinatty - thanks for the 6.13 heads up. Please let us know when you think the patch is ready - and I will help test it. Cheers

drankinatty commented on 2025-01-14 06:06 (UTC)

Linux 6.13 should be released next week and it does appear a patch will be required. The nvidia-470xx-fix-linux-6.13.patch (Joan Bruguera) can likely be adapted and I'll work through it this weekend.

sfranchi commented on 2024-12-22 19:40 (UTC)

After the latest kernel update and after a successful build of the latest version 390xx-dkms package, my external monitor is no longer properly recognized. It does show up, but only as a basic CGA in a 640-400 resolution, instead of being seen as the Dell 1900x1280 that it is. This had never happened to me before. Anyone has any insights?

duht commented on 2024-12-10 20:59 (UTC)

@Foxos thank you so much. Your method worked for me too. A strange thing: when I deleted /etc/X11/xorg.conf.d/10-nvidia-drm-outputclass.conf now, everything still works as it should. I don't know if its due to latest minor kernel update, but it seems this solution is no longer needed.

yayowd commented on 2024-12-05 11:13 (UTC)

@Foxos After configuring according to your method, when using the nvidia-drm.modeset=1 parameter, the xorg starts normally. Thank you very much.

Foxos commented on 2024-12-01 18:51 (UTC) (edited on 2024-12-01 18:56 (UTC) by Foxos)

@duht I faced same problem and fixed it by following steps at NVIDIA/Troubleshooting:

copy /usr/share/X11/xorg.conf.d/10-nvidia-drm-outputclass.conf to /etc/X11/xorg.conf.d/10-nvidia-drm-outputclass.conf, and then edit /etc/X11/xorg.conf.d/10-nvidia-drm-outputclass.conf and add the line Option "PrimaryGPU" "yes"

duht commented on 2024-11-29 13:00 (UTC) (edited on 2024-11-29 13:07 (UTC) by duht)

After upgrade startx fails with

(EE) NVIDIA(GPU-0): Failed to acquire modesetting permission.
(EE) NVIDIA(0): Failing initialization of X screen 0
(EE) Screen(s) found, but none have a usable configuration.
(EE) 
(EE) no screens found(EE)

I use nvidia-drm.modeset=1 parameter, deleting or regenerating via nvidia-xconfig xorg configuration file doesn't help. Downgrading to 6.11 solves problem.

Any ideas??

1 2 3 4 5 6 .. 28 Next › Last »