The title “Intel N150 iGPU not supported” is historical. In late 2024 the source users could see the Alder Lake-N graphics PCI device, but intel_gpu_top found no usable i915 device and /dev/dri was missing on later 1.4 tests. IceWhale acknowledged that the CPU/GPU platform was too new and began driver validation.
By August 2025, one community user reported that N150 graphics had worked for them since ZimaOS 1.4.2 beta1 and showed /dev/dri/card0 plus renderD128. Current ZimaBoard 2 itself now ships with Intel N150, so the old “N150 is unsupported” conclusion should not be applied to current ZimaOS. The remaining question is whether the specific Jellyfin/Plex container has correct GPU device access and is actually using hardware transcoding.
Early ZimaOS Could See the GPU but Not Initialize a Usable i915 Device
The original post showed:
00:02.0 VGA compatible controller:
Intel Corporation Alder Lake-N [Intel Graphics]but intel_gpu_top reported no integrated/discrete i915 device. That means PCI enumeration alone was not enough for hardware acceleration.
A Newer Linux Kernel Changed the Result on Other Distributions
One participant tested Ubuntu-derived distributions and said the GPU began working after moving to kernel 6.12.3. That was community comparison evidence, not a ZimaOS fix, but it supported the diagnosis that kernel/driver maturity was the limiting layer.
IceWhale Targeted N150 Support for ZimaOS 1.4.2
In May 2025, Zima-Jerry said N150 iGPU driver testing was underway and that, barring problems, support should arrive in 1.4.2.
When asked about timing in July, Zima-Giorgio said the release was expected within two weeks.
One User Confirmed /dev/dri on 1.4.2
After 1.4.2 arrived, Jozu said it still did not work for them, while coffee.coyote replied that it had worked since beta1 and posted:
/dev/dri/
by-path
card0
renderD128This is useful but not universal confirmation—one hardware/build combination worked while another source participant still reported difficulty.
Current ZimaBoard 2 Uses Intel N150
IceWhale's current hardware documentation lists ZimaBoard 2 with an Intel N150 quad-core CPU and Mini DisplayPort output. Current Jellyfin hardware guidance also describes the N150 as Quick Sync-capable integrated graphics, while warning that hardware capability alone does not prove acceleration is active in the app.
See the current ZimaBoard 2 N150 platform.
Verify the Host GPU Path First
ls -l /dev/dri
lspci -nnk | grep -A3 -i vgaA current system intended for Intel hardware transcoding should normally expose a render node such as /dev/dri/renderD128. If /dev/dri is absent, fix the host driver/kernel layer before changing Jellyfin.
Pass the GPU into Jellyfin or Plex
The source specifically advised adding /dev/dri to the container's devices/volumes. Current Jellyfin container guidance follows the same general principle: the render device must be accessible inside the container and the runtime user/group must have permission to use it.
Verify a Real Hardware Transcode
Direct Play does not exercise the encoder/decoder. Force a legal test workload that requires transcoding, then check Jellyfin/Plex playback information and GPU activity. High CPU alone is not enough evidence if subtitles, tone mapping, or an unsupported codec keeps part of the pipeline in software.
Intel N150 iGPU FAQ
Is Intel N150 still generally unsupported by current ZimaOS?
No. The old thread predates 1.4.2 support work, and current ZimaBoard 2 itself uses Intel N150.
What host path should appear for Intel GPU acceleration?
A working Linux graphics stack normally exposes /dev/dri, including a render node such as renderD128.
Did every source user report success on 1.4.2?
No. One user still reported trouble while another confirmed a working /dev/dri path since 1.4.2 beta1.
