Not his exploit, but 17k stars went to him: how gpu-unlock turned a firmware bug into "nearly 2x faster after one install"

A Linux kernel module that tells the owners of millions of RTX 3090 and 4090 cards: NVIDIA shipped your GPU with its AI speed cut in half, and this fixes it. The exploit was published by someone else months earlier, and the author himself said on Hacker News, "These exploits aren't my ideas." Yet in 19 days it was he who collected 17,130 stars and 1,720 forks (GitHub, 11-06). This piece covers why it worked, and what you can still take from it.

A tweet with 250k views

On 2026 Oct 21 13:10 (UTC), X user Alexey Fateev (@superalesha) posted:

My 3090s just got 1.9x FASTER at BF16 tensor math!!! Same cards, same driver, same 300W, one Linux kernel module.

("My 3090 runs BF16 tensor ops 1.9x faster! Same card, same driver, same 300 watts, one Linux kernel module.") Below it he listed four 3090 results: BF16 tensor 82 → 155 TFLOPS, TF32 41 → 79. He didn't just brag. In the same thread he honestly noted that real large-model prefill only sped up 10–12%: "Less than I expected, I was wrong." By 11-06 the tweet had 250k views. Two days later he posted a call to action: "Dear NVIDIA, the 30 series is six years old, you no longer make them, it's time to hand them fully to the community."

The "one Linux kernel module" in that tweet was Zagitta/gpu-unlock. The repo had been created only 3 days earlier, with 44 stars, and its description was a line only insiders could parse: "FP/BF16 instruction issue rate on Nvidia 3000's cards".

What it is

The operations GeForce cards most often use for AI (FP16/BF16/TF32, accumulating in FP32) had their tensor cores throttled to half speed. The same chip sold as the RTX A-series professional card runs at full speed. gpu-unlock, at boot and before the NVIDIA driver loads, exploits a stack overflow in a firmware blob that NVIDIA itself signed to change that throttle bit.

Usage takes three steps: git clone, make install, and add one line to the kernel boot parameters: gpu_unlock.targets=all. No driver changes, no GPU BIOS flashing, and no rework when NVIDIA releases new drivers. Packages exist for Arch, Debian/Ubuntu, and Fedora, and it re-unlocks automatically after suspend and resume.

The README numbers: RTX 3090 BF16 goes from 75 to 125 TFLOPS, 4080 from 104 to 193. In real workloads, local large-model prefill is 25–55% faster, image generation is 30–55% faster, and fine-tuning is 25–50% faster. Token-by-token decode for large models, quantized models, and gaming see no change. It now supports three RTX 20/30/40 generations: the 30 series is marked "Stable, 100+ user reports", the 20 and 40 series are marked "Experimental", and RTX 50 is not supported, with the author saying "probably never will be."

The exploit is public, so why does the traffic land here?

The origin of this exploit is clear: in 2026 June, Jon Pry published a paper on Zenodo disclosing this stack overflow in the firmware of the NVIDIA mining card CMP 170HX. Others later used it to unlock the mining cards' VRAM, and LTT Labs reported on it in September. By October, "this bug can unlock NVIDIA cards" was known in local AI circles, but nobody had made it usable for ordinary GeForce users.

Zagitta's words on HN: "None of these exploits were my idea. I just packaged the whole thing into something far easier than patching the NVIDIA driver." That line is the answer. It won on these points:

It was the first that "works on install." Earlier approaches either only covered mining cards, required patched drivers, or needed a USB stick to boot from UEFI. This one is a single make install. Someone on HN tested it and said "it's real"; others failed to install on 5.15 older kernels and had Claude Code patch a few spots to get it running, but nobody called it hard to use.

The name is the category word. The repo is called gpu-unlock. Later media, tutorials, and compilation projects that mention this all treat it as the "original". The README's first FAQ item reads: "This is the only legitimate source of gpu-unlock. The website, coins, and installers have nothing to do with me." So many knockoffs that a debunk was needed, which shows the name had already become valuable.

Jargon turned into plain language. The description changed from that insider jargon to "Your GeForce runs AI at half speed. This fixes it.", paired with a per-card before/after table. The 10-28-million-follower X account 0xMarioNawfal, which shared the news, basically copied that line.

