mirror of
https://github.com/elektricM/amd-bc250-docs.git
synced 2026-07-18 09:51:31 +00:00
f3ce50f13fcd80cd882d51184af35bec8ecf0fad
Trimmed AI-flavored structure from docs/contribute.md and CONTRIBUTING.md: removed the Discord vs Documentation comparison table, merged the High Priority / Also Welcome buckets into a single What is Most Useful list, dropped the duplicate closing exhortation that appeared at the bottom of both files. Added a Pull Request Guidelines section to both pages covering: commit prefix convention (docs/fix/feat/chore, no subscope), one logical change per PR, hardware-verified claims, source attribution for non-obvious claims, cross-reference over duplication, and PR title matching the commit subject.
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, Alpine, 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
- Community cases catalogue - 145 case/enclosure designs, searchable and filterable
- System configuration - GPU governor (cyan-skillfish-governor-smu recommended), 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 3,500+ members)
- BC250 GitHub repository
- Last Updated: March 2026
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.gg/8eZfFWhczz - but please document your solutions here!
License
- Documentation: CC BY-SA 4.0
- Code: MIT
Built with MkDocs and Material for MkDocs
Languages
HTML
100%
