[Plugin] Nvidia-Driver


ich777

Recommended Posts

1 hour ago, sage2050 said:

This plugin isn't playing nice with the GPU statistics plugin (I THINK that's the culprit). whenever I navigate to dash the nvidia plugin repeatedly hits each of my CPUs cores one at a time at about 30-40% usage.

This has nothing to do with the Nvidia Driver plugin and this is somewhat expected behaviour.

 

The GPU Statistics plugin is querying nvidia-smi ervery second IIRC and depending on your installed CPU this can cause spikes which you will see when you are on the Dashboard.

 

@SimonF what do you think about querying nvidia-smi not every second or possibly make the query time user customizable?

Link to comment
3 hours ago, ich777 said:

This has nothing to do with the Nvidia Driver plugin and this is somewhat expected behaviour.

 

The GPU Statistics plugin is querying nvidia-smi ervery second IIRC and depending on your installed CPU this can cause spikes which you will see when you are on the Dashboard.

 

@SimonF what do you think about querying nvidia-smi not every second or possibly make the query time user customizable?

@ich777 you can set the refresh here I have mine set to 30secs

 

image.png

And it needs to be Yes also for refresh

  • Like 1
Link to comment
9 hours ago, ich777 said:

This has nothing to do with the Nvidia Driver plugin and this is somewhat expected behaviour.

 

The GPU Statistics plugin is querying nvidia-smi ervery second IIRC and depending on your installed CPU this can cause spikes which you will see when you are on the Dashboard.

 

@SimonF what do you think about querying nvidia-smi not every second or possibly make the query time user customizable?

Interesting, thanks for the clarification

 

And thanks SimonF for the config tip

Edited by sage2050
Link to comment

Testing out unraid 6.12.0-rc4.1 and it seems containers with gpu's assigned wont run due to a cgroup change (to cgroupv2) that has been made in 6.12.

 

I uninstalled and re installed the driver, disabled and enabled docker (even rebooted) and outcome is always the same: 

 

 

docker run --rm --gpus all nvidia/cuda:12.1.1-runtime-ubuntu22.04 nvidia-smi
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'
nvidia-container-cli: container error: failed to get device cgroup mount path: no cgroup filesystem mounted for the devices subsytem in mountinfo file: unknown.

 

Only solution I have found so far to get the container to start is to edit /etc/nvidia-container-runtime/config.toml and replace  #no-cgroups = false to no-cgroups = true in the [nvidia-container-cli] section. 

Link to comment
10 minutes ago, ich777 said:

There is your problem.

 

Use the GPU UUID like described in the second post, this flag causes most of the times issues.

 

I just gave that a try, it looks like it wants the GPU number rather than the ID, and using 0, without the no_groups change, same issue :

 

docker run --rm --gpus GPU-d532059d-6184-51aa-302a-2411694349df nvidia/cuda:12.1.1-runtime-ubuntu22.04 nvidia-smi
invalid argument "GPU-d532059d-6184-51aa-302a-2411694349df" for "--gpus" flag: count must be an integer: strconv.Atoi: parsing "GPU-d532059d-6184-51aa-302a-2411694349df": invalid syntax
See 'docker run --help'.


docker run --rm --gpus 0 nvidia/cuda:12.1.1-runtime-ubuntu22.04 nvidia-smi
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'
nvidia-container-cli: container error: failed to get device cgroup mount path: no cgroup filesystem mounted for the devices subsytem in mountinfo file: unknown.

 

Link to comment
4 minutes ago, mike--b said:

I just gave that a try, it looks like it wants the GPU number rather than the ID, and using 0, without the no_groups change, same issue :

This is not how you use the UUID, these are environment variables, please look at the second post.

  • Like 1
Link to comment

Hello, I have a P4000 for my Docker applications however sometimes the card will not mount when it is shown perfectly fine within "System Devices"; I can restart my server multiple times where eventually it will be mounted properly and usable for whatever task I throw at it.


This is the System Log from one of the instances where it happens; It will not appear if it is mounted properly.

image.thumb.png.a133cffbca9e4df603eb90f3fa2eebc5.png

localserver-diagnostics-20230502-0008.zip

Link to comment
6 hours ago, PeterNokes said:

Hello

First of all I would recommend that you first clean your /boot/extra directory:

