Arch Linux

benm

Member

Registered: 2021-03-28

Posts: 85

Update broke Plasma Wayland Session

I am using KDE Plasma with the Wayland session, nvidia drivers.
After performing this update, I can get to the login screen of sddm. If I login as the Wayland session, I get a black screen and the only way out is to reboot. If I login as the X11 session, I get the splash screen and boot as normally.

/var/log/pacman.log

[2024-10-01T10:10:46-0400] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --'
[2024-10-01T10:10:46-0400] [PACMAN] synchronizing package lists
[2024-10-01T10:10:49-0400] [PACMAN] Running 'pacman -S -y -u --config /etc/pacman.conf --'
[2024-10-01T10:10:49-0400] [PACMAN] synchronizing package lists
[2024-10-01T10:10:49-0400] [PACMAN] starting full system upgrade
[2024-10-01T10:11:06-0400] [ALPM] running '60-mkinitcpio-remove.hook'...
[2024-10-01T10:11:06-0400] [ALPM] running '71-dkms-remove.hook'...
[2024-10-01T10:11:07-0400] [ALPM-SCRIPTLET] ==> dkms remove --no-depmod binder/1 -k 6.10.10-arch1-1
[2024-10-01T10:11:07-0400] [ALPM-SCRIPTLET] ==> depmod 6.10.10-arch1-1
[2024-10-01T10:11:08-0400] [ALPM] transaction started
[2024-10-01T10:11:08-0400] [ALPM] upgraded borg (1.4.0-1 -> 1.4.0-2)
[2024-10-01T10:11:08-0400] [ALPM] upgraded borgmatic (1.8.14-1 -> 1.8.14-2)
[2024-10-01T10:11:09-0400] [ALPM] upgraded nvidia-utils (560.35.03-3 -> 560.35.03-4)
[2024-10-01T10:11:09-0400] [ALPM-SCRIPTLET] If you run into trouble with CUDA not being available, run nvidia-modprobe first.
[2024-10-01T10:11:09-0400] [ALPM-SCRIPTLET] If you use GDM on Wayland, you might have to run systemctl enable --now nvidia-resume.service
[2024-10-01T10:11:09-0400] [ALPM] upgraded firefox (130.0.1-2 -> 131.0-1)
[2024-10-01T10:11:09-0400] [ALPM] upgraded gdb-common (15.1-1 -> 15.2-1)
[2024-10-01T10:11:09-0400] [ALPM] upgraded gdb (15.1-1 -> 15.2-1)
[2024-10-01T10:11:09-0400] [ALPM] upgraded libindi (2.0.9-2 -> 2.1.0-1)
[2024-10-01T10:11:10-0400] [ALPM] upgraded linux (6.10.10.arch1-1 -> 6.11.1.arch1-1)
[2024-10-01T10:11:11-0400] [ALPM] upgraded linux-headers (6.10.10.arch1-1 -> 6.11.1.arch1-1)
[2024-10-01T10:11:11-0400] [ALPM] upgraded nvidia (560.35.03-6 -> 560.35.03-9)
[2024-10-01T10:11:12-0400] [ALPM] upgraded qt6-base (6.7.3-1 -> 6.7.3-2)
[2024-10-01T10:11:12-0400] [ALPM] upgraded tree-sitter (0.23.0-1 -> 0.23.1-1)
[2024-10-01T10:11:12-0400] [ALPM] upgraded virtualbox-host-modules-arch (7.1.2-1 -> 7.1.2-3)
[2024-10-01T10:11:12-0400] [ALPM] transaction completed
[2024-10-01T10:11:12-0400] [ALPM] running '20-systemd-sysusers.hook'...
[2024-10-01T10:11:12-0400] [ALPM] running '30-systemd-daemon-reload-system.hook'...
[2024-10-01T10:11:12-0400] [ALPM] running '30-systemd-daemon-reload-user.hook'...
[2024-10-01T10:11:13-0400] [ALPM] running '30-systemd-udev-reload.hook'...
[2024-10-01T10:11:14-0400] [ALPM] running '30-systemd-update.hook'...
[2024-10-01T10:11:14-0400] [ALPM] running '60-depmod.hook'...
[2024-10-01T10:11:15-0400] [ALPM] running '70-dkms-install.hook'...
[2024-10-01T10:11:15-0400] [ALPM-SCRIPTLET] ==> dkms install --no-depmod binder/1 -k 6.11.1-arch1-1
[2024-10-01T10:11:17-0400] [ALPM-SCRIPTLET] ==> depmod 6.11.1-arch1-1
[2024-10-01T10:11:18-0400] [ALPM] running '90-mkinitcpio-install.hook'...
[2024-10-01T10:11:18-0400] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2024-10-01T10:11:18-0400] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2024-10-01T10:11:18-0400] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img
[2024-10-01T10:11:18-0400] [ALPM-SCRIPTLET] ==> Starting build: '6.11.1-arch1-1'
[2024-10-01T10:11:18-0400] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2024-10-01T10:11:19-0400] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2024-10-01T10:11:19-0400] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2024-10-01T10:11:19-0400] [ALPM-SCRIPTLET]   -> Running build hook: [microcode]
[2024-10-01T10:11:19-0400] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2024-10-01T10:11:19-0400] [ALPM-SCRIPTLET]   -> Running build hook: [kms]
[2024-10-01T10:11:22-0400] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2024-10-01T10:11:22-0400] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'xhci_pci'
[2024-10-01T10:11:22-0400] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2024-10-01T10:11:22-0400] [ALPM-SCRIPTLET]   -> Running build hook: [consolefont]
[2024-10-01T10:11:22-0400] [ALPM-SCRIPTLET] ==> WARNING: consolefont: no font found in configuration
[2024-10-01T10:11:22-0400] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2024-10-01T10:11:22-0400] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2024-10-01T10:11:23-0400] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2024-10-01T10:11:23-0400] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2024-10-01T10:11:23-0400] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
[2024-10-01T10:11:23-0400] [ALPM-SCRIPTLET]   -> Early uncompressed CPIO image generation successful
[2024-10-01T10:11:23-0400] [ALPM-SCRIPTLET] ==> Initcpio image generation successful
[2024-10-01T10:11:23-0400] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2024-10-01T10:11:23-0400] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2024-10-01T10:11:23-0400] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect
[2024-10-01T10:11:23-0400] [ALPM-SCRIPTLET] ==> Starting build: '6.11.1-arch1-1'
[2024-10-01T10:11:23-0400] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2024-10-01T10:11:23-0400] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2024-10-01T10:11:23-0400] [ALPM-SCRIPTLET]   -> Running build hook: [microcode]
[2024-10-01T10:11:23-0400] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2024-10-01T10:11:23-0400] [ALPM-SCRIPTLET]   -> Running build hook: [kms]
[2024-10-01T10:11:27-0400] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'ast'
[2024-10-01T10:11:27-0400] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2024-10-01T10:11:27-0400] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'xhci_pci'
[2024-10-01T10:11:28-0400] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2024-10-01T10:11:28-0400] [ALPM-SCRIPTLET]   -> Running build hook: [consolefont]
[2024-10-01T10:11:28-0400] [ALPM-SCRIPTLET] ==> WARNING: consolefont: no font found in configuration
[2024-10-01T10:11:28-0400] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2024-10-01T10:11:28-0400] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qla1280'
[2024-10-01T10:11:28-0400] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qla2xxx'
[2024-10-01T10:11:28-0400] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'bfa'
[2024-10-01T10:11:28-0400] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'wd719x'
[2024-10-01T10:11:28-0400] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qed'
[2024-10-01T10:11:28-0400] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'aic94xx'
[2024-10-01T10:11:30-0400] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2024-10-01T10:11:30-0400] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2024-10-01T10:11:31-0400] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2024-10-01T10:11:31-0400] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
[2024-10-01T10:11:32-0400] [ALPM-SCRIPTLET]   -> Early uncompressed CPIO image generation successful
[2024-10-01T10:11:32-0400] [ALPM-SCRIPTLET] ==> Initcpio image generation successful
[2024-10-01T10:11:32-0400] [ALPM] running 'dbus-reload.hook'...
[2024-10-01T10:11:32-0400] [ALPM] running 'gtk-update-icon-cache.hook'...
[2024-10-01T10:11:32-0400] [ALPM] running 'nvidia-ctk-cdi.hook'...
[2024-10-01T10:11:33-0400] [ALPM] running 'texinfo-install.hook'...
[2024-10-01T10:11:33-0400] [ALPM] running 'update-desktop-database.hook'...
[2024-10-01T10:19:59-0400] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --'
[2024-10-01T10:19:59-0400] [PACMAN] synchronizing package lists

