5.16 kernel breaks SDDM and Xorg


Since 5.16 kernal update, Neither sddm nor xorg would work at startup, Stuck on systemd. I restored from snapper and currently using with 5.15 kernal. I thought it must be fixed from future updates but still its here.

inxi info:

Kernel: 5.16.0-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
Desktop: KDE Plasma 5.23.5 Distro: Garuda Linux base: Arch Linux
Type: Desktop Mobo: Micro-Star model: MPG B550 GAMING PLUS (MS-7C56) v: 1.0
serial: <superuser required> UEFI: American Megatrends LLC. v: 1.70
date: 06/23/2021
Info: 12-core model: AMD Ryzen 9 3900X bits: 64 type: MT MCP arch: Zen 2
rev: 0 cache: L1: 768 KiB L2: 6 MiB L3: 64 MiB
Speed (MHz): avg: 2760 high: 4344 min/max: 2200/4672 boost: enabled
cores: 1: 4192 2: 2148 3: 4303 4: 4004 5: 2089 6: 2195 7: 2200 8: 2199
9: 2200 10: 2468 11: 2917 12: 2140 13: 4344 14: 2144 15: 4283 16: 2757
17: 2197 18: 2156 19: 2200 20: 2199 21: 2199 22: 4138 23: 2414 24: 2175
bogomips: 182399
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: Gigabyte
driver: nvidia v: 495.46 bus-ID: 2b:00.0
Display: x11 server: X.Org driver: loaded: nvidia
unloaded: modesetting resolution: 1: 1920x1080 2: 1920x1080~60Hz
OpenGL: renderer: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
v: 4.6.0 NVIDIA 495.46 direct render: Yes
Device-1: NVIDIA GP106 High Definition Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel bus-ID: 2b:00.1
Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus-ID: 2d:00.4
Device-3: JMTek LLC. USB PnP Audio Device type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-2.2:6
Sound Server-1: ALSA v: k5.16.0-zen1-1-zen running: yes
Sound Server-2: sndio v: N/A running: no
Sound Server-3: JACK v: 1.9.20 running: no
Sound Server-4: PulseAudio v: 15.0 running: no
Sound Server-5: PipeWire v: 0.3.43 running: yes
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI driver: r8169 v: kernel port: f000 bus-ID: 2a:00.0
IF: enp42s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB
driver: btusb v: 0.8 bus-ID: 1-2.1:4
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Local Storage: total: 1.59 TiB used: 1.05 TiB (66.1%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 500GB
size: 465.76 GiB temp: 39.9 C
ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 960 EVO 250GB
size: 232.89 GiB temp: 31.9 C
ID-3: /dev/sda vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB
ID-1: / size: 259.52 GiB used: 207.05 GiB (79.8%) fs: btrfs
dev: /dev/nvme0n1p2
ID-2: /boot/efi size: 349.3 MiB used: 596 KiB (0.2%) fs: vfat
dev: /dev/nvme0n1p3
ID-3: /home size: 259.52 GiB used: 207.05 GiB (79.8%) fs: btrfs
dev: /dev/nvme0n1p2
ID-4: /var/log size: 259.52 GiB used: 207.05 GiB (79.8%) fs: btrfs
dev: /dev/nvme0n1p2
ID-5: /var/tmp size: 259.52 GiB used: 207.05 GiB (79.8%) fs: btrfs
dev: /dev/nvme0n1p2
ID-1: swap-1 type: zram size: 15.61 GiB used: 6.15 GiB (39.4%)
dev: /dev/zram0
System Temperatures: cpu: N/A mobo: N/A gpu: nvidia temp: 49 C
Fan Speeds (RPM): cpu: 1883 fan-2: 0 fan-3: 0 fan-4: 0 fan-5: 500
fan-6: 472 fan-7: 0 fan-8: 1091 fan-9: 0 fan-10: 0 gpu: nvidia fan: 12%
Processes: 576 Uptime: 4h 41m Memory: 15.61 GiB used: 12.8 GiB (82.0%)
Init: systemd Compilers: gcc: 11.1.0 clang: 13.0.0 Packages: 1842
Shell: fish v: 3.3.1 inxi: 3.3.11

I've corrected the kernel numbering in your post, and made the title more explicit.

If you could use the output of paclog to provide a list of packages you update when SDDM breaks then it might be possible to identify the reason. The most likely reason is that you did not update the NVIDIA driver modules along with the kernel.

If you'd like a more generic troubleshooting page then read here: Computer doesn’t boot, boots to a black screen, or stops at a message.


I would also test alternate kernels such as:

1 Like

OP implies 5.15 is working OK, though I guess that doesn't mean they're using it from linux-lts (as you say more likely an old version of linux-zen that's still at 5.15.something).



Im using linux zen. Its in inxi info. But I see other people using new updates without issues. How can I resolve this?

Thanks! Im sorry about my wreckless article.

I checked the mentioned link and The issue lies in Xorg. It doesnt start in tty screen too. Gets stuck on No screen found.
I regenerated xorg conf and then xorg would start on only tty screen. No sddm yet, Also Desktop be lagging.

Installing kernels can be done in the terminal:

sudo pacman -Syu linux linux-headers


sudo pacman -Syu linux-mainline linux-mainline-headers


sudo pacman -Syu linux-lts linux-lts-headers

You switch kernels at the advanced grub menu when you reboot. Multiple kernels can be installed at the same time with Garuda.


So the DKMS module compiled correctly?

What about

I asked for previously?

What does this mean? When does it happen? How is this related to kernel 5.16?

1 Like

Yes DKMS modules seems to get compiled correctly, I cannot provide paclog atm since I have restored and need to update again to do that.

And I tried installing LTS kernel, Starting with that kernel produces the same issue.

You should really test the linux-mainline kernel as well.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.