[HW Accel Support]: AMD iGPU configuration #15341

finnaGIT · 2024-12-04T14:21:42Z

finnaGIT
Dec 4, 2024

Describe the problem you are having

I suspect it's an oversight on my part, as I've followed the documentation to specify radeonsi as the environment variable and have included the hwaccel_args in my config. However frigate logs throw the error mentioned below.

I've confirmed I have /dev/dri/renderD128 available in Ubuntu, and have mapped that as a device in docker-compose.yml

I am running a 7800X3D, W11 Pro, Ubuntu 22.04 on WSL2, and Frigate on Docker.

Version

0.15.0-e76f4e9

Frigate config file

mqtt:
  enabled: false

go2rtc:
  streams:
    # Restreams from Scrypted, everything is H.264
    dahua28_main:
      - rtsp://10.0.0.176:46243/*
    dahua28_sub:
      - rtsp://10.0.0.176:46243/*
    dahua36_main:
      - rtsp://10.0.0.176:35793/*
    dahua36_sub:
      - rtsp://10.0.0.176:35793/*

detectors:
  # cpai_default:
  #   api_url: http://10.0.0.29:32168/v1/vision/detection
  #   type: deepstack
  #   api_timeout: 0.1 # seconds
  cpai_ipcam-general:
    api_url: http://10.0.0.29:32168/v1/vision/custom/ipcam-general
    type: deepstack
    api_timeout: 2.0 # seconds
    min_confidence: 0.6 # percent

record:
  enabled: true
  retain:
    days: 0
  alerts:
    retain:
      days: 7
      mode: motion

cameras:
  dahua28:
    enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://10.0.0.29:8554/dahua28_sub
          roles:
            - detect
        - path: rtsp://10.0.0.29:8554/dahua28_main
          roles:
            - record
            - audio
      input_args: preset-rtsp-restream-low-latency
      #hwaccel_args: preset-vaapi (COMMENTED OUT FOR PENDING DISCUSSION)
    detect:
      enabled: true
      width: 1280
      height: 720
    live:
      stream_name: dahua28_main
    motion:
      threshold: 55
      contour_area: 10
      improve_contrast: true
    zones:
      dahua28_street:
        coordinates: 0.242,0.184,0.234,0,0.748,0.004,0.739,0.202,0.578,0.178,0.435,0.18,0.314,0.18
        inertia: 3
        loitering_time: 2
      dahua28_main:
        coordinates: 
          0.243,0.186,0.576,0.181,0.739,0.2,0.746,0.094,0.999,0.195,1,1,0,1,0,0.243,0.061,0.188,0.152,0.147
        loitering_time: 0
        inertia: 3
    review:
      alerts:
        required_zones: dahua28_main

        
environment_vars:
#  LIBVA_DRIVER_NAME: radeonsi
  TZ: America/New_York

version: 0.15-0

docker-compose file or Docker CLI command

services:
  frigate-beta:
    container_name: frigate-beta
    privileged: true
    restart: unless-stopped
    image: ghcr.io/blakeblackshear/frigate:0.15.0-beta2
    shm_size: "128mb"
    volumes:
      - ./config:/config
      - /mnt/d/frigate/storage:/media/frigate
      - type: tmpfs
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    devices:
      - /dev/dri/renderD128
    ports:
      - "8971:8971"
      - "8554:8554" # RTSP feeds
    environment:
      LIBVA_DRIVER_NAME: "radeonsi"

Relevant Frigate log output

