Civic1201 Posted May 18, 2020 Share Posted May 18, 2020 (edited) Hi, I tried everything to get hardware acceleration working on my system: Asrock J4105 mITX Unraid 6.8.3 Whenever I try to transcode a file the cpu load will go up to 100%, so VAAPI is not working. Please have a look at the screenshots: Any ideas what I am doing wrong? Edited May 19, 2020 by Civic1201 Quote Link to comment
switch Posted May 21, 2020 Share Posted May 21, 2020 (edited) 42 minutes ago, switch said: Looks like you're passing through the device incorrectly. Pass just /dev/dri, not /dev/dri/renderD128. See if that helps. 37 minutes ago, Civic1201 said: Same result as before with renderD128... Open up an Unraid terminal and try this: docker exec -it embyserver /bin/bash This'll effectively take you into a terminal session inside of your Emby container. Once you're in, type the follwing commands and paste their output here. ls -la /dev/dri vainfo The vainfo package will most likely not be installed inside the Emby container, assuming it is based on Ubuntu, install it via sudo apt update && sudo apt install vainfo Edited May 21, 2020 by switch Quote Link to comment
Civic1201 Posted May 21, 2020 Author Share Posted May 21, 2020 (edited) This will give me this result: Quote Linux 4.19.107-Unraid. Last login: Thu May 21 19:53:23 +0200 2020 on /dev/pts/0. root@Tower:~# docker exec -it EmbyServer /bin/bash OCI runtime exec failed: exec failed: container_linux.go:346: starting container process caused "exec: \"/bin/bash\": stat /bin/bash: no such file or directory": unknown Edited May 21, 2020 by Civic1201 Quote Link to comment
switch Posted May 21, 2020 Share Posted May 21, 2020 Careful, Linux is case-sensitive. From your first screenshot, the name of the container is "embyserver", not "EmbyServer". Quote Link to comment
Civic1201 Posted May 21, 2020 Author Share Posted May 21, 2020 Yes I know. due to too much modifications I had to create a new container... Quote Link to comment
switch Posted May 21, 2020 Share Posted May 21, 2020 (edited) Then the container doesn't have a bash shell. Try opening up the terminal by clicking on the container icon in the docker manager and select Console. Also, have you tried linuxserver's version of the Emby container? May be worth a shot. Edited May 21, 2020 by switch Quote Link to comment
Civic1201 Posted May 21, 2020 Author Share Posted May 21, 2020 (edited) Here is the output from within the container. vainfo is not installed, but is Unraid really based on Ubuntu? Edited May 21, 2020 by Civic1201 Quote Link to comment
switch Posted May 21, 2020 Share Posted May 21, 2020 (edited) Unraid is based on Slackware. What's important is, what's used as the base for the Emby container. Could be Alpine, could be Arch, Ubuntu... There is something wrong with the passthrough setup, the output should look like this: root@optiplex:/# ls -la /dev/dri total 0 drwxr-xr-x 2 root root 80 May 17 19:20 . drwxr-xr-x 6 root root 360 May 17 19:20 .. crw-rw---- 1 root video 226, 0 May 17 19:20 card0 crw-rw---- 1 root videouYsyOXiq 226, 128 May 17 19:20 renderD128 You're missing the card0 device completely. Ditch the official Emby container and try using Linuxserver's. Edited May 21, 2020 by switch Quote Link to comment
Civic1201 Posted May 21, 2020 Author Share Posted May 21, 2020 sudo won't work. Quote Link to comment
switch Posted May 21, 2020 Share Posted May 21, 2020 (edited) Omit sudo, as you're already root inside the container. But as card0 is missing, you'll likely won't get anything useful from vainfo. How does ls -la /dev/dri look like from the Unraid terminal? Edited May 21, 2020 by switch Quote Link to comment
Civic1201 Posted May 21, 2020 Author Share Posted May 21, 2020 Same result without sudo. So should I try the container you mentioned? Quote Link to comment
switch Posted May 21, 2020 Share Posted May 21, 2020 2 minutes ago, Civic1201 said: Same result without sudo. So should I try the container you mentioned? Don't know what the official Emby container uses as it's base. What I know is it does not use apt as it's package manager Yes, try linuxserver's version of the container. And please post output of ls -la /dev/dri from the Unraid terminal as well. Quote Link to comment
Civic1201 Posted May 21, 2020 Author Share Posted May 21, 2020 (edited) Ok, this works better. But I can not open the web ui and I have no idea where to enter the appdata config. edit: OK, container is running but still 100% cpu load while transcoding. This is frustrating. Edited May 21, 2020 by Civic1201 Quote Link to comment
CS01-HS Posted May 21, 2020 Share Posted May 21, 2020 (edited) With the official EmbySever container, follow the instructions here, substituting Emby where appropriate: Then go to Main -> Flash -> Syslinux Configuration -> Unraid OS and change the line: append initrd=/bzroot to append initrd=/bzroot intel_iommu=igfx_off Hit "Apply" and reboot. At this point hardware encoding should be working but the video output will be garbled. Follow instructions here to resolve that: Edited May 21, 2020 by CS01-HS 1 Quote Link to comment
Civic1201 Posted May 21, 2020 Author Share Posted May 21, 2020 6 minutes ago, CS01-HS said: With the official EmbySever container, follow the instructions here, substituting Emby where appropriate: Then go to Main -> Flash -> Syslinux Configuration -> Unraid OS and change the line: append initrd=/bzroot to append initrd=/bzroot intel_iommu=igfx_off Hit "Apply" and reboot. At this point hardware encoding should be working but the video output will be garbled. Follow instructions here to resolve that: I will try that, thanks for the advice. With the new container I get this in Emby. Quote Link to comment
Civic1201 Posted May 21, 2020 Author Share Posted May 21, 2020 YES, finally! Thank you very much @ CS01-HS Quote Link to comment
CS01-HS Posted May 21, 2020 Share Posted May 21, 2020 Glad it worked. It's a nice little board. 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.