Journald:
https://0x0.st/Xgw3.txt

gromit

Package Maintainer (PM)

From: Germany

Registered: 2024-02-10

Posts: 520

Website

Re: Update broke Plasma Wayland Session

Does it work again after you downgrade linux and nvidia?

benm

Member

Registered: 2021-03-28

Posts: 85

Re: Update broke Plasma Wayland Session

I have not attempted. Is that necessary to try?

roguestew

Member

Registered: 2024-10-01

Posts: 2

Re: Update broke Plasma Wayland Session

I have not attempted. Is that necessary to try?

If you want to help get to the bottom of the problem, yes.

I had the same issue and things are back to normal after downgrading the kernel and Nvidia version. Downgrading the Nvidia version alone did not fix the issue.

benm

Member

Registered: 2021-03-28

Posts: 85

Re: Update broke Plasma Wayland Session

I was able to boot again to the Wayland session by downgrading to one version earlier:
linux-6.11.1.arch1-1  linux-headers-6.11.1.arch1-1  nvidia-560.35.03-9  nvidia-utils-560.35.03-4  virtualbox-host-modules-arch-7.1.2-3

ptr1337

Member

Registered: 2024-09-24

Posts: 5

Re: Update broke Plasma Wayland Session

Can you try to pass  `nvidia_drm.modeset=1` and `nvidia_drm.fbdev=1` to the Kernel Parameters?

