ROCm and Resolve on NixOS: a compatibility checklist

An old workaround can be perfectly documented and still be wrong for today's GPU, ROCm release or application build. Treat the problem as four separate layers. A failure at one layer is not fixed by adding random packages at another.

Start with the exact GPU

Record the GPU model and architecture, not just “AMD Radeon.” Compare it with AMD's current ROCm-on-Radeon compatibility matrix for the specific ROCm release. Support varies by GPU, operating system and workload. An RX 580 workaround from a 2024 blog post does not establish support in a current release.

Prove the runtime independently

Before launching an editor, confirm the operating system detects the GPU, the intended driver is active, and the ROCm/OpenCL runtime enumerates a usable device. If enumeration fails, the video editor is not yet the right debugging surface. Preserve the output of diagnostic tools and compare it with the versions you actually installed.

Then inspect the package boundary

NixOS packages and library paths differ from conventional Linux distributions. Review the package expression and its dependencies for your NixOS channel. Keep a record of the system revision so a working setup can be reproduced. Avoid mixing instructions from different NixOS and ROCm releases without checking every option and package name.

Launch only after the lower layers pass

Check the current DaVinci Resolve release notes and Linux requirements. Run the application from a terminal once so missing-library and device messages are visible. If it still fails, report the GPU, kernel, NixOS revision, ROCm version, Resolve version and the exact error. That evidence is far more actionable than “Resolve does not open.”