-rw------- 1 root root    53828 Oct 10  2022 axel-2.17.11-x86_64-3_SBo.txz
-rw------- 1 root root    53828 Oct 21  2022 axel-2.17.11-x86_64-3_SBo_nerdtools.txz
-rw------- 1 root root    44160 Oct  6  2022 axel-2.4-x86_64-2_slonly_nerdtools.txz
-rw------- 1 root root   115844 Oct 24  2022 bc-1.07.1-x86_64-5_nerdtools.txz
-rw------- 1 root root  4169268 Oct  6  2022 borgbackup-1.1.15-x86_64-1_nerdtools.txz
-rw------- 1 root root   448876 Mar 30 00:30 btop-1.2.13-x86_64-1_SBo_UES_nerdtools.txz
-rw------- 1 root root   112024 Oct 10  2022 ddrescue-1.26-x86_64-1.txz
-rw------- 1 root root   112024 Oct 21  2022 ddrescue-1.26-x86_64-1_nerdtools.txz
-rw------- 1 root root   113520 Mar  6 08:02 ddrescue-1.27-x86_64-1_nerdtools.txz
-rw------- 1 root root  3514580 Oct 10  2022 exiftool-12.47-noarch-1_SBo.txz
-rw------- 1 root root  3514580 Oct 21  2022 exiftool-12.47-noarch-1_SBo_nerdtools.txz
-rw------- 1 root root    17484 Oct  6  2022 fdupes-1.51-x86_64-3_slack_nerdtools.txz
-rw------- 1 root root   901728 Oct  6  2022 fzf-0.20.0-x86_64-3_slonly_nerdtools.txz
-rw------- 1 root root  1030892 Oct 24  2022 gpgme-1.16.0-x86_64-3_nerdtools.txz
-rw------- 1 root root  1058892 Mar  6 08:02 gpgme-1.18.0-x86_64-1_nerdtools.txz
-rw------- 1 root root    40252 Oct 10  2022 iftop-1.0pre4-x86_64-4.txz
-rw------- 1 root root    40252 Oct 21  2022 iftop-1.0pre4-x86_64-4_nerdtools.txz
-rw------- 1 root root    41872 Oct 10  2022 iotop-0.6-x86_64-2_SBo.txz
-rw------- 1 root root    41872 Oct 21  2022 iotop-0.6-x86_64-2_SBo_nerdtools.txz
-rw------- 1 root root   408544 Oct 21  2022 ipmitool-1.8.18-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root   654900 Oct  6  2022 irssi-1.2.3-x86_64-2_nerdtools.txz
-rw------- 1 root root   681604 Mar  6 08:02 irssi-1.4.3-x86_64-1_nerdtools.txz
-rw------- 1 root root    46324 Oct  6  2022 jdupes-1.21.0-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root   906912 Oct 10  2022 lftp-4.9.2-x86_64-3.txz
-rw------- 1 root root   906912 Oct 21  2022 lftp-4.9.2-x86_64-3_nerdtools.txz
-rw------- 1 root root   121496 Oct 24  2022 libassuan-2.5.5-x86_64-1_nerdtools.txz
-rw------- 1 root root    48060 Mar  6 08:02 libffi-3.4.4-x86_64-1_nerdtools.txz
-rw------- 1 root root  2553328 Oct  6  2022 libmediainfo-22.06-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root   169616 Oct  6  2022 libsodium-1.0.18-x86_64-3_nerdtools.txz
-rw------- 1 root root   375968 Oct  6  2022 libzen-0.4.39-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root   221744 Oct 10  2022 llfuse-1.4.2-x86_64-1_SBo.txz
-rw------- 1 root root   221744 Oct 21  2022 llfuse-1.4.2-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root    58460 Oct 24  2022 lzlib-1.13-x86_64-1_nerdtools.txz
-rw------- 1 root root    67296 Oct  6  2022 mediainfo-22.06-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root    18116 Oct  6  2022 mktorrent-1.1-x86_64-1_nerdtools.txz
-rw------- 1 root root   106260 Oct 21  2022 mlocate-0.26-x86_64-4_nerdtools.txz
-rw------- 1 root root    47188 Oct  6  2022 ncdu-1.17-x86_64-1gds_nerdtools.txz
-rw------- 1 root root    89584 Oct  6  2022 neofetch-20211210-noarch-1_nerdtools.txz
-rw------- 1 root root    59996 Oct  6  2022 nload-0.7.4-x86_64-1_slack_nerdtools.txz
-rw------- 1 root root  2359896 Oct  6  2022 p7zip-17.04-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root    70484 Oct 21  2022 pigz-2.7-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root 49279388 Oct 24  2022 powershell-7.2.7-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root   206868 Oct 10  2022 powertop-2.13-x86_64-3.txz
-rw------- 1 root root   206868 Oct 21  2022 powertop-2.13-x86_64-3_nerdtools.txz
-rw------- 1 root root   200264 Mar  6 08:02 powertop-2.15-x86_64-1_nerdtools.txz
-rw------- 1 root root  1809344 Oct  6  2022 python-pip-21.3.1-x86_64-2_nerdtools.txz
-rw------- 1 root root  2199428 Mar  6 08:03 python-pip-22.2.2-x86_64-1_nerdtools.txz
-rw------- 1 root root   673896 Oct  6  2022 python-setuptools-57.4.0-x86_64-1_nerdtools.txz
-rw------- 1 root root   674240 Oct 10  2022 python-setuptools-57.5.0-x86_64-2.txz
-rw------- 1 root root   674240 Oct 21  2022 python-setuptools-57.5.0-x86_64-2_nerdtools.txz
-rw------- 1 root root   914672 Mar  6 08:03 python-setuptools-65.1.1-x86_64-1_nerdtools.txz
-rw------- 1 root root 13018740 Oct  6  2022 python2-2.7.18-x86_64-4_nerdtools.txz
-rw------- 1 root root 18538524 Oct  6  2022 python3-3.9.10-x86_64-1_nerdtools.txz
-rw------- 1 root root 19193916 Mar  6 08:02 python3-3.9.16-x86_64-1_nerdtools.txz
-rw------- 1 root root   314872 Oct  6  2022 rar-6.12-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root  6331588 Mar 30 00:31 restic-0.15.1-x86_64-1_SBo_UES_nerdtools.txz
-rw------- 1 root root   113464 Oct 10  2022 rsnapshot-1.4.4-x86_64-1_SBo.txz
-rw------- 1 root root   113464 Oct 21  2022 rsnapshot-1.4.4-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root  9117740 Mar 30 00:31 ruby-3.2.1-x86_64-2_nerdtools.txz
-rw------- 1 root root   550196 Oct  6  2022 screen-4.9.0-x86_64-1_nerdtools.txz
-rw------- 1 root root    43440 Oct 21  2022 sshfs-3.7.2-x86_64-1_nerdtools.txz
-rw------- 1 root root    43944 Mar  6 08:03 sshfs-3.7.3-x86_64-1_nerdtools.txz
-rw------- 1 root root  3023368 Oct 24  2022 tcl-8.6.12-x86_64-1_nerdtools.txz
-rw------- 1 root root  3057248 Mar  6 08:03 tcl-8.6.13-x86_64-1_nerdtools.txz
-rw------- 1 root root  3865148 Oct 24  2022 tcllib-1.21-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root   366896 Oct  6  2022 tmux-3.2-x86_64-1_nerdtools.txz
-rw------- 1 root root   388528 Mar  6 08:03 tmux-3.3a-x86_64-1_nerdtools.txz
-rw------- 1 root root   356128 Oct  6  2022 unrar-6.12-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root    63420 Oct  6  2022 utf8proc-2.7.0-x86_64-1_nerdtools.txz
-rw------- 1 root root    63600 Mar  6 08:03 utf8proc-2.8.0-x86_64-1_nerdtools.txz
-rw------- 1 root root  8472744 Oct  6  2022 vim-9.0.0623-x86_64-1_nerdtools.txz
-rw------- 1 root root  8582980 Mar  6 08:03 vim-9.0.1362-x86_64-1_nerdtools.txz
-rw------- 1 root root  8584956 Mar 30 00:31 vim-9.0.1418-x86_64-1_nerdtools.txz
-rw------- 1 root root   715608 Oct 24  2022 wget2-2.0.0-x86_64-2_nerdtools.txz
-rw------- 1 root root   531312 Mar  6 08:03 wget2-2.0.1-x86_64-1_nerdtools.txz
-rw------- 1 root root  3056824 Oct  6  2022 zsh-5.8-x86_64-3_nerdtools.txz
-rw------- 1 root root  3156392 Mar  6 08:03 zsh-5.9-x86_64-1_nerdtools.txz

 

