mirror of
https://github.com/elektricM/amd-bc250-docs.git
synced 2026-07-18 05:11:25 +00:00
6a396a70ed
Fixed multiple issues identified by DeathStalker and Astrocast: Hardware corrections: - FSP500 model: FSP500-30AS (not FSP500-50FGBBI) - Board length: 340mm/310mm (not ~200mm) - Added Arctic P12 Pro to cooling (more available than Max) - Power draw: Can exceed 235W with GPU frequency patch GPU comparisons: - Standardized to GTX 1660 Ti (removed inconsistent 3060 Ti refs) VRAM allocation: - Clarified 512MB setting is DYNAMIC (not a limit) - Can allocate nearly full 16GB to GPU (~14GB+) Software updates: - Fedora 42/43: nomodeset no longer needed with working kernels - COPR repos available for governors (Fedora/Bazzite) - Added SteamOS to distro list (Mesa now updated) - Added Ubuntu to supported distros Thanks to DeathStalker and Astrocast for detailed feedback.
AMD BC250 Documentation
Comprehensive, community-driven documentation for the AMD BC250 board.
📖 Read the docs: https://elektricM.github.io/amd-bc250-docs/
✏️ Contribute: Found a solution? Add it to the docs so everyone can find it! See CONTRIBUTING.md
What's Included
- Linux setup guides for 7+ distributions (Fedora, Bazzite, CachyOS, Arch, Debian, etc.)
- BIOS flashing and configuration (including GPU frequency patch)
- Hardware specs - power requirements, cooling, display compatibility
- Troubleshooting - boot issues, performance problems, stability fixes
- Gaming compatibility - tested games, settings, FPS data
- Driver setup - RADV configuration, environment variables
- System configuration - GPU governor, sensors, power management
Building Locally
# Install dependencies
pip install mkdocs-material
# Serve locally with live reload
mkdocs serve
# Build static site
mkdocs build
The site will be available at http://127.0.0.1:8000/
Content Sources
Built from:
- BC250 Discord community (9,716 technical messages from 1000+ members)
- BC250 GitHub repository
- Last Updated: November 21, 2025
Contributing
Please contribute your knowledge! Instead of posting solutions in Discord where they get lost, add them to the documentation:
- Easy way: Click "Edit on GitHub" on any page and submit changes
- Report issues: Found wrong info? Open an issue
- Full guide: See CONTRIBUTING.md for detailed instructions
What we need:
- ✅ Tested hardware configurations
- ✅ Game compatibility reports
- ✅ Troubleshooting solutions you've found
- ✅ Distribution-specific setup steps
- ✅ Fixes for outdated information
Join Discord: https://discord.com/invite/uDvkhNpxRQ - but please document your solutions here!
License
- Documentation: CC BY-SA 4.0
- Code: MIT
Built with MkDocs and Material for MkDocs