[HW Accel Support]: Alder-Lake-N on n150 requires intel-media-va-driver-non-free v25.1

[pznamenskii]

Describe the problem you are having

please update https://packages.debian.org/bullseye/intel-media-va-driver-non-free in docker image to v25.1 to allow VAAPI support for N150's GPU.

Version

0.14.1-f4f3cfa

Frigate config file

ffmpeg:
  hwaccel_args: preset-vaapi
...

docker-compose file or Docker CLI command

- /dev/dri/renderD128:/dev/dri/renderD128

Relevant Frigate log output

n/a

Relevant go2rtc log output

n/a

FFprobe output from your camera

n/a

Install method

Docker Compose

Object Detector

Coral

Network connection

Wired

Camera make and model

icsee

Screenshots of the Frigate UI's System metrics pages

n/a

Any other information that may be helpful

va driver got updated and now supports Alder-Lake-N in Intel's newer n150 chipset PCI-E 46D4 (n100 has different flavor - 46D3). vainfo oin host system now works correctly - need new driver inside container to make hwaccel work there as well.

$ ls /dev/dri
by-path card0 renderD128

$ lspci -nn |grep -Ei 'VGA|DISPLAY'
00:02.0 VGA compatible controller [0300]: Intel Corporation Alder Lake-N [Intel Graphics] [8086:46d4]

[NickM-27]

Thanks, this most likely won't be included until 0.16

[ronaldt80]

@pznamenskii - struggling with the N150 as well, however can't even get the driver to install on my host system, any tips? Running proxmox 8.3.4:

Package intel-media-va-driver-non-free is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'intel-media-va-driver-non-free' has no installation candidate

[pznamenskii]

Running proxmox 8.3.4

not a proxmox user, sorry

P.S. VAAPI HW acceleration now works perfectly fine for N150 both on host system (ubuntu 24.10) and Frigate docker image (0.15).

[ldjts]

How did you get it to work? I'm on Ubuntu 25.04 (host system) and Frigate docker image (0.15) too. My intel-media-va-driver-non-free version is 25.1.2, but still vainfo gives me error:

Trying display: wayland
Trying display: x11
libva info: VA-API version 1.22.0
libva error: vaGetDriverNames() failed with unknown libva error
vaInitialize failed with error code -1 (unknown libva error),exit

[sstawecki]

For my Debian 12, using a Beelink S13 (Intel N150) ended up running something like this

#!/bin/bash

# Add repositories
echo 'deb http://deb.debian.org/debian bookworm-backports main contrib non-free non-free-firmware' | sudo tee -a /etc/apt/sources.list
echo 'deb-src http://deb.debian.org/debian bookworm-backports main non-free-firmware non-free' | sudo tee -a /etc/apt/sources.list
sudo apt update

sudo apt install -t bookworm-backports linux-image-amd64 linux-headers-amd64 # linux-headers-amd64 may be optional
echo 'Reboot after this step and verify using uname -r that your kernel is 6.12.9 or newer, e.g: 6.12.27+bpo-amd64'

# sudo reboot
# uname -r

sudo apt install -t bookworm-backports firmware-intel-graphics firmware-linux-nonfree # intel-media-va-driver-non-free o intel-media-va-driver

# Not sure if this is necessary
sudo apt install -t bookworm-backports mesa-common-dev mesa-drm-shim mesa-libgallium mesa-opencl-icd mesa-utils-bin mesa-utils mesa-va-drivers mesa-vulkan-drivers

I had an issue with the package intel-media-va-driver-non-free, tried removing the -non-free part and it worked, but to be honest, maybe it was working without the package, the renderD128 in the /dev was created after running the first round of apt install

When I say "it worked" I mean, managed to use preset-vaapi in the frigate config, previously I was getting an error related to that.

Sorry for the imprecisions, I'm still learning what is required, this post helped me a bit https://www.reddit.com/r/MiniPCs/comments/1htxoi6/beelink_mini_s13_intel_n150_linux_driver_issues/

Forgot to mention, I'm using Frigate v0.16.beta3