Package Base Details: nvidia-340xx

Git Clone URL: https://aur.archlinux.org/nvidia-340xx.git (read-only, click to copy)
Submitter: simonsmh
Maintainer: JerryXiao (graysky)
Last Packager: JerryXiao
Votes: 50
Popularity: 1.26
First Submitted: 2019-06-07 10:29
Last Updated: 2021-06-06 02:31

Pinned Comments

graysky commented on 2021-05-10 15:03

OK, I honestly forgot that I included an example config file. Since I don't have the hardware for testing, and since I still don't have a sense from users that it is a requirement, I will leave it in the post_install and depend on the user's ability to read pacman's output and manually copy the example over.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 ... Next › Last »

tioguda commented on 2021-05-24 20:42

Thank @NSLW, finally i managed to start my Manjaro Plasma (kernel 5.12.5) after your information.

Greetings.

NSLW commented on 2021-05-24 19:11

I improved the patch to work with sddm again and made it available at https://github.com/rpmfusion/nvidia-340xx-kmod/pull/3

NSLW commented on 2021-05-23 17:03

On 5.11 there is no "kernel: [drm] Initialized nvidia-drm 0.0.0 20150116 for 0000:01:00.0 on minor 0" (drm_drv.c file in kernel) in journalctl, so no "/dev/dri/card0" is created.

udev from systemd doesn't see "/dev/dri/card0", so it returns false for the following command "qdbus --system org.freedesktop.login1 /org/freedesktop/login1/seat/seat0 org.freedesktop.DBus.Properties.Get org.freedesktop.login1.Seat CanGraphical"

sddm disables the greeter because it receives "false" from the above command. Hardcoding it to "true" shows the greeter.

I have already tried to modify "nv-drm.c", but the kernel doesn't even visit that file. Would it be possible to initialize nvidia-drm somehow?

Filkolev commented on 2021-05-17 20:12

Back when 5.11 came out I was unable to make it work after a bit of fiddling and I downgraded back to 5.10. Now I decided I would look into it more closely and it turned out I had to do 2 things to fix it:

  1. After putting 20-nvidia.conf in the xorg config directory, I also had to delete the (empty) Files section from /etc/X11/xorg.conf.
  2. I had to set IGNORE_CC_MISMATCH=1 in /etc/profile. The first time I actually ran sudo -E dkms install ...

M4rty commented on 2021-05-17 15:02

@auriculaire Thanks, it works !

auriculaire commented on 2021-05-17 13:54

M4rty@ Same observation.: ==> Warning, dkms install --no-depmod -m nvidia -v 340.108 -k 5.12.4-arch1-2' returned 10 ==> Warning,dkms install --no-depmod -m nvidia -v 340.108 -k 5.10.37-1-lts' returned 10


You just have to reinstall the module nvidia-340xx-dkms 340.108-19, by ssh for example.

M4rty commented on 2021-05-17 13:07

Hi ! The driver don't work for me with 5.10.37-1-lts (arch, lightdm). It works perfect with 5.10.36

holyArch commented on 2021-05-16 10:28

340.108-19 seems to be working fine with 5.12.3.arch1-1 (e.g. VDPAU works).

I didn't have to change anything in /etc/X11/xorg.conf.d/20-nvidia.conf (I have no /etc/X11/xorg.conf).

Section "Files"
    ModulePath "/usr/lib/nvidia/xorg,/usr/lib/xorg/modules"
EndSection

also works in 20-nvidia.conf.

johnstef commented on 2021-05-14 22:16

PROBLEM SOLVED The thing is that it was working perfectly on 5.11 and broke on 5.12 so my xorg.conf couldn't be the reason. The problem is that I ran nvidia-xconfig which ruined my xorg.conf that I had created back when I updated to 5.11.

The 20-nvidia.conf is not working, all I had to do is to use this minimal config or just add this

Section "Files"
  ModulePath   "/usr/lib64/nvidia/xorg"
  ModulePath   "/usr/lib64/xorg/modules"
EndSection

at the top of xorg.conf. So I can confirm that it's working perfectly on kernel 5.12

jayache80 commented on 2021-05-14 20:50

@johnstef 5.11 would have the same issues as 5.12. If you want to go back to an old kernel, go to 5.10 using linux-lts and point your bootloader at that kernel. However, I'll bet you just have a bad X11 config like I did.

I can't tell- are you using Wayland and getting these errors via an Xwayland session? Or just regular X11? I only ask because it seems Wayland and nvidia will never get along.

I had essentially identical errors as you, and I was able to fix it by correcting a bad xorg.conf configuration. The nvidia ModulePath needs to be above the default xorg one. Something like:

Section "Files"
  ModulePath   "/usr/lib64/nvidia/xorg"
  ModulePath   "/usr/lib64/xorg/modules"
EndSection

I can't say for sure whether or not you should accomplish this by directly modifying /etc/X11/xorg.conf (like I do) or by placing an "overlay" config file (like the /usr/share/nvidia-340xx/20-nvidia.conf provided in this package) into the /etc/X11/xorg.conf.d directory. It depends on your existing configuration and how any existing ModulePath entries may be stepping on each other.

The goal is for X11 to have nvidia-specific hardware acceleration libraries (libEGL, libGL, etc.) available at runtime otherwise you'll get those errors.

(It is probably an upstream bug that allows a double free to occur when a library is missing instead of gracefully failing, but I digress).