frigate: 0.11.0 release - FFMPEG hardware accelleration not working inside docker container on i7-11th gen RocketLake

I have this exact same issue on intel gen12 CPU

Thanks @NickM-27 - driver fix resolves hardware issues on newer Alder Lake NUCs.

loe@nuc:~/containers/frigate$ lscpu
Architecture:            x86_64
  CPU op-mode(s):        32-bit, 64-bit
  Address sizes:         39 bits physical, 48 bits virtual
  Byte Order:            Little Endian
CPU(s):                  16
  On-line CPU(s) list:   0-15
Vendor ID:               GenuineIntel
  Model name:            12th Gen Intel(R) Core(TM) i5-1240P
    CPU family:          6
    Model:               154
    Thread(s) per core:  2
    Core(s) per socket:  12
    Socket(s):           1
    Stepping:            3
    CPU max MHz:         4400.0000
    CPU min MHz:         400.0000
    BogoMIPS:            4224.00
    Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aper
                         fmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_
                         l2 invpcid_single cdp_l2 ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdt_a rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv
                         1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req umip pku ospke waitpkg gfni vaes vpclmulqdq rdpid movdiri movdir64b fsrm md_clear serialize arch_lbr flush_l1d arch_capabili
                         ties
Virtualization features:
  Virtualization:        VT-x
Caches (sum of all):
  L1d:                   448 KiB (12 instances)
  L1i:                   640 KiB (12 instances)
  L2:                    9 MiB (6 instances)
  L3:                    12 MiB (1 instance)
NUMA:
  NUMA node(s):          1
  NUMA node0 CPU(s):     0-15
Vulnerabilities:
  Itlb multihit:         Not affected
  L1tf:                  Not affected
  Mds:                   Not affected
  Meltdown:              Not affected
  Mmio stale data:       Not affected
  Retbleed:              Not affected
  Spec store bypass:     Mitigation; Speculative Store Bypass disabled via prctl and seccomp
  Spectre v1:            Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2:            Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence
  Srbds:                 Not affected
  Tsx async abort:       Not affected

Looking into using a newer driver. Jellyfin was used in RC1 and it had good results even with hosts that had older drivers so 🤞newer driver will mean better backwards compatibility with hosts that have older drivers installed.

Unfortunately I have no Intel devices to test, but my AMD APU is working fine with the newer driver (but it also never had issues even though my Unraids driver was newer than what is currently included). Seems AMD is less picky than Intel in this case.

Definitely don’t want this to be an issue long term, but nice that there is a manual intermediary fix.

Just wanted to say I also have this issue with a i7 11700K running on unRAID 6.10.2.

0.11 r1 worked but everything since fails using “hwaccel_args: -c:v h264_qsv”.

I tried " hwaccel_args: -hwaccel qsv -qsv_device - /dev/dri/renderD128" and it doesn’t fail however my video load on my cpu is 0%.

I did the following

echo 'deb http://deb.debian.org/debian testing main non-free' >> /etc/apt/sources.list
apt -y update
apt -y -t testing install intel-media-va-driver-non-free

Now using “hwaccel_args: -c:v h264_qsv” everything works as expected using the stable version of 0.11.0 and I see video load on my cpu.

new-intel-driver yielded the same error as posted in 3941#issuecomment-1311092042, but testing-driver works fine for me.

Thanks, hopefully we can get a few others to rest and see if it’s a driver issue or not.

If you override those specific cameras with hwaccel_args: [] do those cams work?

I’ll give this a go on my 12th gen intel setup this evening and feed back.

The take I have from this all is that if your host distro is the same as the container distro, and all are up-to-date, it should work as long as driver versions match.

So do a simple vainfo inside the container shell, and also a vainfo on the host and you should see the iHD drivers detected and their versions match.

However if the host driver is upgraded, or if the host distro is using a different version driver (iHD), Intel hardware-acceleration for the newer ‘lake’ cpus fails. Intel split the drivers up a while back, the old i965 is for older cpus, the new iHD is for newer cpus.

Also as has been noted a few times by the very helpful @NickM-27 , sometimes you may not even be hardware-accelerating, as FFMPEG will just resort to CPU for decoding, with only a handful of cameras you won’t notice it on the newer gen chips. This is where as suggested numerous times, start up an instance of ‘intel_gpu_top’ to confirm the ‘VIDEO’ engine is actually showing a percentage equivalent to the decode load.

Actually changing to ;

ffmpeg: hwaccel_args: -c:v h264_qsv

Fixed for me, I don’t think I was passing the device to the container before so it was never doing accelleration anyway, so once I fixed that and changed the above I’ve re-upgraded and its working…

intel-gpu-top: Intel Tigerlake (Gen12) @ /dev/dri/card0 - 75/ 74 MHz 0% RC6; 98 irqs/s

     ENGINES     BUSY                                       MI_SEMA MI_WAIT
   Render/3D    0.00% |                                   |      0%      0%
     Blitter    0.00% |                                   |      0%      0%
       Video    0.93% |▍                                  |      0%      0%
VideoEnhance    0.00% |                                   |      0%      0%

Same issue on a v11 NUC, any way to implement this work-around or should I roll back to v10?

