[HW Accel Support]: Intel NUC8i7HVK AMD GPU #12673

cigas4 · 2024-07-30T10:49:18Z

cigas4
Jul 30, 2024

Describe the problem you are having

Hello, would appreciate some help getting AMD GPU hardware acceleration working on Frigate (docker container).

Actually I have managed to get hardware acceleration running, but for some reason it is using 'intel HD' graphics insted of AMD GPU.

I am running Proxmox 8.2.4, inside I have LXC container running Debian 12. Inside Debian LXC I am running Frigate docker container.

Proxmox shall:
root@proxmox:~# lspci | grep VGA 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Polaris 22 XT [Radeon RX Vega M GH] (rev c0)

Proxmox LXC config:
arch: amd64 cores: 6 features: nesting=1 hostname: Frigate memory: 14336 mp0: /mnt/pve/Synology_Frigate,mp=/mnt/pve/Synology_Frigate nameserver: 192.168.1.13 8.8.8.8 net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.1.1,hwaddr=22:AA:3E:DC:53:0C,ip=192.168.31.13/24,type=veth onboot: 1 ostype: debian rootfs: local-lvm:vm-104-disk-0,size=100G searchdomain: 192.168.1.1 swap: 2048 lxc.cgroup2.devices.allow: c 226:0 rwm lxc.cgroup2.devices.allow: c 226:128 rwm lxc.cgroup2.devices.allow: c 29:0 rwm lxc.cgroup2.devices.allow: c 189:* rwm lxc.apparmor.profile: unconfined lxc.cgroup2.devices.allow: a lxc.mount.entry: /dev/dri/renderD128 dev/dri/renderD128 none bind,optional,create=file 0, 0 lxc.mount.entry: /dev/bus/usb/002 dev/bus/usb/002 none bind,optional,create=dir 0, 0 lxc.cap.drop: lxc.mount.auto: cgroup:rw

Inside Debin LXC container:
root@Frigate:~# 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.17.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_17 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.17 (libva 2.12.0) vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 23.1.1 () vainfo: Supported profile and entrypoints VAProfileNone : VAEntrypointVideoProc VAProfileNone : VAEntrypointStats VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Simple : VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointFEI VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointFEI VAProfileH264High : VAEntrypointEncSliceLP VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointFEI VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileVP8Version0_3 : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointFEI VAProfileHEVCMain10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSlice VAProfileVP9Profile0 : VAEntrypointVLD VAProfileVP9Profile2 : VAEntrypointVLD

Inside Debin LXC container:
root@Frigate:~# ls -al /dev/dri/renderD128 crw-rw---- 1 root input 226, 128 Jul 28 20:37 /dev/dri/renderD128

Version

0.13.2-6476f8a

Frigate config file

detectors:
  coral:
    type: edgetpu
    device: usb
mqtt:
  host: 192.168.1.3
  port: 1883
  topic_prefix: frigate
  client_id: Frigate
  user: Frigate
  password: pass
  stats_interval: 60

birdseye:
  enabled: false
  quality: 10
  mode: continuous

ffmpeg:
  output_args:
    record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy -c:a aac
  hwaccel_args: preset-vaapi

go2rtc:
  streams:
    parking: 
      - rtsp://user:[email protected]:554/Streaming/Channels/101
      - "ffmpeg:rtsp://user:[email protected]:554/Streaming/Channels/101#video=copy#audio=aac"
  webrtc:
    candidates:
      - 192.168.1.13:8555
      - stun:8555

cameras:
  parking:
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-copy
      inputs:
        - path: rtsp://127.0.0.1:8554/parking?video=copy&audio=aac
          input_args: preset-rtsp-restream
          roles:
            - detect
            - record
    detect:
      enabled: True
      width: 2688
      height: 1520
      fps: 8
      max_disappeared: 35
    objects:
      track:
        - person
        - car
        - dog
      filters:
        person:
          mask:
            - 283,862,542,146,950,182,1744,399,2081,545,2217,992,2248,1280,1955,1321,1966,1459,1623,1520,2688,1520,2688,0,0,0,0,701,0,1520,672,1520,170,1441
          min_area: 41000
          min_score: 0.5
          threshold: 0.8
        car:
          mask:
            - 283,862,542,146,950,182,1744,399,2081,545,2217,992,2248,1280,1955,1321,1966,1459,1623,1520,2688,1520,2688,0,0,0,0,701,0,1520,672,1520,170,1441
          max_area: 1000000
          min_score: 0.5
          threshold: 0.75
        dog:
          mask:
            - 283,862,542,146,950,182,1744,399,2081,545,2217,992,2248,1280,1955,1321,1966,1459,1623,1520,2688,1520,2688,0,0,0,0,701,0,1520,672,1520,170,1441
          max_area: 40000
          min_score: 0.5
          threshold: 0.75
    snapshots:
      enabled: True
      crop: True
      quality: 100
      height: 500
      timestamp: False
      bounding_box: True
      retain:
        default: 100
    record:
      enabled: True
      retain:
        days: 13
        mode: all
      events:
        pre_capture: 10
        post_capture: 15
        retain:
          default: 69
    rtmp:
      enabled: False
    live:
      stream_name: parking
    motion:
      threshold: 60
      mask:
        - 283,862,542,146,950,182,1744,399,2081,545,2217,992,2248,1280,1955,1321,1966,1459,1623,1520,2688,1520,2688,0,0,0,0,701,0,1520,672,1520,170,1441
    zones:
      gate:
        coordinates: 1733,1327,1873,1320,1885,1486,1605,1520

