[HW Accel Support]: Unable to start Frigate with AMD Radeon HD 4290 GPU

[rajuga153]

Describe the problem you are having

Frigate container is not starting on AMD Phenom(tm) II X4 965 Processor with AMD Radeon HD 4290.

Version

0.15.0

Frigate config file

ffmpeg:
  path: default
  global_args: -hide_banner -loglevel warning -threads 2
  hwaccel_args: preset-vaapi
  input_args: preset-rtsp-restream
  output_args:
    detect: -threads 2 -f rawvideo -pix_fmt yuv420p
    record: preset-record-generic
  retry_interval: 10

go2rtc:
  streams:
    Portico:
      rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.68.240:554/cam/realmonitor?channel=1&subtype=0
    Portico_sub:
      rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.68.240:554/cam/realmonitor?channel=1&subtype=1
    Left-Side:
      rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.68.241:554/cam/realmonitor?channel=1&subtype=0
    Left-Side_sub:
      rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.68.241:554/cam/realmonitor?channel=1&subtype=1
    Back-Yard:
      rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.68.242:554/cam/realmonitor?channel=1&subtype=0
    Back-Yard_sub:
      rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.68.242:554/cam/realmonitor?channel=1&subtype=1
    Right-Side:
      rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.68.243:554/cam/realmonitor?channel=1&subtype=0
    Right-Side_sub:
      rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.68.243:554/cam/realmonitor?channel=1&subtype=1
    Front-Yard:
      rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.68.244:554/cam/realmonitor?channel=1&subtype=0
    Front-Yard_sub:
      rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.68.244:554/cam/realmonitor?channel=1&subtype=1
    DoorBell:
      - rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.68.230:554/Preview_01_main#backchannel=0
      - rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.68.230:554/Preview_01_sub
      - ffmpeg:DoorBell#audio=opus#hardware
    DoorBell_sub:
      - rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.68.230:554/Preview_01_sub
      - ffmpeg:DoorBell_sub#audio=opus#hardware

docker-compose file or Docker CLI command

frigate:
    container_name: frigate
    image: ghcr.io/blakeblackshear/frigate:stable
    privileged: true # this may not be necessary for all setups
    restart: unless-stopped
    stop_grace_period: 30s # allow enough time to shut down the various services
    network_mode: host
    shm_size: "256mb" # update for your cameras based on calculation above
    devices:
      - /dev/apex_0:/dev/apex_0 # passes a PCIe Coral, follow driver instructions here https://coral.ai/docs/m2/get-started/#2a-on-linux
      - /dev/dri/renderD128 # for intel hwaccel, needs to be updated for your hardware
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /mnt2/Docker/Frigate/config/:/config/
      - /mnt2/Frigate:/media/frigate
      - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - "8971:8971"
      - "8554:8554" # RTSP feeds
      - "8555:8555/tcp" # WebRTC over tcp
      - "8555:8555/udp" # WebRTC over udp
    environment:
      LIBVA_DRIVER_NAME: "radeonsi"

Relevant Frigate log output

