[HW Accel Support]: VA-API iHD driver fails to initialize on kernel 6.17 — Intel Arc A310 (glibc mismatch)

[johnciavarella]

Describe the problem you are having

After upgrading my host kernel from 6.8.0-106-generic to 6.17.0-19-generic, the bundled iHD_drv_video.so in the Frigate container fails to initialize. This causes all ffmpeg processes to crash, cameras show "frames not received", and the watchdog kills Frigate in a restart loop.

The same Frigate version and config worked perfectly on kernel 6.8.

The host's package repos (Intel PPA ppa:kobuk-team/intel-graphics) offer intel-media-va-driver-non-free version 26.1.4, which works with kernel 6.17 — but it requires glibc 2.38, and the Frigate container (Debian Bookworm-based) only has glibc 2.36. Attempting to volume-mount the newer driver into the container fails with:

libva error: dlopen of /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so failed:
  /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found
  (required by /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so)

This is likely to affect an increasing number of users since kernel 6.17 is needed by other software (e.g., Immich OpenVINO requires 6.17 for Arc GPU detection).

Version

0.17.1-416a9b7

Frigate config file

mqtt:
  enabled: true
  host: <REDACTED>
  user: <REDACTED>
  password: <REDACTED>

ffmpeg:
  hwaccel_args: preset-vaapi

go2rtc:
  streams:
    # 6 Dahua cameras via RTSP on a separate VLAN

cameras:
  walkway:
    enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://<REDACTED>
          roles:
            - record
            - detect
  # ... 5 additional cameras with similar config

detect:
  enabled: true

detectors:
  ov:
    type: openvino
    device: GPU

model:
  width: 300
  height: 300
  input_tensor: nhwc
  input_pixel_format: bgr
  path: /openvino-model/ssdlite_mobilenet_v2.xml
  labelmap_path: /openvino-model/coco_91cl_bkgr.txt

record:
  enabled: true

semantic_search:
  enabled: true
face_recognition:
  enabled: true
lpr:
  enabled: true

version: 0.17-0

docker-compose file or Docker CLI command

version: "3.9"
services:
  frigate:
    container_name: frigate
    privileged: true
    restart: unless-stopped
    stop_grace_period: 30s
    image: ghcr.io/blakeblackshear/frigate:stable
    shm_size: "1940mb"
    devices:
      - /dev/dri/renderD128:/dev/dri/renderD128
      - /dev/dri/card0:/dev/dri/card0
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - ${DOCKER_FOLDER}/config:/config
      - recordings:/media/frigate
      - type: tmpfs
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - "8971:8971"
      - "5001:5000"
      - "8554:8554"
      - "8555:8555/tcp"
      - "8555:8555/udp"

Relevant Frigate log output

-na-

Relevant go2rtc log output

-na-

FFprobe output from your camera

-na-

Install method

Docker Compose

Object Detector

OpenVino

Network connection

Wired

Camera make and model

-na-

Screenshots of the Frigate UI's System metrics pages

-na-

Any other information that may be helpful

No response

[inkeep-ai-assistant[bot]]

This is a kernel/driver compatibility issue outside of Frigate's direct control. The Frigate container is built on Debian Bookworm with glibc 2.36, and the newer Intel media driver (26.1.4) requires glibc 2.38, which creates an incompatibility when running on kernel 6.17. (1)

Your configuration for Intel hardware acceleration with VAAPI and OpenVINO on GPU is correct based on the documentation:

ffmpeg:
  hwaccel_args: preset-vaapi

detectors:
  ov:
    type: openvino
    device: GPU

(2), (3)

Potential workarounds to consider:

1. Downgrade the host kernel back to 6.8.x where the bundled driver works, if your other software requirements allow it.

2. Use CPU-based detection temporarily by changing your detector device to CPU until a container update addresses the glibc version:

detectors:
  ov:
    type: openvino
    device: CPU

(3)

3. Report this as an issue on the Frigate GitHub repository, as this will likely require the Frigate container base image to be updated to a newer Debian version with glibc 2.38+ to support kernel 6.17 with Intel Arc GPUs.

The documentation notes that for Intel GPUs, the default driver is iHD, and for older generations you may need to set LIBVA_DRIVER_NAME=i965. (2) However, this won't resolve the glibc mismatch issue you're experiencing.

This appears to be a container base image limitation that would need to be addressed upstream by the Frigate project.

📚 Sources:

1. Installation
2. Video Decoding
3. Supported Hardware

---

Have another question? Just tag @inkeep.

[NickM-27]

Is this specific to latest Immich version? That's not a previous requirement as that kernel is relatively new. Also worth noting that Intel Arc integrated Graphics (Core 120H) is working correctly for me on linux 6.19 in the current Frigate container.

We did update the driver in 0.18 so it is possible this can be improved in your case from that, otherwise there may be something else that is incorrect.

[johnciavarella]

I may have to blow away the entire stack and try again but for Immich smart search it was erroring out on Intel drivers until I upgraded to the latest firmware. What kernel did you test on so I can match?

…

-------- Original Message --------

On Friday, 04/03/26 at 16:14 Nicolas Mowen ***@***.***> wrote: Is this specific to latest Immich version? That's not a previous requirement as that kernel is relatively new. Also worth noting that Intel Arc integrated Graphics (Core 120H) is working correctly for me on linux 6.19 in the current Frigate container. We did update the driver in 0.18 so it is possible this can be improved in your case from that, otherwise there may be something else that is incorrect. — Reply to this email directly, [view it on GitHub](#22748?email_source=notifications&email_token=ABVHSJBUSEBVS6PJW7CX6LT4UALSDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRUGQZDEMBZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-16442209), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ABVHSJEUFE624TL5VJNOMB34UALSDAVCNFSM6AAAAACXMDIYR6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNBUGIZDAOI). You are receiving this because you authored the thread.Message ID: ***@***.***>

[NickM-27]

also worth noting that for Arc you should always use QSV, not VAAPI

Linux IntelPC 6.19.8+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.19.8-1~bpo13+1 (2026-03-28) x86_64 GNU/Linux

[johnciavarella]

Bizarre but it was a Proxmox 9.x issue I found the fix here . I ended up blowing away and rebuilding from a stock Debian Trixie cloudinit image with stock drivers.