Unraid - AMD iGPU - Docker

Channels DVR Server
#1

Has anyone had any success in getting hardware transcording working within a Unraid Docker and an AMD iGPU. I'm a few months off having a dedicated GPU so would have liked to get this going in the meantime.

I have successfully got this working in Plex but unable to get Channels DVR to work.

h264_amf
fork/exec /channels-dvr/2025.02.19.1823/ffmpeg-dl: no such file or directory
h264_nvenc
fork/exec /channels-dvr/2025.02.19.1823/ffmpeg-dl: no such file or directory
h264_nvenc+deint
fork/exec /channels-dvr/2025.02.19.1823/ffmpeg-dl: no such file or directory
h264_nvenc+scaler
fork/exec /channels-dvr/2025.02.19.1823/ffmpeg-dl: no such file or directory
h264_nvenc+tonemap
fork/exec /channels-dvr/2025.02.19.1823/ffmpeg-dl: no such file or directory
h264_vaapi@/dev/dri/card0
[AVHWDeviceContext @ 0x8facd40] libva: VA-API version 1.22.0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [2]
param: 4, val: 0
i915 does not support EXECBUFER2
DRM_IOCTL_VERSION, unsupported drm device by media driver: amdg
DRM_IOCTL_VERSION, unsupported drm device by media driver: amdg
[AVHWDeviceContext @ 0x8facd40] libva: driver init failed
[AVHWDeviceContext @ 0x8facd40] libva: va_openDriver() returns 18
[AVHWDeviceContext @ 0x8facd40] Failed to initialise VAAPI connection: 18 (invalid parameter).
signal: segmentation fault
h264_vaapi@/dev/dri/renderD128
[AVHWDeviceContext @ 0x8facd40] libva: VA-API version 1.22.0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [2]
param: 4, val: 0
i915 does not support EXECBUFER2
DRM_IOCTL_VERSION, unsupported drm device by media driver: amdg
DRM_IOCTL_VERSION, unsupported drm device by media driver: amdg
[AVHWDeviceContext @ 0x8facd40] libva: driver init failed
[AVHWDeviceContext @ 0x8facd40] libva: va_openDriver() returns 18
[AVHWDeviceContext @ 0x8facd40] Failed to initialise VAAPI connection: 18 (invalid parameter).
signal: segmentation fault
h264_vaapi@/dev/dri/renderD129
no such file or directory
h264_vaapi@/dev/renderD128
no such file or directory
#2

What kind of hardware are you using?

#3

AMD Ryzen 5 PRO 3350G

#4

Can you try updating to prerelease

#6

Same result, still not finding any hardware to use.

#7

Does it still say this or something different

#8
h264_amf

fork/exec /channels-dvr/2025.03.12.0028/ffmpeg-dl: no such file or directory

h264_nvenc

fork/exec /channels-dvr/2025.03.12.0028/ffmpeg-dl: no such file or directory

h264_nvenc+deint

fork/exec /channels-dvr/2025.03.12.0028/ffmpeg-dl: no such file or directory

h264_nvenc+scaler

fork/exec /channels-dvr/2025.03.12.0028/ffmpeg-dl: no such file or directory

h264_nvenc+tonemap

fork/exec /channels-dvr/2025.03.12.0028/ffmpeg-dl: no such file or directory

h264_vaapi@/dev/dri/card0

[AVHWDeviceContext @ 0x9f42d40] libva: VA-API version 1.22.0 DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [2] param: 4, val: 0 i915 does not support EXECBUFER2 DRM_IOCTL_VERSION, unsupported drm device by media driver: amdg DRM_IOCTL_VERSION, unsupported drm device by media driver: amdg [AVHWDeviceContext @ 0x9f42d40] libva: driver init failed [AVHWDeviceContext @ 0x9f42d40] libva: va_openDriver() returns 18 [AVHWDeviceContext @ 0x9f42d40] Failed to initialise VAAPI connection: 18 (invalid parameter).

signal: segmentation fault

h264_vaapi@/dev/dri/renderD128

[AVHWDeviceContext @ 0x9f42d40] libva: VA-API version 1.22.0 DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [2] param: 4, val: 0 i915 does not support EXECBUFER2 DRM_IOCTL_VERSION, unsupported drm device by media driver: amdg DRM_IOCTL_VERSION, unsupported drm device by media driver: amdg [AVHWDeviceContext @ 0x9f42d40] libva: driver init failed [AVHWDeviceContext @ 0x9f42d40] libva: va_openDriver() returns 18 [AVHWDeviceContext @ 0x9f42d40] Failed to initialise VAAPI connection: 18 (invalid parameter).

signal: segmentation fault

h264_vaapi@/dev/dri/renderD129

no such file or directory

h264_vaapi@/dev/renderD128

no such file or directory

#10

@CurtisFeatures Can you update to the latest DVR pre-release and then submit diagnostics?

#11

@eric - c961f290-8d1a-46f9-963f-3e5476a7faa3

#12

@CurtisFeatures Similar issue to what you're seeing with an integrated AMD GPU. I'm not running in docker (native linux installation), but could not get hardware acceleration to work with errors similar to what you're seeing. I finally got it to work by copying a newer version of FFmpeg into the 'latest' directory inside the channels install directory, restarted channels, and hardware encoding was enabled. Of course this may create other issues, but seems to be working fine so far. The original version of FFmpeg was 6.0.2, the one I copied in was 7.1.

#13

Thanks, I’m awaiting delivery on a quadro card so hopefully that will just work out of the box

#14

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.