s6-rc: info: service s6rc-fdholder: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service s6rc-fdholder successfully started
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service log-prepare: starting
s6-rc: info: service log-prepare successfully started
s6-rc: info: service nginx-log: starting
s6-rc: info: service go2rtc-log: starting
s6-rc: info: service frigate-log: starting
s6-rc: info: service certsync-log: starting
s6-rc: info: service nginx-log successfully started
s6-rc: info: service go2rtc-log successfully started
s6-rc: info: service go2rtc: starting
s6-rc: info: service certsync-log successfully started
s6-rc: info: service frigate-log successfully started
s6-rc: info: service go2rtc successfully started
s6-rc: info: service go2rtc-healthcheck: starting
s6-rc: info: service frigate: starting
s6-rc: info: service go2rtc-healthcheck successfully started
s6-rc: info: service frigate successfully started
s6-rc: info: service nginx: starting
2025-02-17 20:06:12.575548708  [INFO] Preparing new go2rtc config...
2025-02-17 20:06:12.575563246  [INFO] Preparing Frigate...
2025-02-17 20:06:12.575581892  [INFO] Starting NGINX...
s6-rc: info: service nginx successfully started
s6-rc: info: service certsync: starting
s6-rc: info: service certsync successfully started
s6-rc: info: service legacy-services: starting
2025-02-17 20:06:14.760463912  [INFO] Starting certsync...
s6-rc: info: service legacy-services successfully started
2025-02-17 20:06:15.046135248  [INFO] Starting Frigate...
2025-02-17 20:06:15.067764368  127.0.0.1 - - [17/Feb/2025:20:06:15 +0530] "" 400 0 "-" "-" "-"
2025-02-17 20:06:16.528926117  2025/02/17 20:06:16 [error] 159#159: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"
2025-02-17 20:06:16.528971879  2025/02/17 20:06:16 [error] 159#159: *2 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"
2025-02-17 20:06:19.904505677  [INFO] Starting go2rtc...
2025-02-17 20:06:20.123800259  20:06:20.123 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2025-02-17 20:06:20.123816965  20:06:20.123 INF config path=/dev/shm/go2rtc.yaml
2025-02-17 20:06:20.124763885  20:06:20.124 INF [rtsp] listen addr=:8554
2025-02-17 20:06:20.124922978  20:06:20.124 INF [api] listen addr=:1984
2025-02-17 20:06:20.125230146  20:06:20.124 INF [webrtc] listen addr=:8555/tcp
2025-02-17 20:06:20.757052881  [INFO] Service Frigate exited with code 256 (by signal 4)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service go2rtc-healthcheck: stopping
s6-rc: info: service certsync: stopping
2025-02-17 20:06:20.777846447  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
s6-rc: info: service go2rtc-healthcheck successfully stopped
2025-02-17 20:06:20.779419901  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
s6-rc: info: service certsync successfully stopped
s6-rc: info: service nginx: stopping
s6-rc: info: service certsync-log: stopping
s6-rc: info: service certsync-log successfully stopped
2025-02-17 20:06:20.863650668  [INFO] Service NGINX exited with code 0 (by signal 0)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service nginx-log: stopping
s6-rc: info: service frigate: stopping
s6-rc: info: service frigate successfully stopped
s6-rc: info: service go2rtc: stopping
s6-rc: info: service frigate-log: stopping
2025-02-17 20:06:20.867241246  exit with signal: terminated
s6-rc: info: service nginx-log successfully stopped
s6-rc: info: service frigate-log successfully stopped
2025-02-17 20:06:20.873593528  [INFO] The go2rtc service exited with code 0 (by signal 0)
s6-rc: info: service go2rtc successfully stopped
s6-rc: info: service go2rtc-log: stopping
s6-rc: info: service go2rtc-log successfully stopped
s6-rc: info: service log-prepare: stopping
s6-rc: info: service s6rc-fdholder: stopping
s6-rc: info: service log-prepare successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service s6rc-fdholder successfully stopped
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Relevant go2rtc log output

HTTP/1.1", host: "127.0.0.1:5000"
2025-02-17 20:06:19.904505677  [INFO] Starting go2rtc...
2025-02-17 20:06:20.123800259  20:06:20.123 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2025-02-17 20:06:20.123816965  20:06:20.123 INF config path=/dev/shm/go2rtc.yaml
2025-02-17 20:06:20.124763885  20:06:20.124 INF [rtsp] listen addr=:8554
2025-02-17 20:06:20.124922978  20:06:20.124 INF [api] listen addr=:1984
2025-02-17 20:06:20.125230146  20:06:20.124 INF [webrtc] listen addr=:8555/tcp
2025-02-17 20:06:20.757052881  [INFO] Service Frigate exited with code 256 (by signal 4)

FFprobe output from your camera

NA

Install method

Docker Compose

Object Detector

Coral

Network connection

Wired

Camera make and model

Amcrest

