Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


switch last won the day on July 2 2019

switch had the most liked content!

Community Reputation

12 Good

About switch

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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?
  3. 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.
  4. 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.
  5. Careful, Linux is case-sensitive. From your first screenshot, the name of the container is "embyserver", not "EmbyServer".
  6. 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
  7. As this is not likely related to the issue we were dealing with in this thread, let's take further troubleshooting to the thread you've created.
  8. Looks like you're passing through the device incorrectly. Pass just /dev/dri, not /dev/dri/renderD128. See if that helps.
  9. Thanks. Looks like they're already working on a fix. For now, I'll make a script that'll run after a Plex update to check if the iHD driver exists and if it does, delete it.
  10. Great find, thanks! How did you find out about it? Google doesn't find much about the iHD_drv_video.so driver on the Plex forums. Have you reported the issue to the Plex devs? If so, is there a thread that you can link me to so I can +1 it?
  11. Just wanna let everyone know that this issue is fully fixed on unRAID 6.8.0-rc1. Everything works as expected without disabling IOMMU or any other config edits, patches or hacks.
  12. This is perfect! Thanks a lot for your effort! Can confirm that "intel_iommu=igfx_off" is working for me as well on 6.7.3-rc3. Since this is clearly a bug in the Linux kernel and not within unRAID itself, I have now marked this bug report as resolved. @limetech, this appears to be fixed in the kernel v5.0 and up, will unRAID 6.8 include a v5.0+ kernel?
  13. Can you please clarify what do you mean by "one of the downgrades"?