Tag Archives: miracles

NVIDIA NVML Driver/library version mismatch

if Cuda and Nvidia drivers mismatch, the nvidia-smi command mismatches with Nvidia NVML Driver/library version mismatch, and needs to check the version of the Nvidia Driver to see if it matches.

enter the command as follows: 

ubuntu-drivers devices

will show:

driver: nvidia-driver-418-server-distro non-free

driver: nvidia-driver-440-server-distro non-free:

driver: nvidia-driver-435-distro non-free

driver: nvidia-driver-440-distro non-free

Distro free builtin

driver: xserver-xorg-video-nouveau-distro free builtin

directly install all, command as follows: 

sudo ubuntu-drivers autoinstall

then reboot 

sudo reboot

use nvidia-smi command, found that you can see the graphics card information, and CUDA model 10.2, Driver version 440, successful match.

Tue Aug 4 21:05:21 2020

+—————————————————————————–+

Driver Version: 440.95.01 CUDA Version: 10.2 |

|——————————-+———————-+———————-+

| GPU Name Persistence-M| bb-id disp.a | Volatile uncorr.ecc |

| Fan Temp Perf Pwr:Usage/Cap| memory-usage | gpu-util Compute m. |

|===============================+======================+======================|

| 0 GeForce RTX 208… Off | 00000000:7 p.m. Off | 0 N/A |

23 c | 41% P8 2 12 mib/11019 w/260 w | mib | 0% Default |

+——————————-+———————-+———————-+

Solution to CUDA installation failure problem visual studio integration failed

– CUDA10.0 failed installation

is basically due to a visual studio integration installation failure. As shown in the figure.

  • solution 1
    . Find the graphics card related options in the driver management

    2. Stop associated service

    3. Delete all folders associated with NVIDIA (C:\ data, C:\Program Files, C:\Program Files(x86)NVIDIA associated folders). 4. Restart

  • . If the problem cannot be solved
    is largely because the installation of visual studio version is incompatible with CUDA10.0 version, it can be solved by installing CUDA9.0 version. This installment was successfully installed with visual studio2015.
    there is also a way to uninstall visual studio integration by selecting custom installation at installation time. However, after this installation, you will not be able to create CUDA if you create Pj with Visual Studio. Solution reference links: https://blog.csdn.net/zzpong/article/details/80282814
    Reference URL:https://devtalk.nvidia.com/default/topic/1033111/cuda-setup-and-installation/cuda-9-1-cannot-install-due-to-failed-visual-studio-integration/

CUDA Visual Studio Integration Installation failed

To sum up, the first possible reason for the failure of cuda installation is the graphics driver problem (it is obvious that the surface driver problem is mentioned in this tip), and the other reason is that cuda has not been unmounted cleanly. After the update of the graphics driver, cuda failed to load, and only reinstall cuda
uninstall cuda first. I tried to install CUDA again, but the error of “CUDa Visual Studio Integration Installation failure” appeared during the Installation. I had been looking for a long time but could not find the Installation log of CUDa. Turned over an article

https://devtalk.nvidia.com/default/topic/1032284/cuda-setup-and-installation/cuda-visual-studio-integration-installation-failed/ speculation may be associated with nsight integrated debugging tools in vs.
then uninstall the


finally cuda can be installed correctly. This tool was always supposed to be installed by myself, but later I reinstalled it and found that It must be installed when I installed CUDA. Of course, I may cancel this thing in the configuration options when Installing CUDA.

Solution to permission denied

gets an installation file ending in.run, giving it executable permissions. If the SElinux module is enabled, disable it first!

Such as:

# chmod + x NVIDIA – Linux – x86_64-295.59. The run

When you paste

into a directory (myResources), this prompt appears: 

Permission denied

is not set, just copy and paste a file, how can that be?

solution: 

$ sudo chmod -R 777 myResources

-where
-r refers to all subdirectories and files cascading to the directory
-777 is that all users have the highest permissions