Arch Linux User Repository

For testing users, contributors: check out https://github.com/archlinux-jerry/nvidia-340xx
Warning: force push may happen to match the aur tree

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 ...

@auriculaire Thanks, it works !

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.

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

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.

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

@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).

I installed kernel 5.12 and I get the message that EGL could not be initialized on mpv and other apps.

[vo/gpu] Probing for best GPU context.
[vo/gpu/opengl] Initializing GPU context 'wayland'
[vo/gpu/opengl] Initializing GPU context 'x11egl'
[vo/gpu/x11] X11 opening display: :0
[vo/gpu/x11] Display 0 (HDMI-0): [0, 0, 1920, 1080] @ 60.000000 FPS
[vo/gpu/x11] Current display FPS: 60.000000
[vo/gpu/opengl] Could not initialize EGL.
free(): double free detected in tcache 2

I tried downgrading back to 5.11 but that error still exist! Do I have to do anything special to go back to the old kernel?

It works perfect, I had kernel 5.11 with driver 340.108-18 I did not have to modify anything.