-
As title. Kai. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 6 replies
-
Sorry I have no idea as I have no nvidia GPU. But on a related note: Could you please try the jlmkr.py file from the develop branch? I think it should now load the nvidia kernel module automatically. Which means you can disable the Post Init script to load the kernel module at boot. |
Beta Was this translation helpful? Give feedback.
-
Also I recommend to download the nvtop appimage on the TrueNAS host directly. Run it there. If you then also get the "no gpu to monitor" error, then we can conclude that jailmaker isn't causing the error. |
Beta Was this translation helpful? Give feedback.
-
Ok all seems solved now - I created a new jail with the non-dev jlmkr.py, installed my compute software, and nothing else, and all works as expected, including nvtop. As a heads-up, this is a jammy jail, debian bookwork seems to not provide nvtop through apt... |
Beta Was this translation helpful? Give feedback.
Those logs don't look good. This is what it looks like to me:
curl --location --remote-name https://raw.githubusercontent.com/Jip-Hop/jailmaker/develop/jlmkr.py ./jlmkr.py install systemd-nspawn is already installed. The jlmkr command is available. Done installing jailmaker.
Regarding those nvidia API mismatch errors. You did mention you tried to install the nvidia driver (which you don't have to, and shouldn't, when you have
gpu_passthrough_nvidia=1
in your jail config). Jailmaker bind mounts the driver from the host, so it can't have introduced this mismatch.Perhaps this is just how it is on SCALE, which sounds unlikely but then it would be a SCALE bug. Which version of SCALE do you ha…