mr-hexen

Members
 View Profile  See their activity

  • Posts

    2300

  • Joined

  • Last visited

 Content Type 

Posts posted by mr-hexen

    [Support] Linuxserver.io - Plex Media Server

    in Docker Containers

    Posted · Edited by mr-hexen

    5 hours ago, saarg said:

    The HD5450 shouldn't have any drivers loaded, so it shouldn't be used.

    Is /dev/dri the device or does it have subfolders? If it doesn't have subfolders, the reason why it didn't work is the chmod /dev/dri/*. If it has subfolders, I'm not sure what's happening.

     

    Edit:

    I just tested this on a test server and it's working here without the privileged flag.  It's crazy how much CPU it saves on a i5-4590. I added some pictures.

    This is a Blu-ray rip of one episode 42 min long.

     

    Did you do the 'go' file edits too? I'm wondering because I couldnt get it to work w/o priviledged...i5-4460 here.

     

    This is from putty to the host: 

    root@Tower:~# ls -la /dev/dri/
total 0
drwxr-xr-x  2 root root       100 Mar  9 16:14 ./
drwxr-xr-x 16 root root      4000 Mar 10 20:09 ../
crwxrwxrwx  1 root video 226,   0 Mar  9 16:14 card0
crwxrwxrwx  1 root video 226,  64 Mar  9 16:14 controlD64
crwxrwxrwx  1 root video 226, 128 Mar  9 16:14 renderD128

     

    This is exec'd into the docker: 

    root@Tower:~# docker exec -it PlexMediaServer /bin/bash
root@Tower:/# ls -la /dev/dri
total 0
drwxr-xr-x  2 root root      100 Mar 10 20:20 .
drwxr-xr-x 14 root root     3840 Mar 10 20:20 ..
crwxrwxrwx  1 root   18 226,   0 Mar 10 20:20 card0
crwxrwxrwx  1 root   18 226,  64 Mar 10 20:20 controlD64
crwxrwxrwx  1 root   18 226, 128 Mar 10 20:20 renderD128

     

    Not sure if those perms are right ??? Plex logs say "renderD128" not found...
     

    [Support] Linuxserver.io - Plex Media Server

    in Docker Containers

    Posted

    4 minutes ago, saarg said:

     

    You don't need both privileged and the device tag. Using privileged let's the container access all devices. In this case it should be enough to use the device tag. It's also not needed to use both host and  container path anymore. --device=/dev/dri is enough.

     

    It only started working for me when I added the privileged setting. Otherwise it always software encoded.  I'm wondering if the container is using my HD5450 (passed to a VM) to encode or the iGPU?

    [Support] binhex - DelugeVPN

    in Docker Containers

    Posted · Edited by mr-hexen

    2 minutes ago, binhex said:

     

    yep thats fine, that is correctly configured, still going through your logs...

     

    Ya nothing is jumping out from the logs for me either...do you have any special characters or spaces in your username / password? Verify the username / password on the pia website too.

     

    The log's saying using previous IP, never seen that message before.

    [Support] Linuxserver.io - Plex Media Server

    in Docker Containers

    Posted · Edited by mr-hexen

    13 hours ago, leejbarker said:

     

    How do you do that?

     

    Credit goes to: https://forums.lime-technology.com/topic/53388-enabling-i915-for-host/?do=findComment&comment=530722   I had to change some things around in the plex config to get it to work. Not sure if these changes apply to just the LSIO docker or all docker variants. Changes highlighted for reference.

     

    Must be on unRAID 6.3.x or higher as they added the i915 to the kernel in the RC phases.

     

    Add to "/boot/config/go" (very first lines):

    modprobe i915

    chmod 777 /dev/dri/*

     

    Then to the Plex docker config:

    Change to mode to Privileged.

    Extra Parameters: "--device=/dev/dri:/dev/dri"

    Version: "#.#.#.####-xxxxxxx"   (need plexpass)

     

    Reboot system

     

    open Plex > settings > SERVER > transcoder, "Show Advanced" > check off "Use hardware acceleration when available (Experimental)"

     

    Start a stream, force transcoding by lowering bitrate.

     

    Open a new plex window, click Status > Now Playing and click the (i) on the stream. If you see (hw) in the video line you've enabled it successfully.

     

    • Like 1
    • Upvote 1

    [Support] binhex - DelugeVPN

    in Docker Containers

    Posted

    Just now, chesh said:

    Know where to find SickRage's in-depth changelog? All I could seem to find was last updated in February.

     

    Nope, i moved away from SickRage a year or two ago and never looked back. I think this was the era where their updates / development was stale..Sonarr has been ROCK solid and a pleasure.

    [Support] binhex - DelugeVPN

    in Docker Containers

    Posted

    This was fixed in Sonarr on Mar 7, 2017:

     

    2.0.0.4645 - Mar 7 2017 Installed

    Fixed Deluge 1.3.14 API support due to changed json-rpc checks. (hotfix)
    Fixed DownloadStation client stuck in infinite loop in some cases.
    Fixed DownloadStation client failing if non-bt/nzb downloads exist.
    Fixed NZBGet delete:scan treated as failure

    Phantom Power Failures reported by UPS

    in General Support

    Posted

    1 hour ago, unevent said:

    Could be the power company switching in/out capacitor banks or other devices based on load/time of day

     

    Lack of supply would be indicated by low voltage (i.e. brown outs). But general switching you wouldn't notice a difference because they run them in parallel to limit disruptions.

    [Support] binhex - DelugeVPN

    in Docker Containers

    Posted

    2 hours ago, fc0712 said:

    I just updated the docker and it now it won't let me acces the web ui. 

     

    Should I change some ports or anything after update?

     

    Edit: It seem that sonarr and radarr still have a connection to radarr. I just can't acces it.

     

    I'm away from home and accessing through openvpn reverse vpn. Openvpn on a VPS and Openvpn client acting as vpn gateway (Acces to private subnet) It works fine with unraid webui and other dockers just not delugeVPN after the update.

     

     

    If this included a server restart before hand its probably the ipmangle issue.