Community Solution

AMD Radeon 890M on ZimaOS: GPU Acceleration, VA-API, and ROCm Limits

A feature-request thread that began with a Radeon 890M appearing unused in ZimaOS and developed into an official clarification: many AMD iGPUs are supported at kernel level, but IceWhale had only validated a 5800H for Jellyfin transcoding and did not have ROCm support resources at the time.

Seeing an AMD GPU in ZimaOS Device Info does not prove that a specific application can use it. That is the central lesson from this October 2025 thread about the Radeon 890M in a Ryzen AI 9 HX 370 PRO system.

The original request asked for three related but different capabilities: AMD video acceleration for Plex/Jellyfin, passing /dev/dri into containers, and ROCm support for local AI workloads. IceWhale later clarified that these should not be treated as one support status.

What IceWhale Actually Confirmed

Zima-Jerry clarified that ZimaOS already supported most AMD integrated graphics at the kernel level, but the team did not have enough AMD devices to test broadly. The one configuration he personally validated was an AMD Ryzen 7 5800H, where the integrated Radeon GPU successfully accelerated Jellyfin transcoding.

ZimaOS Device Info showing an AMD Ryzen 7 5800H and integrated Radeon Vega graphics
This 5800H system is the AMD iGPU configuration IceWhale explicitly said it had tested in the thread.

Zima-Giorgio separately said that broader AMD integrated-graphics testing was not a short-term priority because of limited engineering resources.

Jellyfin Hardware Transcoding Worked in the 5800H Test

The official screenshots show Jellyfin configured for Video Acceleration API (VA-API) with /dev/dri/renderD128 selected as the render node.

Jellyfin transcoding settings using VA-API with the /dev/dri/renderD128 render device
The screenshot demonstrates the tested Jellyfin configuration, not a blanket guarantee for every AMD GPU model.
Jellyfin playback information showing HEVC transcoding at more than 200 frames per second
IceWhale's 5800H test showed active HEVC transcoding in Jellyfin.

The Radeon 890M Was Not Officially Validated

The source poster's Radeon 890M appeared in ZimaOS but seemed idle. The thread never contains an IceWhale test confirming that the 890M specifically supports VA-API encode/decode, Plex hardware transcoding, VM passthrough, or AI workloads on that ZimaOS release.

Zima-Jerry explicitly warned that appearing in Device Info does not necessarily mean the device is fully driven. Actual workload testing is required.

ROCm Was a Separate Unsupported Area

Community users wanted /dev/kfd, ROCm libraries, rocminfo, and related tooling for Ollama and other AI applications. IceWhale's response was that it did not have the resources to support ROCm at that time.

That means successful VA-API video transcoding on one AMD APU should not be interpreted as proof of ROCm compute support.

Later Replies Showed Discrete RDNA GPUs Still Had Gaps

By March 2026, users with Navi 23 and Navi 10 discrete GPUs were still reporting VA-API driver failures inside containers. Those reports are community evidence, not an IceWhale compatibility matrix, but they reinforce why model-specific testing matters.

For current releases, use the latest ZimaOS release information rather than treating the October 2025 support boundary as permanent.

AMD GPU on ZimaOS FAQ

Does ZimaOS support the Radeon 890M?

The thread does not establish full 890M support. It was detected, but IceWhale did not publish a successful 890M acceleration test there.

Which AMD iGPU did IceWhale confirm for Jellyfin?

Zima-Jerry said he tested the integrated graphics in an AMD Ryzen 7 5800H and successfully used it for Jellyfin hardware transcoding.

Does AMD video acceleration mean ROCm works?

No. VA-API video acceleration and ROCm compute are different stacks. IceWhale explicitly said ROCm support was not available as an engineering priority in that thread.

Is Device Info enough to verify GPU acceleration?

No. IceWhale said that a GPU appearing in Device Info does not necessarily mean the required userspace driver path is working.