

I remember hearing during lockdown that sales of business pants had tanked, but sales of business shirts hadn’t.


I remember hearing during lockdown that sales of business pants had tanked, but sales of business shirts hadn’t.


It was originally one computer that everyone connected to, it wasn’t a fleet of separate computers like Windows PCs.


12% of humans believe we aren’t apes
All humans are apes, those people more so than most.


it’s a good beginner distro because getting thrown into deep water is how one learns to swim
That’s… not how it works, for distros or for actual swimming. Usually when someone who can’t swim is thrown into deep water, they drown and/or reinstall Windows which is much the same thing.
Isn’t this the guy who got called out for trying to use social media brigading to force Linux kernel rust patches through? There’s a good chance those stalkers are fictional.


The benchmarks are against vanilla Wine. A lot of people are using the fsync patches, so ntsync is more about accuracy - things that didn’t work under fsync should work under ntsync.
Instead of choosing between accuracy and performance hacks, ntsync should do it properly.


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?


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.
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.
Well, Nvidia initially didn’t intend to support Wayland at all. They’re being dragged into it kicking and screaming, one step at a time.
Depends on what they actually need to do. When it’s a drive that’s working and they just have to image it and run some recovery software it should be pretty cheap.
Clean room repair of dead hard disks is a different story.
If there’s something really important on that disk, don’t do ANYTHING, just unplug it and hand it over to a data recovery company.
If there isn’t anything really important on there, go ahead and try and do it yourself.
Paying $100 to a data recovery company can save you a ton of headaches if it has the only copy of your thesis on there and you mess it up trying to fix things yourself.
This sort of thing makes me want to tear my hair out when I hear “Why bother rolling out IPv6 when IPv4 just WORKS!?”
NAT, port forwarding and the problems they cause are seen as expected, just the way the internet works instead of the dirty hacks they actually are. Most people aren’t old enough to remember the time when everything connected to the internet had a routable IPv4 address.