[2022-09-27 14:02:03] watchdog.Driveway              ERROR   : Ffmpeg process crashed unexpectedly for Driveway.,
[2022-09-27 14:02:03] watchdog.Driveway              ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.,
[2022-09-27 14:02:03] ffmpeg.Driveway.detect         ERROR   : [AVHWDeviceContext @ 0x556239505380] No VA display found for device /dev/dri/renderD128.,
[2022-09-27 14:02:03] ffmpeg.Driveway.detect         ERROR   : Device creation failed: -22.,
[2022-09-27 14:02:03] ffmpeg.Driveway.detect         ERROR   : Failed to set value '/dev/dri/renderD128' for option 'qsv_device': Invalid argument,
[2022-09-27 14:02:03] ffmpeg.Driveway.record_rtmp    ERROR   : [AVHWDeviceContext @ 0x55f610d3f640] No VA display found for device /dev/dri/renderD128.,
[2022-09-27 14:02:03] ffmpeg.Driveway.detect         ERROR   : Error parsing global options: Invalid argument,
[2022-09-27 14:02:03] ffmpeg.Driveway.record_rtmp    ERROR   : Device creation failed: -22.,
[2022-09-27 14:02:03] ffmpeg.Driveway.record_rtmp    ERROR   : Failed to set value '/dev/dri/renderD128' for option 'qsv_device': Invalid argument,
[2022-09-27 14:02:03] ffmpeg.Driveway.record_rtmp    ERROR   : Error parsing global options: Invalid argument,
[2022-09-27 14:02:03] watchdog.Driveway              INFO    : Terminating the existing ffmpeg process...,
[2022-09-27 14:02:03] frigate.video                  ERROR   : Driveway: Unable to read frames from ffmpeg process.,
[2022-09-27 14:02:03] watchdog.Driveway              INFO    : Waiting for ffmpeg to exit gracefully...,
[2022-09-27 14:02:03] frigate.video                  ERROR   : Driveway: ffmpeg process is not running. exiting capture thread...,
[2022-09-27 14:02:03] watchdog.Garage                ERROR   : Ffmpeg process crashed unexpectedly for Garage.,
[2022-09-27 14:02:03] watchdog.Front                 ERROR   : Ffmpeg process crashed unexpectedly for Front.,
[2022-09-27 14:02:03] watchdog.Front                 ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.,
[2022-09-27 14:02:03] watchdog.Garage                ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.,
[2022-09-27 14:02:03] ffmpeg.Garage.detect           ERROR   : [AVHWDeviceContext @ 0x55b5233aa380] No VA display found for device /dev/dri/renderD128.,
[2022-09-27 14:02:03] ffmpeg.Garage.detect           ERROR   : Device creation failed: -22.,
[2022-09-27 14:02:03] ffmpeg.Garage.detect           ERROR   : Failed to set value '/dev/dri/renderD128' for option 'qsv_device': Invalid argument,
[2022-09-27 14:02:03] ffmpeg.Front.detect            ERROR   : [AVHWDeviceContext @ 0x55a1632ce380] No VA display found for device /dev/dri/renderD128.,
[2022-09-27 14:02:03] ffmpeg.Garage.detect           ERROR   : Error parsing global options: Invalid argument,
[2022-09-27 14:02:03] ffmpeg.Front.detect            ERROR   : Device creation failed: -22.,
[2022-09-27 14:02:03] ffmpeg.Front.detect            ERROR   : Error parsing global options: Invalid argument,
[2022-09-27 14:02:03] ffmpeg.Front.detect            ERROR   : Failed to set value '/dev/dri/renderD128' for option 'qsv_device': Invalid argument,
[2022-09-27 14:02:03] ffmpeg.Front.record_rtmp       ERROR   : Device creation failed: -22.,
[2022-09-27 14:02:03] ffmpeg.Front.record_rtmp       ERROR   : [AVHWDeviceContext @ 0x55e666e6f640] No VA display found for device /dev/dri/renderD128.,
[2022-09-27 14:02:03] ffmpeg.Front.record_rtmp       ERROR   : Failed to set value '/dev/dri/renderD128' for option 'qsv_device': Invalid argument,
[2022-09-27 14:02:03] ffmpeg.Front.record_rtmp       ERROR   : Error parsing global options: Invalid argument,
[2022-09-27 14:02:03] watchdog.Front                 INFO    : Terminating the existing ffmpeg process...,
[2022-09-27 14:02:03] watchdog.Front                 INFO    : Waiting for ffmpeg to exit gracefully...,
[2022-09-27 14:02:03] ffmpeg.Garage.record_rtmp      ERROR   : [AVHWDeviceContext @ 0x55ee56f5a640] No VA display found for device /dev/dri/renderD128.,
[2022-09-27 14:02:03] ffmpeg.Garage.record_rtmp      ERROR   : Failed to set value '/dev/dri/renderD128' for option 'qsv_device': Invalid argument,
[2022-09-27 14:02:03] ffmpeg.Garage.record_rtmp      ERROR   : Device creation failed: -22.,
[2022-09-27 14:02:03] ffmpeg.Garage.record_rtmp      ERROR   : Error parsing global options: Invalid argument