ROCm’s open problems & how you can help

A living tracker of cited consumer gaps. We do not invent issue numbers. Unverified rows stay labeled TODO. As of 2026-10-12.

How you can help Write a good report Forum What is ROCm

Workaroundgfx1201Windows
Ollama ROCm fails to init on R9700 Windows
Ollama on Windows 11 with an Radeon AI PRO R9700 (gfx1201) detects the card, then logs that the device did not fully initialize and falls back to CPU. The bundled ROCm libraries (amdhip64_6.dll / 6.x tensiles) do not include gfx1201 kernels. HSA_OVERRIDE_GFX_VERSION does not add the missing kernels. Vulkan on the same box works.
Checked 2026-10-12
Workaroundgfx1201Linux
Ollama gfx1201 looks for hipBLASLt tensiles in the wrong folder
Official `ollama:rocm` images (reported on RX 9070 XT and related gfx1201 cards) ask hipBLASLt for `hipblaslt/library/TensileLibrary_lazy_gfx1201.dat` while the file is shipped under `rocblas/library/`. hipBLASLt then fails heuristic fetch. A packaging PR to install the hipblaslt directory has been discussed; do not assume your image has it until you list the files.
Checked 2026-10-12
Workaroundgfx1201gfx1031LinuxWindows
HSA_OVERRIDE_GFX_VERSION is unofficial — and the wrong gfx1201 fix
`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.
Checked 2026-10-12
Opengfx1201gfx1200Linux
amdgpu MODE1 reset / MES hang on gfx12
The amdgpu driver declares the GPU hung and issues a MODE1 (SMU) reset. VRAM is lost across the reset. Cited reports: an amd-gfx thread (July 2026) on gfx12 HSA selftests after MES failed to suspend compute gangs; ROCm #6127 on an R9700 where `gst-plugin-scan` / VA-API probing ended in MODE1; and a gfx1201 llama.cpp HIP hang (legacy-rocm-build #6630) where Vulkan on the same card passed. #6127 was later closed for inactivity, not marked fixed.
Checked 2026-10-12
Workaroundgfx1201Linux
Distro HIP/HSA packages shadow AMD’s ROCm install
Mixing Ubuntu archive `rocm` / `libamdhip64-dev` / `libhsa-runtime*` with AMD’s repo install loads the wrong runtime. ROCm #6110 on gfx1201 looked like “has 2 ISAs but can only support a single ISA” until the reporter removed Ubuntu-packaged HIP/HSA 5.7.1 libraries that shadowed ROCm 7.2.1. The HIP sources for that log line are old (6.x-era). The issue is closed as a packaging conflict, not a gfx1201 ISA bug.
Checked 2026-10-12
WorkaroundWindowsWSL
Windows and WSL2 ROCm are a technical preview, not the home-lab path
ROCm 10.1.0 release notes add WSL2 support in TheRock artifacts as a technical preview (Ubuntu `.deb` and Python wheels; not RPM). Profiling, debugging, and KFD-dependent tools are out of scope at launch. AMD SMI on WSL2 is discovery/monitoring only. Radeon-Ryzen Windows notes have said only PyTorch is available on Windows — the rest of the stack is Linux. Native Linux is still the path this site writes install steps for.
Checked 2026-10-12
Open
Official ROCm is a table — your card may not be on it
“Official” on this site means the SKU or OS appears on AMD’s current compatibility matrix or the matching release notes. ROCm 10.1.0 lists specific RDNA 4 / RDNA 3 / RDNA 2 rows (including R9700 and RX 9070 XT as gfx1201). A card that is not on that table is unofficial here, even if a wheel loads. Instinct and Radeon are different product lines with different validation.
Checked 2026-10-12
Workaroundgfx1031Linux
gfx1031 (RX 67xx class) is not the gfx1030 official row
Navi 22 / RX 67xx cards are gfx1031. A community comment on ROCm #2353 says you can export `HSA_OVERRIDE_GFX_VERSION=10.3.0` on Linux to load gfx1030 code objects. That is unofficial. gfx1030 (for example some PRO W6800 / V620 rows) is what official tables list for RDNA 2 in current 10.1 notes — do not collapse 1031 into 1030 in the directory.
Checked 2026-10-12
Workaroundgfx1201
hipErrorNoBinaryForGpu — the wheel was not built for your ISA
HIP has a GPU but no compiled kernel image for that ISA. Official HIP wording: “No kernel image is available for execution on the device.” On gfx1201 this usually means the wheel, container, or llama.cpp HIP build was compiled for a different `AMDGPU_TARGETS` list — not that the card is dead.
Checked 2026-10-12
OpenTODOgfx1201
ROCm 10.0 fine-tune GPU-reset on R9700 (URL still TODO)
Living notes mention a ROCm 10.0 fine-tune / training GPU-reset class on the R9700 and a first mitigation of `TORCH_BLAS_PREFER_HIPBLASLT=0`. We do not yet have a first-party AMD known-issue URL copied here. Do not treat this as a measured inference fix.
Checked 2026-10-12