Screenshots of the Frigate UI's System metrics pages

NA

Any other information that may be helpful

30: PCI 105.0: 0300 VGA compatible controller (VGA)
[Created at pci.386]
Unique ID: ul7N.uBw2Qv5foDD
Parent ID: vSkL.2yY_xudKZ6E
SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:05.0
SysFS BusID: 0000:01:05.0
Hardware Class: graphics card
Model: "ATI RS880 [Radeon HD 4290]"
Vendor: pci 0x1002 "ATI Technologies Inc"
Device: pci 0x9714 "RS880 [Radeon HD 4290]"
SubVendor: pci 0x1458 "Gigabyte Technology Co., Ltd"
SubDevice: pci 0xd000
Driver: "radeon"
Driver Modules: "radeon"
Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable)
I/O Ports: 0xce00-0xceff (rw)
Memory Range: 0xfd5e0000-0xfd5effff (rw,non-prefetchable)
Memory Range: 0xfd400000-0xfd4fffff (rw,non-prefetchable)
Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled)
IRQ: 18 (2 events)
Module Alias: "pci:v00001002d00009714sv00001458sd0000D000bc03sc00i00"
Driver Info #0:
Driver Status: radeon is active
Driver Activation Cmd: "modprobe radeon"
Driver Info #1:
Driver Status: amdgpu is active
Driver Activation Cmd: "modprobe amdgpu"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #12 (PCI bridge)

Primary display adapter: #30

[NickM-27]

You haven't defined any cameras

[rajuga153]

I forgot to copy Camera related config settings. Pls find same in below.

Front-Yard:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/Front-Yard
roles:
- record
- path: rtsp://127.0.0.1:8554/Front-Yard_sub
roles:
- detect
live:
stream_name: Front-Yard_sub
DoorBell:
ffmpeg:
output_args:
record: preset-record-generic-audio-aac
inputs:
- path: rtsp://127.0.0.1:8554/DoorBell?video=copy&audio=aac
roles:
- record
- path: rtsp://127.0.0.1:8554/DoorBell_sub?video=copy&audio=aac
roles:
- audio
- detect
live:
stream_name: DoorBell_sub

[hawkeye217]

2025-02-17 20:06:20.757052881 [INFO] Service Frigate exited with code 256 (by signal 4)

Signal 4 is an illegal instruction. What docker image are you using?

[rajuga153]

frigate:
container_name: frigate
image: ghcr.io/blakeblackshear/frigate:stable

/mnt2/Docker # docker info
Client:
Version: 26.1.5-ce
Context: default
Debug Mode: false
Plugins:
compose: Docker Compose (Docker Inc.)
Version: 2.22.0
Path: /usr/lib/docker/cli-plugins/docker-compose

Server:
Containers: 6
Running: 5
Paused: 0
Stopped: 1
Images: 6
Server Version: 26.1.5-ce
Storage Driver: btrfs
Btrfs:
Logging Driver: journald
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 oci runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 57f17b0a6295a39009d861b89e3b3b87b005ca27
runc version: v1.1.14-0-g2c9f5602f0ba
init version:
Security Options:
apparmor
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.4.0-150600.23.38-default
Operating System: Rockstor built on openSUSE Leap 15.6
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 15.13GiB
Name: RazNAS
ID: 28b4172c-03c6-475d-9d5e-07600298fa6b
Docker Root Dir: /mnt2/Rock-ons
Debug Mode: false
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false

[hawkeye217]

Your AMD processor is from 2009. A signal 4 illegal instruction error indicates that it may not support code that Frigate needs.

[rajuga153]

You mean to say that this processor is not compatible for Frigate? Any alternate or workarounds?

[hawkeye217]

Your processor is too old and doesn't support AVX instructions, which is required for Frigate. There is an "oldcpu" variant available as a Home Assistant addon, but it does not come without caveats. The recommendation is to upgrade to a more modern CPU.

https://github.com/blakeblackshear/frigate-hass-addons/blob/main/frigate_oldcpu/Dockerfile