Okay, but that’s still partially on Nvidia for refusing to participate. They could have argued for explicit sync early in Wayland’s development but they weren’t at the table at all, so they got stuck with the technology that was decided on without them and had to argue for changes much later.

And they started off arguing for EGLStreams, but it didn’t work well either. Explicit sync came later.

Wayland has a bunch of features that are so new they aren’t in the stable distros yet.

Nvidia went from declaring they were never going to support Wayland to trying to force their own EGLStreams stuff on everybody to reluctantly accepting the standard that was developed without them and trying to make it work for their driver. They’re playing catchup and it’s entirely their own fault for refusing to cooperate with anybody.

They’re moving more towards open source drivers now, probably because the people buying billions of dollars worth of GPUs to use on Linux servers for AI training have had words with Nvidia on the subject.

Network namespaces and policy based routing are black magic, IMO.

I’ve got a VPN set up on my router and separate VLANs set up for ordinary traffic and VPN traffic. A device doesn’t need to support VPNs at all, I just connect it to the VPN VLAN and all its traffic goes over the VPN whether it likes it or not. I’ve got separate wifi SSIDs for each VLAN.

My desktop is connected to both VLANs with a network namespace set up for the VPN VLAN, so sudo vpn rtorrent runs rtorrent in the namespace that’s connected to the VPN VLAN.

My setup is nice, but I wouldn’t recommend it to anyone who doesn’t want to learn quite a bit about networking.

Yeah, but because pricing jumped like someone set a firecracker off under it’s chair people are actually still using vintage GPUs.

The devs have been working hard to hammer out those troublesome edge cases. There’s a lot less of them than there was a year or two ago.

IIRC Nvidia needs explicit sync support to work reliably. It’s fairly new and might not have landed in some distros, especially the stable releases.

Well, for starters, unless you’re running a quite old card you should be using amdgpu, not radeon. You seem to have them both loaded.

Post a dmesg?

Nuclear subs probably aren’t set up to handle lightning hitting the grid, either.

Do what you want instead of what we want? Lol, no. And if you find a registry hack or something to do it, we’ll ‘fix’ that in the next update.

ERROR: […/src/amd/vulkan/radv_physical_device.c:1877] Code 0 : Device ‘/dev/dri/renderD128’ is not using the AMDGPU kernel driver

This is the smoking gun, btw.

I see you’ve got it working, so I’ll just add a bit of explanation.

AMD GPUs used to use a driver called radeon. It was replaced with the current amdgpu driver. For a while, you had devices that were supported by both drivers and you could choose between the stable radeon driver that was missing features like Vulkan and HDMI audio or the brand new amdgpu driver that had the newest features but was unstable and not well tested.

The kernel has a policy of not unnecessarily breaking things with kernel changes so even though amdgpu has been well tested in the years since, devices from that era still default to the radeon driver and need to be forced onto the amdgpu driver.

I mean, there is, but people have worked hard to set it up so you can just click the button and it all happens.

Slackware just does as it’s told and gets out of the way.

There’s no such thing as stopping processor degradation, it’s just that it usually takes so long that nobody cares anymore.

I meant to do this when I built my old system back in 2018, but I found the handful of games I regularly play worked okay on Linux so I never got around to it, and Linux game compatibility has improved leaps and bounds from there.

If it’s a Steam game, for most of them these days you only have to tick a box in Steam’s settings to tell it to use Proton for all games and the game will just work when you click play.

You might give it a try. Or don’t, I’m not your mother.

If stuff is designed for big servers that run Linux, it’s easier to get it to run on a desktop PC if the PC runs Linux too because then it’s the same thing except much less powerful.

Because grabbing a random prefix from the pool is easier than remembering which prefix is assigned to which subscriber account and keeping it static through ISP network changes.

My ISP does ‘sticky’ prefixes, which means they change when they move users between BNGs but otherwise don’t.