We’re releasing a new CUDA 2.0 beta today. Support for GT200-based cards with new features (double precision, shared atomics, voting, double registers–compile with --arch compute_13), more documentation, more support for newer Linux distributions. more examples, and more…
It should be on the website soon, but in the interim, download links:
The new beta installed fine in Suse 10.3 and seems to work fine - SDK compiled, tests passed, etc. Thx.
The new beta does not seem to want to let me overclock my 8800GT like the previous beta, however. Attempts to do so have locked up the system. Before I was getting 600->700 MHz core, 900->1000 MHz memory, now not so much. The autoscan for overclocking in nvidia-settings suggested 700/1100, which promptly froze the system.
(AMD Phenom 9600 on a Gigabyte MA790X motherboard; PNY 8800GT.)
(Still searching for code for matrix division: solution to A*X=B; glimmers of happiness over the horizon, but no joy yet…)
The 177.35 don’t work with my GF8500GT/GF8600GTS under Vista x64(SP1).
On the other hand, to separate the x86 and x64 installers is a very bad idea… because if I want to cross-compile from Vista x64 to winXP 32 I cannot… the toolkit says it’s already installed and I need to uninstall it… why you cannot just make one installer and deploy the DLLS and .LIBs into two different folders(x86 and x64)? External Image
On the other hand you continue deploying only the /MT(Multithreaded ) cudart.lib… For IJW/CLI/CLR/.NET/.NET STL we NEED also the /MD ( Multithreaded DLL) libraries <img src=‘http://hqnveipbwb20/public/style_emoticons/<#EMO_DIR#>/crying.gif’ class=‘bbc_emoticon’ alt=‘:’(’ /> If not, it’s impossible to link the CUDA libraries without getting a zillion of linking errors, /NODEFAULTLIB problems, etc…
And, finally, the libraries generates memory leaks under VS2008… because the deployment you did its for VS2005… and the VS2008 crt is different…
For example… see the FBX SDK… Autodesk deploys the .LIB as:
fbx_vs2003_mt.lib → x86, Multithread for Visual Studio 2003
fbx_vs2003_md.lib → x86, Multithread DLL for Visual Studio 2003
fbx_vs2003_mtd.lib → x86, Multithread Debug for Visual Studio 2003
fbx_vs2003_mdd.lib → x86, Multithread DLL Debug for Visual Studio 2003
fbx_vs2003_mt_x64.lib → x64, Multithread for Visual Studio 2003
fbx_vs2003_md_x64.lib → x64, Multithread DLL for Visual Studio 2003
fbx_vs2003_mtd_x64.lib → x64, Multithread Debug for Visual Studio 2003
fbx_vs2003_mdd_x64.lib → x64, Multithread DLL Debug for Visual Studio 2003
fbx_vs2005_mt.lib → x86, Multithread for Visual Studio 2005
fbx_vs2005_md.lib → x86, Multithread DLL for Visual Studio 2005
fbx_vs2005_mtd.lib → x86, Multithread Debug for Visual Studio 2005
fbx_vs2005_mdd.lib → x86, Multithread DLL Debug for Visual Studio 2005
fbx_vs2005_mt_x64.lib → x64, Multithread for Visual Studio 2005
fbx_vs2005_md_x64.lib → x64, Multithread DLL for Visual Studio 2005
fbx_vs2005_mtd_x64.lib → x64, Multithread Debug for Visual Studio 2005
fbx_vs2005_mdd_x64.lib → x64, Multithread DLL Debug for Visual Studio 2005
fbx_vs2008_mt.lib → x86, Multithread for Visual Studio 2008
fbx_vs2008_md.lib → x86, Multithread DLL for Visual Studio 2008
fbx_vs2008_mtd.lib → x86, Multithread Debug for Visual Studio 2008
fbx_vs2008_mdd.lib → x86, Multithread DLL Debug for Visual Studio 2008
fbx_vs2008_mt_x64.lib → x64, Multithread for Visual Studio 2008
fbx_vs2008_md_x64.lib → x64, Multithread DLL for Visual Studio 2008
fbx_vs2008_mtd_x64.lib → x64, Multithread Debug for Visual Studio 2008
fbx_vs2008_mdd_x64.lib → x64, Multithread DLL Debug for Visual Studio 2008
That’s a correct deployment… the current CUDA 2 toolkit/sdk is incomplete… because without that you will get lots of problems with .NET and memory leaks due to C CRT incompatibilities… If you could add a very simple Managed C++/CLR/IJW/WinForms/.NET STL example to the SDK you could see what i’m referrering to…
some examples complain because can’t find glew64.dll
The driver does not work with FX570m on Vista, even with a modded .inf. Very sad :(
However, on XP it works (with modded .inf), and slightly faster than the previous.
has anyone successfully installed the new driver 177.35 (NVIDIADisplayWin2K_177.35,…)? What kind of hardware is required?
I tried to install two drivers on two different setups:
Windows XP (x86), GeForce 8600 GT, NVIDIADisplayWin2K_177.35
Windows Vista (x64), GeForce 9600 GT, NVIDIADisplayWinVista64_177.35
In both cases setup is terminated:
“NVIDIA Setup Error
The NVIDIA Setup program could not locate any drivers that are compatible with your current hardware. …”
Would it be possible to have the reference manual either in HTML form or to include links within the PDF? It’s nice to be able to scroll through the list of function names and then jump straight to ones of interest.
Additionally, could you please kill the “see also” sections? Searching for a function name always finds these, but not the function you’re looking for.
Hey, have you noticed the NVIDIA’s web still selects the 177.35 driver when you select the “download CUDA”? That driver does not work with GF8/9 series… only with the GTX … any idea how to fix that, pls? Touching the .ini file or…?
That is not the first time nvidia makes real mess with official driver. Somebody should be fired for such mistake. I expect after spending over 2000$ for Tesla, 9800GX2 and 790i Ultra mobo, drivers for those expensive pieces should work without mods and tweaks. Unfortunately history repeats and it looks like nvidia doesn’t feel responsible (again). Hey NGuys wtf you are doing?
This is the last time I do their job.
This is workaround for windows
Find display driver 175.70 (www.guru3d.com) and download it
Uninstal current Nvidia Display driver
start 175.70 selfextracting exe but DO NOT install that driver
find folder where exe extracts files and copy nv4_disp.inf file from that folder to some temp location
start installation of 177.35 driver
when setup fails (it reports error and terminate installation but all files are extracted usually in C:\NVIDIA)Winblablabla\177.35\english)
take nv4_disp.inf from temp location and paste (overwrite) existing nv4_disp.inf file in 177.35\english folder
start setup again
now it should recognize your hardware
reboot your comp
Followed steps are necessary only if you use nTune and have problems with GPU’s fan(s) when windows boot (it is necessary only once)
11. when windows boots go to folder
C:\Documents and Settings\Administrator\Local Settings\Application Data\NVIDIA Corporation\nTune\Profiles
12. using wordpad open file osbootpf.nsu
13. find lines:
GPUFAN3D0=0
GPUFAN3D1=0 // this line exists only if you have more than one GPU
GPUFAN3D2=0 // this line exists only if you have more than two GPU
and replace zeros with percentage initial values. For example if you want GPU0 fan works on 60% when windows boot then line should looks like
GPUFAN3D0=60
Save changes
reboot
thats it
Note: if you have new Nvidia g2xx card you shouldn’t do this because original nv4_disp.inf already has support for it
Mandrak is completely right. This is a huge mess. This driver only works for a VERY small subset of CUDA compatible cards. (just do a diff between beta1-174.55 and beta2-177.35 inf files to see) I thought about doing the workaround, but I would much rather have a “supported” driver. NV guys, any idea when you will get this fixed?? Very few people can use beta2 in its current form on windows. And how did this ever get past QA?!
The official 175.19(released yesterday) does not support CUDA2… and I still cannot download the old-working 174.77… I only can download the 177.35 for GT200… but I need the old 174.77 because I use a GF8600GTS… but I deleted the 174.77 and now I cannot continue programming CUDA2 anymore… could you pls solve that? I think the web’s guys need to add a combo box to select your GPU… and download the 174.77 for GF8/9 or 177.35 for GTX…
We’re sorry about the driver problems–obviously there’s been a mix-up with the driver INF. We’re working on getting this fixed right now, and we should have a new driver package up for WinXP and Vista that resolves these issues.
I’ll update the first post as soon as the new driver is up.
