Two small additions to make it easier for readers to find their way back
to the GitHub side of the project (stars, Discussions, PRs):
- overrides/main.html: site-wide announce banner with links to the repo
and Discussions. Uses Material's announce block, dismissable by the
reader once they've seen it
- mkdocs.yml: enable custom_dir for the override and add
announce.dismiss to theme features
- docs/index.md: replace the brief Contributing paragraph with a
Get Involved card grid (Star, Discussions, PRs, Issues). Sits on the
home page where most first-time visitors land
No content changes outside of these blocks.
Document the modded and stock BIOS files that are publicly hosted in
community repos, with hashes cross-verified across multiple independent
sources (TuxThePenguin0 GitLab, forgenam, MrrZed0, csabakecskemeti,
scrakcho, tipitochen, kenavru).
- flashing.md: replace the vague "Stock BIOS Sources" section with a
proper table of sources + SHA256 for every publicly hosted file
- flashing.md: rewrite the P5.00_clv note to reflect reality (Discord-only,
no public hash, get two independent copies and compare before flashing)
- recovery.md: replace the "compare with known-good hash from community"
placeholder with the actual table, and link back to flashing.md
- recovery.md: correct file-size note (all known BC-250 BIOS files are
exactly 16 MB, not 8 to 16)
Refs #17.
- flashing: soften "essential" wording, point at fanoush/bc250_memcfg for VRAM-only use case (#21)
- vram: add "From Linux" section documenting bc250_memcfg as an alternative to BIOS flashing (#21)
- debian: drop unsourced prebuilt-image claim (#22)
- kernel: document the 40 CU unlock patch (CachyOS PR #159) as experimental (#23)
In my testing while using Bazzite, I always had consistent micro-stutters (every couple of seconds) while playing the least demanding of 2D games.
Disabling the governor had no impact, stuttering continued. Later in my testing, I identified Bazzite's Handheld Daemon as the root cause of this stuttering. The journalctl revealed that the process kept failing and restarting. Disabling it fixed the micro-stuttering completely. This proposed solution informs users to disable this software to fix the micro-stutters.
Key fixes:
- nct6687 for fan control (not nct6683 which is read-only)
- GPU is card1 not card0 in all sysfs paths
- Fan on pwm2/fan2 (Pump Fan header), not pwm1
- Vulkan 1.4.328 (not 1.3), Mesa 25.3.6 (not 25.2.4)
- cpupower doesn't work on BC-250 (removed recommendations)
- pp_dmu_clock -> pp_dpm_mclk
- ACPI fix marked as optional/experimental (not essential)
- amdgpu.sg_display=0 only needed for kernels < 6.10
- GPU voltage range 700-1129 mV (from OD_RANGE)
- Added CoolerControl installation instructions
- Expanded sensors.md with proper nct6687 setup guide
- display.md: DisplayLink unreliable (latency, no game mode), DP MST max 2 screens
- cooling.md: 3 heatsink variants (QR code = 9-row), thermal pads 1.5mm front/2.0mm back
- distributions.md: Ubuntu 26.04 daily server ISO works out of box
- radv.md: LLM headless mode tip (~14.2GB available VRAM, headless saves ~800MB)
- stability.md: P5.00 BIOS more susceptible to bricking from memory timing;
tREF most rewarding timing, GDDR6 ICs are bottom-binned Micron
Troubleshooting and overclocking sections now show cyan-skillfish-governor-tt
as primary example with oberon-governor as alternative comment. Oberon-specific
sections (config, build-from-source, iostream fix) left as-is.
- Replace oberon-governor with cyan-skillfish-governor-tt as default across
bazzite, debian, arch, cachyos, fedora, power, quick-reference, display,
performance, radv, and stability pages (oberon remains documented as legacy)
- Add "Black Screen on GPU Reset (Governor Running)" section to
troubleshooting/stability.md (source: Discord user nohanmv, Feb 26)
- Remove AI filler: "comprehensive" from index/sensors, unverifiable stats
(3500+ members, 100+ solutions, 30+ games, 9716/7000+ messages analyzed,
90%/95% success rates)
- Remove unverifiable 8K @60Hz display claim
- Update governor config examples from oberon YAML format to
cyan-skillfish-governor-tt TOML format
- Normalize community links to point to filippor/cyan-skillfish-governor
Update default governor commands to cyan-skillfish-governor-tt in
quick-reference cheatsheet and stability troubleshooting diagnostic section.
Oberon-governor noted as alternative where applicable.
- Remove oberon-governor as "Option 1 (Recommended)" from performance
troubleshooting, replace with cyan-skillfish-governor-tt
- Remove stale RADV_DEBUG=nocompute advice (deprecated in Mesa 25.1+)
- Update checklist and system info commands to reference current governor
- Remove unverifiable PS5 comparison percentages from gaming page
Discord criticism (astrocast): "VRAM configuration section is SO verbose its
a little absurd, its like when you gotta reach a word limit for an essay"
- Remove 3 redundant recommendation-by-use-case tables from VRAM page
(info already covered in each option's description)
- Remove FAQ section with trivially obvious answers
- Remove power consumption impact table (duplicated from config options)
- Remove PSU efficiency filler section from power page
- Remove DIY cable-making and ATX shorting sections (excessive padding)
- Remove old oberon-setup.sh script from quick-start (conflicts with
cyan-skillfish-governor-tt install instructions above it)
- Remove unverifiable performance target numbers from quick-start
- Update troubleshooting to reference cyan-skillfish-governor-tt
- Tone down backplate VRAM cooling from DANGER/required to info/recommended
(community: "ram cooling nonsense" — akxfile, Dec 2025)
- Remove oberon automated setup as primary install method on bazzite page
Discord criticism: oberon-governor references are outdated, cyan-skillfish-governor-tt
is the community standard. Removed duplicate oberon config examples from overclocking
page, removed contradictory dual-"Recommended" labels from governor page, updated
verification section to default to cyan-skillfish-governor-tt.
Second pass cleanup:
- overclocking: remove fabricated FPS numbers, restructure to lead with
governor install, remove bloated cooling/PSU tables, add community refs
- vram: 512MB is not universally best — some games need 4-8GB static
- cooling: tone down VRAM backplate alarmism (recommended, not critical)
- power: 6-pin works fine for most setups, not just 8-pin
- quick-start: match toned-down backplate cooling language
- Update recommended launch options: nohiz instead of nocompute
- Clarify nocompute is no longer needed on Mesa 25.1+
- Update best practices to reflect current Mesa state
- Add explicit note that HW video encode/decode doesn't work (VCN firmware blocked by Sony)
- Add danger warning about Smokeless_UMAF causing permanent damage
- Add note that Bazzite already includes the frequency range patch
- Add note that SMU governor bypasses kernel patching on all distros
- Add explicit 700mV minimum voltage warning (locks GPU otherwise)
- Add Smokeless_UMAF warning to "Do NOT" list
- arch.md, debian.md: correct sensor module from nct6687 to nct6683 with
force=true (consistent with other guides)
- bazzite.md: clarify that standard Bazzite kernel already includes GPU
frequency patch as of early 2026, custom images only needed for extra
optimizations
- Replace oberon-governor with cyan-skillfish-governor-smu as recommended
option (no kernel patch needed on CachyOS)
- Add TT governor as alternative requiring kernel patch
- Mark oberon-governor build-from-source as legacy option
- Fix sensor module from nct6687 to nct6683 with force=true
- cooling.md: correct to nct6683 with force=true for sensor readings
- bazzite.md: document both nct6687 (PWM control) and nct6683 (read-only
sensors) as valid options depending on use case
- Add warning that performance mode rebase can kill WiFi drivers (issue #10)
- Update SMU governor from "emerging" to established alternative
- Add nct6683 alternative for sensor module (per mothenjoyer69's docs)
- Note both nct6687 (PWM control) and nct6683 (read-only) options
- cyan-skillfish-governor → cyan-skillfish-governor-tt (service names and
config paths throughout overclocking, power, and troubleshooting docs)
- Update TTM page pool parameters to 3959290 for correct 14.75GB VRAM
- Add SMU governor variant to AUR install instructions
- Clarify 700mV minimum voltage behavior (locks GPU to 1500MHz)
- Update SMU governor description from "emerging" to established
- Fix ttm.pages_limit and ttm.page_pool_size: 3776000 → 3959290
(per mothenjoyer69's docs for >8GB shared memory)
- Add note that Bazzite already includes the frequency range patch
- Add note that SMU governor bypasses kernel patching entirely
- Clarify manual patching only needed for TT governor on non-Bazzite distros
- Fix Oberon Governor URL from TuxThePenguin0 to mothenjoyer69 in power.md
- Add zswap as alternative to zram in performance troubleshooting, with
Bazzite-specific setup commands from community Discord (Dec 2025)
Rebasing to patched Bazzite images can remove USB WiFi drivers since the
BC-250 has no built-in wireless. Added prominent warnings to bazzite.md
performance section and prerequisites.md with recovery steps.
- Fix service name: oberon-governor.service → cyan-skillfish-governor-tt.service
(matches the package actually being installed)
- Promote SMU governor from "emerging" to recommended alternative
- Add essential ACPI fix warning
- Update verification commands to match installed governor
Added section documenting the bc250_smu_oc tool (Dec 2025) for CPU
overclocking/undervolting via SMU reverse engineering. Also corrected
the memory overclocking status — a community Mem Timing Utility exists.
The broken kernel range is 6.17.8-6.17.10, not 6.17.8+ — kernel 6.17.11+
has the fix applied. Updated 11 files to use the precise range and added
6.17.11+/6.18.x as recommended alternatives. Also added a warning about
6.19.x PCIe issues reported in March 2026.