You have many packages twice or even three times in there, why? I also can't tell for sure if there is a package in there which actually causes the incompatibility.

Do you need all those packages?

 

The next thing that you can try is to boot in Legacy mode and not in UEFI.

 

6 hours ago, PeterNokes said:

This is the System Log from one of the instances where it happens; It will not appear if it is mounted properly.

I can't also see the call trace, can you maybe post a diagnostics file after the call trace happened?

Link to comment
5 hours ago, ich777 said:

First of all I would recommend that you first clean your /boot/extra directory:

-rw------- 1 root root    53828 Oct 10  2022 axel-2.17.11-x86_64-3_SBo.txz
-rw------- 1 root root    53828 Oct 21  2022 axel-2.17.11-x86_64-3_SBo_nerdtools.txz
-rw------- 1 root root    44160 Oct  6  2022 axel-2.4-x86_64-2_slonly_nerdtools.txz
-rw------- 1 root root   115844 Oct 24  2022 bc-1.07.1-x86_64-5_nerdtools.txz
-rw------- 1 root root  4169268 Oct  6  2022 borgbackup-1.1.15-x86_64-1_nerdtools.txz
-rw------- 1 root root   448876 Mar 30 00:30 btop-1.2.13-x86_64-1_SBo_UES_nerdtools.txz
-rw------- 1 root root   112024 Oct 10  2022 ddrescue-1.26-x86_64-1.txz
-rw------- 1 root root   112024 Oct 21  2022 ddrescue-1.26-x86_64-1_nerdtools.txz
-rw------- 1 root root   113520 Mar  6 08:02 ddrescue-1.27-x86_64-1_nerdtools.txz
-rw------- 1 root root  3514580 Oct 10  2022 exiftool-12.47-noarch-1_SBo.txz
-rw------- 1 root root  3514580 Oct 21  2022 exiftool-12.47-noarch-1_SBo_nerdtools.txz
-rw------- 1 root root    17484 Oct  6  2022 fdupes-1.51-x86_64-3_slack_nerdtools.txz
-rw------- 1 root root   901728 Oct  6  2022 fzf-0.20.0-x86_64-3_slonly_nerdtools.txz
-rw------- 1 root root  1030892 Oct 24  2022 gpgme-1.16.0-x86_64-3_nerdtools.txz
-rw------- 1 root root  1058892 Mar  6 08:02 gpgme-1.18.0-x86_64-1_nerdtools.txz
-rw------- 1 root root    40252 Oct 10  2022 iftop-1.0pre4-x86_64-4.txz
-rw------- 1 root root    40252 Oct 21  2022 iftop-1.0pre4-x86_64-4_nerdtools.txz
-rw------- 1 root root    41872 Oct 10  2022 iotop-0.6-x86_64-2_SBo.txz
-rw------- 1 root root    41872 Oct 21  2022 iotop-0.6-x86_64-2_SBo_nerdtools.txz
-rw------- 1 root root   408544 Oct 21  2022 ipmitool-1.8.18-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root   654900 Oct  6  2022 irssi-1.2.3-x86_64-2_nerdtools.txz
-rw------- 1 root root   681604 Mar  6 08:02 irssi-1.4.3-x86_64-1_nerdtools.txz
-rw------- 1 root root    46324 Oct  6  2022 jdupes-1.21.0-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root   906912 Oct 10  2022 lftp-4.9.2-x86_64-3.txz
-rw------- 1 root root   906912 Oct 21  2022 lftp-4.9.2-x86_64-3_nerdtools.txz
-rw------- 1 root root   121496 Oct 24  2022 libassuan-2.5.5-x86_64-1_nerdtools.txz
-rw------- 1 root root    48060 Mar  6 08:02 libffi-3.4.4-x86_64-1_nerdtools.txz
-rw------- 1 root root  2553328 Oct  6  2022 libmediainfo-22.06-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root   169616 Oct  6  2022 libsodium-1.0.18-x86_64-3_nerdtools.txz
-rw------- 1 root root   375968 Oct  6  2022 libzen-0.4.39-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root   221744 Oct 10  2022 llfuse-1.4.2-x86_64-1_SBo.txz
-rw------- 1 root root   221744 Oct 21  2022 llfuse-1.4.2-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root    58460 Oct 24  2022 lzlib-1.13-x86_64-1_nerdtools.txz
-rw------- 1 root root    67296 Oct  6  2022 mediainfo-22.06-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root    18116 Oct  6  2022 mktorrent-1.1-x86_64-1_nerdtools.txz
-rw------- 1 root root   106260 Oct 21  2022 mlocate-0.26-x86_64-4_nerdtools.txz
-rw------- 1 root root    47188 Oct  6  2022 ncdu-1.17-x86_64-1gds_nerdtools.txz
-rw------- 1 root root    89584 Oct  6  2022 neofetch-20211210-noarch-1_nerdtools.txz
-rw------- 1 root root    59996 Oct  6  2022 nload-0.7.4-x86_64-1_slack_nerdtools.txz
-rw------- 1 root root  2359896 Oct  6  2022 p7zip-17.04-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root    70484 Oct 21  2022 pigz-2.7-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root 49279388 Oct 24  2022 powershell-7.2.7-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root   206868 Oct 10  2022 powertop-2.13-x86_64-3.txz
-rw------- 1 root root   206868 Oct 21  2022 powertop-2.13-x86_64-3_nerdtools.txz
-rw------- 1 root root   200264 Mar  6 08:02 powertop-2.15-x86_64-1_nerdtools.txz
-rw------- 1 root root  1809344 Oct  6  2022 python-pip-21.3.1-x86_64-2_nerdtools.txz
-rw------- 1 root root  2199428 Mar  6 08:03 python-pip-22.2.2-x86_64-1_nerdtools.txz
-rw------- 1 root root   673896 Oct  6  2022 python-setuptools-57.4.0-x86_64-1_nerdtools.txz
-rw------- 1 root root   674240 Oct 10  2022 python-setuptools-57.5.0-x86_64-2.txz
-rw------- 1 root root   674240 Oct 21  2022 python-setuptools-57.5.0-x86_64-2_nerdtools.txz
-rw------- 1 root root   914672 Mar  6 08:03 python-setuptools-65.1.1-x86_64-1_nerdtools.txz
-rw------- 1 root root 13018740 Oct  6  2022 python2-2.7.18-x86_64-4_nerdtools.txz
-rw------- 1 root root 18538524 Oct  6  2022 python3-3.9.10-x86_64-1_nerdtools.txz
-rw------- 1 root root 19193916 Mar  6 08:02 python3-3.9.16-x86_64-1_nerdtools.txz
-rw------- 1 root root   314872 Oct  6  2022 rar-6.12-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root  6331588 Mar 30 00:31 restic-0.15.1-x86_64-1_SBo_UES_nerdtools.txz
-rw------- 1 root root   113464 Oct 10  2022 rsnapshot-1.4.4-x86_64-1_SBo.txz
-rw------- 1 root root   113464 Oct 21  2022 rsnapshot-1.4.4-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root  9117740 Mar 30 00:31 ruby-3.2.1-x86_64-2_nerdtools.txz
-rw------- 1 root root   550196 Oct  6  2022 screen-4.9.0-x86_64-1_nerdtools.txz
-rw------- 1 root root    43440 Oct 21  2022 sshfs-3.7.2-x86_64-1_nerdtools.txz
-rw------- 1 root root    43944 Mar  6 08:03 sshfs-3.7.3-x86_64-1_nerdtools.txz
-rw------- 1 root root  3023368 Oct 24  2022 tcl-8.6.12-x86_64-1_nerdtools.txz
-rw------- 1 root root  3057248 Mar  6 08:03 tcl-8.6.13-x86_64-1_nerdtools.txz
-rw------- 1 root root  3865148 Oct 24  2022 tcllib-1.21-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root   366896 Oct  6  2022 tmux-3.2-x86_64-1_nerdtools.txz
-rw------- 1 root root   388528 Mar  6 08:03 tmux-3.3a-x86_64-1_nerdtools.txz
-rw------- 1 root root   356128 Oct  6  2022 unrar-6.12-x86_64-1_SBo_nerdtools.txz
-rw------- 1 root root    63420 Oct  6  2022 utf8proc-2.7.0-x86_64-1_nerdtools.txz
-rw------- 1 root root    63600 Mar  6 08:03 utf8proc-2.8.0-x86_64-1_nerdtools.txz
-rw------- 1 root root  8472744 Oct  6  2022 vim-9.0.0623-x86_64-1_nerdtools.txz
-rw------- 1 root root  8582980 Mar  6 08:03 vim-9.0.1362-x86_64-1_nerdtools.txz
-rw------- 1 root root  8584956 Mar 30 00:31 vim-9.0.1418-x86_64-1_nerdtools.txz
-rw------- 1 root root   715608 Oct 24  2022 wget2-2.0.0-x86_64-2_nerdtools.txz
-rw------- 1 root root   531312 Mar  6 08:03 wget2-2.0.1-x86_64-1_nerdtools.txz
-rw------- 1 root root  3056824 Oct  6  2022 zsh-5.8-x86_64-3_nerdtools.txz
-rw------- 1 root root  3156392 Mar  6 08:03 zsh-5.9-x86_64-1_nerdtools.txz

 