docker-compose file or Docker CLI command

version: '3.9'
services:
  frigate:
    container_name: frigate
    privileged: true
    restart: unless-stopped
    shm_size: '1024mb'
    image: ghcr.io/blakeblackshear/frigate:0.13.2
    devices:
      - /dev/bus/usb:/dev/bus/usb
      - /dev/dri/renderD128
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /home/frigate/frigate.yml:/config/config.yml
      - /mnt/HDD_8TB/Frigate/media:/media/frigate
      - /mnt/HDD_8TB/Frigate/config:/config
      - /mnt/HDD_8TB/Frigate/db:/db
      - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - '5000:5000'
      - '1935:1935'
      - '8555:8555/tcp'
      - '8555:8555/udp'
    environment:
      FRIGATE_RTSP_PASSWORD: 'pass'
      LIBVA_DRIVER_NAME: radeonsi

Relevant log output

Vainfo Output
Return Code: 0

Process Output:

vainfo: VA-API version: 1.17 (libva 2.10.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 23.1.1 ()
vainfo: Supported profile and entrypoints
      VAProfileNone                   :	VAEntrypointVideoProc
      VAProfileNone                   :	VAEntrypointStats
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Simple            :	VAEntrypointEncSlice
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointFEI
      VAProfileH264Main               :	VAEntrypointEncSliceLP
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointEncSlice
      VAProfileH264High               :	VAEntrypointFEI
      VAProfileH264High               :	VAEntrypointEncSliceLP
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD
      VAProfileJPEGBaseline           :	VAEntrypointVLD
      VAProfileJPEGBaseline           :	VAEntrypointEncPicture
      VAProfileH264ConstrainedBaseline:	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline:	VAEntrypointFEI
      VAProfileH264ConstrainedBaseline:	VAEntrypointEncSliceLP
      VAProfileVP8Version0_3          :	VAEntrypointVLD
      VAProfileVP8Version0_3          :	VAEntrypointEncSlice
      VAProfileHEVCMain               :	VAEntrypointVLD
      VAProfileHEVCMain               :	VAEntrypointEncSlice
      VAProfileHEVCMain               :	VAEntrypointFEI
      VAProfileHEVCMain10             :	VAEntrypointVLD
      VAProfileHEVCMain10             :	VAEntrypointEncSlice
      VAProfileVP9Profile0            :	VAEntrypointVLD
      VAProfileVP9Profile2            :	VAEntrypointVLD

FFprobe output from your camera

Ffprobe Output
Stream 0:
Return Code: 0

Video:

Codec: H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10
Resolution: 2688x1520
FPS: 25/1

Audio:

Codec: AAC (Advanced Audio Coding)

Operating system

Proxmox

Install method

Docker Compose

Network connection

Wired

Camera make and model

Hikvision

Any other information that may be helpful

I have another exactly same hardware machine (Intel NUC8i7HVK) running in different premises. It is setup in exactly same way - running Proxmox and has Debian 12 LXC running Frigate docker container.
On this machine somehow I have managed to make it working, but do not know how I did it and can't repeat same steps for this machine.

On the other NUC:

Proxmox shall:
root@proxmoxve:~# lspci | grep VGA 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Polaris 22 XL [Radeon RX Vega M GL] (rev c0)

Inside Debin LXC container:
root@Debian:~# 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.17.0 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 info: va_openDriver() returns 0 vainfo: VA-API version: 1.17 (libva 2.12.0) vainfo: Driver version: Mesa Gallium driver 22.3.6 for AMD Radeon RX Vega M GL Graphics (vegam, LLVM 15.0.6, DRM 3.57, 6.8.8-4-pve) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc

Inside Frigate UI under System HW ACCEL:
Vainfo Output Return Code: 0 Process Output: vainfo: VA-API version: 1.17 (libva 2.10.0) vainfo: Driver version: Mesa Gallium driver 22.3.6 for AMD Radeon RX Vega M GL Graphics (vegam, LLVM 15.0.6, DRM 3.57, 6.8.8-4-pve) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc

Answered by cigas4

Aug 2, 2024

I already spent quite some time trying to install all these drivers, but mostly I did it in my Debian LXC.. Do you know how it actually works? Proxmox host has to have all the drivers and it does not matter what drivers you have inside LXC? Or, Proxmox just passes hardware device to LXC and then all drivers has to be managed inside LXC?

When hosting VMs on Proxmox and passing through GPU (or other devices), you need to take steps to ensure the device isn't initialised by the host machine at all and then pass it through to the guest, wherein it is initialised and correct drivers are to be installed (only).

When hosting LXCs on Proxmox, the GPU should be properly initialised (including c…

View full answer

cigas4 · 2024-07-30T10:57:29Z

cigas4
Jul 30, 2024
Author

Currently I am running Frigate container with disabled environment variable "LIBVA_DRIVER_NAME: radeonsi". So my Frigate uses iHD drivers for acceleration.

If I enable this variable in my docker-compose file, my Frigate stops running correctly and I find these errors in logs:
2024-07-30 10:55:09.942383451 [2024-07-30 10:55:09] watchdog.parking ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2024-07-30 10:55:09.942469297 [2024-07-30 10:55:09] ffmpeg.parking.detect ERROR : iris: driver missing 2024-07-30 10:55:09.942549888 [2024-07-30 10:55:09] ffmpeg.parking.detect ERROR : [AVHWDeviceContext @ 0x61bcb481dcc0] libva: /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so init failed 2024-07-30 10:55:09.942662650 [2024-07-30 10:55:09] ffmpeg.parking.detect ERROR : [AVHWDeviceContext @ 0x61bcb481dcc0] Failed to initialise VAAPI connection: 2 (resource allocation failed). 2024-07-30 10:55:09.942694668 [2024-07-30 10:55:09] ffmpeg.parking.detect ERROR : Device creation failed: -5. 2024-07-30 10:55:09.942795123 [2024-07-30 10:55:09] ffmpeg.parking.detect ERROR : [h264 @ 0x61bcb481c380] No device available for decoder: device type vaapi needed for codec h264. 2024-07-30 10:55:09.942852778 [2024-07-30 10:55:09] ffmpeg.parking.detect ERROR : Device setup failed for decoder on input stream #0:0 : Input/output error

Inside Frigate UI under System HW ACCEL:
Vainfo Output Return Code: 3 Process Error: 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.17.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 iris: driver missing 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-07-30T11:57:09Z

NickM-27
Jul 30, 2024
Collaborator Sponsor

Why do you think your intel NUC has an AMD GPU? I have very high doubts such a configuration exists considering that NUCs very rarely have discrete graphics

5 replies

NickM-27 Jul 30, 2024
Collaborator Sponsor

Interesting, well the issue will start back with what driver is installed and used in proxmox

cigas4 Jul 30, 2024
Author

I already spent quite some time trying to install all these drivers, but mostly I did it in my Debian LXC..
Do you know how it actually works? Proxmox host has to have all the drivers and it does not matter what drivers you have inside LXC? Or, Proxmox just passes hardware device to LXC and then all drivers has to be managed inside LXC?

nicoleise Jul 31, 2024

I already spent quite some time trying to install all these drivers, but mostly I did it in my Debian LXC.. Do you know how it actually works? Proxmox host has to have all the drivers and it does not matter what drivers you have inside LXC? Or, Proxmox just passes hardware device to LXC and then all drivers has to be managed inside LXC?

When hosting VMs on Proxmox and passing through GPU (or other devices), you need to take steps to ensure the device isn't initialised by the host machine at all and then pass it through to the guest, wherein it is initialised and correct drivers are to be installed (only).

When hosting LXCs on Proxmox, the GPU should be properly initialised (including correct drivers) on the host and inside the LXC, and these should be the same drivers/versions. Typically, these must be installed manually (not through repositories), and care must be taken when doing apt upgrade on the host in the future.

I realise you're not asking, but I'll offer the advice that I would very much consider using a VM instead. In any case, I think that these guides are both worthwhile reading/skimming, even if they are using nVidia hardware. They'll both give you good insight into the overall process and thus what you can expect from the result. :)

LXC: https://sluijsjes.nl/2024/05/18/coral-and-nvidia-passthrough-for-proxmox-lxc-to-install-frigate-video-surveillance-server/
VM: https://www.reddit.com/r/homelab/comments/b5xpua/the_ultimate_beginners_guide_to_gpu_passthrough/

cigas4 Aug 2, 2024
Author

I already spent quite some time trying to install all these drivers, but mostly I did it in my Debian LXC.. Do you know how it actually works? Proxmox host has to have all the drivers and it does not matter what drivers you have inside LXC? Or, Proxmox just passes hardware device to LXC and then all drivers has to be managed inside LXC?

When hosting VMs on Proxmox and passing through GPU (or other devices), you need to take steps to ensure the device isn't initialised by the host machine at all and then pass it through to the guest, wherein it is initialised and correct drivers are to be installed (only).

When hosting LXCs on Proxmox, the GPU should be properly initialised (including correct drivers) on the host and inside the LXC, and these should be the same drivers/versions. Typically, these must be installed manually (not through repositories), and care must be taken when doing apt upgrade on the host in the future.

I realise you're not asking, but I'll offer the advice that I would very much consider using a VM instead. In any case, I think that these guides are both worthwhile reading/skimming, even if they are using nVidia hardware. They'll both give you good insight into the overall process and thus what you can expect from the result. :)

LXC: https://sluijsjes.nl/2024/05/18/coral-and-nvidia-passthrough-for-proxmox-lxc-to-install-frigate-video-surveillance-server/ VM: https://www.reddit.com/r/homelab/comments/b5xpua/the_ultimate_beginners_guide_to_gpu_passthrough/

Hi, thanks for your replay.

Looks like I have managed to work this out. In some video I found info that you can't pass-through device if it is used by proxmox host. Therefore it is important to make sure that Proxmox host is not using your target graphic card as its primary VGA device.
I think for me this was the case. Most likely Proxmox used Radeon card as primary vga device so I was left only with integrated intel graphics to pass-though to my LCX.

This config helped me to change primary vga device of proxmox host, but in some cases it could also be BIOS setting:
nano /etc/default/grub

Old config:
GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on"

New:
GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on video=vesafb:off,efifb:off"

Sources used:
https://www.youtube.com/watch?v=IE0ew8WwxLM
https://www.youtube.com/watch?v=_hOBAGKLQkI&t=906s

Answer selected by NickM-27

nicoleise · 2024-07-30T14:27:04Z

nicoleise
Jul 30, 2024

I'm not sure if this is enough to cause the ENV variable to not set correctly (and thus for Docker to use the wrong driver), but you're declaring the variable with a different syntax than is in the documentation.

    environment:
      FRIGATE_RTSP_PASSWORD: 'pass'
      LIBVA_DRIVER_NAME: radeonsi

Docs state to add LIBVA_DRIVER_NAME=radeonsi

2 replies

NickM-27 Jul 30, 2024
Collaborator Sponsor

to be clear it depends how it is added, the syntax is different depending on what is used (docker cli, docker compose, etc)

cigas4 Jul 30, 2024
Author

Yes, it depends on a platform. In my case I use docker-compose. If I try to use = instead of :, compose of docker container fails due to syntax error. So this is not the issue.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[HW Accel Support]: Intel NUC8i7HVK AMD GPU #12673

{{title}}

Replies: 3 comments 7 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

[HW Accel Support]: Intel NUC8i7HVK AMD GPU #12673

cigas4 Jul 30, 2024

Describe the problem you are having

Version

Frigate config file

docker-compose file or Docker CLI command

Relevant log output

FFprobe output from your camera

Operating system

Install method

Network connection

Camera make and model

Any other information that may be helpful

Replies: 3 comments · 7 replies

cigas4 Jul 30, 2024 Author

NickM-27 Jul 30, 2024 Collaborator Sponsor

NickM-27 Jul 30, 2024 Collaborator Sponsor

cigas4 Jul 30, 2024 Author

nicoleise Jul 31, 2024

cigas4 Aug 2, 2024 Author

nicoleise Jul 30, 2024

NickM-27 Jul 30, 2024 Collaborator Sponsor

cigas4 Jul 30, 2024 Author

cigas4
Jul 30, 2024

Replies: 3 comments 7 replies

cigas4
Jul 30, 2024
Author

NickM-27
Jul 30, 2024
Collaborator Sponsor

NickM-27 Jul 30, 2024
Collaborator Sponsor

cigas4 Jul 30, 2024
Author

cigas4 Aug 2, 2024
Author

nicoleise
Jul 30, 2024

NickM-27 Jul 30, 2024
Collaborator Sponsor

cigas4 Jul 30, 2024
Author