Jump to content


Photo

OMV DOCKER EMBY problem with VAAPI

OMV Emby Vaapi Transcode

  • Please log in to reply
33 replies to this topic

#21 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 124473 posts
  • Local time: 06:18 AM

Posted 18 February 2019 - 01:10 AM

Have you mapped the device properly? To do so, simply use --device=/dev/dri/card1:/dev/dri/card0 --device /dev/dri/renderD129:/dev/dri/renderD128

Of course, adapt the number avec cardX and renderDXYZ to match your system.


#22 ZiemaF OFFLINE  

ZiemaF

    Member

  • Members
  • 18 posts
  • Local time: 11:18 AM
  • LocationPoland

Posted 18 February 2019 - 06:24 AM

Now I'm lost :)
I had set in DEVICE /dev/dri/renderD128
Is this the wrong setting?


#23 sephx OFFLINE  

sephx

    Newbie

  • Members
  • 5 posts
  • Local time: 08:18 PM
  • LocationOZ

Posted 25 February 2019 - 07:55 AM

Not sure if you got this problem fixed. Others mentioned adding devices, nobody mentioned /dev/dri permissions?

 

If use portainer to manage docker. Edit Emby, find Runtime & Resources Tab. Add Device - > /dev/dri Rebuild your container.

Permissions so container can talk to igpu = chmod -R 777 /dev/dri (rebuilt on server boot, best to add in to compose/boot scripts)

 

Hope that helps!


Edited by sephx, 25 February 2019 - 07:59 AM.


#24 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 124473 posts
  • Local time: 06:18 AM

Posted 25 February 2019 - 05:59 PM

@sephx thanks for the info !



#25 ZiemaF OFFLINE  

ZiemaF

    Member

  • Members
  • 18 posts
  • Local time: 11:18 AM
  • LocationPoland

Posted 26 February 2019 - 04:09 AM

I found a message in the EMBY log: "Failed to open the drm device /dev/dri/renderD128"

 

 

I also set the permissions for this directory.
My user for Doker also has full permissions for this directory

    "Devices": [
        {
            "DeviceIndex": 0,
            "DeviceInfo": {
                "VendorId": 32902,
                "DeviceId": 16018,
                "SubsytemVendorId": 5208,
                "SubsytemDeviceId": 53248,
                "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"
                }
            }
        }

Edited by ZiemaF, 26 February 2019 - 04:12 AM.


#26 EODCrafter ONLINE  

EODCrafter

    Advanced Member

  • Members
  • 659 posts
  • Local time: 05:18 AM
  • LocationSouthEastern USA

Posted 26 February 2019 - 05:46 AM

Would like to Piggy Back on this if I may........

 

Why is it better to use Software Decoding compared to this? FPS with HW enabled is @5-10 but when I switch it off it jumps to 50-60. Is it cause this GPU is just too old?

 

5c750aeb39083_Screenshotfrom201902260343



#27 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 124473 posts
  • Local time: 06:18 AM

Posted 26 February 2019 - 01:36 PM

Are you running Docker on OMV?



#28 EODCrafter ONLINE  

EODCrafter

    Advanced Member

  • Members
  • 659 posts
  • Local time: 05:18 AM
  • LocationSouthEastern USA

Posted 26 February 2019 - 01:39 PM

Are you running Docker on OMV?

No go ahead and delete that, just thought I would slip it in.


Edited by EODCrafter, 26 February 2019 - 01:39 PM.


#29 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 124473 posts
  • Local time: 06:18 AM

Posted 26 February 2019 - 01:40 PM

Please open a new topic. Thanks.



#30 sephx OFFLINE  

sephx

    Newbie

  • Members
  • 5 posts
  • Local time: 08:18 PM
  • LocationOZ

Posted 26 February 2019 - 05:36 PM

in docker container devices, just add /dev/dri not a specific number.

permissions should look like this on /dev/dri. they reset on boot.

drwxrwxrwx  2 root root        80 Feb 26 21:52 by-path
crwxrwxrwx  1 root video 226,   0 Feb 26 21:52 card0
crwxrwxrwx  1 root video 226, 128 Feb 26 21:52 renderD128

 

check the user running emby is part of the video group.

add user to video group with usermod -a -G video USERNAME


Edited by sephx, 26 February 2019 - 05:42 PM.


#31 ZiemaF OFFLINE  

ZiemaF

    Member

  • Members
  • 18 posts
  • Local time: 11:18 AM
  • LocationPoland

Posted 27 February 2019 - 03:00 AM

It looks like everything is ok
But then I do not see the graphics card in EMBY
root@OMV:/dev/dri# id docker
uid=1001(docker) gid=100(users) grupy=100(users),44(video),996(docker)
root@OMV:/dev/dri# ls -l
razem 0
crwxrwxrwx 1 root video 226,   0 lut 25 07:17 card0
crwxrwxrwx 1 root video 226, 128 lut 25 07:17 renderD128



#32 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 124473 posts
  • Local time: 06:18 AM

Posted 18 March 2019 - 01:02 AM

@ZiemaF did you find the answer?



#33 ZiemaF OFFLINE  

ZiemaF

    Member

  • Members
  • 18 posts
  • Local time: 11:18 AM
  • LocationPoland

Posted 19 March 2019 - 03:40 AM

Unfortunately, I gave up.
I can not run it on OpenMediaVault 4.0.
I am now waiting for OMV5.0, it will be on Debian 10, then maybe it will work.
On windows 10 and windows server 2019 it works perfectly (I installed myself for testing for a moment)
Overall, I'm very happy with the EMBY server on OMV through Docker
I also recommend OMV to everyone, a great solution for the home server.


#34 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 124473 posts
  • Local time: 06:18 AM

Posted 19 March 2019 - 12:38 PM

Thanks for the feedback.







Also tagged with one or more of these keywords: OMV, Emby, Vaapi, Transcode

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users