You are not logged in.
Hello Community,
I’m encountering a problem with Wayland since updating to Kernel 6.6.68-1-lts.
Previously, I always used the latest kernel, but after experiencing driver issues with NVIDIA on Kernel 6.12, I switched to the LTS kernel, which initially resolved the driver problems.
Now, after updating the kernel from 6.6.65 to 6.6.68, I can no longer select Wayland during login (Gnome). It used to work flawlessly. I generally don’t have an issue with X11, but I need different scaling on different monitors, which only Wayland natively supports.
I’ve scoured Google and worked through the wiki. Currently, I’m at a loss about what else I can do, and I’m hoping someone here can help.
journalctl indicates that Wayland couldn’t load due to “an unmet condition check,” but I can’t figure out what this unmet condition check is.
Jan 04 11:56:00 archbook systemd[2719]: GNOME Shell on Wayland was skipped because of an unmet condition check (ConditionEnvironment=XDG_SESSION_TYPE=wayland).
My full log file is available at:
http://0x0.st/8iNk.txt
My current kernel version:
uname -r
6.6.68-1-lts
Kernel parameters and hooks are set:
cat /proc/cmdline
initrd=\intel-ucode.img initrd=\initramfs-linux-lts.img cryptdevice=UUID=581c58bd-b727-475a-ab8e-1f86d64705c0:luks:allow-discards root=/dev/mapper/luks rootflags=subvol=@ rd.luks.options=discard resume=/dev/mapper/luks resume_offset=126009843 rw quiet splash nvidia_drm.modeset=1 nvidia_drm.fbdev=1 loglevel=3
cat /etc/mkinitcpio.conf
(...)
MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)
(...)
The NVIDIA-DRM kernel mode is also loaded:
sudo cat /sys/module/nvidia_drm/parameters/modeset
Y
Wayland is enabled in custom.conf:
cat /etc/gdm/custom.conf
## GDM configuration storage
[daemon]
# Uncomment the line below to force the login screen to use Xorg
WaylandEnable=True
The UDEV rule is redirected to /dev/null:
ls -la /etc/udev/rules.d/61-gdm.rules
lrwxrwxrwx 1 root root 9 6. Okt 2023 /etc/udev/rules.d/61-gdm.rules -> /dev/null
The following NVIDIA packages are installed:
pacman -Qs nvidia
local/cuda 12.6.3-1
NVIDIA's GPU programming toolkit
local/egl-gbm 1.1.2-1
The GBM EGL external platform library
local/egl-wayland 4:1.1.17-1
EGLStream-based Wayland external platform
local/egl-x11 1.0.0-1
NVIDIA XLib and XCB EGL Platform Library
local/envycontrol 3.5.1-1
CLI tool for Nvidia Optimus graphics mode switching on Linux
local/lib32-nvidia-utils 565.77-1
NVIDIA drivers utilities (32-bit)
local/libvdpau 1.5-3
Nvidia VDPAU library
local/libxnvctrl 565.57.01-1
NVIDIA NV-CONTROL X extension
local/nvidia-lts 1:565.77-8
NVIDIA drivers for linux-lts
local/nvidia-prime 1.0-5
NVIDIA Prime Render Offload configuration and utilities
local/nvidia-settings 565.57.01-1
Tool for configuring the NVIDIA graphics driver
local/nvidia-utils 565.77-3
NVIDIA drivers utilities
local/nvtop 3.1.0-1
GPUs process monitoring for AMD, Intel and NVIDIA
local/opencl-nvidia 565.77-3
OpenCL implemention for NVIDIA
Does anyone have any ideas, or should I consider downgrading the kernel?
Offline
Your nvidia-lts package is at the wrong version. If "updating kernel" was really just the kernel, then that's a partial upgrade, and not supported: https://wiki.archlinux.org/title/System … nsupported . Update your entire system make sure you get nvidia-lts 1:565.77-9
Offline
How can I determine in the future if the nvidia-lts package is in the "wrong version" or incompatible?
Admittedly, I not only updated linux-lts but also the NVIDIA drivers. It seems that is has been an partial upgrade.
After downgrading both the drivers and linux-lts, Wayland works again.
However, with pacman -Syu, both are offered as updates again
~ $ checkupdates
linux-lts 6.6.65-1 -> 6.6.69-1
linux-lts-headers 6.6.65-1 -> 6.6.69-1
nvidia-lts 1:565.57.01-6 -> 1:565.77-9
nvidia-utils 565.57.01-2 -> 565.77-3
Offline
"They're not both the last available ones", but you can check whether "pacman -Ql nvidia-lts | grep modules", "pacman -Q linux-lts" and "uname -r" indicate the exact same version.
Offline