2024-12-04 15:35:49.833997716  [INFO] Preparing Frigate...
2024-12-04 15:35:49.850920997  [INFO] Starting Frigate...
2024-12-04 15:35:52.389153228  [2024-12-04 10:35:52] frigate.util.config            INFO    : Checking if frigate config needs migration...
2024-12-04 15:35:52.413624816  [2024-12-04 10:35:52] frigate.util.config            INFO    : frigate config does not need migration...
2024-12-04 15:35:52.462983730  [2024-12-04 10:35:52] frigate.util.services          WARNING : Did not detect hwaccel, using a GPU for accelerated video decoding is highly recommended
2024-12-04 15:35:52.466616668  [2024-12-04 10:35:52] frigate.app                    INFO    : Starting Frigate (0.15.0-e76f4e9)
2024-12-04 15:35:52.475607998  [2024-12-04 10:35:52] peewee_migrate.logs            INFO    : Starting migrations
2024-12-04 15:35:52.475946296  [2024-12-04 10:35:52] peewee_migrate.logs            INFO    : There is nothing to migrate
2024-12-04 15:35:52.491831451  [2024-12-04 10:35:52] frigate.app                    INFO    : Recording process started: 380
2024-12-04 15:35:52.491943533  [2024-12-04 10:35:52] frigate.app                    INFO    : Review process started: 382
2024-12-04 15:35:52.493653593  [2024-12-04 10:35:52] frigate.app                    INFO    : go2rtc process pid: 98
2024-12-04 15:35:52.510509426  [2024-12-04 10:35:52] detector.cpai_ipcam-general    INFO    : Starting detection process: 396
2024-12-04 15:35:52.546552093  [2024-12-04 10:35:52] frigate.app                    INFO    : Output process started: 411
2024-12-04 15:35:52.555157677  [2024-12-04 10:35:52] frigate.app                    INFO    : Camera processor started for dahua28: 425
2024-12-04 15:35:52.559975879  [2024-12-04 10:35:52] frigate.app                    INFO    : Capture process started for dahua28: 427
2024-12-04 15:35:52.666664175  [2024-12-04 10:35:52] frigate.api.fastapi_app        INFO    : Starting FastAPI app
2024-12-04 15:35:52.814907469  [2024-12-04 10:35:52] frigate.api.fastapi_app        INFO    : FastAPI started
2024-12-04 15:35:53.627490990  [2024-12-04 10:35:53] frigate.video                  ERROR   : dahua28: Unable to read frames from ffmpeg process.
2024-12-04 15:35:53.627699530  [2024-12-04 10:35:53] frigate.video                  ERROR   : dahua28: ffmpeg process is not running. exiting capture thread...
2024-12-04 15:36:00.610748488  [2024-12-04 10:36:00] frigate.util.services          ERROR   : Unable to poll radeon GPU stats:
2024-12-04 15:36:12.581337944  [2024-12-04 10:36:12] watchdog.dahua28               ERROR   : Ffmpeg process crashed unexpectedly for dahua28.
2024-12-04 15:36:12.584783147  [2024-12-04 10:36:12] watchdog.dahua28               ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2024-12-04 15:36:12.584809874  [2024-12-04 10:36:12] ffmpeg.dahua28.detect          ERROR   : [AVHWDeviceContext @ 0x5574bd496b80] libva: /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so init failed
2024-12-04 15:36:12.584825945  [2024-12-04 10:36:12] ffmpeg.dahua28.detect          ERROR   : [AVHWDeviceContext @ 0x5574bd496b80] Failed to initialise VAAPI connection: 2 (resource allocation failed).
2024-12-04 15:36:12.584866866  [2024-12-04 10:36:12] ffmpeg.dahua28.detect          ERROR   : Device creation failed: -5.
2024-12-04 15:36:12.584915656  [2024-12-04 10:36:12] ffmpeg.dahua28.detect          ERROR   : [vist#0:0/h264 @ 0x5574bd49a240] [dec:h264 @ 0x5574bd40f080] No device available for decoder: device type vaapi needed for codec h264.
2024-12-04 15:36:12.584943048  [2024-12-04 10:36:12] ffmpeg.dahua28.detect          ERROR   : [vist#0:0/h264 @ 0x5574bd49a240] [dec:h264 @ 0x5574bd40f080] Hardware device setup failed for decoder: Input/output error
2024-12-04 15:36:12.584956905  [2024-12-04 10:36:12] ffmpeg.dahua28.detect          ERROR   : [vost#0:0/rawvideo @ 0x5574bd498e00] Error initializing a simple filtergraph
2024-12-04 15:36:12.584993343  [2024-12-04 10:36:12] ffmpeg.dahua28.detect          ERROR   : Error opening output file pipe:.
2024-12-04 15:36:12.585016910  [2024-12-04 10:36:12] ffmpeg.dahua28.detect          ERROR   : Error opening output files: Input/output error
2024-12-04 15:36:13.029172578  [2024-12-04 10:36:13] frigate.video                  ERROR   : dahua28: Unable to read frames from ffmpeg process.
2024-12-04 15:36:13.029332020  [2024-12-04 10:36:13] frigate.video                  ERROR   : dahua28: ffmpeg process is not running. exiting capture thread...
2024-12-04 15:36:22.589796097  [2024-12-04 10:36:22] watchdog.dahua28               ERROR   : Ffmpeg process crashed unexpectedly for dahua28.
2024-12-04 15:36:22.589837737  [2024-12-04 10:36:22] watchdog.dahua28               ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2024-12-04 15:36:22.589845311  [2024-12-04 10:36:22] ffmpeg.dahua28.detect          ERROR   : [AVHWDeviceContext @ 0x5643e287fe80] libva: /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so init failed
2024-12-04 15:36:22.589901225  [2024-12-04 10:36:22] ffmpeg.dahua28.detect          ERROR   : [AVHWDeviceContext @ 0x5643e287fe80] Failed to initialise VAAPI connection: 2 (resource allocation failed).
2024-12-04 15:36:22.589961542  [2024-12-04 10:36:22] ffmpeg.dahua28.detect          ERROR   : Device creation failed: -5.
2024-12-04 15:36:22.590030458  [2024-12-04 10:36:22] ffmpeg.dahua28.detect          ERROR   : [vist#0:0/h264 @ 0x5643e293f980] [dec:h264 @ 0x5643e2946800] No device available for decoder: device type vaapi needed for codec h264.
2024-12-04 15:36:22.590090189  [2024-12-04 10:36:22] ffmpeg.dahua28.detect          ERROR   : [vist#0:0/h264 @ 0x5643e293f980] [dec:h264 @ 0x5643e2946800] Hardware device setup failed for decoder: Input/output error
2024-12-04 15:36:22.590143886  [2024-12-04 10:36:22] ffmpeg.dahua28.detect          ERROR   : [vost#0:0/rawvideo @ 0x5643e2942680] Error initializing a simple filtergraph
2024-12-04 15:36:22.590191440  [2024-12-04 10:36:22] ffmpeg.dahua28.detect          ERROR   : Error opening output file pipe:.
2024-12-04 15:36:22.590244630  [2024-12-04 10:36:22] ffmpeg.dahua28.detect          ERROR   : Error opening output files: Input/output error
2024-12-04 15:36:22.636018090  [2024-12-04 10:36:22] frigate.video                  ERROR   : dahua28: Unable to read frames from ffmpeg process.
2024-12-04 15:36:22.636163033  [2024-12-04 10:36:22] frigate.video                  ERROR   : dahua28: ffmpeg process is not running. exiting capture thread...

Relevant go2rtc log output

n/a

FFprobe output from your camera

n/a

Install method

Windows WSL2

Object Detector

Other

Network connection

Wired

Camera make and model

IPC-Color-4K-T? but N/A... i think

Screenshots of the Frigate UI's System metrics pages

none yet

Any other information that may be helpful

No response

finnaGIT · 2024-12-04T14:48:52Z

finnaGIT
Dec 4, 2024
Author

from within the container, vainfo:

error: XDG_RUNTIME_DIR is invalid or not set in the environment.
error: can't connect to X server!
libva info: VA-API version 1.22.0
libva info: User environment variable requested driver 'radeonsi'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_17
libva error: /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so init failed
libva info: va_openDriver() returns 2
vaInitialize failed with error code 2 (resource allocation failed),exit```

0 replies

NickM-27 · 2024-12-04T16:31:46Z

NickM-27
Dec 4, 2024
Collaborator Sponsor

2024-12-04 15:36:12.584825945 [2024-12-04 10:36:12] ffmpeg.dahua28.detect ERROR : [AVHWDeviceContext @ 0x5574bd496b80] Failed to initialise VAAPI connection: 2 (resource allocation failed).

looks like it doesn't have enough RAM allocated to the GPU or something, what happens if you run vainfo on the host?

8 replies

finnaGIT Dec 4, 2024
Author

i also ran the ffmpeg -decoders | grep cuvid in the container per the documentation because i continued to get errors, but ffmpeg is not installed?

tried installing ffmpeg, but these dependencies are not installed:

libavcodec58 =7:4.3.8-0+deb11u1
libavfilter7 =7:4.3.8-0+deb11u1

what's going on...

@NickM-27 any help is appreciated

NickM-27 Dec 4, 2024
Collaborator Sponsor

2024-12-04 18:46:22.179197986 [2024-12-04 13:46:22] ffmpeg.dahua28.detect ERROR : [AVHWDeviceContext @ 0x564ead608700] Cannot load libcuda.so.1

the nvidia runtime is not installed correctly

finnaGIT Dec 4, 2024
Author

the runtime was installed correctly.
i accidentally omitted count: 1 from the docker compose file which created additional issues.

i have nvidia hwaccel working now, but there are a couple of concerns here:

The documentation says "You can use ffmpeg -decoders | grep cuvid in the container." When you run this from within the container, bash: ffmpeg: command not found is returned. Unless I misunderstand, I think the documentation can be more clear here.
Despite hwaccel working as confirmed by nvidia-smi and indicated the frigate logs, vainfo in the container returns:

error: XDG_RUNTIME_DIR is invalid or not set in the environment.
error: can't connect to X server!
error: failed to initialize display

and vainfo in the host returns the same:

libva info: VA-API version 1.14.0
libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null)
vaInitialize failed with error code 3 (invalid VADisplay),exit

so, this suggests that the results of vainfo are not directly correlated with hwaccel functioning properly in this WSL/Ubuntu/Docker configuration.

and was still unable to get hardware acceleration to work with the AMD iGPU.

tell me this: is it expected that frigate will puke if you pass `hwaccel_args: preset-nvidia-h264' to a stream that is encoded in 264?

finnaGIT Dec 4, 2024
Author

i can now answer that myself - yes it will puke because the arg is preset-nvidia in this version. the hwaccel page linked incorrectly states `preset-nvidia-h264' and the hwaccel presets is correct and seems to work on this version of frigate.

let me know if you'd recommend an issue for any of these items id'd

NickM-27 Dec 4, 2024
Collaborator Sponsor

so, this suggests that the results of vainfo are not directly correlated with hwaccel functioning properly in this WSL/Ubuntu/Docker configuration.

vainfo and nvidia are entirely unrelated, this is expected

preset-nvidia-h264 still exists and works

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[HW Accel Support]: AMD iGPU configuration #15341

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 2 comments 8 replies

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

Select a reply

[HW Accel Support]: AMD iGPU configuration #15341

finnaGIT Dec 4, 2024

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: 2 comments · 8 replies

finnaGIT Dec 4, 2024 Author

NickM-27 Dec 4, 2024 Collaborator Sponsor

finnaGIT Dec 4, 2024 Author

NickM-27 Dec 4, 2024 Collaborator Sponsor

finnaGIT Dec 4, 2024 Author

finnaGIT Dec 4, 2024 Author

NickM-27 Dec 4, 2024 Collaborator Sponsor

finnaGIT
Dec 4, 2024

Replies: 2 comments 8 replies

finnaGIT
Dec 4, 2024
Author

NickM-27
Dec 4, 2024
Collaborator Sponsor

finnaGIT Dec 4, 2024
Author

NickM-27 Dec 4, 2024
Collaborator Sponsor

finnaGIT Dec 4, 2024
Author

finnaGIT Dec 4, 2024
Author

NickM-27 Dec 4, 2024
Collaborator Sponsor