No power or no fans.
- Disconnect mains before checking cables. Verify the correct PCIe/GPU 6+2 lead is fully seated at J1000.
- Confirm the ATX PSU startup control. Plugging in a supply alone may not start it; the Apevia compact model has no rear switch.
- Check AUTO_PWRON1 against the original board documentation. PSU startup and board startup are separate.
- Verify fan power. J4003 is signal-only; it cannot power the fans.
Do not keep attempting a boot without working cooling. Use the wiring checklist to work through the whole route.
No picture.
- Select the correct monitor input and check both ends of the cable. Try native DisplayPort if available.
- DP-to-HDMI adapters are directional. The board is the DisplayPort source; the display is the HDMI destination.
- Try a lower-resolution display or another known-working cable. A linked 4K30 adapter does not establish 4K60 support.
- Separate “no firmware picture” from “firmware works, Linux goes blank.” Note the last visible screen.
- If the issue began after an update, try an already-installed previous kernel as a diagnostic and record the difference.
Use a current live image before changing installed-system settings. Keep firmware flashing out of first-line diagnosis.
The SSD or installer isn’t working.
This guide uses an M.2 2280 NVMe drive. The original hardware documentation also describes SATA III support; check the actual drive protocol and firmware detection instead of treating every M.2 drive as NVMe. Disconnect power before reseating it. Write the installer with the distribution’s official tool and verify the image if the USB will not boot.
The slot’s PCIe 2.0 ×2 link caps performance; speeds below a modern SSD’s advertised maximum are expected. If installation reports an error, record the exact message and the destination drive before attempting another install.
Low FPS, CPU rendering or game-session crashes.
The desktop runs, but games are very slow
vulkaninfo --summary
uname -r
rpm -q mesa-vulkan-drivers
cat /proc/cmdlineConfirm that Vulkan sees the GPU. A leftover installer fallback such as nomodeset can affect normal graphics; change it only using your distribution’s documented bootloader procedure. Then check the governor service and temperatures.
“Failed to pin framebuffer” or a gamescope crash
A community investigation reports this failure with a 512 MB minimum VRAM allocation, resolved by raising the minimum to 6 GB. That is a symptom-specific result, not the best split for every workload.
On supported stock P3.00/P5.00 firmware, build the maintainer’s utility and read the saved configuration first:
sudo dnf install git make gcc-c++
git clone https://github.com/fanoush/bc250_memcfg.git
cd bc250_memcfg
make
sudo ./bc250memcfgRecord UMA_SIZE. Only when investigating this documented low-allocation symptom, the corresponding change is:
sudo ./bc250memcfg UMA_SIZE 6144It writes CMOS settings and applies after reboot. To undo, restore the previously recorded value and reboot. If the board stops booting, follow its documented CMOS recovery procedure. This is not a BIOS flash.
Only one game fails
Check the game’s current Linux/Proton status, remove copied launch flags and test Steam’s supplied compatibility tools. Save files before reinstalling or resetting a prefix. See the gaming guide.
Heat, fan noise or high idle power.
Check physical airflow before changing clocks. The heatsink needs forced airflow, and the GDDR6 memory on the underside needs cooling too. Keep airflow over both sides of the board. A printed duct or shroud must match the fan and enclosure.
sensors
systemctl status cyan-skillfish-governor-smu --no-pager
systemctl list-units --type=service --all '*governor*'One clock-control service should manage the GPU. Use its logs and configuration to investigate high clocks at idle. Sensor power is not wall power; compare idle readings with the same display, refresh rate and services.
Re-pasting is a repair option when contact or thermal material is suspect. Do not open a functioning cooler just because a shopping list includes paste. Gap-filling putty and die paste serve different jobs. See the 4 g paste and 30 g putty options for a repair that calls for them.
No sound.
Select the intended output in the desktop’s audio settings. DisplayPort/HDMI audio depends on the monitor or adapter chain; USB digital audio provides another path if you already own a headset or speaker.
Community reports describe a DisplayPort audio clock issue. A kernel update alone is not a universal fix. Compare your symptoms and versions with the community audio troubleshooting notes before applying a workaround. Test direct DisplayPort where possible and note whether the sound problem follows the adapter.
Wi-Fi or Bluetooth isn’t available.
The site owner reports that the linked TP-Link TX10UB Nano worked on a BC-250. The exact Linux release, hardware revision and steps were not recorded; manufacturer Windows support claims do not establish or disprove that specific Linux experience.
Use Ethernet during installation if available. Record the USB identifier and kernel version before looking for a driver. Test a receiver away from USB 3 devices and hubs when interference is suspected.
lsusb
uname -rDo not install a random out-of-tree driver merely because a dongle has the same brand name. Match its actual USB ID and chipset first.
Make your help request answerable.
Include the board’s BIOS version and memory split, distribution, PSU, cooling, display chain, the exact symptom and what changed immediately before it began.
cat /etc/os-release
uname -r
vulkaninfo --summary
free -h
systemctl status cyan-skillfish-governor-smu --no-pager
sudo journalctl -k -b -p warning --no-pagerReview logs for identifying information before posting them. Use -b -1 for the previous boot if those logs are retained. Report the first relevant error instead of a screenshot of an entire scrolling terminal.