I have the Nvidia Quadro NVS4200M along with Intel Integrated Graphics (on my laptop). I can't seem to get the CUDA 5.0 toolkit installation to succeed.
I am running Windows 7 Enterprise Edition 64-bit. I tried the 64-bit desktop & notebook installers and the 32-bit installers.
All of them seem to fail with the error message "Display Driver failed installation". I installed the latest drivers from here, and it is supposed to support CUDA-5.0, and despite that, the installation fails.
After failure, the libraries and binaries are present, but NSight Eclipse (which seems to have no standalone installation link) isn't installed. What could be the possible issue?
I'm not sure why the driver install failed in your case, but if you
have a "recent" driver installed, it's not necessary to use the
driver that comes with the cuda installer. The cuda installer
offers individual options to install the toolkit (required), samples
(optional), and driver (required only if you have an older driver),
so you can just select "no" when prompted for the driver install, to
avoid this, assuming you have a recent driver or installed one such
as the 307.45 driver.
You should always use a 64 bit installer if you have a 64 bit OS.
The only officially supported C/C++ compiler for windows is cl.exe, the microsoft compiler that ships with either Microsoft Visual Studio (the Express edition will do, it is free), or the Windows SDK (for command line use only). You're free to experiment with other stuff, but your mileage may vary. MS VS 2010 (and 2008) are the easiest to use. MS VS 2012 can be made to work but may require extra steps.
I recommend installing cuda after installing Microsoft Visual Studio. This is because the cuda installer should automatically find your VS installation and update some important files to make building cuda projects easier.
nsight Eclipse Edition is a linux-only tool (or mac). It is not for windows use, and will not be installed by the windows cuda installers. nsight EE provides an environment for code building, debugging, and profiling. In windows, the corresponding operations can be done via MS VS IDE for code building, the standalone visual profiler for profiling, and using a separate plug-in, nsight visual studio edition, for debugging and profiling within visual studio. Due to the way visual studio is constructed, nsight visual studio edition will not work with the free versions of visual studio. nsight visual studio has it's own separate installer.
The windows getting started guide may also be of interest.
Related
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.
I have DLL, which contain CUDA function (image processing). This DLL is compiled with VISUAL STUDIO 2008 Express edition. I call this DLL with LabVIEW.
This DLL and LabVIEW VI are developed on one computer (office) and I need to run same program in differen computer (in lab).
Q1: Do I have to instal cuda toolkit or cuda SDK on computer in lab?
Q2: Do I have to recompile DLL on computer in lab or DLL are completly portable?
Thanks
Yes, you have to install CUDA toolkit and SDK if you use any functions/ wrappers ( like cudaSafeCall) from SDK. In general SDK is not nesessary. You need in compatible NVIDIA GPU driver instaled on Lab computer, too.
You need not recompile if Lab computer and your own have the same Microsoft Visual Studio runtime, CUDA runtime version and Lab computer have GPU device with proper compute capability that your code was compiled for. For more information about CUDA code compatibility see 3.1.2 - 3.1.4 sections in CUDA C programming Guide.
I'm mostly set up for CUDA development. I've installed the developer drivers, CUDA 4.0 toolkit, and the 4.0 SDK, as well as the bugfix. I'm running Windows 7 x64, and am using Visual C++ 2010 Express. For 32-bit applications, I perform the following steps and my CUDA applications work properly.
Create new empty project
make sure Platform Toolset is set to v100 (normally the default)
check the CUDA 4.0 Build Customization for the project
set the item type of my .cu file to CUDA C/C++
add 'cudart.lib' to Properties->Linker->Input->Additional Dependencies
I can also run non-CUDA 64-bit applications. Visual C++ 2010 Express does not come with 64-bit dependencies automatically, so I had to install the Windows 7.1 SDK w/ .NET Framework 4.0. Then I simply set the Platform Toolset for the VC++ project to Windows7.1SDK, change the Active solution platform to x64, and I'm good to go.
However, I can't seem to do both at the same time - I can't create a 64-bit CUDA application. If I change the Platform Toolset of a CUDA application to Windows7.1SDK, whether the Active solution platform is x64 or Win32, I get the compile error that nvcc.exe exited with code -1. And if I leave the Platform Toolset set to v100 and change the Active solution platform to x64, I get the compile error "fatal error LNK1104: cannot open file 'kernel32.lib'. The only combination that works is v100 and Win32, and obviously that prevents me from running a 64-bit application.
Is there a procedure for enabling this functionality that I just haven't been able to find online? Any ideas or suggestions? Thanks for your time.
Not possible in express edition , ( does not support plugins ) unless you want to setup nvcc manually , and use notepad to write cu files, I very much prefer the VS integration .
You could check that the host compiler properties for the .cu files are set to 64-bit.
Right-click the "Code.cu" file and click 'Properties'.
Expand the "CUDA C/C++" item and select "Common".
Change "Target Machine Platform" to 64-bit.
I have installed Parallel Nsight for Visual Studio 2010. Due to my research, it is not able to debugging on machines which dont have NVIDIA graphic card.
Therefore, I would like to debug it on the server (connecting to the server), would it be possible?
Thanks in advance.
Yes. You can install Visual Studio and Parallel Nsight on your developer machine, and install Parallel Nsight on the remote machine with the GPU. Then you simply configure Parallel Nsight to execute on the remote machine.
Behind the scenes, when you "start CUDA debugging", Nsight will copy the executable (and any specified data files) to the remote machine and launch the task.
See the Parallel Nsight website for more details and to check system requirements, as well as the documentation that is installed.
To develop NVIDIA CUDA programs, the tools needed are:
Developer drivers
CUDA Toolkit
GPU Computing SDK
What is this developer driver? Installing it silently overrides any NVIDIA graphics driver that is already installed. So, how is the developer driver different from the usual NVIDIA graphics driver? What extra components or functionality does it contain?
The developer driver is available in both 32-bit and 64-bit flavours. If I am developing 32-bit Visual C++/CUDA projects on 64-bit Windows 7, which flavour of the developer driver do I choose? Why?
From the developer download page:
Note: The developer driver packages below provide baseline support for the widest number of NVIDIA products in the smallest number of installers. More recent production driver packages for developers and end users may be available at www.nvidia.com/drivers.
The developer driver is released with the Toolkit and is intended to have wide support for all CUDA capable devices. On the other hand the drivers on the main driver page are released as appropriate; the main drivers have full support for CUDA, but each one may support a subset of devices.
Incidentally, when you install a NVIDIA driver it tells you what version is currently installed and what version you're installing (unless you choose a silent install!).