Sway displays black screen on startup on Cape Verde GPU

swaywm / sway

i3-compatible Wayland compositor

https://swaywm.org

MIT License

14.69k stars 1.11k forks source link

Sway displays black screen on startup on Cape Verde GPU #8442

Open askiiart opened 6 days ago

askiiart commented 6 days ago

Sway Version: 1.10
Debug Log:
Configuration File:
- Likely not applicable, but here; it's a .tar.gz file in base64, sorry for the odd format.
Stack Trace: Sway didn't crash, so I'm not gonna go through the trouble of doing this upfront, but I can provide it if needed.
Description:
- Reproduction: Just run Sway. This has been tested with Sway 1.10 on both Arch and the Fedora 41 Sway spin installation live iso, with the same results. The logs were from Fedora.
- This is most likely related to my GPU, which is a Firepro W4100/Cape Verde.
- Upon running Sway, it just shows a black screen, and I can't get out of it; I have to switch to another tty.

askiiart commented 6 days ago

If I had to guess, I'd say it's probably related to this:

The legacy wl_drm protocol is now disabled by default (superseded by the standard linux-dmabuf-v1 protocol). This causes breakage in xorg-xwayland < 24.1.0, libva < 2.22.0 and amdvlk < 2024.Q4.1, and can be re-enabled manually via -Dlegacy-wl-drm

I'll try compiling it with that flag when I've got time, maybe tomorrow.

emersion commented 5 days ago

Sounds like a duplicate of https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/3918:

00:00:00.310 [ERROR] [wlr] [backend/drm/legacy.c:175] connector DP-1: drmModePageFlip failed: Device or resource busy
00:00:00.310 [ERROR] [sway/config/output.c:923] Backend commit failed

If I had to guess, I'd say it's probably related to this:

That's unrelated, that one is about some GPU-accelerated clients failing to start up or falling back to software rendering. Also this flag is a runtime Sway flag, not a build flag.

askiiart commented 5 days ago

Ah alright. I tried it at runtime already in case that actually was the case, and it made no difference, so that doesn't seem to be the issue. I've got no idea where to go from here, but if you've got any suggestions or want anything logged, I'll give it a shot.

askiiart commented 5 days ago

Also, Sway does work when being started from a GNOME session. It doesn't work when being run from a console/by a greeter, though.

Also, wlroots issue 3918 doesn't mention the screen(s) being black, showing nothing, and not functioning, so maybe the issues are related, but I don't think it's the same problem.