The newcomer's bible for the ASRock AMD BC-250 — a PlayStation 5-derived APU board (Cyan Skillfish / Oberon, 6-core Zen 2 + RDNA 2, 16 GB GDDR6) repurposed as a cheap Linux gaming & AI mini PC — a DIY budget Steam Machine.
Everything you need to go from a board in a box to running games — curated from 130k+ messages of the BC-250 community, ranked by what people upvoted and pinned, and cross-checked against the canonical project repos.
🌍 English · Русский · Українська · Қазақша · Кыргызча · Español · Português (BR) · Français · Deutsch · Polski · Türkçe · 中文 · 日本語 · العربية · हिन्दी
Maintained · last updated August 2026 · llms.txt for AI agents
- What is the ASRock AMD BC-250? A PlayStation 5-derived APU board — 6-core Zen 2 + 24/40 RDNA 2 CUs ("Cyan Skillfish"), 16 GB GDDR6 — sold cheap as an ex-mining card and repurposed into a Linux gaming & AI mini PC, a DIY budget Steam Machine.
- How much does it cost? Around $60–130 for the bare board; a full build (PSU, cooler, SSD) lands near $150–250. See Buying.
- How well does it game? Roughly 1080p 60 FPS in most titles (RX 6600-class) with FSR / Frame-Gen and a GPU+CPU overclock. See Gaming results.
- Which OS? Linux only for GPU acceleration — Bazzite, Fedora, CachyOS or Arch with Mesa 25.1+. There is no Windows GPU driver. See Linux setup.
- Can it run LLMs? Yes — llama.cpp / Ollama over Vulkan use the 16 GB GDDR6 as VRAM (~30–47 tok/s on small models). See AI / LLM.
- How do I cool it? The stock server heatsink throttles on a desk; thin the fins and add a 120 mm fan, or go water. See Cooling.
New board, know nothing? Follow the golden path in order:
docs/en/00-start-here.md — Buy → Power → Cool → Install OS → Drivers → Overclock → Play.
Every knob on this board trades something. These are the four that matter, drawn from what the community measured — read them before you flash anything.
Those five points are measurements, not a model: going from 1800 to 2000 MHz costs about 90 W — roughly what the previous 600 MHz cost — and pushing 960 mV to 1025 mV buys nothing but 2 W of heat. At 350 W a 300 W supply trips within 30 seconds and the +12V rail is carrying 26 A.
Idle power — why the wall meter barely moves
The governor and undervolt cut the GPU, but the CPU and GDDR6 keep drawing regardless. Until auto-suspend kicks in, the wall meter hardly notices. High-leakage batches floor out around 70–80 W.
Source data: assets/diagrams/data.json · rebuild with node assets/diagrams/build.mjs
| # | Section | For |
|---|---|---|
| 01 | What Is the BC-250 | specs, sizes, pinout, expectations |
| 02 | Buying Guide | where, price, risks, group buys |
| 03 | Power Supply | LOP / Flex ATX, 8-pin pinout, wiring |
| 04 | Cooling | heatsink, fan shrouds, test method |
| 05 | Cases & 3D Printing | printable cases catalog (STL) |
| 06 | Linux Drivers & Setup | distro choice, amdgpu, install |
| 07 | Windows Drivers & Setup | driver status, how-to |
| 08 | BIOS & Brick Recovery | mod BIOS, flashing, un-brick |
| 09 | Overclocking & Undervolting | governor, SMU, 40CU unlock |
| 10 | WiFi & Bluetooth Dongles | dongles that actually work |
| 11 | Gaming Results & Settings | benchmarks, per-game tuning |
| 12 | AI / LLM on BC-250 | llama.cpp, ROCm |
| 13 | macOS / Hackintosh | status |
| 14 | Display & Output | DisplayPort, DP→HDMI adapters, dual screen |
| 15 | Emulation | every console/platform, realistic status |
| 16 | USB, Hubs & Storage | hubs, 5V mod, M.2 / SATA adapters |
| ❓ | FAQ · Troubleshooting | common problems |
Canonical community projects, ranked by how often the community pointed to them.
- mothenjoyer69/bc250-documentation — the main hardware reference (reverse-engineering)
- elektricM/amd-bc250-docs · site — comprehensive community docs (pinouts, per-distro, troubleshooting)
- AMD-BC-250/documentation — organization documentation
- kenavru/BC-250 — builds and scripts
- mothenjoyer69/oberon-governor — the governor most builds run (sets clocks and voltage)
- ZEROAESQUERDA/PS5GPU-BC250 — oberon-governor fork with a Linux GUI
- bc250-collective/amd_smu_reverse_engineering
- bc250-collective/bc250_smu_oc
- filippor/cyan-skillfish-governor · bc250-collective fork
- rw-r-r-0644/bc250-core-unlock — unlock the 2 disabled CPU cores (stock mask 0x77; a 0xB7 mask means physically defective cores — forcing it gives artifacts and crashes)
- duggasco/bc250-40cu-unlock — unlock all 40 CUs
- WinnieLV/bc250-cu-live-manager
- alexghow903/oberon-governor-atomic
- redbeard1083/bc250-toolkit — menu-driven setup for CachyOS: kernel, CPU/GPU governors, swap, ZRAM→ZSWAP, ACPI and boot tweaks
- 62fixolab/Latest-Bazzite-AMD-BC-250-Patched-Images — prebuilt Bazzite Deck/GNOME/KDE images with the BC-250 patches applied
- ZEROAESQUERDA/BC250-windowsDriverTest — Windows GPU driver (experimental, no full acceleration as of early 2026)
- Keshas-dev/AMD-BC-250-PSP-Driver — PSP and GPU driver development
- DryhoppedIPA/bc250-gfx1013-fix — kernel + Mesa/RADV patches for the broken GPU compute queue (async compute); also fixes the FSR 4 / XeSS 3 INT8 path
- MastaG/linux-cachyos-bc250 — CachyOS kernel with BC-250 cherry-picks
- AMD-BC-250/kernel.opensuse — Linux kernel
- TuxThePenguin0/bc250-bios — most-referenced BIOS images and mods
- TheRetroWeb — BC-250 BIOS database — stock BIOS dumps, browse/download by version
- Forbidden-Darkness/AMD-BC-250-UEFI-v2.2-Firmware-Menu-Script — menu-driven firmware backup and custom-firmware flashing
- See docs/en/08-bios.md for flashing and brick recovery
- onemorecap/bc-250-sleeve-adapter · bc-250-shell-case
- Printables & MakerWorld — see docs/en/05-case.md
This is a living repo. Knowledge is extracted from the community chat by a reproducible pipeline (see CONTRIBUTING.md) and re-run on new exports. PRs with fixes, new dongles, new cases, verified commands welcome.
Docs: CC-BY-SA-4.0. Scripts under assets/scripts/: MIT. Mirrored third-party firmware/drivers retain their original rights — see assets/firmware/DISCLAIMER.md.
The entire BC-250 community — see CREDITS for the top contributors who made this handbook possible. Source: the AMD BC-250 community chat. Project authors credited by their repo handle above.
