Bonum Certa Men Certa

On Nvidia Cards and GNU/Linux: Why You Should Make Sure Your Next PC Doesn’t Have an Nvidia Card

Guest post by Ryan, reprinted with permission from the original

Back in the days, nobody made a good GNU/Linux graphics solution that had an open source driver stack.



In fact, even today 15 or 20 years later, AMD and Intel do not have drivers that are fully open or Free (as in Freedom). All of the big three require at least signed binary-only firmware modules to be downloaded into the cards, or else they don’t expose their 3d engines to the operating system, and without that, you won’t be doing much of anything.



But Nvidia has been a longtime thorn in the side of the GNU/Linux desktop user. On one hand, there’s the argument that when you load their proprietary driver, you get great performance. I’m not here to argue this point because nobody is saying you won’t.



"Since Nvidia’s driver is not supported by Linux, it may run, but nobody will know how to help you when it causes problems."What I will argue, instead, is the maintainability problems and the ethical side of the debate.



When you choose Nvidia, instead of funding hardware companies that put working drivers into the Linux kernel, X11, Wayland, and Mesa3d (an open source implementation of OpenGL and Vulkan 3d graphics APIs), you give money to a company that bypasses the GNU/Linux driver stack and tosses a large “blob” of code that’s literally just a Windows driver that they ported over with a “kernel glue layer”.



Many people consider it to be illegal to ship an operating system with this driver included, which is why most of them make you go get it somehow, and bolt it on after the fact. The process isn’t even consistent because there’s as many ways to do it as there are distributions you could install it on.



Although Nvidia’s license doesn’t disallow it, Linux is under the GNU General Public License, which says that anything that is linked to the kernel and distributed with it is a derived work.



"Nvidia likes to refuse to implement standard programming interfaces and then demand that unpaid (by Nvidia, at least) Free Software developers instead port their project to Nvidia’s alternative facts."Therefore, if a distribution ships Nvidia’s proprietary driver in a way that you don’t have to do anything in order to get it, they’re a GPL violator. Plain and simple. The Linux maintainers probably won’t enforce it, but it’s still wrong.



Debian and many other distributions warn (in neutral language, but most people have no reason to use the proprietary AMD driver since the open source one is fine) that if you get the Nvidia driver straight from Nvidia’s website, and install it, it will only work for the kernel you installed it with.



As soon as your distribution ships a new kernel, it will have a different application binary interface, and even if somehow it does not, Nvidia’s generic installer package isn’t set up to where it would place a new module into the new kernel. In fact, even if you do get Nvidia’s driver from a source that rebuilds it automatically, you have to wait until dkms rebuilds it each time you get a new kernel. That doesn’t happen a lot with Debian, but new kernels arrive all the time in Fedora. It also adds complexity, and something that might fail.



Also, I think that with Microsoft’s “Security Theater Boot” turned on, you can’t actually install Nvidia’s package directly. It needs to be from your distribution so they can sign it. Not that this will stop Nvidia’s installer from saying it succeeded, but when you reboot you’ll see a security policy violation instead of your OS booting. Lovely.



I don’t know exactly how badly this would break these days, because I got tired of Nvidia and was one of the earliest adopters of AMD’s Evergreen series (Radeon HD 5xxx) when they announced an open source solution. At the time I last saw, the kernel would boot the broken configuration Nvidia left it in and then X11 wouldn’t start because the settings referenced a driver setup that no longer existed.



Further, Nvidia would overwrite the system’s OpenGL drivers, so if you removed their driver and installed a competitor’s product, it wouldn’t function properly if it used Mesa3d to provide OpenGL, at least unless you knew how to fix it, or until your operating system installed an update that replaced Mesa3d’s missing libGL.so library. It also left behind deliberately misconfigured settings files all over the OS.



The Romans used to call this “poisoning the well”. If they couldn’t hold territory that they invaded, nobody else could have it either.



Since Nvidia’s driver is not supported by Linux, it may run, but nobody will know how to help you when it causes problems.



Loading the Nvidia module “taints” the kernel, so that you can’t file bug reports. Every kernel developer I’ve talked to was fed up with wasting their time when the Nvidia driver causes bugs all over the kernel tree, including sometimes in the printing system, the file system, and the input devices, or causes an internal structure to become corrupt resulting in a system crash.



