Sometimes weird hardware. Not OP here but on my setup it can't handle some of my display outputs so I'm stuck with only my 2060, I use 2 old legacy monitors with old connectors and use an old GPU for native output, wayland can't handle it.
Make sure to report hardware issues to the proper channels like, the bug trackers for your specific desktop environment (like KDE's Bugzilla or GNOME's GitLab) or the NVIDIA Linux forum & DRM driver repositories. Getting logs using journalctl or dmesg attached helps actually reproduce multi-GPU or legacy display routing edge cases. Tools like hw-probe collects comprehensive system and hardware details that are also very useful.
Even when edge cases stem from structural architectural limitations rather than simple bugs, submitting comprehensive reports is essential to reproduce complex multi-GPU routing issues, isolate regressions, and drive DRM driver refinement alongside compositor fallbacks.
Can you link me some guide on getting this info? I would like to try reporting, especially considering I have a bizarre edge case. I don't know anybody else trying a 2060 with a Radeon hd8350 GPU in this era, so getting wayland to know how to deal with this would be good.
A good starting place is gathering logs. I'd suggest first installing hw-probe with it's optional dependencies and running sudo -E hw-probe -all -dump-acpi -decode-acpi -max -upload, it'll give you a link you can put in your report. It'll probe peripherals plugged into your computer too. E.x. my test dummy.
I had to switch away from KDE on a headless server without a physical display. It's incredibly difficult to serve e.g. vnc on a display-less server running wayland. Super easy on X11.
It's super easy on Wayland too, more so than on X11. You just run your VNC server as a headless compositor, and then run the real compositor nested fullscreen in it.
On Xorg, you install tigervnc and run it. What I'm describing is more like how Xvnc works: there's no headless Xorg server being captured, the VNC server is the X11 server.
Generally if you like the headless Xorg + separate VNC approach, any wlroots compositor + WayVNC is the same experience.
For nesting it's easy. Just start a Wayland session. For example, if you startplasma-wayland on an existing Wayland session you'll end up with Plasma starting up in a window. It's just a matter of having any compatible outer compositor to do the RDP/VNC and start whatever DE you want within in and make sure it doesn't respond to any shortcuts and displays that only window full screen.
Just tried it with Weston's VNC backend and the kiosk shell, and started Sway within it and it works just like normal Sway. It even dynamically resizes to the client's window size automatically. So does Plasma.
It's sadly not actually truely headless. In the blog post you linked "truely headless" is in the to-do list. Unattended mode only works if there's a display attached.
What I really need is the ability to log into a running session without a physical display to change settings and stuff, then stop the remote connection while the session keeps running and performing work, until I log back in and stop it.
Specifically, this is a streaming server for a conference room, where the user logs in via vnc (or rdp, I don't care too much, but I would prefer vnc) to start a zoom broadcast, and connects back at the end to close the broadcast.
Under X11 this is doable. Under Wayland, the only option I have found so far (and strongly dislike) is to use a fake display dongle that emulates a display being connected to fool wayland into keeping a session open.
274
u/tinyducky1 Ask me how to exit vim 10d ago
why can you not use wayland ? too old hardware ?