In plain English
`HSA_OVERRIDE_GFX_VERSION` is a community environment variable that pretends the GPU is a different LLVM target so an older code object will load. A comment on ROCm #2353 documents `10.3.0` so gfx1031 can run gfx1030 objects. It is not an AMD recommendation, and it is not on the official ROCR environment-variable page we could find. On Windows Ollama + R9700, 12.0.1 / 12.0.0 / 11.0.0 still failed to initialize ROCm.
Impact on consumers
Home users copy a number from a Discord thread, load the wrong kernels, and then blame RDNA 4. On a card current ROCm already lists (gfx1201 on 10.1.0), you should not need an override.
Workaround
On official gfx1201 + ROCm 10.0/10.1, unset it. Install a userspace that actually lists your gfx ID, or run llama.cpp Vulkan. If you keep an override on an unofficial ISA (see gfx1031), treat it as unofficial and expect wrong kernels.
Upstream
- ROCm (ROCm/ROCm)
- Ollama (ollama/ollama)
- ROCm 10.1.0 hardware table (gfx1201 is listed — no override) (AMD docs)