You have many packages twice or even three times in there, why? I also can't tell for sure if there is a package in there which actually causes the incompatibility.

Do you need all those packages?

 

The next thing that you can try is to boot in Legacy mode and not in UEFI.

 

I can't also see the call trace, can you maybe post a diagnostics file after the call trace happened?

 

Hello when I try to post a diagnostics file when the issue happens it gets stuck at "/usr/bin/nvidia-smi --query 2>/dev/null|todos >>'/localserver-diagnostics-20230502-1242/system/nvidia-smi.txt'" and freezes my server. (Which happens to anything NVIDIA related)

 

image.thumb.png.f890961a5dbd77812ede46a1e5ad7b04.png

 

I have deleted everything in /boot/extra just to make sure that is not the issue and that has apparently fixed it after restarting twice so I will have to have another look.

Thanks

  • Like 1
Link to comment
Just now, PeterNokes said:

I have deleted everything in /boot/extra just to make sure that is not the issue and that has apparently fixed it after restarting twice so I will have to have another look.

Now that I see it, how do you added the GPU to the template?

Have you done it like mentioned in the second post from this thread?

 

Please note that the flag: --gpus all causes issues on many systems is not recommended by me...

Link to comment
1 minute ago, ich777 said:

Now that I see it, how do you added the GPU to the template?

