Ch1wuu 1 Posted April 27, 2020 Share Posted April 27, 2020 Hi, Preferred Hardware Decoders / Encoders is blank. I've followed the guide & have Nvidia drivers installed and a subscription account. Hardware log attached. $ dpkg -l |grep nvidia-driver ii nvidia-driver 440.82-1~bpo10+1 amd64 NVIDIA metapackage ii nvidia-driver-bin 440.82-1~bpo10+1 amd64 NVIDIA driver support binaries ii nvidia-driver-libs:amd64 440.82-1~bpo10+1 amd64 NVIDIA metapackage (OpenGL/GLX/EGL/GLES libraries) ii nvidia-driver-libs:i386 440.82-1~bpo10+1 i386 NVIDIA metapackage (OpenGL/GLX/EGL/GLES libraries) ii nvidia-driver-libs-i386:i386 440.82-1~bpo10+1 i386 NVIDIA metapackage (OpenGL/GLX/EGL/GLES 32-bit libraries) $ lspci |grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev a1) $ cat /etc/debian_version 10.3 $ dpkg -l |grep emby ii emby-server 4.4.2.0 amd64 Emby Server is a personal media server with apps on just about every device. hardware_detection-63723603564.txt Link to comment Share on other sites More sharing options...
Luke 36879 Posted April 27, 2020 Share Posted April 27, 2020 Hi there, please attach the emby server log as well. thanks. Link to comment Share on other sites More sharing options...
Ch1wuu 1 Posted April 28, 2020 Author Share Posted April 28, 2020 Hey, Sent via PM Link to comment Share on other sites More sharing options...
softworkz 3301 Posted May 3, 2020 Share Posted May 3, 2020 @@Ch1wuu - Please install the original Nvidia drivers from the Nvidia website: https://www.nvidia.com/Download/index.aspx Link to comment Share on other sites More sharing options...
softworkz 3301 Posted May 3, 2020 Share Posted May 3, 2020 In case that doesn't help or you have already done so: There are several tools included in Nvidia's Linux driver installation. Please make sure that they are working, especially those that are related to CUDA. Then it should work with Emby as well. Link to comment Share on other sites More sharing options...
Ch1wuu 1 Posted May 3, 2020 Author Share Posted May 3, 2020 Hey, I've tried offical drivers, but no diffrence. I'm back on Debians version now & installed nvidia-cuda-toolkit it's still not working. Do you know how test CUDA is working? $ nvcc -V nvcc: NVIDIA (R) Cuda compiler driver Copyright (c) 2005-2018 NVIDIA Corporation Built on Tue_Jun_12_23:07:04_CDT_2018 Cuda compilation tools, release 9.2, V9.2.148 $ nvidia-smi Sun May 3 16:37:57 2020 +-----------------------------------------------------------------------------+ | NVIDIA-SMI 440.82 Driver Version: 440.82 CUDA Version: 10.2 | |-------------------------------+----------------------+----------------------+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===============================+======================+======================| | 0 GeForce GTX 105... On | 00000000:01:00.0 On | N/A | | 32% 46C P0 N/A / 75W | 377MiB / 4039MiB | 0% Default | +-------------------------------+----------------------+----------------------+ +-----------------------------------------------------------------------------+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=============================================================================| | 0 2430 G /usr/lib/xorg/Xorg 157MiB | | 0 3564 G /usr/bin/kwin_x11 50MiB | | 0 3589 G /usr/bin/krunner 1MiB | | 0 3592 G /usr/bin/plasmashell 70MiB | | 0 3924 G /usr/bin/akonadi_archivemail_agent 1MiB | | 0 3947 G /usr/bin/akonadi_mailfilter_agent 1MiB | | 0 3958 G /usr/bin/akonadi_sendlater_agent 1MiB | | 0 7141 G ...AAAAAAAAAAAACAAAAAAAAAA= --shared-files 86MiB | +-----------------------------------------------------------------------------+ Thanks, Link to comment Share on other sites More sharing options...
Ch1wuu 1 Posted May 3, 2020 Author Share Posted May 3, 2020 Not sure if it's related, but iss this expected $ /opt/emby-server/bin/ffmpeg /opt/emby-server/bin/ffmpeg: relocation error: /opt/emby-server/bin/ffmpeg: symbol avio_find_protocol version LIBAVFORMAT_58 not defined in file libavformat.so.58 with link time reference Link to comment Share on other sites More sharing options...
Luke 36879 Posted May 3, 2020 Share Posted May 3, 2020 Not sure if it's related, but iss this expected $ /opt/emby-server/bin/ffmpeg /opt/emby-server/bin/ffmpeg: relocation error: /opt/emby-server/bin/ffmpeg: symbol avio_find_protocol version LIBAVFORMAT_58 not defined in file libavformat.so.58 with link time reference Yes, you're not going to be able to run our ffmpeg on the terminal without first setting up some things such as environment variables. Link to comment Share on other sites More sharing options...
softworkz 3301 Posted May 4, 2020 Share Posted May 4, 2020 I've tried offical drivers Really? I'm back on Debians version now Why? The error is: Cannot load libcuda.so.1 It is usually fixed by installing Nvidias driver. Link to comment Share on other sites More sharing options...
Solution Ch1wuu 1 Posted May 5, 2020 Author Solution Share Posted May 5, 2020 Hey, Yeah, tried offical and no joy, just tested again & it's now working! Why - I prefer if pos to keep everything managed by the package manager. Thank you 1 Link to comment Share on other sites More sharing options...
softworkz 3301 Posted May 5, 2020 Share Posted May 5, 2020 Haha, I knew you'd need 'another' try.. :-) Link to comment Share on other sites More sharing options...
mlcarson 13 Posted September 30, 2020 Share Posted September 30, 2020 I've been looking for a better solution to this myself. I don't like installing video drivers from Nvidia directly on my Debian system. I've had no luck so far in determining why the Debian files are not working but know that it affects the Docker and Flatpak installs and not the direct Linux installation. The whole point of the other install methods was to make software distribution easier. I've finally just chose to do the local install and change the /etc/emby-server.conf file to point the EMBY_DATA directory the same location my Docker container was pointing to and problem solved. I'm assuming that there's something amiss with the nvidia-docker2 install that installs the nvidia-container-toolkit and then nvidia-container-runtime or maybe the cuda-compat-11.0_*_amd64.deb package. I figure if the process to support Docker HW acceleration is more difficult to solve than dealing with a local install then maybe it's time to eliminate this layer of abstraction. Link to comment Share on other sites More sharing options...
Luke 36879 Posted September 30, 2020 Share Posted September 30, 2020 3 hours ago, mlcarson said: I've been looking for a better solution to this myself. I don't like installing video drivers from Nvidia directly on my Debian system. I've had no luck so far in determining why the Debian files are not working but know that it affects the Docker and Flatpak installs and not the direct Linux installation. The whole point of the other install methods was to make software distribution easier. I've finally just chose to do the local install and change the /etc/emby-server.conf file to point the EMBY_DATA directory the same location my Docker container was pointing to and problem solved. I'm assuming that there's something amiss with the nvidia-docker2 install that installs the nvidia-container-toolkit and then nvidia-container-runtime or maybe the cuda-compat-11.0_*_amd64.deb package. I figure if the process to support Docker HW acceleration is more difficult to solve than dealing with a local install then maybe it's time to eliminate this layer of abstraction. Regarding docker, have you seen this method? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now