Hey, why would you want stability anyway?



So they fixed the problem on their end by ignoring bug reports from people with this driver loaded. Since they can’t fix the driver, and you can’t ask them to, go talk to Nvidia. But Nvidia doesn’t always care. Like most companies, if they can hide behind the fact that you can’t “prove it” or at least that you have no power to compel them to fix it, they will, and things stay broken.



Since Nvidia doesn’t implement standard GNU/Linux, X, Wayland, and Mesa interfaces, sometimes their users don’t get features that the rest of us do for years, or at all.



Nvidia likes to refuse to implement standard programming interfaces and then demand that unpaid (by Nvidia, at least) Free Software developers instead port their project to Nvidia’s alternative facts.



This is sleazy because it abuses the Free Software developers and forces them to do unpaid work for Nvidia to keep their users happy. In the case of GNOME, you couldn’t use the Wayland session at all on Nvidia cards for years. Then it loaded but was too broken to use for years. And I think you can use it now.



Not because Nvidia fixed anything, but because Red Hat implemented a nasty hack that got “XWayland” to run, and you need that for a ton of software, even today, including Wine (to run Windows programs).



But you’ll get used to nasty hacks soon enough if you use proprietary drivers. In fact, most vendors aren’t even as “good” as Nvidia about ever updating them again.



Did I tell you the story about my Avermedia TV Tuner Card that only worked on 32-bit Ubuntu 8.04 and never got updated again? It crashed the kernel too. Cool story, right? I know.



In the past, Nvidia wrote a very slow 2d-only driver called NV.



The only reason it existed was so that X11 would have something to load so you could load the proprietary driver. Today, the “stub” (although on older cards it usually works well enough to keep) usually ends up being nouveau.



If you have an old Nvidia card, nouveau (a reverse engineered open source driver) might run it satisfactorily, but almost certainly won’t if the card is new.



Early on, I was excited for nouveau because they were reverse engineering the card’s firmware too, which meant you didn’t need anything from Nvidia to make the supported cards work.



Then Nvidia announced that they would enforce firmware signing. Allegedly for security reasons, but really because they don’t want anyone to know how their cards work. At all. Not on the driver level, but especially not in firmware.



So they made their binary-only firmware redistributable, but mostly don’t contribute to the nouveau driver. So you would have the same firmware situation (binary-only, redistributable) as with the other drivers, only without an open source operating system-level driver to run the card correctly once it was initialized. The worst possible outcome.



If you need high performance graphics, the AMD open source driver is good. If you just need acceptable graphics in a laptop, Intel’s graphics are at least alright, and both have open source drivers you don’t ever have to configure or think about.



If you install a new operating system component that relates to the drivers, you get a newer version of that component, and it all happens behind the scenes while you use the computer normally.



In software development, there’s a term called technical debt, where a solution that is “fast and easy” at first becomes a snowballing burden that causes more work for you to maintain than having just done things right the first time.



Nvidia will cause you more work and problems than they are worth, even if their products are a bit faster than the competing ones in the lineup.



Right, but how bad can Nvidia be?



I gave away my last Nvidia card and forked the Linux kernel and brought in updated Mesa3d packages before there was a proper release working with my AMD Evergreen card to get early access to AMD’s code. This was somehow more pleasant than dealing with a crashing unstable system due to the Nvidia driver.



Today, over a decade later, you obviously wouldn’t even need to do that, if you want an AMD card, because the infrastructure is mature.



Nvidia does nasty things to Windows users too.



They do market segmentation and use their driver to selectively cripple the hardware. At one point, last year I think, they used the driver to limit bitcoin mining, but Nvidia ultimately proved themselves to be too stupid to enforce that when they accidentally leaked a driver that didn’t enforce the hash rate limiter.



Most of the “updates” to make particular applications work “better” just disable features in the program that their hardware doesn’t get along well with and which is making them look bad. Then the framerate goes up. It doesn’t actually make the game or application any better.



In fact, it may look worse. Speed cheats have been around in proprietary video drivers for a long time. ATI even did it with Quake. At that point in time, it was so crude that if you wanted to cause the driver not to load the hacks, I believe you just needed to rename the executable file for the game.



Nvidia has a history of killing companies that do innovate.



