PS5 Linux Lead Quits Over LLMs: How to Run It Now

The LLM blame game is missing the real break

Most takes on the PS5 Linux lead quitting over “a bunch of noobs using LLMs” that “they don’t understand” treat it as culture-war bait. I don’t. Private vulnerability holding for community benefit collapses when AI drops the skill floor and bug-bounty cash is one report away.

You’re on a disc PS5 or Slim still running 3.00-7.61. You saw the GTA V ray-tracing demos, you wanted a living-room Steam box, and TheFloW (Andy Nguyen) just walked – on or around 15-16 September 2026, per his posts and the write-ups that followed. This is the path that still works. Not another quote dump.

What you’re booting (and why the quit hurts)

Eight Zen 2 cores / 16 threads up to 3.5 GHz. RDNA 2 GPU to 2.23 GHz. 4K60 HDMI. That is the silicon ps5-linux-loader hands you when it chains patched hypervisor bugs into a real Linux userspace – Ubuntu images are the documented happy path; the stock FreeBSD-based OS stays on the internal SSD. Specs and port notes come straight from the official loader README (as of the v2.5 tree).

Pro work aimed at 2027 is dead from the original lead. Last build he shipped: v2.5. He had held what he called the final useful HV bug to keep a window around GTA 6 and leave room for Pro. People found the same bug independently – Al Azif said as much – and after a brief agree-to-wait, the report went to Sony the next day. VideoCardz and Frandroid carried the same arc: GPL-3.0 code stays public; the timeline he was protecting does not.

Freeze a console on supported firmware. Treat v2.5 as the stable base. Forks already exist.

Practical setup: boot Linux on a supported PS5 right now

Settings → System → Console Information. You need Phat or Slim on 3.00 / 3.10 / 3.20 / 3.21 (no M.2) or 4.00-4.51 / 5.00-5.50 / 6.00-6.50 / 7.00-7.61 (M.2 OK), matching the v2.5 README lists. No downgrades. Kill automatic updates now.

1. Rest Mode USB power: Settings → System → Power Saving → Features Available in Rest Mode → Supply Power to USB Ports → Always. Disable HDMI Device Link.
2. Flash a pre-built image (ps5-ubuntu2604.img.xz is the README-oriented pick) to 64 GB+ USB – external SSD preferred – with dd or Balena Etcher. Boot only from front-bottom Type-C or rear Type-A.
3. Jailbreak path splits by firmware. 3.00-5.50: umtx2 + fakedns/host aimed at manuals.playstation.net, PS5 primary DNS to your PC, open User Manual. 6.00-7.61: Y2JB, then lapse.js.
4. Loader send: socat -t 99999999 - TCP:$PS5IP:9021 < ps5-linux-loader.elf (v2.5 release or self-built). Console drops to rest mode. Orange LED goes solid, then you power on. White LED means Linux landed.

Orange still blinking when you hit power? You jumped early. Stock OS. That is the whole signal story – white is success; anything else is a redo.

First boot is boring on purpose: password you will remember, kill the flaky screensaver, toggle wired/WLAN if the stack is dead. Then lock the custom kernel so a casual apt upgrade does not yank it:

sudo apt-mark hold linux-generic linux-generic-hwe-24.04 linux-generic-hwe-26.04 linux-image-generic linux-image-generic-hwe-24.04 linux-image-generic-hwe-26.04 linux-headers-generic linux-headers-generic-hwe-24.04 linux-headers-generic-hwe-26.04

Clone ps5-linux-tools and build it before you chase FPS. One binary covers fan curves, CPU/GPU boost, and M.2 helpers. Fan on first, boost second – same order the stock OS respects, and the difference between a warm Steam session and a thermal crawl.

Advanced usage after the lead walked

Desktop up. Refresh Mesa from whatever channel your image docs recommend, install a browser, confirm Ethernet before you debug Wi-Fi. Steam, Proton, emulators – earlier public runs already showed GTA V Enhanced with ray tracing at 60 fps. Plan on 60 Hz output for now.

M.2 is how the softmod stops feeling like a USB ritual every week. Format the drive on the PS5 first if it ever held games. Boot Linux from USB, run sudo ./m2_init from the tools, reboot, then sudo ./m2_install.sh --install /path/to/img. Later entries go through m2_exec.sh. Want root on the SSD? Point cmdline.txt at the ubuntu2604-m2 label. You still keep a small FAT32 USB for the early loader stage – that part does not vanish.

cd ps5-linux-tools
sudo ./ps5_control --fan on
sudo ./ps5_control --boost on

Watching Discord and GitHub issues after the announcement felt like a research lab filling with people who could paste a prompt but could not explain a single gadget. The models did not invent the bounty incentive. They just made the path trivial.

Honest limitations now that TheFloW is gone

The catch is persistence: this stays a softmod on the USB path. Every cold boot means jailbreak + payload again. Internal SSD stays untouched – good for stock games – but zero persistence without the M.2 workflow above.

etahen or kstuff left enabled? Handoff freezes. Disable them before you send ps5-linux-loader.elf (README troubleshooting, not folklore).

Black screen on some monitors: strip a bad video= line or add amdgpu.force_1080p=1 in cmdline.txt on the FAT32 partition. Capture EDID if you need help. Do not mash power while orange is still blinking; that is how you bounce to stock.

But here’s the part that bites long-term. The reported “last” HV bug is with Sony. Any fix firmware – and anything a GTA 6 release might force – closes this chain. Stay offline or block updates if you care about the current window. Original-lead Pro support is gone. Whether a fork reaches it is the community’s problem now.

If you use an LLM on this code, treat it like a search engine that lies with confidence. Read every offset, every shellcode comment, every gadget yourself. That failure mode is exactly what Nguyen called out – and what burned the private bug.

Will a fork restore Pro-class work without repeating the same disclosure mess? Open question. The license allows the attempt; the incentive structure has not improved.

FAQ

Does the existing PS5 Linux still work after the quit?

Yes. Phat/Slim on 3.00-7.61 with public v2.5. Repos did not vanish.

Can I still play PS5 games after installing Linux?

Yes. Linux sits on USB or a dedicated M.2. Power on, re-run the chain, pick the environment. Block firmware auto-update or you own the brick of the feature set – not the NAND wipe, the window close.

Is using ChatGPT or other LLMs for PS5 reverse-engineering automatically “slop”?

No. Shipping or reporting what you do not understand is. Nguyen’s complaint was never “AI exists.” It was hypervisor work generated without grasp of side effects, then cashed as a bounty, collapsing a multi-year community timeline. If a model drafts a patch, you own the review, the test matrix, and the disclose-or-hold call. Skip any of those and you are the example in the next resignation post.

Tonight: read your exact firmware, pull the v2.5 elf plus an Ubuntu image, freeze the console before the next Sony push. The window is open – narrower than last month.