(Please do not pass it to the module parameters, otherwise the patch from the "linux" kernel does not work https://github.com/archlinux/linux/comm … 78a9411924

Last edited by ptr1337 (2024-10-01 19:45:44)

roguestew

Member

Registered: 2024-10-01

Posts: 2

Re: Update broke Plasma Wayland Session

I tried adding both of those parameters to no avail before I rolled the version back.

Adding KWIN_DRM_NO_AMS=1 to /etc/environment did allow me to reach my desktop but introduced a lot of jitter/stutter

ptr1337

Member

Registered: 2024-09-24

Posts: 5

Re: Update broke Plasma Wayland Session

Could you give the output of cat /proc/cmdline ?

Last edited by ptr1337 (2024-10-01 19:35:34)

ptr1337

Member

Registered: 2024-09-24

Posts: 5

Re: Update broke Plasma Wayland Session

I see the issue. On the kernel side following workaround was not applied, which could maybe introduce the issue: https://github.com/archlinux/linux/comm … 78a9411924

If you get the blackscreen with the "_" you can workaround it with:

CTRL + ALT + F3 and then go back with CTRL + ALT + F2 or F1

ptr1337

Member

Registered: 2024-09-24

Posts: 5

Re: Update broke Plasma Wayland Session

Please try following, this should fix the issue, with above patch pulled in:

sudo pacman -U https://pkgbuild.com/~ptr1337/kernel-testing/simplefb-skip/linux-6.11.1.arch1-2-x86_64.pkg.tar.zst https://pkgbuild.com/~ptr1337/kernel-testing/simplefb-skip/linux-headers-6.11.1.arch1-2-x86_64.pkg.tar.zst

Please also use then the "nvidia-dkms" package.

Last edited by ptr1337 (2024-10-01 20:14:10)

benm

Member

Registered: 2021-03-28

Posts: 85

Re: Update broke Plasma Wayland Session

Looks like there is a parallel thread describing the same issue: https://bbs.archlinux.org/viewtopic.php?id=299868

fettouhi

Member

Registered: 2007-05-07

Posts: 753

Re: Update broke Plasma Wayland Session

Can you try to pass  `nvidia_drm.modeset=1` and `nvidia_drm.fbdev=1` to the Kernel Parameters?

(Please do not pass it to the module parameters, otherwise the patch from the "linux" kernel does not work https://github.com/archlinux/linux/comm … 78a9411924

I am a bit confused by these kernel parameter. I some places I read people that one should pass `nvidia-drm.modeset=1` and `nvidia-drm.fbdev=1` and then I read here what you recommend. What is the correct way `nvidia-drm` or `nvidia_drm`?

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 22,862

Re: Update broke Plasma Wayland Session

Both work, it doesn't matter whether you use hyphens or underscores

fettouhi

Member

Registered: 2007-05-07

Posts: 753

Re: Update broke Plasma Wayland Session

Both work, it doesn't matter whether you use hyphens or underscores

OK thanks for the clarification.

Torom

Member

Registered: 2024-10-03

Posts: 1

Re: Update broke Plasma Wayland Session

I ran into the same problem after updating.

I can confirm that setting `nvidia_drm.fbdev=1` in addition to the already set `nvidia_drm.modeset=1` fixed the problem.

benm

Member

Registered: 2021-03-28

Posts: 85

Re: Update broke Plasma Wayland Session

Is this something that needs to be done from here on out (edit arch wiki) or is this a bug report?

iq2luc

Member

Registered: 2012-11-19

Posts: 15

Re: Update broke Plasma Wayland Session

I ran into the same problem after updating.

I can confirm that setting `nvidia_drm.fbdev=1` in addition to the already set `nvidia_drm.modeset=1` fixed the problem.

With fbdev=1 I loose the Linux console. Does the console still works for you?

Thank you,
L.

fettouhi

Member

Registered: 2007-05-07

Posts: 753

Re: Update broke Plasma Wayland Session

I ran into the same problem after updating.

I can confirm that setting `nvidia_drm.fbdev=1` in addition to the already set `nvidia_drm.modeset=1` fixed the problem.

With fbdev=1 I loose the Linux console. Does the console still works for you?

Thank you,
L.

Same here. Lost the console as well. I added fbdev and modeset in the grub file. Is there a way to get it back?

benm

Member

Registered: 2021-03-28

Posts: 85

Re: Update broke Plasma Wayland Session

I added nvidia_drm.fbdev=1 to my grub config in /etc/default/grub and it fixed the problem. Just to confirm, did you remember to run `sudo grub-mkconfig -o /boot/grub/grub.cfg` after editing?

fettouhi

Member

Registered: 2007-05-07

Posts: 753

Re: Update broke Plasma Wayland Session

I added nvidia_drm.fbdev=1 to my grub config in /etc/default/grub and it fixed the problem. Just to confirm, did you remember to run `sudo grub-mkconfig -o /boot/grub/grub.cfg` after editing?

Yes, I did.

iq2luc

Member

Registered: 2012-11-19

Posts: 15

Re: Update broke Plasma Wayland Session

Same here. Lost the console as well. I added fbdev and modeset in the grub file. Is there a way to get it back?

I got back the console by removing fbdev (I was using modeset already).

For the moment I'm using X instead of Wayland.

zebulon

Member

Registered: 2008-10-20

Posts: 368

Re: Update broke Plasma Wayland Session

For me the nvidia-dkms 560.35.03-5 package update fixed the Wayland + Plasma problem.

Absolosba

Member

Registered: 2011-05-09

Posts: 3

Re: Update broke Plasma Wayland Session

I managed to get Wayland running with console by setting nvidia_drm.fbdev=0 in the kernel parameters and copying this file into /lib/udev/rules.d/
https://github.com/canonical/ubuntu-dri … tion.rules

iq2luc

Member

Registered: 2012-11-19

Posts: 15

Re: Update broke Plasma Wayland Session

I managed to get Wayland running with console by setting nvidia_drm.fbdev=0 in the kernel parameters and copying this file into /lib/udev/rules.d/
https://github.com/canonical/ubuntu-dri … tion.rules

Thank you so much.
This is the only solution that works for me for the moment.

---

linux 6.11.2.arch1-1
nvidia-dkms 560.35.03-5
wayland 1.23.1-1
kwin 6.1.5-2
plasma-desktop 6.1.5-1

+

nvidia_drm kernel module parameters: fbdev=0 (defaults to modeset=1 and fbdev=1, so I only had to change fbdev to 0)
/sys/module/nvidia_drm/parameters/modeset = Y
/sys/module/nvidia_drm/parameters/fbdev = N

=>

KDE + Wayland + Linux console works

- - -

Thank you again.