Host OS Upgrade - Now Receiving: "h264 @ 0x5a0476c00f40] No support for codec h264 profile 100" #18970

davidjmeier · 2025-07-03T00:39:19Z

davidjmeier
Jul 3, 2025

Describe the problem you are having

I run Frigate in an LXC on Proxmox. The underlying system is using an Intel 11th Gen Core i7-1165G7. I've not changed anything in the LXC and from the container's perspective it appears that the GPU is still passed through appropriately.

From in the frigate LXC, and I run ffmpeg -hwaccels I see that it's available:

ffmpeg version n7.0.2-18-g3e6cec1286-20240919 Copyright (c) 2000-2024 the FFmpeg developers
  built with gcc 14.2.0 (crosstool-NG 1.26.0.106_ed12fa6)
  configuration: --prefix=/ffbuild/prefix --pkg-config-flags=--static --pkg-config=pkg-config --cross-prefix=x86_64-ffbuild-linux-gnu- --arch=x86_64 --target-os=linux --enable-gpl --enable-version3 --disable-debug --enable-iconv --enable-zlib --enable-libfreetype --enable-libfribidi --enable-gmp --enable-libxml2 --enable-openssl --enable-lzma --enable-fontconfig --enable-libharfbuzz --enable-libvorbis --enable-opencl --enable-libpulse --enable-libvmaf --enable-libxcb --enable-xlib --enable-amf --enable-libaom --enable-libaribb24 --enable-avisynth --enable-chromaprint --enable-libdav1d --enable-libdavs2 --enable-libdvdread --enable-libdvdnav --disable-libfdk-aac --enable-ffnvcodec --enable-cuda-llvm --enable-frei0r --enable-libgme --enable-libkvazaar --enable-libaribcaption --enable-libass --enable-libbluray --enable-libjxl --enable-libmp3lame --enable-libopus --enable-librist --enable-libssh --enable-libtheora --enable-libvpx --enable-libwebp --enable-libzmq --enable-lv2 --enable-libvpl --enable-openal --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopenmpt --enable-librav1e --enable-librubberband --disable-schannel --enable-sdl2 --enable-libsoxr --enable-libsrt --enable-libsvtav1 --enable-libtwolame --enable-libuavs3d --enable-libdrm --enable-vaapi --enable-libvidstab --enable-vulkan --enable-libshaderc --enable-libplacebo --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxvid --enable-libzimg --enable-libzvbi --extra-cflags=-DLIBTWOLAME_STATIC --extra-cxxflags= --extra-libs='-ldl -lgomp' --extra-ldflags=-pthread --extra-ldexeflags=-pie --cc=x86_64-ffbuild-linux-gnu-gcc --cxx=x86_64-ffbuild-linux-gnu-g++ --ar=x86_64-ffbuild-linux-gnu-gcc-ar --ranlib=x86_64-ffbuild-linux-gnu-gcc-ranlib --nm=x86_64-ffbuild-linux-gnu-gcc-nm --extra-version=20240919
  libavutil      59.  8.100 / 59.  8.100
  libavcodec     61.  3.100 / 61.  3.100
  libavformat    61.  1.100 / 61.  1.100
  libavdevice    61.  1.100 / 61.  1.100
  libavfilter    10.  1.100 / 10.  1.100
  libswscale      8.  1.100 /  8.  1.100
  libswresample   5.  1.100 /  5.  1.100
  libpostproc    58.  1.100 / 58.  1.100
Hardware acceleration methods:
cuda
vaapi
qsv
drm
opencl
vulkan

The errors I'm seeing (for all cams now - which were all previously working) is:

