←back to thread

Are We Wayland Yet?

(arewewaylandyet.com)
96 points picture | 9 comments | | HN request time: 1.125s | source | bottom
1. jpgvm ◴[] No.32020896[source]
Ah yes. Nvidia. The green death.

At this point my systems are going to be pure AMD until status quo changes. I begrudgingly used Nvidia while they were the better of 2 proprietary blob options but now that AMD GPUs work out of the box with no hassle (for the ones I have tried at-least) and are competitive on performance for what I do (consumer workloads/gaming) then there is no contest.

Right now I'm daily driving Wayland + Sway on Arch and it's been mostly good. Only issues I have ran into have been weirdness in the whole Alsa + Pipewire + etc stack which is hairy AF. Configuring Electron things to use Ozone auto detection makes them run native rather than via XWayland which is nice too.

replies(5): >>32020938 #>>32020954 #>>32021123 #>>32021211 #>>32024717 #
2. doodlesdev ◴[] No.32020938[source]
> Configuring Electron things to use Ozone auto detection makes them run native rather than via XWayland which is nice too.

How did you manage to set this up? Some environment variable? The best I've managed to do was to change the applications .desktop file to include Ozone wayland parameters.

replies(1): >>32021157 #
3. BeetleB ◴[] No.32020954[source]
Interesting how the pendulum swings.

My first PC I built and used with Linux used an ATI Radeon graphics card (now owned by AMD). It had such poor Linux support that I swore I'd never buy ATI again. Nvidia's drivers were way better in those days.

4. ddtaylor ◴[] No.32021123[source]
I use Nvidia for gaming systems that only run Windows and never get any of my important credentials entered on them; they strictly run games only. For development and non-gaming tasks I use an Intel integrated graphics system on Linux instead. Wayland on the iGPU systems runs great!
replies(1): >>32021599 #
5. jpgvm ◴[] No.32021157[source]
On Arch they tend to use flags files in `$HOME/.config` can generally just add `--ozone-platform=wayland` to force it to use Wayland.
replies(1): >>32021698 #
6. zamadatix ◴[] No.32021211[source]
Nvidia with Sway actually works well now since the big GBM announcement last fall. Some are even using the newer open source driver but I haven't bothered yet as it is still alpha quality for the desktop use case. For me it doesn't matter too much until Wayland HDR lands though, my non HDR system was already AMD because the GPU support was better.
7. heywoodlh ◴[] No.32021599[source]
I am in the exact same boat.

Additionally, I have set up Nvidia's gamestream so I can keep my Windows devices tucked away in a closet and that allows me to game on the go -- and not have to directly interface with my Windows machine aside for gaming related stuff. So most games I stream to either my Apple TV, iPhone or Dell XPS running Arch (when I want to use a mouse+keyboard).

My Wireguard setup combined with Moonlight allows me to stream remotely, too! When I am visiting in-laws a few hundred miles away it works flawlessly.

It's super nice to be able to game remotely :)

8. doubled112 ◴[] No.32021698{3}[source]
I had mixed results with the flags files.

At least the last time I tried, between Arch repos and AUR, I had some versions of Electron that'd pick it up, and some that wouldn't.

9. sam_lowry_ ◴[] No.32024717[source]
You can drop Pipewire, and use alsa + dmix for system-wide sound mixer.

However, if you are also using ungoogled Chromium from Arch, you are doomed to use Pipewire.