Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 38 additions & 0 deletions src/content/docs/configuration/dual_gpu.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -162,6 +162,44 @@ functionality.

## Troubleshooting

### AMD Dual-Monitor Setup (AMD iGPU + AMD dGPU)

If you have an AMD CPU with integrated graphics (e.g., Ryzen 9 9950X3D with RDNA3 iGPU) and a dedicated AMD GPU (e.g., Radeon RX 9070 XT), with monitors connected to both GPUs, there are some important considerations:

**You cannot disable the iGPU** if a monitor is connected to it (e.g., via the motherboard's HDMI port). The iGPU must remain active to drive that display.

#### Identifying Render Nodes

Each GPU has its own render device under `/dev/dri/`:

```bash
ls -la /dev/dri/renderD*
```

Typically:
- `/dev/dri/renderD128` — iGPU (first AMD GPU enumerated)
- `/dev/dri/renderD129` — dGPU (second AMD GPU)

You can verify which GPU owns which render node:

```bash
for f in /dev/dri/renderD*; do echo "$f: $(cat /sys/class/drm/$(basename $f)/device/vendor 2>/dev/null)"; done
```

#### Forcing Applications to Use the dGPU

On AMD+AMD setups, use `DRI_PRIME=1` to run applications on the discrete GPU:

```bash
DRI_PRIME=1 <program>
```

Or use the graphical methods described above (KDE Plasma, GNOME, etc.) with `switcheroo-control`.

#### Chromium-Based Browsers

Chrome and Chromium-based browsers may default to the iGPU. To force them to use the dGPU, configure the flags file. See the [Chrome Hardware Acceleration guide](/configuration/enabling_hardware_acceleration_in_google_chrome/) for details on configuring the correct GPU and enabling hardware acceleration.

### "My external monitor is very laggy on PRIME"

This is a known NVIDIA driver issue. You should have the latest NVIDIA
Expand Down
21 changes: 21 additions & 0 deletions src/content/docs/configuration/general_system_tweaks.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -251,6 +251,27 @@ To enable RCU Lazy, add the following parameter to your kernel [cmdline](/config
rcutree.enable_rcu_lazy=1
```

## AMD GPU Troubleshooting

### RDNA4 Display Controller Timeouts (Blue Artifacts / Screen Freeze)

On RDNA4 GPUs (e.g., Radeon RX 9070 XT), you may encounter display controller timeouts that cause blue screen artifacts or a complete display freeze. This is identifiable in kernel logs as:

```
amdgpu: REG_WAIT timeout optc31_disable_crtc
```

This is not a kernel panic — the system is still running but the display is frozen. To recover the GPU automatically when this happens, add the following kernel parameters to your [bootloader configuration](/configuration/boot_manager_configuration/):

```text
amdgpu.gpu_recovery=1 amdgpu.lockup_timeout=10000
```

- `amdgpu.gpu_recovery=1` — enables automatic GPU recovery on lockup
- `amdgpu.lockup_timeout=10000` — sets the lockup detection timeout to 10 seconds (default is 0, which waits indefinitely)

After adding the parameters, rebuild your initramfs and reboot.

## NVIDIA Troubleshooting

### Disabling SDDM Wayland Backend
Expand Down