You are not logged in.

#1 2023-12-22 23:16:40

Rays42
Member
Registered: 2022-08-14
Posts: 8

SDDM: Failed to read display number from pipe

I'm running Arch Linux with KDE Plasma Wayland on a Desktop with three GPUs:
Ryzen 7000 iGPU -> disabled through BIOS, but I experimented with it on and off and preferably I would like it on for hardware decoding, but let's ignore that for now.
RTX4090 -> "disabled" with vfio. However my BIOS appears to initialize it as the primary GPU, so systemd-boot shows some stuff on its outputs first. This appears to be due to it being in the first PCIe slot and I can't reconfigure it nor do I want to swap the GPUs since only that first one has x16 bandwidth
RX550 dedicated GPU -> DisplayPort connection to my Monitor.

sddm doesn't load anymore, I've been swapping my GPUs around in various ways. It worked when I was using the iGPU only with the disabled RTX4090. Plasma works perfectly when started manually using startplasma-wayland.

journalctl -u sddm
Dec 07 20:07:44 shogun systemd[1]: Started Simple Desktop Display Manager.
Dec 07 20:07:44 shogun sddm[3864]: Initializing...
Dec 07 20:07:44 shogun sddm[3864]: Starting...
Dec 07 20:07:44 shogun sddm[3864]: Logind interface found
Dec 07 20:07:44 shogun sddm[3864]: Adding new display...
Dec 07 20:07:44 shogun sddm[3864]: Loaded empty theme configuration
Dec 07 20:07:44 shogun sddm[3864]: Xauthority path: "/run/sddm/xauth_JCpUsS"
Dec 07 20:07:44 shogun sddm[3864]: Using VT 2
Dec 07 20:07:44 shogun sddm[3864]: Display server starting...
Dec 07 20:07:44 shogun sddm[3864]: Writing cookie to "/run/sddm/xauth_JCpUsS"
Dec 07 20:07:44 shogun sddm[3864]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth />
Dec 07 20:07:44 shogun sddm[3864]: Failed to read display number from pipe
Dec 07 20:07:44 shogun sddm[3864]: Display server stopping...
Dec 07 20:07:44 shogun sddm[3864]: Attempt 1 starting the Display server on vt 2 failed
Dec 07 20:07:46 shogun sddm[3864]: Display server starting...
Dec 07 20:07:46 shogun sddm[3864]: Writing cookie to "/run/sddm/xauth_JCpUsS"
Dec 07 20:07:46 shogun sddm[3864]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth />
Dec 07 20:07:46 shogun sddm[3864]: Failed to read display number from pipe
Dec 07 20:07:46 shogun sddm[3864]: Display server stopping...
Dec 07 20:07:46 shogun sddm[3864]: Attempt 2 starting the Display server on vt 2 failed
Dec 07 20:07:48 shogun sddm[3864]: Display server starting...
Dec 07 20:07:48 shogun sddm[3864]: Writing cookie to "/run/sddm/xauth_JCpUsS"
Dec 07 20:07:48 shogun sddm[3864]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth />
Dec 07 20:07:48 shogun sddm[3864]: Failed to read display number from pipe
Dec 07 20:07:48 shogun sddm[3864]: Display server stopping...
Dec 07 20:07:48 shogun sddm[3864]: Attempt 3 starting the Display server on vt 2 failed
Dec 07 20:07:48 shogun sddm[3864]: Could not start Display server on vt 2

I'm using early modesetting like this (but I experimented without):
mkinitcpio.conf:
MODULES=(btrfs vfio_pci vfio vfio_iommu_type1 amdgpu)
BINARIES=(/usr/bin/btrfs)
FILES=()
HOOKS=(base udev autodetect keyboard keymap modconf kms block encrypt filesystems fsck)

systemd-boot entry (amdgpu.sg_display=1 was needed for a workaround when I was still using the iGPU, I tested its removal, but it didn't resolve this issue):
title Arch Linux (linux-zen)
linux /vmlinuz-linux-zen
initrd /amd-ucode.img
initrd /initramfs-linux-zen.img
options cryptdevice=PARTUUID=XXX:luksdev root=/dev/mapper/luksdev rootflags=subvol=@ rw rootfstype=btrfs iommu=pt vfio-pci.ids=10de:2684,10de:22ba amdgpu.sg_display=1

More hardware info:
X670E ProArt + Ryzen 7950X

A different approach I tried was to plug the monitor into the iGPU, enable it in BIOS and then try to use PRIME for 3D tasks, but I wasn't able to properly get my monitor to work in that setup. It has an unusual ultra wide resolution (which the iGPU should support), and regardless of my global DRI_PRIME setting it would not show up.

Offline

#2 2023-12-23 20:50:15

Rays42
Member
Registered: 2022-08-14
Posts: 8

Re: SDDM: Failed to read display number from pipe

My current workaround is switching SDDM to experimental wayland mode. Then I can use weston to log in, but it is very glitchy and I can't set my keymap properly. So now I switched to KWin Wayland in sddm and enabled autologin. Kind of silly since now I'm bypassing the greeter entirely and also I can't log out either. Not a big deal for me, but I'd still like to fix this properly.

Offline

Board footer

Powered by FluxBB