frigate  | 2025-07-03 00:20:56.638918828  [2025-07-03 00:20:56] watchdog.shop-driveway         ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
frigate  | 2025-07-03 00:20:56.638919817  [2025-07-03 00:20:56] ffmpeg.shop-driveway.detect    ERROR   : [h264 @ 0x617ced288c00] No support for codec h264 profile 100.
frigate  | 2025-07-03 00:20:56.638920808  [2025-07-03 00:20:56] ffmpeg.shop-driveway.detect    ERROR   : [h264 @ 0x617ced288c00] Failed setup for format vaapi: hwaccel initialisation returned error.
frigate  | 2025-07-03 00:20:56.638921872  [2025-07-03 00:20:56] ffmpeg.shop-driveway.detect    ERROR   : Impossible to convert between the formats supported by the filter 'Parsed_fps_0' and the filter 'auto_scale_0'
frigate  | 2025-07-03 00:20:56.638922687  [2025-07-03 00:20:56] ffmpeg.shop-driveway.detect    ERROR   : [vf#1:0 @ 0x617cecdf5f00] Error reinitializing filters!
frigate  | 2025-07-03 00:20:56.638923565  [2025-07-03 00:20:56] ffmpeg.shop-driveway.detect    ERROR   : [vf#1:0 @ 0x617cecdf5f00] Task finished with error code: -38 (Function not implemented)
frigate  | 2025-07-03 00:20:56.638924463  [2025-07-03 00:20:56] ffmpeg.shop-driveway.detect    ERROR   : [vf#1:0 @ 0x617cecdf5f00] Terminating thread with return code -38 (Function not implemented)
frigate  | 2025-07-03 00:20:56.638925260  [2025-07-03 00:20:56] ffmpeg.shop-driveway.detect    ERROR   : [vost#1:0/rawvideo @ 0x617cecdf4d00] Could not open encoder before EOF
frigate  | 2025-07-03 00:20:56.638926187  [2025-07-03 00:20:56] ffmpeg.shop-driveway.detect    ERROR   : [vost#1:0/rawvideo @ 0x617cecdf4d00] Task finished with error code: -22 (Invalid argument)
frigate  | 2025-07-03 00:20:56.638927024  [2025-07-03 00:20:56] ffmpeg.shop-driveway.detect    ERROR   : [vost#1:0/rawvideo @ 0x617cecdf4d00] Terminating thread with return code -22 (Invalid argument)

Not really sure what could have gone wrong given that I'm using the same setup with no changes. This is the only LXC running with access to the iGPU and that config looks has passthrough that looks like:

lxc.cgroup2.devices.allow: c 29:0 rwm
lxc.cgroup2.devices.allow: c 189:* rwm
lxc.cgroup2.devices.allow: c 226:* rwm
lxc.mount.entry: /dev/bus/usb/004 dev/bus/usb/004 none bind,optional,create=dir 0, 0
lxc.mount.entry: /dev/dri dev/dri none bind,optional,create=dir
lxc.mount.entry: /dev/fb0 dev/fb0 none bind,optional,create=file

The above was abbreviated - the TPU still seems to be initialized correctly. At a loss here, what else could be impacting this? The odd thing is my substreams seem to work fine.

Version

0.15.1

Frigate config file

mqtt:
  enabled: false

ffmpeg:
  hwaccel_args: "auto" 
  output_args:
    record: preset-record-generic-audio-aac

detectors:
  coral:
    type: edgetpu
    device: usb

objects:
  track:
    - person
    - face
    - license_plate
    - bicycle
    - car
    - motorcycle
    - cat
    - dog
    - amazon
    - fedex
    - ups
    - usps
    - dhl
    - package
    - waste_bin

model:
  path: plus://<snip>

review:
  alerts:
    labels:
      - person
      - car
      - motorcycle
      - amazon
      - fedex
      - ups
      - usps
      - dhl

go2rtc:
  streams:
    shopinterior-s-sub:
      - rtsp://<snip>@<snip>/cam/realmonitor?channel=1&subtype=2
      - ffmpeg:shopinterior-s-sub#audio=opus
    shopinterior-s:
      - rtsp://<snip>@<snip>/cam/realmonitor?channel=1&subtype=0
      - ffmpeg:shopinterior-s#audio=opus
    shopdriveway-sub:
      - rtsp://<snip>@<snip>/Preview_01_sub
      - ffmpeg:shopdriveway-sub#audio=opus
    shopdriveway:
      - rtsp://<snip>@<snip>/Preview_01_main
      - ffmpeg:shopdriveway#audio=opus
    housedriveway-sub:
      - rtsp://<snip>@<snip>/Preview_01_sub
      - ffmpeg:housedriveway-sub#audio=opus
    housedriveway:
      - rtsp://<snip>@<snip>/Preview_01_main
      - ffmpeg:housedriveway#audio=opus
    shopbackyard-sub:
      - rtsp://<snip>@<snip>/Preview_01_sub
      - ffmpeg:housedriveway-sub#audio=opus
    shopbackyard:
      - rtsp://<snip>@<snip>/Preview_01_main
      - ffmpeg:housedriveway#audio=opus
  webrtc:
    candidates:
      - <snip>:8555
      - stun:8555

birdseye:
  enabled: true
  mode: continuous

audio:
  enabled: true
  listen:
    - bark
    - fire_alarm
    - scream
    - speech
    - yell

record:
  enabled: true
  expire_interval: 30
  sync_recordings: true
  retain:
    days: 5
    mode: all
  alerts:
    retain:
      days: 30
    pre_capture: 30
    post_capture: 30
  detections:
    retain:
      days: 30
    pre_capture: 30
    post_capture: 30
snapshots:
  enabled: true
  clean_copy: true
  timestamp: false
  bounding_box: true
  crop: false
  required_zones: []
  retain:
    default: 7
    objects:
      person: 14
  quality: 85

cameras:
  shop-interior-s:
    enabled: true
    detect:
      enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/shopinterior-s
          input_args: preset-rtsp-restream
          roles:
            - detect
            - audio
            - record
    audio:
      enabled: true
    objects:
      track:
        - person
        - cat
        - dog
    live:
      stream_name: shopinterior-s-sub
    motion:
      mask: 1920,1006,1920,1080,1389,1080,1390,1010
  shop-driveway:
    enabled: true
    detect:
      enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/shopdriveway
          input_args: preset-rtsp-restream
          roles:
            - detect
            - audio
            - record
    live:
      stream_name: shopdriveway-sub
    motion:
      mask: 855,1210,855,1296,0,1296,0,1210
      threshold: 50
      contour_area: 25
      improve_contrast: 'true'
  house-driveway:
    enabled: true
    detect:
      enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/housedriveway
          input_args: preset-rtsp-restream
          roles:
            - detect
            - audio
            - record
    audio:
      enabled: true
    live:
      stream_name: housedriveway-sub
    motion:
      mask: 0,0.937,0.37,0.938,0.369,1,0,1
      threshold: 50
      contour_area: 25
      improve_contrast: 'true'
  shop-backyard:
    enabled: true
    detect:
      enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/shopbackyard
          input_args: preset-rtsp-restream
          roles:
            - detect
            - audio
            - record
    live:
      stream_name: shopbackyard-sub
    motion:
      mask: 0,0.937,0.373,0.937,0.373,1,0,1
      threshold: 50
      contour_area: 25
      improve_contrast: 'true'
version: 0.15-1

docker-compose file or Docker CLI command

services:
  frigate:
    container_name: frigate
    privileged: true
    restart: unless-stopped
    image: ghcr.io/blakeblackshear/frigate:stable 
    shm_size: "4096mb" # update for your cameras based on calculation above
    devices:
      - /dev/bus/usb:/dev/bus/usb  # Passes the USB Google Coral
      - /dev/dri/renderD128:/dev/dri/renderD128 # For Intel hardware acceleration 
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - ./config:/config
      - /mnt/<snip>:/media/frigate
    ports:
      - "5000:5000"
      - "1984:1984"
      - "8554:8554" # RTSP feeds
      - "8555:8555/tcp" # WebRTC over tcp
      - "8555:8555/udp" # WebRTC over udp
    environment:
      FRIGATE_RTSP_PASSWORD: "<snip>"
      PLUS_API_KEY: "<snip>"

Relevant Frigate log output

frigate  | 2025-07-03 00:20:56.638918828  [2025-07-03 00:20:56] watchdog.shop-driveway         ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
frigate  | 2025-07-03 00:20:56.638919817  [2025-07-03 00:20:56] ffmpeg.shop-driveway.detect    ERROR   : [h264 @ 0x617ced288c00] No support for codec h264 profile 100.
frigate  | 2025-07-03 00:20:56.638920808  [2025-07-03 00:20:56] ffmpeg.shop-driveway.detect    ERROR   : [h264 @ 0x617ced288c00] Failed setup for format vaapi: hwaccel initialisation returned error.
frigate  | 2025-07-03 00:20:56.638921872  [2025-07-03 00:20:56] ffmpeg.shop-driveway.detect    ERROR   : Impossible to convert between the formats supported by the filter 'Parsed_fps_0' and the filter 'auto_scale_0'
frigate  | 2025-07-03 00:20:56.638922687  [2025-07-03 00:20:56] ffmpeg.shop-driveway.detect    ERROR   : [vf#1:0 @ 0x617cecdf5f00] Error reinitializing filters!
frigate  | 2025-07-03 00:20:56.638923565  [2025-07-03 00:20:56] ffmpeg.shop-driveway.detect    ERROR   : [vf#1:0 @ 0x617cecdf5f00] Task finished with error code: -38 (Function not implemented)
frigate  | 2025-07-03 00:20:56.638924463  [2025-07-03 00:20:56] ffmpeg.shop-driveway.detect    ERROR   : [vf#1:0 @ 0x617cecdf5f00] Terminating thread with return code -38 (Function not implemented)
frigate  | 2025-07-03 00:20:56.638925260  [2025-07-03 00:20:56] ffmpeg.shop-driveway.detect    ERROR   : [vost#1:0/rawvideo @ 0x617cecdf4d00] Could not open encoder before EOF
frigate  | 2025-07-03 00:20:56.638926187  [2025-07-03 00:20:56] ffmpeg.shop-driveway.detect    ERROR   : [vost#1:0/rawvideo @ 0x617cecdf4d00] Task finished with error code: -22 (Invalid argument)
frigate  | 2025-07-03 00:20:56.638927024  [2025-07-03 00:20:56] ffmpeg.shop-driveway.detect    ERROR   : [vost#1:0/rawvideo @ 0x617cecdf4d00] Terminating thread with return code -22 (Invalid argument)

Relevant go2rtc log output

Not sure there are any...

FFprobe output from your camera

root@0f2f5eb5aec5:/usr/lib/ffmpeg/7.0/bin# ./ffprobe rtsp://<snip>/Preview_01_main
ffprobe version n7.0.2-18-g3e6cec1286-20240919 Copyright (c) 2007-2024 the FFmpeg developers
  built with gcc 14.2.0 (crosstool-NG 1.26.0.106_ed12fa6)
  configuration: --prefix=/ffbuild/prefix --pkg-config-flags=--static --pkg-config=pkg-config --cross-prefix=x86_64-ffbuild-linux-gnu- --arch=x86_64 --target-os=linux --enable-gpl --enable-version3 --disable-debug --enable-iconv --enable-zlib --enable-libfreetype --enable-libfribidi --enable-gmp --enable-libxml2 --enable-openssl --enable-lzma --enable-fontconfig --enable-libharfbuzz --enable-libvorbis --enable-opencl --enable-libpulse --enable-libvmaf --enable-libxcb --enable-xlib --enable-amf --enable-libaom --enable-libaribb24 --enable-avisynth --enable-chromaprint --enable-libdav1d --enable-libdavs2 --enable-libdvdread --enable-libdvdnav --disable-libfdk-aac --enable-ffnvcodec --enable-cuda-llvm --enable-frei0r --enable-libgme --enable-libkvazaar --enable-libaribcaption --enable-libass --enable-libbluray --enable-libjxl --enable-libmp3lame --enable-libopus --enable-librist --enable-libssh --enable-libtheora --enable-libvpx --enable-libwebp --enable-libzmq --enable-lv2 --enable-libvpl --enable-openal --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopenmpt --enable-librav1e --enable-librubberband --disable-schannel --enable-sdl2 --enable-libsoxr --enable-libsrt --enable-libsvtav1 --enable-libtwolame --enable-libuavs3d --enable-libdrm --enable-vaapi --enable-libvidstab --enable-vulkan --enable-libshaderc --enable-libplacebo --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxvid --enable-libzimg --enable-libzvbi --extra-cflags=-DLIBTWOLAME_STATIC --extra-cxxflags= --extra-libs='-ldl -lgomp' --extra-ldflags=-pthread --extra-ldexeflags=-pie --cc=x86_64-ffbuild-linux-gnu-gcc --cxx=x86_64-ffbuild-linux-gnu-g++ --ar=x86_64-ffbuild-linux-gnu-gcc-ar --ranlib=x86_64-ffbuild-linux-gnu-gcc-ranlib --nm=x86_64-ffbuild-linux-gnu-gcc-nm --extra-version=20240919
  libavutil      59.  8.100 / 59.  8.100
  libavcodec     61.  3.100 / 61.  3.100
  libavformat    61.  1.100 / 61.  1.100
  libavdevice    61.  1.100 / 61.  1.100
  libavfilter    10.  1.100 / 10.  1.100
  libswscale      8.  1.100 /  8.  1.100
  libswresample   5.  1.100 /  5.  1.100
  libpostproc    58.  1.100 / 58.  1.100
Input #0, rtsp, from 'rtsp://opercam:[email protected]/Preview_01_main':
  Metadata:
    title           : Session streamed by "preview"
    comment         : Preview_01_main
  Duration: N/A, start: 0.000188, bitrate: N/A
  Stream #0:0: Video: h264 (High), yuv420p(progressive), 2304x1296, 15 fps, 25 tbr, 90k tbn
  Stream #0:1: Audio: aac (LC), 16000 Hz, mono, fltp

Install method

Docker Compose

Object Detector

Coral

Network connection

Wired

Camera make and model

Reolink

Screenshots of the Frigate UI's System metrics pages

Any other information that may be helpful

No response

hawkeye217 · 2025-07-03T02:40:40Z

hawkeye217
Jul 3, 2025
Collaborator

hwaccel_args: "auto"

If you upgraded your host OS, your host iGPU driver could have changed. You probably want to explicitly specify preset-vaapi instead of auto.

https://docs.frigate.video/configuration/hardware_acceleration/#intel-based-cpus

Proxmox is an officially unsupported installation method as myself nor any of the other maintainers use it. But perhaps the community can provide additional assistance.

5 replies

davidjmeier Jul 3, 2025
Author

Thanks @hawkeye217 - I only changed to auto while testing. I had been using preset-vaapi - in either situation the HW accel is correctly identified. Still sifting through everything.

When I access the go2rtc streams directly they're fine. I see Frigate connect and then die, and retry over and over. So it's something off with ffmpeg which seems very odd. I may just move this system to bare metal to avoid the middleware.

hawkeye217 Jul 3, 2025
Collaborator

Frigate does run best in Docker on bare metal. While some users do find success with Proxmox, a surprisingly large number of support issues over the years have come from struggles with hypervisors, not from Frigate itself.

davidjmeier Jul 3, 2025
Author

Kind of disappointing because I've been running it like this for probably close to 2 years. I tried recreating it fresh on the same LXC and, no dice. Something is definitely broken.

jeeftor Jul 3, 2025

For proxmox - you just need to bump your kernel version -> it shoudl work 100% fine.

The general workflow on proxmox:

Bump Kernel
get the vainfo + correct drivers stuff working on host.
Make sure to "share" /dev/dri etc with the LXC
do the same stuff in the container

jeeftor Jul 3, 2025

Try this on the host (I think) apt install proxmox-kernel-6.14 first (and reboot). Off the top of my head I don't remember the driver stuff you need to do. iHD or i95x or something...

You can hang out with an LLM and come up with the steps likely.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Host OS Upgrade - Now Receiving: "h264 @ 0x5a0476c00f40] No support for codec h264 profile 100" #18970

Uh oh!

{{title}}

Uh oh!

Replies: 1 comment 5 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Select a reply

Uh oh!

Uh oh!

Host OS Upgrade - Now Receiving: "h264 @ 0x5a0476c00f40] No support for codec h264 profile 100" #18970

Uh oh!

davidjmeier Jul 3, 2025

Describe the problem you are having

Version

Frigate config file

docker-compose file or Docker CLI command

Relevant Frigate log output

Relevant go2rtc log output

FFprobe output from your camera

Install method

Object Detector

Network connection

Camera make and model

Screenshots of the Frigate UI's System metrics pages

Any other information that may be helpful

Replies: 1 comment · 5 replies

Uh oh!

hawkeye217 Jul 3, 2025 Collaborator

Uh oh!

davidjmeier Jul 3, 2025 Author

Uh oh!

hawkeye217 Jul 3, 2025 Collaborator

Uh oh!

davidjmeier Jul 3, 2025 Author

Uh oh!

Uh oh!

jeeftor Jul 3, 2025

Uh oh!

Uh oh!

jeeftor Jul 3, 2025

davidjmeier
Jul 3, 2025

Replies: 1 comment 5 replies

hawkeye217
Jul 3, 2025
Collaborator

davidjmeier Jul 3, 2025
Author

hawkeye217 Jul 3, 2025
Collaborator

davidjmeier Jul 3, 2025
Author