Safe to install CUDA toolkit separately on WSL2 and Windows 10? - cuda

I've installed Nvidia CUDA toolkit on WSL2 Ubuntu following the specified instructions from the Windows site. I was wondering if installing the Nvidia toolkit on Windows 10 directly as well would cause any conflicts or override anything potentially for the WSL2 install?
I'll be using the two separate toolkits for two separate purposes (WSL2 for linux libraries requiring the linux toolkit, Windows for things such as VS NSight requiring the Windows toolkikt)

No, it won't be a problem and this is what you would have to do to use CUDA on the pure-windows side as well as on the WSL2 side.
Other expectations/requirements still apply. For example the CUDA toolkit versions installed in each location should be consistent with the GPU driver you have already installed.

Related

While uninstalling CUDA toolkit ran into this problem, what to do?

I was installing CUDA toolkit and cuDNN for deep learning.
I downloaded the cuDNN libs, downloaded the CUDA toolkit and while installing the toolkit I get this,
And I never downloaded this, it's always been there.
Then I searched a bit about this and some guy said that we have to uninstall.
This is from my control panel,
So is it safe to uninstall these programs? And is this how to actually do it too?
It seems you previously installed higher versions of CUDA - maybe partially -
Try installing CUDA 11.4 instead.
Even if you want to use CUDA 11.2, uninstalling the above two components will not be a problem, as older versions will be installed instead.

How to run cuda-gdb in windows? Can I use cygwin for it?

I want to debug my application using cuda-gdb in windows. Is it possible to run cuda-gdb in windows? Will cygwin help to do it?
cuda-gdb is not officially supported for or intended for usage in a windows environment. From here:
This document introduces CUDA-GDB, the NVIDIA® CUDA® debugger for Linux and Mac OS.
cygwin is not an officially supported environment for running any of the CUDA linux tools on windows.
The recommended debugger for windows applications is NSIGHT Visual Studio Edition, which will be automatically installed by the CUDA 7.5 installer for windows, assuming a compatible version of visual studio is found.
For supported configurations, refer to the CUDA 7.5 windows installation guide.

installing 340.29 driver along with cuda 6.0

I have recently installed cuda 6.0 with a view of performance increment in windows 7 . the toolkit installer has display driver installer along with it and it installed display driver version named as 9.18.13.4062 . is this version mean 340.62???
Also it is mentioned that driver version 340.29 with cuda increases performance according to this link
does 340.xx series have the same performance ?? I couldnot get the version 340.29 driver. where can i download it from???
340.62 is the Windows GPU driver that ships with the CUDA 6.5 (windows) installer.
340.29 is the Linux GPU driver that ships with the CUDA 6.5 (linux) installer.
The link you have provided is referring to linux. 340.62 and 340.29 should be comparable, as much as "comparable" can be stated about a windows platform vs. a linux platform
Regarding the performance in the article linked, CUDA 6.5 (i.e. not just the driver) has significant performance increases in various libraries and in the compiler as well.
To get an idea of these performance increases, there is a webinar you can attend tomorrow (wednesday, September 17th) by following the link here.

CUDA 6.5 and Jetson TK1

I have CUDA 6.5 in my host machine. To do cross compilation for Jetson TK1, do I have to have CUDA 6.0 in the host machine?
If you have CUDA 6.0 installed on your jetson, then to do cross-compiling you need to have CUDA 6.0 (nvcc and libraries) installed on your host machine. (You could also have CUDA 6.5 installed on the host machine, if desired, but your build environment for cross-compiling would need to use CUDA 6.0 tools and libraries.)
This blog post will be a useful read, I think.
Cross compiling means the target executable is built on the host machine, not on the target. Therefore, the target executable must be compatible with (in particular with the libraries on) the target machine. This compatibility is achieved by having the correct version of nvcc as well as the correct library versions (CUDA version and target OS) to link against, that match your target.
Note that it is possible to "remotely" build on the jetson directly, as mentioned in the blog post, which would alleviate this requirement.

CUDA driver 4.2 version mismatch? 295.40 vs 295.41

I'm trying to install CUDA 4.2 on my Alienware Aurora desktop system. It's running Ubuntu 12.04, and Linux kernel 3.2.0-32 with an Nvidia GTX 690. I am able to install the CUDA SDK and display driver without issue. However, when Xorg starts, it dies with this error:
Error: API mismatch: the NVIDIA kernel module has version 295.40, but the NVIDIA driver component has version 295.41. Please make sure that the kernel module and all NVIDIA driver components have the same version.
The same thing happens when trying to run a CUDA application. Any thoughts? I have a lab of over a dozen other CUDA workstations which don't have this problem, but are also running Ubuntu 10.10.
In short: Ubuntu 12 is not yer supported distro.
If you still want to run cuda on usupported platform and expose yourself to other such problems see answer https://stackoverflow.com/a/13062766/56875