Community Solution

ZimaCube GPU Compatibility and Detection

ZimaCube users discussed GPU support, Plex acceleration, Intel graphics detection, and the lack of a complete officially tested compatibility list.

What the ZimaCube GPU Thread Actually Confirmed

The community discussion began with a request for a definitive GPU compatibility list. The replies did not establish a complete certified list. They did confirm that ZimaOS 1.2.5 had a newer kernel with broader Intel graphics support, that Plex packaging differed between NVIDIA and Intel paths at the time, and that an Intel Arc A380 user was troubleshooting device detection.

For current hardware selection, use the current ZimaCube 2 product page and the Jellyfin hardware requirements rather than treating a 2024 thread as a current certified GPU list.

Do Not Treat Community Detection as Certification

A GPU appearing in PCIe enumeration, a driver loading, and an application successfully using hardware acceleration are three separate checks. A card can be visible to Linux but unavailable inside a container, or visible to the container but unsupported by the media application for a specific codec.

Intel GPU Detection

ZimaCube terminal showing an lspci and grep command error during GPU detection
Community screenshot showing the first GPU-detection attempt, where the lspci and grep command returned errors.
Example intel_gpu_top output listing Intel Alder Lake and DG2 graphics devices
Community screenshot supplied in the troubleshooting thread showing the expected intel_gpu_top -L style output with integrated and discrete Intel graphics.
ZimaCube terminal output listing Intel Alder Lake and DG2 devices with intel_gpu_top
Community screenshot from the ZimaCube test showing card0 and card1 in intel_gpu_top -L; the follow-up identifies card1 as the external graphics card.

The thread first suggested a generic PCI command and later used intel_gpu_top -L. Intel GPU tools are useful for confirming that an Intel graphics device is exposed to the OS. The current Linux manual for intel_gpu_top explains the tool's purpose and options.

Also inspect PCI and DRM devices before changing application settings:

lspci -nnk | grep -A3 -Ei "VGA|3D|Display"
ls -l /dev/dri

Plex and Container Access Are Separate

If Plex is containerized, the GPU device must be exposed to the container and the application must be configured to use a supported acceleration path. Plex documents hardware-accelerated streaming requirements and supported environments in Plex hardware acceleration documentation.

Do not uninstall a working Plex setup solely because an old community reply mentioned a GPU-specific package. First check the current ZimaOS App Store package and its device mapping.

A Better GPU Troubleshooting Order

  1. Confirm the PCIe card is physically detected.
  2. Confirm the expected kernel driver is bound.
  3. Confirm the relevant device nodes exist, such as /dev/dri for Intel graphics.
  4. Confirm the ZimaOS app/container has access to the device.
  5. Confirm Plex, Jellyfin or another workload is configured for that accelerator.
  6. Measure an actual transcode or compute workload instead of relying only on a dashboard widget.

FAQ

Is the Intel Arc A380 officially supported because one user installed it?

No. A community installation report is not the same as an official compatibility guarantee.

Do I need a BIOS change?

The thread's official reply said no additional BIOS setting was needed for that case, but platform firmware and GPU configuration can differ. Use current ZimaCube documentation for your hardware revision.

Should I choose a GPU for Plex or for local AI?

Size the GPU for the actual workload. Media transcoding, CUDA/local AI and VM passthrough have different driver, memory and software requirements.