mirror of
https://github.com/elektricM/amd-bc250-docs.git
synced 2026-07-16 03:00:55 +00:00
wip: leftover changes from first pass
This commit is contained in:
@@ -96,6 +96,7 @@ This installs:
|
||||
!!!warning "Critical Step"
|
||||
After drivers are installed, you MUST remove nomodeset or the GPU won't work properly.
|
||||
|
||||
**Fedora / Standard GRUB distributions:**
|
||||
```bash
|
||||
sudo nano /etc/default/grub
|
||||
|
||||
@@ -112,6 +113,27 @@ sudo grub2-mkconfig -o /boot/grub2/grub.cfg
|
||||
sudo reboot
|
||||
```
|
||||
|
||||
**Bazzite / Fedora Atomic (rpm-ostree):**
|
||||
|
||||
Bazzite does not use `/etc/default/grub` — editing it directly has no effect. Use `rpm-ostree kargs` instead:
|
||||
|
||||
```bash
|
||||
# Remove nomodeset if it was added
|
||||
rpm-ostree kargs --delete-if-present="nomodeset"
|
||||
|
||||
# Reboot
|
||||
systemctl reboot
|
||||
```
|
||||
|
||||
Alternatively, create or edit `/etc/default/grub.d/user.cfg` for persistent kernel parameter changes:
|
||||
|
||||
```bash
|
||||
echo 'GRUB_CMDLINE_LINUX_DEFAULT="quiet"' | sudo tee /etc/default/grub.d/user.cfg
|
||||
```
|
||||
|
||||
!!!info "Bazzite Usually Doesn't Need nomodeset"
|
||||
Bazzite typically boots correctly without nomodeset. If you didn't add it, you can skip this step.
|
||||
|
||||
### Step 6: Verify Installation
|
||||
|
||||
Check that everything works:
|
||||
|
||||
@@ -269,8 +269,8 @@ sudo systemctl restart oberon-governor
|
||||
|
||||
**Advanced Multi-Step Configuration:**
|
||||
|
||||
!!!warning "Requires Kernel Patch"
|
||||
The 350 MHz minimum frequency requires the GPU frequency range kernel patch. Without the patch, the governor will crash with `std::__ios_failure`. Use `min: 1000` on stock kernels.
|
||||
!!!warning "Requires Kernel Patch (or SMU Governor)"
|
||||
The 350 MHz minimum frequency requires either the GPU frequency range kernel patch (pre-included in Bazzite) or the SMU governor. On stock kernels without the patch, the governor will crash with `std::__ios_failure`. Use `min: 1000` on stock kernels, or switch to `cyan-skillfish-governor-smu` which bypasses the patch requirement entirely.
|
||||
|
||||
```yaml
|
||||
opps:
|
||||
@@ -499,6 +499,21 @@ cat /sys/class/drm/card1/device/pp_dpm_sclk
|
||||
!!!note "GPU Card Number"
|
||||
Your GPU may be `card0` or `card1` depending on system configuration. Check with `ls /sys/class/drm/` to find the correct card.
|
||||
|
||||
### Black Screen on GPU Reset (Governor Running)
|
||||
|
||||
**Symptoms:**
|
||||
- GPU crashes during a game, screen goes black and never recovers
|
||||
- System appears to be running (fans spinning, SSH may work) but no display output
|
||||
- Hard reboot required
|
||||
|
||||
**Cause:** When the GPU crashes while the governor is actively managing frequencies, the GPU reset mechanism can't complete properly. The governor continues trying to write to sysfs during the reset, preventing recovery.
|
||||
|
||||
**Workaround:**
|
||||
- Disable governor before playing crash-prone games: `sudo systemctl stop cyan-skillfish-governor-tt`
|
||||
- Re-enable after: `sudo systemctl start cyan-skillfish-governor-tt`
|
||||
|
||||
**Long-term fix:** Use stable voltage/frequency settings that don't cause GPU crashes in the first place. If a specific game consistently crashes the GPU, increase voltage or reduce max frequency.
|
||||
|
||||
### System Crashes with Governor
|
||||
|
||||
**Symptoms:**
|
||||
|
||||
Reference in New Issue
Block a user