Start with the kernel first. The 5.19 pve (proxmox) kernel works as well as the 5.18 bpo (backports) kernel.
Beiträge von chris_kmn
-
-
You can do it after xconfig.
And yes, it should also work with jellyfin as long as you are using the nvidia runtime in docker
-
Yes you are right, the message should be normal. During driver installation the nouveau driver should be deactivated. That‘s why one should reboot after installation.
Installing kernels could be done under the omv-extras page (see picture). Reboot needed afterwards.
-
I just checked debian page and your nvidia chip should be supported, but still a very low performance chip.
You need to work on installing OMV extras and there to activate the latest backport or pve kernel.
So start getting comfortable with the cli 😉
-
-
Well, then I think your hardware is not supported and even if it would be, your old nvidia chip would not improve transcoding performance
-
Which kernel are u running and which version of omv ?
-
-
Do you have the latest omv kernel updates installed ?
May be it could work with the latest backports kernel. But I don‘t know how to fix the broken packages. Maybe starting over again ….
-
Just in case you might be interested with this RE: Nvidia working with OMV 6 direct Install and once again all credits goes to @chris_kmn
By the way, I‘ve changed from a nvidia Quadro P to a nvidia T (Turing architecture) which supports newer codecs and is also a low power gpu compared to the gtx versions with higher performance as the P versions. P2000 is equal to a T1000
-
Hm, that is really strange…. Sorry for blaming you🙈
-
Well, you said you followed my guide, but you obviously did not !
Some more precise reading would have saved you (and us) some time…..
-
Are you running plex via docker ? My guide is for running plex in a docker container. The nvidia docker toolkit supports driver etc. It seems that in you case the graphics acceleration lib (libva) is not accessible or not installed.
On OMV6 you should run plex in a docker container via portainer and you should install docker via omv-extras.
And did you make a fresh install of omv6 ? Until now I don‘t know a case where HW transcoding worked on an updated omv5 -> omv6 system
-
If nvidia-smi is not working something went wrong with the driver installation
And google tells you:
The logging driver enables you to choose how and where to ship your data. The default logging driver as I mentioned above is a JSON file located on the local disk of your Docker host: /var/lib/docker/containers/[container-id]/[container-id]-json. log.
-
Also for me to install docker I do it through omv-extras and that enables backports by default could that be the reason why I having so much trouble passing my GPU through docker?
No, that‘s the right way to do. Also for portainer !
Is nvidia-smi showing a working nvidia driver ?
And again, what for errors is the docker-log showing ?
-
Ok, it might be possible that it is already included with the newer nvidia driver packages. You could try if it works without that lib. I will try and see if I‘ve installed it on my machine.
But it could also be an issue with your sources.list file. Did you check that under step 3?
-
Hm, that’s strange. But „error 400“ doesn‘t tell a lot. You have to look into the docker log and check the error messages.
What is going wrong in step 4?
-
Did you do an update from omv5 or did you make a fresh installation of omv6 ?
I did not manage to install nvidia driver and docker from an omv5 to 6 update….
-
if you have only one graphics card you can discard that variable. The standard value is „all“
-
