is it possible to set the steamdeck to “default” to always keep picking the steamdeck speaker as default audio out also when an HDMI is connected through the USB-C?

Some audio issues were introduced in the SteamOS 3.5 update (partly due to having to handle the OLED model around the same time) which causes the HDMI problem. Hopefully it will be fixed in SteamOS 3.6 or 3.7. I’ve found that Bazzite doesn’t have the issue, although obviously that’s an invasive change, and I understand it’s still a bit buggy with the OLED model.

how do y’all combine music and games?

I think doing what you want could be a bit technically involved. One way might be to have one device control the music, and then cast it to the deck with snapcast or similar. Then, if you can get a snapcast client on the deck to be persistently running in the background, any music that is played on the other device, will be heard on the Deck.

Or more simply, you could try pairing your Deck in bluetooth from another device, and then select that Deck as an output. This is assuming that the Deck allows this, and that your source device supports it (Android did last time I tried).

Note: Not actual Linux ports to be clear but I believe the original versions already ran fine, including their limitations.

Yeah, I understand. It was more of a shout into the void type comment, then a criticism.

They’re keeping the 256gb LCD for now, although that could change in the future of course.

Monado is the only semi-viable thing at the moment, but it’s still really in the tinkerer phase. Annoyingly, much of the discussion about it is on discord.

EDIT: And Linux VR Adventures is the place to go for relatively simple instructions about how to set things up, and what is currently supported.

Should work out of the box with Plasma 5/6 (6 if you want HDR) and Sway.

VRR didn’t work with older firmware versions but there have been updates since so the manufacturer information may be out of date. If it doesn’t work, there are links in the gitlab thread for newer firmware (you’ll probably need Windows to update although I saw some vague references that it might be possible on Linux). The adapter is mostly useless on Windows for the record, although you can just swap to a direct HDMI connection in that case.

Oh and I’ll add there are some instances where you may need to power cycle your TV/monitor and/or switch console VTs, if you get a black screen or if HDR fails to toggle on/off.

And lastly, gamescope session didn’t work reliably last time I checked, but it’s been a while.

I think there are more people that are #1 and #2 the same time

Probably where some of the attitude comes from. People are assuming that it’s paid IT people bringing their work home with them, which is a different case then a casual user trying out self-hosting without the broader background.

Although I haven’t seen this attitude myself so I suspect it’s not that common, and probably just a handful of users jumping to conclusions.

I haven’t tried it, but Tube Archivist may fit the bill.

The downside with ULA is that ipv4 is given preference, which is annoying on dual stack networks. I believe there is a draft RFC to change this but it will take a while for it to be approved and longer still for OSes to change their behaviour. I workaround it by using one of the unused (but not ULA) prefixes.

Pretty cool especially since it’s RISC-V. I’d have some concerns about the software and driver side of things, though (and the performance).

Ah Nvidia. Bazzite uses Wayland I believe since it uses the same gamescope session as SteamOS (unless something has changed recently). While it may be possible to get it working, I’d expect a much better time with an AMD card.

A traditional distribution may be a better bet with Nvidia for now.

My bad, the two clipboards on Linux still trip me up after all of these years. Anyway, I’ve added a link to the above.

There’s a bunch of other variants like PiKVM and BIiKVM as well. Even some cheap knockoffs on Aliexpress that may do the job.

Mainly because running multiple desktop machines adds up to a lot of power, even at idle. If you power them off and on as needed it’s better, but then it’s not as convenient. Of course, if you leave a single machine with multiple GPUs on 24/7 that will also eat a lot of power, but it will be less than multiple machines turned on 24/7 at least.

And the physical space taken up by multiple desktop machines starts to add up significantly, particularly if you live in an apartment or smaller house.

Vanguard is especially bad because it will not allow to run the game with Intel-VT/AMD-V enabled even if you are running bare metal as of its last update.

The Vanguard anti-cheat is incredibly invasive and something akin to malware, so that’s not surprising.

I’ve recently tried to do that using sunsine and different linux gaming distros and it was awful, the VM was working great for a few minutes and then suddenly crashes and I have to hard stop it.

Are you running this with something like libvirtd/qemu? If so, VFIO configurations can get pretty complex. Random crashes seem like MSI interrupt issues (or you’ve allocated too much RAM to the guest). Or it could be GPU reset issues that would also occur on the (Linux) host, a newer kernel and Mesa version in the guest may help.

Setting on the kernel commandline for the host to workaround MSR interrupt crashes:

kvm.ignore_msrs=1

If you’re running on a Windows host or with something like Virtualbox (assuming GPU passthrough is supported by these), YMMV but I wouldn’t expect good results.

The followups do usually come, just later. It’s more like the GTA double dipping strategy where they get console users (and impatient PC users who buy a console) then PC users, both often paying at full price.

Do they support VRR though? Last I heard that was still an issue with these converters.

Yes, some of them do but it can be dependent on the firmware (some of them are flashable). I will add that my display supports both Freesync over HDMI and VRR, and it’s not always clear which it is actually using under the hood, so be aware of that. You’ll need a pretty recent kernel. Definitely at least 6.3 but prefer 6.6 or later.

My experience is the adapters have much better support under Linux as well, with them being almost useless on Windows (no HDR, no VRR, and potentially no 120Hz). But it’s been a while since I’ve tested.

Here’s the adapter I use: https://www.amazon.com/Cable-Matters-102101-BLK-Computer-Adapter/dp/B08XFSLWQF/

And a long discussion thread about HDMI 2.1 and adapters used to workaround the issue: https://gitlab.freedesktop.org/drm/amd/-/issues/1417 which may be helpful if you run into issues.

EDIT: Fixed the link

I would expect so. It might already be on the Deck, as sometimes Valve is ahead on kernel and firmware related issues.

Systems themselves are all around 5-20W, although the ones with mechanical HDDs obviously add their own idle usage.