Pulling forks back in. 10-23 someone made gpu-unlock-ada, a version for the 4090 series (now 4.8k stars), and someone else made a port covering only the 20 series. 10-27's 2.0 version restructured everything as "one recipe per card" and merged the 20 and 40 series into the main repo. All three generations live here, so others' work didn't split off its traffic.

Getting users to run its tests. The issue template is specifically for compatibility reports, and the "real workload" numbers in the README are explicitly sourced from those reports. Benchmarks users posted became material for the next round of news.

How the stars grew day by day

(Daily stars from GitHub, dated by that day's snapshot)

A few takeaways. The tweet itself didn't bring many stars; in the 250k-views days, the repo gained only dozens a day. What pushed the curve up was the HN front page, followed by hardware outlets all covering it, one step per day. The whole chain ran X benchmark post → r/LocalLLaMA → HN → hardware outlets → big X accounts, YouTube "is it real" tests, and tutorial sites. No paid promotion is visible.

The HN comments are worth reading because they also spell out the project's ceiling. Someone ran vLLM across four 3090 cards and saw only 7–8% overall; someone said 3060 training got about 6% faster, capped by the 170-watt power limit; someone warned you need to raise it to 450 watts to use it fully, and stock cooling can't handle that. One commenter put it bluntly: "The next generation will surely block this with signed firmware."

Who it's competing with

The exploit is public, and over two weeks in late October more than a dozen repos appeared on GitHub:

There's also an ad-laden tutorial site, gpuunlock.org, capturing search traffic. The original author wrote in the FAQ, "I don't use Windows and don't plan to maintain it," and the Windows gap has already been filled by physicsdolphin and windows-GPU-UNLOCK.

If it were you

C. This project itself can't be carried forward: the Linux slot is already taken, Windows is claimed by others, and the RTX 50 author himself says it can't be done. A dozen-plus outlets have covered it, there are plenty of copycat repos, the buzz is fading, and NVIDIA could block it at any time. What's worth taking is the playbook: the exploit went public, ordinary users still couldn't use it, the missing piece was packaging, and whoever packaged it well took most of the stars.

Who it suits: developers who watch sources where research first appears, such as HN, arXiv, security conferences, and Zenodo; who can turn a PoC into something installable with one command; and who have the hardware on hand to test it.

Who it doesn't suit: anyone wanting to make yet another unlocker in this wave (the space is already crowded); anyone who hasn't worked with kernels, firmware, or drivers (a mistake can black out someone else's card); and anyone who cares about warranties and legal disputes.

How to do it:

1. Find the next thing where "the paper is out, nobody has packaged it." Hardware limits, model inference speedups, privacy or jailbreak techniques all count. The test is the same as for gpu-unlock: the audience already owns that hardware or software, packaging gets them the benefit at zero cost, and the benefit can be stated as a single number.
2. On day one, do these four things it did: name the repo with a category word; write the description as a plain-language statement of what users lose ("your X only runs at half"); put a before/after table at the top of the README; and make the issue template collect compatibility reports only.
3. Absorb forks once they appear. When someone else covers a model or platform you don't, merge it into the main repo, credit them by name in the README, and don't give up the "official" position.

How to get users: first have someone with real hardware post a benchmark (on X or a vertical community like r/LocalLLaMA), with concrete numbers and the bad news included, which makes it more credible; the HN front page is the step from a few hundred to tens of thousands of stars, so the author has to answer questions in the comments personally; after that, hardware and tech outlets come to you on their own, and your job is to make the README numbers easy for them to copy.

Deadline: this kind of opportunity moves in weeks. This one went from tweet to peak in just 5 days. First ports that came 2 to 5 days late got only a fraction of the original's traction.

Misread: ① A project built on the same playbook after the benchmark posts still couldn't get onto HN and got under 500 stars in a month. That suggests gpu-unlock's stars came from the "NVIDIA deliberately cuts your card in half" anti-big-company angle, and the packaging layer wasn't worth much. ② NVIDIA patched it quickly via driver or firmware, and the press turned it into "unlocking is risky." That shows these projects get stars fast but don't keep their reputation.