Channels, Unraid, AMD and Transcoding

Is Hardware transcoding available for AMD graphics (Ryzen 7 5700G) running on UnRaid 6.12.3?
I have seen some try to get AMD going but none pertain to UnRaid. I know it's probably no, but just want to make sure.

And does one really need hardware transcoding?

Can't get Channels to see my Video Processor. I can pick it in Plex but Channels does not see it. Not sure what is wrong. I am up to date on the Pre-Release. I did do a rescan for hardware.

image

amf
fork/exec /channels-dvr/2023.08.09.2030/ffmpeg-dl: no such file or directory
nvenc
fork/exec /channels-dvr/2023.08.09.2030/ffmpeg-dl: no such file or directory
vaapi@/dev/dri/card0
[AVHWDeviceContext @ 0x7b89280] libva: VA-API version 1.16.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
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
[AVHWDeviceContext @ 0x7b89280] libva: driver init failed
[AVHWDeviceContext @ 0x7b89280] libva: va_openDriver() returns 18
[AVHWDeviceContext @ 0x7b89280] Failed to initialise VAAPI connection: 18 (invalid parameter).
signal: segmentation fault
vaapi@/dev/dri/renderD128
[AVHWDeviceContext @ 0x7b89280] libva: VA-API version 1.16.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
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
[AVHWDeviceContext @ 0x7b89280] libva: driver init failed
[AVHWDeviceContext @ 0x7b89280] libva: va_openDriver() returns 18
[AVHWDeviceContext @ 0x7b89280] Failed to initialise VAAPI connection: 18 (invalid parameter).
signal: segmentation fault
vaapi@/dev/dri/renderD129
no such file or directory
vaapi@/dev/renderD128
no such file or directory

Is it running natively, or in a container? If in a container (such as via Docker), you need to also pass in the appropriate device nodes, and ensure that permissions on those nodes match the permissions the container runs under.

It's in a container. I have the dev/dri added to Channels. My Go has
modprobe amdgpu
chmod -R 777 /dev/dri
Unraid sees it fine. Plex sees it fine. Channels cannot see it.

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

I do have that file and not sure why it's hosed.

Looks like the BIOS Is out of date. Will update that and see what happens.

Yeah, still forked. I think the issue is that my instance is at channelsDVR and it's looking at channels-dvr...

Submitted Diagnostics.

a255ba5a-79db-4da3-925b-b9eeae2675ad

Has somewhat the same error as the Pi issue.

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