Hardware transcoding is not working

[random_eric]

I followed the guide but hardware transcoding is not working (for quicksync at least)

The guide assumes that everything is working well, but does not offer troubleshooting steps.

This is the output of vainfo:

libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_10
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.14 (libva 2.12.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Skylake - 2.4.1
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Simple            : VAEntrypointEncSlice
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
      VAProfileH264ConstrainedBaseline: VAEntrypointFEI
      VAProfileH264ConstrainedBaseline: VAEntrypointStats
      VAProfileH264Main               : VAEntrypointVLD
      VAProfileH264Main               : VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointEncSliceLP
      VAProfileH264Main               : VAEntrypointFEI
      VAProfileH264Main               : VAEntrypointStats
      VAProfileH264High               : VAEntrypointVLD
      VAProfileH264High               : VAEntrypointEncSlice
      VAProfileH264High               : VAEntrypointEncSliceLP
      VAProfileH264High               : VAEntrypointFEI
      VAProfileH264High               : VAEntrypointStats
      VAProfileH264MultiviewHigh      : VAEntrypointVLD
      VAProfileH264StereoHigh         : VAEntrypointVLD
      VAProfileVC1Simple              : VAEntrypointVLD
      VAProfileVC1Main                : VAEntrypointVLD
      VAProfileVC1Advanced            : VAEntrypointVLD
      VAProfileJPEGBaseline           : VAEntrypointVLD
      VAProfileJPEGBaseline           : VAEntrypointEncPicture
      VAProfileVP8Version0_3          : VAEntrypointVLD
      VAProfileHEVCMain               : VAEntrypointVLD

and this the hardware_detection in emby:

DeviceIndex": 0,
"DeviceInfo": {
"VendorName": "Intel Corporation",
"DeviceName": "HD Graphics 530",
"SubsytemVendorName": "Hewlett-Packard Company",
"VendorId": 32902,
"DeviceId": 6418,
"SubsytemVendorId": 4156,
"SubsytemDeviceId": 32854,
"DevPath": "/sys/bus/pci/devices/0000:00:02.0",
"DrmCard": "/dev/dri/card0",
"DrmRender": "/dev/dri/renderD128",
"IsEnabled": 1,
"IsBootVga": 1
},
"Error": {
"Number": -1,
"Message": "Failed to open the drm device /dev/dri/renderD128"
}

So I do have quick sync on my cpu, but it looks like something is not setup correctly with the emby image.

I don't know if this is normal, but this is theoutput that I see when I run ls /dev/dri from within the docker container.

root@2109ec5d-beb5-4287-a080-b4591978c3e6:/dev/dri# ls -l
total 0
crw-rw---- 1 root video 226,   0 Oct  7 21:03 card0
crw-rw---- 1 root   109 226, 128 Oct  7 21:03 renderD128

[subven]

What OS do you use? Ubuntu 20.04 or 22.04? Your problem seems to be permission related. Maybe because of docker and cgroup.

"Message": "Failed to open the drm device /dev/dri/renderD128"

crw-rw---- 1 root   109 226, 128 Oct  7 21:03 renderD128

Emby is not able to access renderD128 and what is group 109? Can someone else please compare that with his own configuration?

[random_eric]

@subven
Interesting. I thought I had changed the permission to ensure that was not it, but you're right. It really was the permissions.
Group 109 is render on the host..

Thanks for pointing out the issue
(It's 22.04)

[nebulon]

@random_eric does it work now after adjusting the permissions?

[random_eric]

@nebulon
Yes, it works now.
I chmodded with a+rw

[randyjc]

@random_eric sorry to be reopening this topic. But how did you managed to get this permission being set?

I got the exact same issue currently.

"DeviceIndex": 0,
"DeviceInfo": {
"VendorName": "Intel Corporation",
"DeviceName": "Iris Pro Graphics 580",
"SubsytemVendorName": "Intel Corporation",
"VendorId": 32902,
"DeviceId": 6459,
"SubsytemVendorId": 32902,
"SubsytemDeviceId": 8292,
"DevPath": "/sys/bus/pci/devices/0000:00:02.0",
"DrmCard": "/dev/dri/card0",
"DrmRender": "/dev/dri/renderD128",
"IsEnabled": 1,
"IsBootVga": 1,
"Error": {
"Number": -1,
"Message": "Failed to open the drm device /dev/dri/renderD128"

------

drwxr-xr-x  3 root root        100 Jan  4 11:45 .
drwxr-xr-x 20 root root       4.3K Jan  4 11:45 ..
drwxr-xr-x  2 root root         80 Jan  4 11:45 by-path
crw-rw----  1 root video  226,   0 Jan  4 11:45 card0
crw-rw----  1 root render 226, 128 Jan  4 11:45 renderD128

[randyjc]

Fixed it:
Create:

/etc/udev/rules.d/99-dri.rules

paste:

KERNEL=="card[0-9]*", GROUP="video", MODE="0666"
KERNEL=="renderD*", GROUP="video", MODE="0666"

source:

https://emby.media/community/index.php?/topic/67576-omv-docker-emby-problem-with-vaapi/&do=findComment&comment=1002606