- Top Pick: SanDisk Extreme PRO USB 3.2 Solid State Flash Drive 128GB
- Runner-up: Samsung T9 Portable SSD 2TB (MU-PG2T0B/AM)
- Also consider: Crucial X10 Pro 2TB Portable SSD (CT2000X10PROSSD902)
The update finishes, you reboot, and something is wrong: a black screen after login, games that suddenly stutter, a Vulkan title that refuses to launch, or a desktop in software rendering. On Linux there is no single undo button for a graphics driver, because the driver is not one thing. NVIDIA’s proprietary stack arrives as distro packages, while AMD and Intel graphics ride inside Mesa and the kernel, and each layer has its own way back, with the previous working state usually still on disk.
This guide is the reverse procedure only. Installing or updating NVIDIA drivers going forward is covered by the site’s NVIDIA update guide, and chasing the newest Mesa builds is covered by the bleeding-edge Mesa article; neither is repeated here. What follows: confirming the driver is the culprit, stepping each stack back one version, recovering when the driver rides the kernel, and the habits that make the next rollback painless.
As an Amazon Associate, we earn from qualifying purchases.
Quick answer
Roll back in the order the layers stack. Boot the previous kernel from the boot menu first: one reboot separates kernel problems from package problems. If the fault stays, downgrade the packages themselves: NVIDIA through the package manager’s history or a pinned older version, Mesa through a package downgrade or by removing the repository that supplied it. Then hold the working version.
Step zero: confirm the driver is actually the culprit
Three checks take minutes, and they matter, because rolling back the wrong component wastes diagnostic clarity. First, timing: did the breakage start on the first reboot after a system update? The package manager’s history shows exactly which graphics packages changed and when. Second, scope: one game breaking after its own patch is a game problem, while every 3D application degrading at once points at the shared layer underneath. Third, the session test: if the desktop breaks under Wayland but works under X11, or the reverse, the fault sits in the driver-and-compositor pairing, not in your games.
The NVIDIA path: stepping back the proprietary driver
NVIDIA’s driver is a set of ordinary packages on most distributions, so the package manager already knows how to reverse it. On Ubuntu and Debian-family systems, the transaction history lists the driver packages that were replaced; reinstalling the previous version by name and marking the packages on hold stops the updater reapplying it. On Fedora, the package history can undo the transaction, and a version lock pins the result. On Arch and its derivatives, earlier packages remain in the local package cache, so reinstalling the cached driver set restores the earlier stack; the ignore list holds it there. Two cautions apply everywhere. The userspace libraries and kernel module must match versions, so always move the whole set together. And if the driver came from NVIDIA’s standalone installer file rather than packages, use that installer’s own uninstall option, then install the distro-packaged driver cleanly.
The Mesa path: AMD and Intel graphics
For AMD and Intel hardware there is no separate driver installer to remove, because the graphics stack is Mesa plus the in-kernel driver, and Mesa arrives as system packages. The rollback is a package downgrade of the Mesa set as a group: the core libraries, the Vulkan drivers and the OpenGL components move together. Where the newer Mesa came from an add-on repository, such as a community PPA on Ubuntu-family systems, the cleanest reversal is the purge tool built for this: it removes the repository and returns its packages to the stock versions in one operation. On Fedora, the downgrade command steps the Mesa packages back to the previous build, and on Arch the package cache again supplies the earlier versions. One wrinkle matters: Flatpak applications do not use the system Mesa, because their graphics drivers ship inside the Flatpak runtime. If only Flatpak games broke while native games stayed healthy, the runtime is the layer that changed.
When the driver rides the kernel
The AMD kernel driver, and increasingly the Intel one, lives inside the kernel itself, so a bad driver can arrive wearing a kernel update’s clothes. Linux systems keep previously installed kernels, and the boot menu lets you start the machine on the earlier one. If games work there, the fault is isolated to the new kernel build, and you have a working machine while you decide on the longer fix. That fix is pinning: lock the kernel packages on Debian and Ubuntu family systems, version-lock or raise the retained-kernel count on Fedora, or ignore the kernel package on Arch until a fixed build appears. Never let the system prune away your last known-good kernel, and treat a kernel update and a driver update as the same event for testing, because on AMD and Intel hardware they often are. On image-based systems such as Bazzite, the previous system image stays available at boot and restores everything, driver included.
Habits that make the next rollback painless
Every technique above works better when prepared before it is needed. A filesystem snapshot taken before a driver update turns the whole question into a reboot and a restore; the folder’s Btrfs snapshot guide covers the gaming-specific setup. Keeping one known-good kernel installed preserves the cheapest diagnostic in this article. Writing down the driver and Mesa versions that worked, somewhere readable when the screen will not start, removes the guesswork from the downgrade target. A current rescue USB in a drawer and a system image on an external drive are the floor under everything: the worst rollback failure still ends with your library and saves intact.
How to choose
Match the depth of the rollback to the symptom. If one game broke and everything else renders fine, stop at step zero and treat it as a game or Proton issue. If every 3D application degraded after an update but the desktop still starts, a package-level rollback of the driver or Mesa set is the right depth. If the machine reaches a black screen or software rendering, boot the previous kernel, confirm the diagnosis there, then pin or downgrade from that working session. If only Flatpak games broke, leave the system stack alone and address the runtime. Going deeper than the symptom requires is how a fifteen-minute fix becomes a fresh install.
Who should skip this
Skip the manual rollback if your system is image-based and still boots: selecting the previous image at the boot menu restores the earlier driver with it, and the package steps here do not apply. Skip it if the breakage began before the update you are blaming, since downgrading cannot fix a fault that predates the change. Skip it if your problem is tuning rather than breakage; an older driver remedies a regression, not a frame rate. And skip the pinning steps if you are content to wait: most regressions are fixed in a follow-up release.
Gear that makes recovery boring
None of this hardware rolls a driver back for you. It keeps the safety nets — snapshots, system images and rescue media — fast and roomy enough that you actually maintain them.
SanDisk Extreme PRO USB 3.2 Solid State Flash Drive 128GB
The stick to write your installer and rescue image to. Its solid-state internals load the live environment far faster than a bargain flash drive.
Specs
– Capacity: 128GB
– Model: SDCZ880-128G-GAM46
– Interface: USB 3.2 Gen 1, USB Type-A
– Maker-stated speeds: up to 420 MB/s read, up to 380 MB/s write
– Housing: aluminium casing
– Extras: password protection and file recovery software from the maker
Samsung T9 Portable SSD 2TB
Snapshots and system images only protect you if they exist, and they exist when writing them is quick. The T9 is the target for a system image taken before a big update: fast, and roomy enough for the image plus your saves.
Specs
– Capacity: 2TB
– Model: MU-PG2T0B/AM
– Interface: USB 3.2 Gen 2×2 over USB-C
– Maker-stated speeds: up to 2,000 MB/s read, up to 1,950 MB/s write on this capacity
– Build: aluminium body with a maker-stated drop resistance rating
– Security: hardware encryption support stated by the maker
Crucial X10 Pro 2TB Portable SSD
The second-copy drive. The image you restore from should not be the only one, and the X10 Pro suits the copy that lives away from the desk: compact, bus-powered, and quick to refresh after a successful update.
Specs
– Capacity: 2TB
– Model: CT2000X10PROSSD902
– Interface: USB 3.2 Gen 2×2 over USB-C
– Maker-stated speeds: up to 2,100 MB/s read, up to 2,000 MB/s write
– Build: anodised aluminium body, maker-stated dust and water resistance
– Power: bus-powered, no separate adapter
Samsung 990 PRO 2TB NVMe SSD
A spare internal drive changes your options: clone your working system onto it before a major driver jump, and the rollback becomes choosing which drive boots.
Specs
– Capacity: 2TB
– Model: MZ-V9P2T0B/AM
– Interface: PCIe 4.0 x4, NVMe, M.2 2280
– Maker-stated speeds: up to 7,450 MB/s read, up to 6,900 MB/s write
– Cache: 2GB LPDDR4 DRAM stated by the maker
– Version: bare drive, no heatsink fitted
WD Black SN850X 2TB NVMe SSD
The alternative rehearsal drive, from its maker’s gaming line: test a new kernel and driver pairing here without endangering the installation you play on.
Specs
– Capacity: 2TB
– Model: WDS200T2X0E
– Interface: PCIe 4.0 x4, NVMe, M.2 2280
– Maker-stated speeds: up to 7,300 MB/s read on this capacity class
– NAND: TLC 3D NAND stated by the maker
– Version: bare drive, no heatsink fitted
FAQ
Will rolling back the driver delete my games or saves?
No. A driver or Mesa downgrade changes system packages only; your Steam library, Proton prefixes and save files live in your home directory and are untouched.
How do I stop the updater from reinstalling the broken driver?
Hold or pin the working version with your package manager: a hold on Debian and Ubuntu family systems, a version lock on Fedora, or the ignore list on Arch. Remember to lift the hold once a fixed release appears, or you will fall behind on later fixes.
The screen is black and I cannot log in at all. Where do I start?
Start at the boot menu and select the previous kernel, the recovery path that needs no working graphics. If the desktop appears there, you have a diagnosis and a working machine to roll back from. If every kernel fails the same way, boot rescue media and restore the snapshot or image you kept.
My AMD card got worse after a kernel update, not a driver update. Is that the same thing?
Usually, yes. On AMD and Intel hardware the kernel component of the graphics driver ships inside the kernel package, so booting the previous kernel is the correct first rollback for those systems, ahead of any Mesa downgrade.
Final verdict
A bad GPU driver update on Linux is reversible at every layer: prove the driver is guilty, test the previous kernel, then downgrade the package set as a matched group and pin the version that works. NVIDIA owners reverse through package history, AMD and Intel owners through Mesa packages and kernels, and Flatpak users through the runtime. The deeper lesson is procedural: snapshots before updates, one known-good kernel always kept, rescue media in the drawer and an image on an external drive turn the next bad driver into a short, boring procedure.











