Well, after feeling the pain for a few days I have Cuda 2.0 Beta up and running on:
- Dell Latitude D630 (laptop)
- Quadro NVS135m with 256 megs of ram
- Ubuntu Hardy (8.04) w/ latest updates
- Kernel is 2.6.24-18-generic for x86_64
I won’t take you through the ups and downs of my trials, but I will try to mention some of the pitfalls…
== Cleanup ==
First, get rid of everything nvidia on your machine. No envyng, no nvidia related packages at all. They just mess with your setup, and in order to get Cuda2b working you need to have the latest kernel and glx drivers from Nvidia anyway. I had old drivers that kept getting loaded, so I even recommend going into your /lib/modules/… directories and getting rid of any nvidia.ko files you find in kernel/drivers/video.
== Preparations ==
I recommend doing a BIOS upgrade before starting in with CUDA. It did change some behavior on my machine and in the forums it is discussed often, so save yourself the pain and upgrade first.
For Cuda1.1 you needed to use older compilers (gcc-4.1), but this is no longer the case. You should get gcc and g++ 4.2 in Hardy by default, and they will work fine.
You need 3 packages, all found here:
Kernel and GLX drivers (174.55), which are listed as Redhat Enterprise, but they work fine in Ubuntu Hardy. (Many very solid developers are on Ubuntu these days so Nvidia should really get rid of this RedHat focused crap…)
Cuda Toolkit 2 (Also falsely listed for RedHat…)
CUDA SDK 2.0
Kill X and install the driver from the terminal.
sudo /etc/init.d/gdm stop
sudo sh NVIDIA-Linux-x86_64-174.55-pkg2.run
You will want to compile a kernel driver and probably just let it configure your xorg.conf. These days they auto-configure most everything anyway. If you are 64-bit you probably want to install the 32-bit compat libraries also. I did, and stuff works.
Alright, startx or reboot and login. (Reboot is safest in case you had leftover modules already loaded. Otherwise you can modprobe -r nvidia too)
Now you can install the toolkit and then the sdk. (I did it in a directory in my home directory because I don’t like polluting the system.)
Read the release notes. Seriously, all of them. I missed the fact that I needed the latest driver and it caused me about a weekend of banging my head on the wall. Read the notes, follow the directions.
Setup your PATH and LD_LIBRARY_PATH to point into your toolkit’s bin and lib directories. Go into the sdk directory and run:
That -k will tell it to keep going after errors. This is beta software, so it might not all build yet.
Anyway, it works. I can run fluids, particles, nbody, the works. Almost all of the demos that compute values pass their tests, although a few do still fail. I donÂ´t remember which. Good luck everyone, and happy hacking!