Have you done it like mentioned in the second post from this thread?

 

Please note that the flag: --gpus all causes issues on many systems is not recommended by me...

I use the GPU ID (GPU-2066de26-xxxx-xxxx-xxxxxxx) for both of my Dockers which uses it; The only place where I have "all" is for the "NVIDIA_DRIVER_CAPABILITIES"

Link to comment
28 minutes ago, PeterNokes said:

I use the GPU ID (GPU-2066de26-xxxx-xxxx-xxxxxxx) for both of my Dockers which uses it; The only place where I have "all" is for the "NVIDIA_DRIVER_CAPABILITIES"

This is perfectly fine.

 

Please keep me updated on this...

Link to comment

I am asking for the entire community, as I see that there isn't an actual post with these instructions listed.
I've installed your driver and am using with a Docker package as a transcoder.
When I recieve a notification about a new Nvidia driver plugin version, how do I update the package?

I've already installed the plugin following the instructions contained here: https://www.youtube.com/watch?v=VkC5Hi-rO2c&t=1s


If I simply click on "Update" in the package, is it supposed to work right out the box once the driver plugin has been updated?

Link to comment
51 minutes ago, couzin2000 said:

When I recieve a notification about a new Nvidia driver plugin version, how do I update the package?

The notification should mention that you should reboot or am I wrong? The notification text should be:

