VA API not working (Podman/Linux, Intel quiksync)

[pierrepaap 0]

Hey there,

I'm running emby with podman on Arch Linux and thought I'd have a look at hardware acceleration now that I have a subscription and modern Intel CPU

Unfortunately after a lot of trying, it still won't work.

You'll find here the hardware detection log file and some commands I ran on my machine to make sure everything is as it should.
(e.g. user in the correct video groups on the host, appropriate UID and GID between host and container including on /dev/dri devices, appropriate GIDLIST, etc.)

So maybe I missed something and somebody will see it when I didn't, or... there's another hiccup ?

Please note I read the Arch linux page on hardware accel, the docker hub page and linuxserver page for the emby container, a variety of pages and posts on the emby website.

Thanks in advance for you help !

Let me know if you need more info, I'll be happy to oblige and grateful for the help.

[root@arch ~]# grep container /etc/passwd /etc/group
/etc/passwd:container:x:122:122::/home/container:/bin/bash
/etc/group:render:x:989:container
/etc/group:video:x:985:container
/etc/group:container:x:122:
[root@arch ~]# ls -la /dev/dri
total 0
drwxr-xr-x  3 root root        100 Jan 25 10:52 .
drwxr-xr-x 21 root root       4660 Jan 25 10:52 ..
drwxr-xr-x  2 root root         80 Jan 25 10:52 by-path
crw-rw----  1 root video  226,   0 Jan 25 10:52 card0
crw-rw-rw-  1 root render 226, 128 Jan 25 10:52 renderD128
[root@arch ~]# podman exec -ti /bin/bash
Error: no container with name or ID "bin/bash" found: no such container
[root@arch ~]# podman exec -ti emby /bin/bash
root@2e2d596b2ca3:/# grep abc /etc/passwd /etc/group
/etc/passwd:abc:x:122:122::/config:/bin/false
/etc/group:users:x:100:abc
/etc/group:abc:x:122:
/etc/group:videofyjd:x:985:abc
/etc/group:video9235:x:989:abc
root@2e2d596b2ca3:/# ls -la /dev/dri
total 0
drwxr-xr-x 2 root root            80 Jan 25 10:52 .
drwxr-xr-x 6 root root           360 Jan 25 10:52 ..
crw-rw---- 1 root videofyjd 226,   0 Jan 25 10:52 card0
crw-rw-rw- 1 root video9235 226, 128 Jan 25 10:52 renderD128
root@2e2d596b2ca3:/# 
exit
[root@arch ~]# vainfo
Trying display: wayland
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
Trying display: x11
error: can't connect to X server!
Trying display: drm
vainfo: VA-API version: 1.20 (libva 2.20.1)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 24.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
      VAProfileHEVCMain               :	VAEntrypointVLD
      VAProfileHEVCMain               :	VAEntrypointEncSlice
      VAProfileHEVCMain               :	VAEntrypointFEI
      VAProfileHEVCMain               :	VAEntrypointEncSliceLP
      VAProfileHEVCMain10             :	VAEntrypointVLD
      VAProfileHEVCMain10             :	VAEntrypointEncSlice
      VAProfileHEVCMain10             :	VAEntrypointEncSliceLP
      VAProfileVP9Profile0            :	VAEntrypointVLD
      VAProfileVP9Profile0            :	VAEntrypointEncSliceLP
      VAProfileVP9Profile1            :	VAEntrypointVLD
      VAProfileVP9Profile1            :	VAEntrypointEncSliceLP
      VAProfileVP9Profile2            :	VAEntrypointVLD
      VAProfileVP9Profile2            :	VAEntrypointEncSliceLP
      VAProfileVP9Profile3            :	VAEntrypointVLD
      VAProfileVP9Profile3            :	VAEntrypointEncSliceLP
      VAProfileHEVCMain12             :	VAEntrypointVLD
      VAProfileHEVCMain12             :	VAEntrypointEncSlice
      VAProfileHEVCMain422_10         :	VAEntrypointVLD
      VAProfileHEVCMain422_10         :	VAEntrypointEncSlice
      VAProfileHEVCMain422_12         :	VAEntrypointVLD
      VAProfileHEVCMain422_12         :	VAEntrypointEncSlice
      VAProfileHEVCMain444            :	VAEntrypointVLD
      VAProfileHEVCMain444            :	VAEntrypointEncSliceLP
      VAProfileHEVCMain444_10         :	VAEntrypointVLD
      VAProfileHEVCMain444_10         :	VAEntrypointEncSliceLP
      VAProfileHEVCMain444_12         :	VAEntrypointVLD
      VAProfileHEVCSccMain            :	VAEntrypointVLD
      VAProfileHEVCSccMain            :	VAEntrypointEncSliceLP
      VAProfileHEVCSccMain10          :	VAEntrypointVLD
      VAProfileHEVCSccMain10          :	VAEntrypointEncSliceLP
      VAProfileHEVCSccMain444         :	VAEntrypointVLD
      VAProfileHEVCSccMain444         :	VAEntrypointEncSliceLP
      VAProfileAV1Profile0            :	VAEntrypointVLD
      VAProfileHEVCSccMain444_10      :	VAEntrypointVLD
      VAProfileHEVCSccMain444_10      :	VAEntrypointEncSliceLP
[root@arch ~]# grep dir /etc/systemd/system/container-emby.service 
[root@arch ~]# grep dri /etc/systemd/system/container-emby.service 
	--device=/dev/dri:/dev/dri \
[root@arch ~]# grep GIDLIST /etc/systemd/system/container-emby.service 
	-e GIDLIST=985,989 \
[root@arch ~]# grep P?ID /etc/systemd/system/container-emby.service 
[root@arch ~]# grep PUID /etc/systemd/system/container-emby.service 
	-e PUID=122 \
[root@arch ~]# grep PGID /etc/systemd/system/container-emby.service 
	-e PGID=122 \
[root@arch ~]#

 

 

hardware_detection-63841765536.json

Edited January 25 by pierrepaap
typos

[Q-Droid 653]

Raptor Lake is too new for the Emby stable release (4.7.x). Try the official Emby beta (4.8.x) Docker image if you want HW accel. The LSIO image may or may not work.

[pierrepaap 0]

ah still ? I saw a message like this from last may I think.

Anyway, thanks, i'll try that then.

if not LSIO i suppose it should be from the official docker hub image ?

[Q-Droid 653]

You can use either image but if LSIO still doesn't work then you should try the Emby official (yes, Emby docker hub) before reporting any problems because they've had differences in the past.