No display via DP or HDMI after boot. [SOLVED]

avalyn0x45 · 2026-06-05 03:24:57

Using 7.0.11-zen1-1-zen kernel
Ryzen 9 5900XT CPU
Radeon RX 5700XT GPU

I don't know if this is a problem with arch, or something else, but I get no display output whatsoever after initial boot (systemd stuff shows up, and then display is lost). I am still able to SSH into the machine, so it seems to just be a display issue. The computer has been working well for several years, and has just now encountered this issue.

Display is also verified to work.

Last edited by avalyn0x45 (2026-06-06 05:25:45)

avalyn0x45 · 2026-06-05 04:11:41

running my wm with systemd-run seems to work? still a weird issue, but not weird enough for me to care.

seth · 2026-06-05 07:29:54

systemd-run as root? Is it the permission or the delay that matters?
What "WM"? How do you run/start it? What is your actual graphical.target?

avalyn0x45 · 2026-06-05 10:10:19

I use river-classic, and the command i used is
systemd-run --uid="$(whoami)" -p PAMName=login -E XDG_SEAT=seat0 -E XDG_VTNR=1 -E XDG_SESSION_TYPE=tty -E XDG_SESSION_CLASS=user river
(i just found it on stackoverflow to run a command as if it were through a tty)

i normally just launch river through the tty

seth · 2026-06-05 14:42:43

i normally just launch river through the tty

Manually or automatically? What if you delay that after the boot?

avalyn0x45 · 2026-06-05 17:24:04

Manually, and there is no tty, so I can't test that.

seth · 2026-06-05 19:11:31

Manually, and there is no tty

Err… what? How do you manually start river if there's no tty where you login and manually run the command??

avalyn0x45 · 2026-06-05 20:02:33

The tty normally works, and just now stopped working, thats why i needed to use the systemd-run command through ssh to get it working.

Last edited by avalyn0x45 (2026-06-05 20:03:26)

seth · 2026-06-05 20:38:16

Oh, so booting the multi-user.target leaves you w/o out but then starting the display server gets you one??
Please post your complete system journal for the boot:

sudo journalctl -b | curl -s -H "Accept: application/json, */*" --upload-file - 'https://paste.c-net.org/'

avalyn0x45 · 2026-06-05 21:12:22

https://paste.c-net.org/HematomaGrammy

seth · 2026-06-05 21:27:18

Jun 04 22:43:47 chonk kernel: amdgpu 0000:2f:00.0: [drm] Cannot find any crtc or sizes
Jun 04 23:01:52 chonk chrome-remote-desktop[1009]: 2026-06-04 23:01:52,502:INFO:Sending SIGTERM to crash-uploader proc (pid=3636)
Jun 04 23:01:52 chonk chrome-remote-desktop[1009]: 2026-06-04 23:01:52,509:INFO:Sending SIGTERM to display server proc (pid=3579)
Jun 04 23:01:52 chonk chrome-remote-desktop[3579]: (II) Server terminated successfully (0). Closing log file.
Jun 04 23:02:03 chonk sshd-session[3701]: Accepted password for ava from 100.100.207.76 port 51024 ssh2
Jun 04 23:02:03 chonk sshd-session[3701]: pam_unix(sshd:session): session opened for user ava(uid=1000) by ava(uid=0)
Jun 04 23:02:03 chonk systemd-logind[881]: New session '2' of user 'ava' with class 'user' and type 'tty'.

There're no local outputs, you're using chrome-remote-desktop, that crashes, then you log in via ssh (there's the systemd-run "requirement") and interesting when river starts

Jun 05 00:10:22 chonk river[23336]: info: raised file descriptor limit of the river process to 4096
Jun 05 00:10:22 chonk river[23412]: info(wlroots): [xwayland/server.c:107] Starting Xwayland on :0
Jun 05 00:10:22 chonk river[23336]: info(wlroots): [backend/drm/drm.c:1781] Scanning DRM connectors on /dev/dri/card1
Jun 05 00:10:22 chonk river[23336]: info(wlroots): [backend/drm/drm.c:1836] Found connector 'DP-1'
Jun 05 00:10:22 chonk river[23336]: info(wlroots): [backend/drm/drm.c:1836] Found connector 'DP-2'
Jun 05 00:10:22 chonk river[23336]: info(wlroots): [backend/drm/drm.c:1836] Found connector 'DP-3'
Jun 05 00:10:22 chonk river[23336]: info(wlroots): [backend/drm/drm.c:1836] Found connector 'HDMI-A-1'
Jun 05 00:10:22 chonk river[23336]: info(wlroots): [backend/drm/drm.c:1861] 'HDMI-A-1' connected
Jun 05 00:10:22 chonk river[23336]: info(wlroots): [backend/drm/drm.c:1646] Detected modes:
Jun 05 00:10:22 chonk river[23336]: info(wlroots): [backend/drm/drm.c:1670]   3440x1440 @ 59.973 Hz (preferred)

=> What if you disable chrome-remote-desktop ?
From the ssh login, can you

for OUT in /sys/class/drm/card*; do echo $OUT; edid-decode $OUT/edid; echo "================="; done

?
You'll need https://archlinux.org/packages/extra/x86_64/v4l-utils/

avalyn0x45 · 2026-06-05 21:34:20

Uninstalling chrome-remote desktop seems to have worked. Thanks for your help.

LinuxLover471 · 2026-06-06 05:25:08

Since your issue is resolved, @avalyn0x45, please add [SOLVED] to the title of the original post.

So that the community can know there isn't anything left to solve.
Thanks!

Arch Linux

#1 2026-06-05 03:24:57

No display via DP or HDMI after boot. [SOLVED]

#2 2026-06-05 04:11:41

Re: No display via DP or HDMI after boot. [SOLVED]

#3 2026-06-05 07:29:54

Re: No display via DP or HDMI after boot. [SOLVED]

#4 2026-06-05 10:10:19

Re: No display via DP or HDMI after boot. [SOLVED]

#5 2026-06-05 14:42:43

Re: No display via DP or HDMI after boot. [SOLVED]

#6 2026-06-05 17:24:04

Re: No display via DP or HDMI after boot. [SOLVED]

#7 2026-06-05 19:11:31

Re: No display via DP or HDMI after boot. [SOLVED]

#8 2026-06-05 20:02:33

Re: No display via DP or HDMI after boot. [SOLVED]

#9 2026-06-05 20:38:16

Re: No display via DP or HDMI after boot. [SOLVED]

#10 2026-06-05 21:12:22

Re: No display via DP or HDMI after boot. [SOLVED]

#11 2026-06-05 21:27:18

Re: No display via DP or HDMI after boot. [SOLVED]

#12 2026-06-05 21:34:20

Re: No display via DP or HDMI after boot. [SOLVED]

#13 2026-06-06 05:25:08

Re: No display via DP or HDMI after boot. [SOLVED]

Board footer