When they bought 3dfx and shut them down, for example. 3dfx had better products, but had run into financial dire straits, and so Nvidia bought them simply to acquire patents, eliminate a competitor, and then keep pushing Nvidia junk on us.



Like most companies, they use others, but they don’t contribute.



Like Microsoft not paying taxes, but getting government contracts anyway, Nvidia treats the organizations that make it possible to run their products at all on GNU/Linux badly.



Recently, the Xorg maintainers have lamented the fact that nobody in the industry wants to step up and even be a stable release branch maintainer. For a long time, the stable release branch maintainer was Apple, which at least needed a working X Server, for XQuartz (similar to XWayland in concept), but now Xorg is basically bit rotting, while companies that make serious bank off of GNU/Linux business, such as Nvidia, let it happen, and won’t even lift a finger to assist in making bugfix releases to this thing that’s almost in mothball development mode.



IBM/Red Hat’s solution to Xorg rotting away is to try to take the next step away from it on GNU/Linux and just abandon the pieces that Wayland doesn’t use. Even Debian 11 with GNOME doesn’t strictly need all of Xorg in order to run properly these days. With Wayland-compatible graphics, you could run a system with no Xorg, only XWayland, but I think we’re still a couple of years off from ditching Xorg. Ubuntu still defaults to it for reasons, and some of those reasons are Nvidia won’t help make their cards work well in Wayland, but also won’t help maintain Xorg.



Giving money to Nvidia helps them harm us and set us back.



Funding Nvidia is similar in concept, I think, to funding hostile countries that have oil that sponsor terror and politicians who deny global warming instead of having public transportation.



Okay, well, maybe it’s not THAT bad, but you get my point. That it takes money that could go to a company that actually supports us and minimizes the overall harm to the computing ecosystem that we all benefit from, and sends it to a company hostile to all things Free and Open Source, which makes massive profits, and then won’t support the infrastructure.



Nvidia is riding high on a Bitcoin Bubble.



I really hope, for many reasons, this crashes, hard and fast, someday soon, and that it completely hoses Nvidia when it does. We would be better off with Nvidia in bankruptcy than churning out products that are this harmful and corrosive to our cause.



But you can help, a little, in your individual capacity, by not buying anything that has an Nvidia logo on it.



When I was critical of Nvidia in the Fedora support channels, I was warned that I violated their Code of Conduct by “insulting” a company. This is just one of the many reasons I won’t use Fedora anymore. Their community is gone, their other desktop spins are horrible, their main spin doesn’t work all that well these days and the people making the decisions do bizarre and incomprehensible things, but the idea that you can’t speak openly, and honestly, and not even in a profane manner about Nvidia… And how do you insult a company anyway, and why would anyone honestly care if you did?



Fedora’s position is “These Nvidia devices are out there and you can’t avoid them, especially on laptops.”. I have three laptops and zero Nvidia chips in them. It must be because that’s impossible.

Recent Techrights' Posts

You Should Probably Self-Host Your E-mail and Never Use a Web Browser for Mail
Does anyone still believe Gmail is "free"?
StatCounter Shows the Market Share of Vista 11 is Decreasing in Ukraine This Year
Microsoft abandoning Vista 10 users would be a victory for Vladimir Putin
The "Gold" Rule: Taking Money for Reputation Laundering and Openwashing Under the "Linux" Banner
Seller of expensive toilet paper, Jim Zemlin
LLM Slop Says Slop is "coming for white-collar jobs. Microsoft’s layoffs are just the start"
Look what the Web has become
Reporting Facts About Violence Against Women Deserves Awards, Not Frivolous Lawsuits and Threats
What is Microsoft's stance on women's safety?
Linux.com as Spamfarm of the Linux Foundation, Partner of the Gates Foundation
They no longer publish articles
Slopwatch: The Typical Slopfarms and the 'Brian Fagioli Dilemma'
To the Web and to society (exposed to the Web) LLMs are a net negative
 