Quote

New Nvidia Driver v<DRIVER VERISON> found and downloaded! Please reboot your Server to install the new version!

 

Or do you mean that a new version from the plugin is available?

A new version from the plugin doesn‘t mean that a new driver package is available…

If you want to update the driver package itself, go to the plugin page.

But you really don‘t have to update the driver if you are using the card for transcoding, a new driver will not speed up the transcodes.

 

51 minutes ago, couzin2000 said:

If I simply click on "Update" in the package, is it supposed to work right out the box once the driver plugin has been updated?

No, even if you do it manually the notification should tell you to reboot.

The message should be something like that:

Quote

To install the new Nvidia Driver v<DRIVER VERSIN> please reboot your Server!

 

I really couldn't do more then writing to reboot in the notification. ;)

  • Thanks 1
Link to comment
On 5/2/2023 at 4:07 AM, ich777 said:

@supawiz6991, @Draco1544 & @ezhik please update the plugin to version 2023.05.02 and see if the issue is fixed.

I updated and rechecked. Something is still wonky for me. When I select production branch and click update I get the following:
---Can't find Nvidia Driver vlatest_prb for your Kernel v5.19.17 falling back to latest Nvidia Driver v530.41.03---
It then downloads 530.41.03 and asks me to reboot. Then after closing the dialog window, the selector changes to latest, matching the error messages behavior. 

If I manually select version 525.116.03 it works fine. 

 

Link to comment
16 minutes ago, supawiz6991 said:

---Can't find Nvidia Driver vlatest_prb for your Kernel v5.19.17 falling back to latest Nvidia Driver v530.41.03---

I will look into that but I'll maybe drop some features from the plugin anyways.

 

Can you try to uninstall the plugin, reboot, reinstall the plugin and see if that helps?

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.