September 19, 20206 yr Any one have an issue where after transcoding is done the fans on the video card don't stop running? I've noticed unless I restart the Plex container they just continously run. Any idea how to solve this issue besides restarting the container? Nvm, didn't see the above post Edited September 19, 20206 yr by Roken
September 27, 20206 yr Looking for a little help, I am seeing this within my Jellyfin container. I am passing through the gpu properly, but I enabled a new tone mapping feature that requires OpenCL. This should work right? [AVHWDeviceContext @ 0x561dcd631340] Failed to get number of OpenCL platforms: -1001. Device creation failed: -19. Failed to set value 'opencl=ocl:0.0' for option 'init_hw_device': No such device Error parsing global options: No such device Edited September 27, 20206 yr by cryzis
September 27, 20206 yr 2 hours ago, cryzis said: Looking for a little help, I am seeing this within my Jellyfin container. I am passing through the gpu properly, but I enabled a new tone mapping feature that requires OpenCL. This should work right? [AVHWDeviceContext @ 0x561dcd631340] Failed to get number of OpenCL platforms: -1001. Device creation failed: -19. Failed to set value 'opencl=ocl:0.0' for option 'init_hw_device': No such device Error parsing global options: No such device I don't think the image supports opencl. What feature is that?
September 27, 20206 yr 1 hour ago, aptalca said: I don't think the image supports opencl. What feature is that? This is brand new tone mapping during transcode feature that will be released in the upcoming 10.7.0 release of jellyfin. See PR#3442 . I have been running Jellyfin:unstable and have been waiting to test this out but I guess the image doesn't support OpenCL
September 28, 20206 yr 4 hours ago, cryzis said: This is brand new tone mapping during transcode feature that will be released in the upcoming 10.7.0 release of jellyfin. See PR#3442 . I have been running Jellyfin:unstable and have been waiting to test this out but I guess the image doesn't support OpenCL We'll look into it. It probably just needs some opencl packages added. We have other images that do that.
September 28, 20206 yr 4 hours ago, cryzis said: This is brand new tone mapping during transcode feature that will be released in the upcoming 10.7.0 release of jellyfin. See PR#3442 . I have been running Jellyfin:unstable and have been waiting to test this out but I guess the image doesn't support OpenCL Can you exec into the container and install the package "ocl-icd-opencl-dev", restart and see if it works?
September 28, 20206 yr 18 hours ago, aptalca said: Can you exec into the container and install the package "ocl-icd-opencl-dev", restart and see if it works? I installed "ocl-icd-opencl-dev" into the jellyfin container and restarted. Still seeing the same issue.
September 29, 20206 yr 3 hours ago, cryzis said: I installed "ocl-icd-opencl-dev" into the jellyfin container and restarted. Still seeing the same issue. Ok I got it working, I added the below repo and used aptitude to install "nvidia-opencl-icd" deb http://deb.debian.org/debian buster-backports main contrib non-free
September 29, 20206 yr 18 hours ago, cryzis said: Ok I got it working, I added the below repo and used aptitude to install "nvidia-opencl-icd" deb http://deb.debian.org/debian buster-backports main contrib non-free It's better to use an ubuntu package since we are using an ubuntu base image.
September 30, 20206 yr 2 hours ago, CHBMB said: v6.9.0 beta29 uploaded. I just updated and confirmed the build works and Plex HW transcoding is functional. Thank you @CHBMB!
September 30, 20206 yr 1 hour ago, xaositek said: I just updated and confirmed the build works and Plex HW transcoding is functional. Thank you @CHBMB! If you have the GPU Plugin installed can you verify that your GPU returns to the lowest P-State (P8) after a transcode?
September 30, 20206 yr 23 minutes ago, MowMdown said: If you have the GPU Plugin installed can you verify that your GPU returns to the lowest P-State (P8) after a transcode? See attached screenshot - I believe this confirms P8 state after Transcoding.
October 1, 20206 yr 14 hours ago, CHBMB said: v6.9.0 beta29 uploaded. can the stable ver 6.8.3 get the latest nvidia drivers? PLEX betas (and likely next stable) now require 450.66 or later drivers to keep nvenc operational -- hw transcoding is broken on latest versions because of this. i prefer to not run betas, so essentially i am stuck on a previous working plex version (1.20.1.3252-1-01) https://www.reddit.com/r/PleX/comments/j0bzu1/it_was_working_before_but_now_im_having_issues/ https://forums.plex.tv/t/help-fixing-my-broken-nvidia-nvenc-driver-config-ubuntu-20-04/637854 https://forums.plex.tv/t/nvenc-hardware-encoding-broken-on-1-20-2-3370/637925 Edited October 1, 20206 yr by therapist
October 4, 20206 yr I just installed 6.9.0-beta29 [haven't run any encode / decode yet] and it looks like my card is in the P0 state after booting. I've attached a screen shot from the GPU plugin. Sorry, really new to this. Is this expected? UPDATE: Just did a HW transcode w/in Plex. As soon as the transcode stopped, the GPU went to P8. Is there a way I can get the GPU to P8 w/o having to run a transcode? Edited October 4, 20206 yr by tkenn1s
October 7, 20206 yr On 10/4/2020 at 12:10 PM, tkenn1s said: UPDATE: Just did a HW transcode w/in Plex. As soon as the transcode stopped, the GPU went to P8. Is there a way I can get the GPU to P8 w/o having to run a transcode? Apparently this is expected whenever you're running headless. You can force your GPU into P8 by: Enabling a dummy X-server Installing and running Nvidia's persistenced daemon Toggling persistence mode using nvidia-smi from /boot/config/go I opted for #3 since I didn't want to have a bunch of stuff running just to get to a lower power mode. I added the following to the go file and it now boots into power state P8. # enable nvidia persistence mode if [ -x /usr/bin/nvidia-smi ]; then /usr/bin/nvidia-smi -pm 1 fi
October 7, 20206 yr 21 minutes ago, lp0101 said: What versions of the nvidia drivers does 6.9.0 beta30 use? There are no Nvidia drivers in unRAID itself (maybe some day). The drivers are installed with this plugin.
October 7, 20206 yr 2 minutes ago, Hoopster said: There are no Nvidia drivers in unRAID itself (maybe some day). The drivers are installed with this plugin. I believe that's what the question was about.
October 7, 20206 yr 26 minutes ago, lp0101 said: What versions of the nvidia drivers does 6.9.0 beta30 use? While unRAID themselves to not package drivers with the installation, the unRAID nVidia package installs 450.80.02 (for beta 29/30). I believe it is 440.... for 6.8.3 (stable) Edited October 7, 20206 yr by xaositek Updated version definition
October 7, 20206 yr 2 minutes ago, xaositek said: While unRAID themselves to not package drivers with the installation, the unRAID nVidia package installs 450.80.02 (for beta 29/30). I believe it is 440.... for 6.8.3 (stable) Yeah. Unless the images have been updated recently, stable is on 440 which has busted P-states using Plex.
October 7, 20206 yr 1 minute ago, tkenn1s said: I believe that's what the question was about. Then that should have been the question asked (driver version in the plugin). There are many users who assume the 6.9.0 unRAID betas contain Nvidia drivers since it has been mentioned several times by Limetech personnel that the inclusion of video drivers is something they are exploring in the 6.9 time frame.
October 7, 20206 yr Quote Then that should have been the question asked (driver version in the plugin). We're on the forum thread for the unraid nvidia plugin. I figured that was implied.
October 10, 20206 yr I have some issues getting the Installation to Work on 6.8.3. The installation runs fine but after the Reboot i get a Kernel Panic kernel panic -not syncing VFS: unable to mount root fs on unknown block(0,0) the normal Installation runs fine. Did some research and it got suggested that the RAM could be an Issue, Replaced the Ram but with the same Result. Ordered now a new Flash Drive that will arrive Tuesday i guess. --Edit: Fixed the Issue by running the make bootable script after the Installation again. (thanks Stranger on Reddit) Edited October 10, 20206 yr by Superbrain
Archived
This topic is now archived and is closed to further replies.