I ported Linux to the PS5 and turned it into a Steam Machine
Exploit, Firmware, and Practicality
- Linux currently requires a full exploit chain (e.g., Byepervisor) and only works on very old PS5 firmware (around 1.xx–2.xx).
- Latest firmware users likely cannot do this; one commenter notes if a console isn’t on 2.x or below, “he is out of luck.”
- There is mention of a separate userland-only exploit on newer firmware, but it does not provide kernel-level control needed for Linux.
Dual-Boot and Access to Original OS
- People ask whether Linux can coexist with the stock PS5 OS so they can still play their PS5 library.
- The thread does not provide a clear answer or confirmed dual‑boot setup. This remains unclear.
GPU, BC‑250, and Porting Details
- The PS5 uses a custom AMD GPU broadly similar to RDNA2 but reportedly missing some RDNA2 features (e.g., mesh shaders; closer to “RDNA1+RT”).
- A mining board (BC‑250) based on binned PS5 APUs was sold cheaply; prior work on running Linux and AMDGPU/Mesa on this hardware heavily enabled the PS5 port.
- Mesa support for PS5 reportedly hinged on a tiny change (GPU ID range), though people note kernel/platform patches are also needed for PS5’s custom I/O and SuperIO.
Use Cases: Gaming, Media, AI, and Clusters
- Enthusiasm around turning PS5 into a “Steam Machine,” media server, or general Linux box.
- Some ask about running AI models and leveraging the 16 GB shared memory; replies say unified memory alone doesn’t make it a great LLM platform compared to cheap GPUs.
- Historical PS3 supercomputing clusters (e.g., Air Force use) are discussed; opinions differ on whether similar PS5 clusters are likely or practical now.
Locked-Down Hardware, Ownership, and Business Models
- Strong debate over whether it’s “sad” that running your own software on your own hardware is noteworthy.
- One side: consoles are sold at or below cost and subsidized by game licensing, so locking them down is economically rational and expected.
- Other side: PS5 is architecturally a general-purpose computer, and restricting user software is seen as harmful lock‑in and an erosion of computing freedom.
Security, Liability, and DRM Justifications
- Pro‑lockdown arguments: open platforms increase attack surface, malware risk, and reputational damage from users bricking devices.
- Critics argue this is mostly a pretext for profit and control; they note PCs and older phones allowed custom OSes without “the world burning.”
- Some point to liability and certification (e.g., UL) as a partial driver, but others say lock‑down primarily serves vendor business interests.
Hacker Culture and Accessibility
- Many celebrate this as classic “hacker spirit”: making single‑purpose devices do unintended things.
- Others lament decreasing access to open hardware (consoles, IoT, appliances, tractors, 3D printers) and the loss of outlets like big electronics stores.
- There’s disagreement over whether hacker culture has declined or just shifted (more software‑focused, more startup/“build to sell” mindset).