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

"systemd is essentially a corporate IBM/Redhat project and corporations of course will comply"
Microsoft and IBM care about users' freedom like Cheeto Lump cares about the US Constitution
Gemini Links 20/03/2026: Digital Identity Bifurcation and a "Return to Gemini"
Links for the day
 
Gemini Links 20/03/2026: Depictions of Culture and The Social Smolnet
Links for the day
SimilarWeb Was Never a Reliable Yardstick for Traffic
5RB may need some "house-cleaning"
Strangulation, suffocation, Jonathan Carter & Debian toxic culture confirmed
Reprinted with permission from Daniel Pocock
Reports or Hearsay Suggest Ogilvy Broke Up With IBM and Insiders Report Mass Layoffs in "Infrastructure" (Might Impact Red Hat Entrants)
hearsay in Social Control Media
Scheduled Server Maintenance Tomorrow Night
Starting 9PM
None of the Above (NotA) & Debian snubbing Sruthi Chandran
Reprinted with permission from Daniel Pocock
Links 20/03/2026: Cryptography Pioneers Win Turing Award and BMG Sues Anthropic for Copyright Infringement
Links for the day
Even Uganda Understands That Journalists Never Belong in Prison
"Ugandan authorities must respect the spirit of this ruling and abandon any measures that seek to jail Ugandans for the free flow of ideas."
Inaction Helps Your Enemies
Without freedom, there's nothing else left
Windows Down From 99% to ~50% in Republic of Seychelles (République des Seychelles)
Windows fell by a lot
Confluent Insiders: IBM Laid Over Over 800 at Confluent, Not Just 800
For the record, the layoffs at Confluent won't be over. After the bluewashing there will be "IBM RAs" impacting Confluent folks, aside from PIPs
The Layoffs at IBM Carry on (Shades of Enron)
Is IBM another Enron?
"IBM boss Arvind Krishna... financial package valued at $38 million in calendar 2025 - equivalent to the average collective pay of 765 Big Blue workers."
continues to ruin the company to enrich himself while pretending he has a strategy
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Thursday, March 19, 2026
IRC logs for Thursday, March 19, 2026
SLAPP Censorship - Part 16 Out of 200: Detailing the Actors and Explaining Techrights' Own Internet Relay Chat (IRC) Network
For those who have not followed our story
Microsoft "hiding behind bigger news of war, Epstein, other companies' layoffs"
They know what's coming, they just don't know when
Joerg Jaspert (Debian Account Manager/DAM) personally approved Raphael Hertzog's wife Sophie Brun
Reprinted with permission from Daniel Pocock
Letter 'A' prohibited by Code of Conduct extremism
Reprinted with permission from Daniel Pocock
Spoiler: Diversity & Debian means different things to different people
Reprinted with permission from Daniel Pocock
Solicitors Regulation Authority (SRA) Admits Failures and Criticism of Inaction on SLAPPs
many if not all solicitors and solicitor firms in the UK are in effect unregulated
Archiving or Preserving Pages About IBM Layoffs
Layoffs at IBM and the media does not talk about these
ABC, the American National Broadcaster, "Now Publishes Slop"
If the "big media" absorbs slop, it'll no longer be trusted and therefore not read/watched by the public
Links 19/03/2026: Culling Deepfakes of Artists’ Music and "Age Verification Isn’t the Answer"
Links for the day
Gemini Links 19/03/2026: "Aktion GPT-4" and "Kill All Descendants"
Links for the day
"AI" 15 Times in Short 'Article' From The Register MS. And The Register MS Got Paid to Publish It.
gets paid to do this
People Who Decided to Boycott Novell Over Its Microsoft Alliance Should Also Boycott Canonical
As an associate put it, "selling out further, due to Microsoft moles inside Canonical"
Links 19/03/2026: "AI Glasses" as Euphemism for Mass Surveillance and ABC (US) Has Begun Publishing Slop as 'News'
Links for the day
The European Patent Office, Europe's Second-Largest Institution, is on Strike Today
Lots more to come
What People Impacted by the Bluewashing Layoffs at IBM Confluent Say (While the Media Says Nothing at All, in Effect Burying the News)
Worse yet, the mainstream media spreads lies about it right now
IBM Has Turned Red Hat and Fedora Into Slop
This is IBM policy
IBM is Being Robbed, Companies and Jobs Are Destroyed
Companies taken over by IBM will be exploited and destroyed to keep a bubble inflated for a little while longer
In Confluent Layoffs, IBM Vapourises a Quarter of Its Workforce (IBM Buys Something That It Destroys Already)
In the past, such things were typically referred to as "media blackout"; now it's just "the norm".
IBM Effect at Confluent: Mass Layoffs and IBM's Business Conduct Guidelines (BCGs) Said to be Violated
For Confluent employees who survived the layoffs there will be "culture chock"
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Wednesday, March 18, 2026
IRC logs for Wednesday, March 18, 2026
Links 19/03/2026: LLM Fatigue (It Doesn't Work as Advertised), "Small Web Feeds"
Links for the day
SLAPP Censorship - Part 15 Out of 200: Background and Particulars of Truth Regarding Techrights and Tux Machines
the basic facts (this has aged well, except the times/ages/numbers)
A Slopfarms Survey for Today (linuxteck.com, linuxsecurity.com, linuxjournal.com)
Not only did Google news link to a slopfarm; it linked to three run by the same team!
Links 18/03/2026: "Venture Capitalist Warns That It’s All About to Come Crashing Down" Due to Slop Bubble, "Birdwatching for Fun and no Profit"
Links for the day
IBM Red Hat is Still Promoting Restricted Boot Which Restricts Users' Control Over Their Computers
Red Hat under IBM is a total catastrophe
Arvind Says... Something Something "Hey Hi" (the State of Today's Media)
Look for news about IBM and most likely it'll boil down to some sound bites from an executive and nothing else
New Post Has Just Explained How IBM Gets Robbed by the People Who Fail IBM
Their plan for IBM is a personal plan
Slop-Spewing GAFAM LLM That Knows Nothing and Understands Nothing, It's a Stochastic Parrot That Cannot Even Figure Out Tux Machines is a Community That Started in Tennessee 22 Years Ago
RMS rightly calls those things "bullshit generators"
Cusdeb Makes New Presentation About Where GNU Hurd (Still a Possible Linux Replacement) Stands in 2026
coming from a generally RMS-friendly account
Gemini Links 18/03/2026: Librarians, Phone Anxiety, Growing 'Small' Net, and Slop Versus Software Engineering
Links for the day
Estimates That IBM to Lay Off Close to 10,000 Workers in 2026 (Not Counting People Pushed Out)
There's still chatter about Confluent mass layoffs
Smug Threat by Garrett to Put My Family and I in Prison Doesn't Prove We Did Anything Wrong, It Only Proves He's Truly Desperate to Stop Further Publications That Embarrass Him
his reputation is poor in the United States
systemd Increasingly Microsoft Project, Controlled by Microsoft and Slopware
Cannot allow choice
What IBM Meant to Red Hat: "Proprietary Bundling, Restricted Source Access"
Anyone or anything that joins IBM likely shortens its lifespan
IBM Thrashing Confluent Upon Arrival, Based on Rumours
We deem it a bigger issue that investigative journalism perished, not that one must rely on hearsay online or mere "rumours"
Slop Is Plagiarism, Not (Vibe) Coding, and It's Not Automated, It Doesn't Save Money
Reject misnomers, explain what's actually happening
UPC is Still Illegal and Unconstitutional (Kangaroo Court for Patents, Manned by Corporate Staff), Federal Court of Justice of Germany Receives Belated Complaint About It
What is happening to Europe???
EPO Demonstration Happening Right Now, Later This Week Things Will Only Escalate Further
The SUEPO The Hague Committee wrote to staff this morning
Sophie Brun, Raphael Hertzog & Debian sexual conflicts of interest
Reprinted with permission from Daniel Pocock
Links 18/03/2026: Commodore's Hedley Davis Dies, Apple Not Good Enough, Cheeto "Floats Treason Charges for Iran War Coverage"
Links for the day
A Step Close to Shutting Down the European Patent Office (EPO)
Not going to work all month long
EPO Staff Demonstration Today
The demonstration will be live-streamed for those thousands of colleagues who don't live in Munich
Gemini Links 18/03/2026: Brazilian SYN Attacks and BGP
Links for the day
LibreLocal Also Coming to Jordan, Kenya, Mexico, New Zealand, and Spain
It helps raise awareness of Software Freedom
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Tuesday, March 17, 2026
IRC logs for Tuesday, March 17, 2026