Implemented the above fix and am now back on Wayland but it kind of feels strange. Came back to this post, checked all the settings and also noticed the gdm.rules had changed a lot as mentioned. So after the stable update, I noticed I was back on X11. Congratulations, you should now be running GNOME with Wayland despite proprietary NVIDIA drivers! Add the kernel parameter nvidia-drm.modeset=1 to /etc/default/grub and run the command sudo update-grubĮnsure xorg-xwayland, libxcb and egl-wayland are installed: sudo pacman -Syu -needed xorg-xwayland libxcb egl-wayland.Add the modules nvidia, nvidia_modeset, nvidia_uvm and nvidia_drm to /etc/nf and run the command sudo mkinitcpio -P.Follow the instructions in the Arch wiki: This can be done with the following command: gsettings set experimental-features ''ĭE(Desktop Environment)-agnostic instructions begin hereĮnable modesetting for nvdia drivers. Kms-modifiers must be enabled through gsettings. To force-enable Wayland, disable the udev rule responsible for disabling Wayland in GDM: sudo ln -s /dev/null /etc/udev/rules.d/les # Uncomment the line below to turn on debugging
# Uncomment the line below to force the login screen to use Xorg
The correct file will then look something like this: # GDM configuration storage If not using GNOME, skip to DE (Desktop Environment)-agnostic instructions in Step 4 :Įdit the /etc/gdm/nf file and comment out the line WaylandEnable=false. However, if this does not deter you, you can use Wayland with NVIDIA drivers. This is why GNOME automatically disables Wayland if you have NVIDIA. This includes most games, which are the most common use case for proprietary NVIDIA drivers. Currently the biggest issue is that NVIDIA does currently not support Xwayland properly, so apps that require it get software rendering. Wayland does not play well with proprietary drivers.
0 kommentar(er)
