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.
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.
IPv6 has privacy addresses, though. Stuff on my network generates a new random address every day and uses that address for outgoing connections, so you can’t really track individual devices inside my network.
IPv6 has a policy of throwing more address space at stuff to make routing simpler, though.
IPv4 will individually route tiny slices of address space all over the world, IPv6 just assigns a massive chunk of space in the first place and calls it a day.
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?
Reports are mixed.
If you want to post logs, I’ll have a look to see if I see any obvious problems: https://github.com/ValveSoftware/Proton/wiki/Proton-FAQ#how-to-enable-proton-logs
I think you only get the VRR setting if the screen does support VRR. No point asking the user if the system can’t do it.
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.
I’d argue that power is more the issue. All that processor time the antivirus spends scanning and rescanning is a chunk of battery gone.
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.
I’d argue that if pushing the brakes hard can blow up the brake lines, they already needed fixed.
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.
GNU Parallel works well for this kind of thing. A lot of audio stuff is single threaded, so unlike video transcoding running multiple conversions simultaneously is a useful thing to do. The command is simpler, too:
parallel ffmpeg -i {} {.}.opus ::: *.m4a
I switched my laptop to Wayland about three years ago. AMD graphics, normal DPI 60Hz screen, doesn’t really do more than run a web browser.
My gaming desktop needed more of those troublesome edge cases hammered out - freesync in xwayland, app DPI scaling in xwayland, etc. I only switched it last year.
I’d argue the root cause was Nvidia insisting that X11 was the future, they’d never support Wayland, and refusing to participate in any of the design processes. As a result when they got dragged kicking and screaming into supporting Wayland, nothing that had been developed without Nvidia suited their hardware or drivers.
They first tried to throw their weight around by forcing EGLStreams on everyone, failed, and they’ve been scrambling to catch up ever since.
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.