Trump Authority (CA) With a Trump NSA is All About Security, But Whose?
A "turnkey tyranny", as the NSA whistleblower Thomas Drake loved to call it
Confirming IBM Shutdowns and Layoffs Today
It's not over yet
Gemini Links 16/04/2025: The 2010s Are Calling and Why "Tools Will Not Liberate Us"
Links for the day
Links 16/04/2025: Cliff Lynch RIP, More Attacks on Science (NASA)
Links for the day
Google Promotes Fake Articles (LLM Slop) Instead of Originals, Relaying Microsoft's Linux FUD Emanating From Microsoft LLMs
Shame on Google for participating in the slopfest
In Some Countries the Largest OEMs Already Dump Microsoft Windows
Windows at 18.9%, Android 60.2%
Microsoft Down From 100% to 10% in Myanmar/Burma
only about 4% of Web requests in Myanmar/Burma come from Vista 11, soon to be the only "supported" version of Windows
When Fedora Said It Was Looking to Integrate "AI" It Meant Promoting Microsoft's Proprietary Spyware and GPL-Violating Slop
When they say "AI" they mean Microsoft
It Used to be IBM, Now It's Microsoft (Why You Need to Fire Microsofters or CIOs Working for Microsoft)
Typically the only effective solution is to identity and remove Microsofters from one's project/organisation (before they can bring more Microsofters in)
IBM Closes Offices and Labs in the United States to Open New Ones in India
It's not layoffs per se; they're substituting/swapping veteran employees for lesser-paid ones
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Tuesday, April 15, 2025
IRC logs for Tuesday, April 15, 2025
Gemini Links 16/04/2025: IndieWeb Carnival, Tinylog RFC, "Focus, the Web and Gemini"
Links for the day
Links 15/04/2025: Touchable Volumetric Display and Resistance to American Spying Firms
Links for the day
Links 15/04/2025: Some People Cannot Read and Re-discovering of 'Web 1.0'
Links for the day
Links 15/04/2025: China Admits Targetting Critical Infrastructure Using CALEA Back Doors, NASCAR Cracked by Windows Usage
Links for the day
Why We Support Carole Cadwalladr (Even If We Don't Agree With Everything She Said)
I first became aware of Cadwalladr's work a long time ago
Microsoft's Serial Strangler Chose to Attack Techrights With SLAPP When Over 400 Victims of Mohamed Al Fayed Complained About Media's Role in Enabling Him
There is a strong element of "free press" here
A Coalition or a Coup of Sexism
In the Free software community it's hard to avoid this issue
statCounter Sees GNU/Linux at New High of 6% in Bosnia and Herzegovina
GNU/Linux is measured at all-time high
To Celebrate Git Turning 20 Linus Torvalds is 'Selling Out' to Microsoft and Proprietary Software Which Attacks Git (E.E.E.)
He makes it seem like he's endorsing his attackers
Gemini Protocol Milestone (3,000 Active Capsules)
and a total of nearly 4,500
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Monday, April 14, 2025
IRC logs for Monday, April 14, 2025
Gemini Links 14/04/2025: Silver Pigs and more Foundation, Disliking Computers
Links for the day
Hundreds of Microsoft Layoffs (Net Headcount Decrease) in the United Kingdom
headcount decreased
Links 14/04/2025: Russian Attack on Sumy Shows No Intention of Peace, Virgin Australia Admits Overcharging People
Links for the day
The Dilemma of Web Browsers Lying About What They Are (in Order to Bypass Discriminatory Gateways Like Clownflare) Worsens Due to LLM Slop
LLM crawlers/scrapers have made sites more restrictive and hostile towards browsers that are potent but not "famous"
What Really Matters to Companies is Net Income or Profit (Bankruptcy is Possible Even With High Revenue)
We ought to stop talking about revenue without focusing on actual profit
Carole Cadwalladr Talks About How Big Business Tried to Silence Her (and Why You Might be Next)
Our story is very different from Cadwalladr's for many reasons
Companies Conspiring to Keep Salaries Down and Undermine Competition
People who do all the practical work are being paid less and made to work for much longer
Links 14/04/2025: Disinformation, Public Disdain for LLMs, and "Lessons on Tyranny"
Links for the day
LLM Slop and SEO SPAM Take Us Further Away From Facts (the Case of IBM Layoffs)
Some of these can impact Red Hat as well
Gemini Links 14/04/2025: Ween and Historic Ada Project Management
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Sunday, April 13, 2025
IRC logs for Sunday, April 13, 2025
Influencers: Red Hat, Inc's IPO, 1999, post-mortem on the directed share offer to open source developer community
Reprinted with permission from Daniel Pocock