Can't login to wayland (Nvidia KDE)

Hi I'm been trying to take a look into wayland, installed plasma-wayland-session and I have the option to choose wayland on the login screen, but when I type the password and enter, it justs loop back to the login screen. No problem to access Xorg.

I know wayland is not the best option right now with an Nvidia card, but I-d been using it on other computer with Nvidia and wanted to give it a go on my main system with Garuda, is it possible to log in?

Here is my garuda-inxi, I'm using bore right now, but tried on LTS kernel too. Can post a journalctl if that's relevant.

Kernel: 5.19.12-1-bore arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-bore
root=UUID=99d14c88-b1e3-48f2-8bb8-be8ca898c637 rw [email protected]
quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
Desktop: KDE Plasma v: 5.25.5 tk: Qt v: 5.15.6 info: latte-dock
wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Type: Desktop System: Gigabyte product: Z390 AORUS ULTRA v: N/A
serial: <superuser required>
Mobo: Gigabyte model: Z390 AORUS ULTRA-CF v: x.x
serial: <superuser required> UEFI: American Megatrends v: F10h
date: 01/19/2021
ID-1: hidpp_battery_0 charge: 57% condition: N/A volts: 3.8 min: N/A
model: Logitech G Pro Wireless Gaming Mouse type: N/A serial: <filter>
status: discharging
Info: model: Intel Core i9-9900K bits: 64 type: MT MCP arch: Coffee Lake
gen: core 9 level: v3 note: check built: 2018 process: Intel 14nm family: 6
model-id: 0x9E (158) stepping: 0xC (12) microcode: 0xF0
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 2 MiB desc: 8x256 KiB
L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 5000 min/max: 800/5000 scaling: driver: intel_pstate
governor: performance cores: 1: 5000 2: 5000 3: 5000 4: 5000 5: 5000
6: 5000 7: 5000 8: 5000 9: 5000 10: 5000 11: 5000 12: 5000 13: 5000
14: 5000 15: 5000 16: 5000 bogomips: 115312
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf status: Not affected
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown status: Not affected
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: retbleed mitigation: IBRS
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
Type: spectre_v2 mitigation: IBRS, IBPB: conditional, RSB filling,
PBRSB-eIBRS: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort mitigation: TSX disabled
Device-1: NVIDIA TU102 [GeForce RTX 2080 Ti Rev. A] vendor: ZOTAC
driver: nvidia v: 515.76 alternate: nouveau non-free: 515.xx+ status: current
(as of 2022-10) arch: Turing code: TUxxx process: TSMC 12nm
built: 2018-22 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.0
chip-ID: 10de:1e07 class-ID: 0300
Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.3
compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia display-ID: :0
screens: 1
Screen-1: 0 s-res: 5120x2880 s-dpi: 80 s-size: 1624x914mm (63.94x35.98")
s-diag: 1864mm (73.37")
Monitor-1: DP-2 pos: primary,bottom-l res: 5120x1440 hz: 120 dpi: 130048
size: 1x1mm (0.04x0.04") diag: 1mm (0.06") modes: N/A
Monitor-2: DP-4 pos: top-right res: 3440x1440 dpi: 109
size: 800x330mm (31.5x12.99") diag: 865mm (34.07") modes: N/A
OpenGL: renderer: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA
515.76 direct render: Yes
Device-1: Intel Cannon Lake PCH cAVS vendor: Gigabyte driver: snd_hda_intel
bus-ID: 1-11.4:7 v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl
chip-ID: b58e:9e84 class-ID: 0300 bus-ID: 00:1f.3 serial: <filter>
chip-ID: 8086:a348 class-ID: 0403
Device-2: NVIDIA TU102 High Definition Audio vendor: ZOTAC
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:10f7 class-ID: 0403
Device-3: C-Media CMI8788 [Oxygen HD Audio] vendor: ASUSTeK Virtuoso 100
driver: snd_virtuoso v: kernel bus-ID: 05:04.0 chip-ID: 13f6:8788
class-ID: 0401
Device-4: Blue Microphones Yeti Stereo Microphone type: USB
driver: hid-generic,snd-usb-audio,usbhid
Sound API: ALSA v: k5.19.12-1-bore running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.59 running: yes
Device-1: Intel Cannon Lake PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:a370 class-ID: 0280
IF: wlo1 state: down mac: <filter>
Device-2: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15bc class-ID: 0200
IF: eno2 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) type: USB
driver: btusb v: 0.8 bus-ID: 1-14:9 chip-ID: 8087:0aaa class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 1 state: down
bt-service: enabled,running rfk-block: hardware: no software: no
address: <filter>
Local Storage: total: 6.77 TiB used: 4.89 TiB (72.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Corsair model: Force MP510
size: 894.25 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: ECFM12.1
temp: 44.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:3 vendor: Crucial model: CT1000P1SSD8
size: 931.51 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: P3CR013
temp: 60.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: SanDisk model: SSD PLUS 480GB
size: 447.13 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 00RL scheme: MBR
ID-4: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD20EARX-00PASB0 size: 1.82 TiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s type: N/A serial: <filter> rev: AB51
scheme: MBR
ID-5: /dev/sdc maj-min: 8:32 vendor: Toshiba model: DT01ACA300
size: 2.73 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
type: HDD rpm: 7200 serial: <filter> rev: ABB0 scheme: GPT
ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 772.06 GiB
(82.9%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:5
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 592 KiB
(0.2%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:4
ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 772.06
GiB (82.9%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:5
ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 772.06
GiB (82.9%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:5
ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 772.06
GiB (82.9%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:5
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.29 GiB used: 516 MiB (1.6%)
priority: 100 dev: /dev/zram0
System Temperatures: cpu: 61.0 C pch: 51.0 C mobo: N/A gpu: nvidia
temp: 51 C
Fan Speeds (RPM): fan-2: 1514 fan-3: 1485 fan-4: 1503 gpu: nvidia
fan: 43%
Processes: 406 Uptime: 5m wakeups: 3 Memory: 31.29 GiB used: 6.68 GiB
(21.4%) Init: systemd v: 251 default: graphical tool: systemctl
Compilers: gcc: 12.2.0 clang: 14.0.6 Packages: 2046 pm: pacman pkgs: 2041
libs: 541 tools: octopi,pamac,paru pm: flatpak pkgs: 5 Shell: fish v: 3.5.1
default: Bash v: 5.1.16 running-in: yakuake inxi: 3.3.22
Garuda (2.6.8-1):
System install date:     2022-08-07
Last full system update: 2022-10-12
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       Probably (Run as root to verify)
Snapshots:               Snapper
Failed units:

Add nvidia-drm.modeset=1 to your kernel parameters.


Thanks for the help, these are my kernel parameters now, I added your suggestion, still same problem

quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3 ibt=off # Modified by garuda-migrations: ibt=off mitigations=off usbcore.autosuspend=-1 btusb.enable_autosuspend=0 nvidia-drm.modeset=1

Anything after "#" is ignored. You should add the parameter before "#". The first part of garuda-inxi shows your current parameters, you can use that to check if you managed to add that parameter.


That was the problem, now I'm answering from wayland desktop. Thanks a lot for your time and help.

1 Like

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