while(true){💩};
For AMD, it’s literally just make sure mesa is installed (it is by default on most distros), make sure radv is installed (it is by default on most distros), and then go.
From there, if you are gaming, you handle whatever your games need like enabling 32-bit libraries for Steam if your distro doesn’t by default, or doing whatever WINE or Lutris wants you to do.
Done.
The story goes that around the time the AMD RX480 came out - or maybe a little after - AMD almost completely opensourced their GPU drivers on Linux.
They gave two offerings: amdgpu (open source) and amdgpu-pro (Closed source, included some extra features most people wouldn’t care about but some really do). Thus retiring the old radeon driver.
At first, the new drivers were decent, if slightly unstable.
AMD also provided a Vulkan driver by the name of amdvlk, which was good but the performance wasn’t very exciting.
Then Valve started contributing. They started providing a Vulkan driver for AMD cards that is better than AMD’s called RADV, which has since become the default and has been mainlined into mesa. Performance went through the roof.
I may be wrong but I think Valve may also contribute back to the amdgpu driver.
Wayland finally became a thing, and between AMD, Nvidia, and Intel, AMD was king in stability and performance in this arena. Especially on KDE, which had very early adoption of many important features long before Gnome had them - Mixed monitor scaling, Variable refresh rate, mixed monitor refresh rate, DRM modesetting for VR headsets, HDR monitor support, etc., in addition to a bunch of extra security features which some appreciate greatly and others find frustrating.
Over in Nvidia land, they were busy doing Nvidia things. And by Nvidia things, I mean doing nothing new.
Nvidia’s drivers mostly remained just as you remember them from 15 years ago, with the Nvidia config tool for X11 and so on. Their closed-source driver performance on Linux was good but not great.
Wayland threw a wrench in Nvidia’s gears. Nvidia tried to control the narrative by trying to force EGLStreams as the standard, several years after the community had settled on GBM as the standard (I won’t dive much into what those are - for now, you only need to know that they’re important in making Wayland work at all and affect performance, stability, and the ability to talk to the Wayland protocol). For a very long time, Nvidia card users were either unable to use Wayland, or had a very poor experience with it; experiencing stuttering, flashing or flickering screens, black boxes, and so on. This whole thing locked Nvidia users to the outdated X11 system which is missing a lot of modern features mentioned previously in the AMD section.
Some time later, Nvidia was hacked by a group called LAPSUS$, who among other things demanded that Nvidia fully open-source their drivers. They essentially got ahold of Nvidia’s code and said “Either you open-source it or we do.”
I forget exactly what Nvidia’s direct response to them was, but interestingly some time later, they opted to “open-source” their drivers by reducing the size of and wrapping the closed proprietary binaries in what the Linux community was calling an “open-source condom.” Effectively, we got drivers that behaved the way the Linux kernel expected, despite not being truly open source. A neat hat trick.
Something else happened, I think maybe more bits got open sourced, but as of recently there are now new open source Nvidia drivers as of driver version 555, called nvidia-open (not to be confused with nouveau open source community drivers), and you can now use Nvidia cards with 80-90% as much ease and performance as AMD users have on Linux. There is still some jank and rough edges that need to be smoothed out, but Nvidia is now part of the 21st century on Linux.
I personally would recommend avoiding Nvidia due to their history and how they treat their Linux customers, but if you already have an Nvidia card and don’t want to or can’t afford to switch, you can now use your card with relatively smooth and high performance on Linux - and use Wayland to boot.
I think it’s still valuable to document these things so that the users who insist on sticking with X11 can receive a healthy dose of this (replace diapers with vulnerabilities) when the proverbial shit hits the fan and it becomes as hackable as Windows XP
They would need to fix the SMS app first (lots and lots of bugs, not the least of which is that it likes to split MMS group chats up into separate 1 on 1 threads with every single participant as soon as you reply to the group)
winlator can run windows apps on android
Hey that sounds neat!
uses ubuntu as a base
Oh no…
MIT license
oh no
Have to install from github/no F-Droid build
oh no
You are clearly not the target audience then. There is a lot of extremely useful info in those model names.
This+Homeassistant web portal should make for a very nice little tablet-kiosk
Thats kind of like saying Valve and Steam are not the same thing. Like, yea, Valve owns and develops Steam, but most people will understand someone who calls the company “Steam” (even if they sound a bit daft in doing so).
There is fairly substantial rumor that there may be a smear campaign against firefox lately because they are still supporting manifest v2, which our owning class does not care for.
Mozilla has made their fair share of stupid decisions lately, but they are still leagues ahead of Google, Amazon, and the other FAANG-type companies in ethics and trustworthiness. Definitely something to keep a pulse on, but nothing to throw the baby out with the bathwater over. And if it really bothers you, use LibreWolf/Fennec.
Its free on f-droid
Isn’t Snikket just a fork of Conversations for Android? It doesn’t look like it’s any better either.
Conversations+Prosody all the way.
I am a neural network that can generate highly photorealistic frames of Doom that seem like real life. I have no output port so these images cannot be seen by others.
Lmao, its everywhere now isnt it
Thats not necessarily dead, some FOSS projects move very slow as these are not the dev’s day job. And slow development doesnt equal non-functional. Especially for something as simple as an alarm clock.
It sounds like at least some of the features released in 4.0 were needed to make that work. Glide typing got disabled as a result of the new framework, so it’s definitely on its way (more now than before)
Did it get turned off? This is gonna be a major problem for me 😬
EDIT: It totally did. Looks like I’ll be on 3.1.6 for a while
It even has water markers for longer trails where youd be hiking for weeks or months at a time. Sometimes those spots are dry, but you can clearly see water channels in the ground where it would be flowing.
Pretty sure KDE’s Discover store hooks into Debian’s repos just fine too
Please no. if you want this, please use Gnome.
Auxio is excellent. Has the UI I’ve been looking for for ages, can shuffle by genre, great queue system, etc.
Only part i dont like is that it has an unskippable modal at startup where it scans your library instead of doing this as an invisible async step in the background and displaying what it has as it gets it.