Questions and Answers :
GPU applications :
CUDA on Ubuntu?
Message board moderation
Author | Message |
---|---|
Chuckles Send message Joined: 8 Dec 01 Posts: 2 Credit: 4,697,353 RAC: 0 |
I'm trying to get CUDA working on my Dell D630 running Ubuntu Jaunty. It has an Quadro NVS 135M and version 180.44 of the Nvidia drivers. I upgraded to version 6.6.36 of the Boinc client software but it still says "No CUDA devices found" in the Messages tab when it starts up. Maybe I need a newer Nvidia driver? Thanks, Chuck |
bloodrain Send message Joined: 8 Dec 08 Posts: 231 Credit: 28,112,547 RAC: 1 |
check the list of cuda device. it has to be a 8 series or up |
Chuckles Send message Joined: 8 Dec 01 Posts: 2 Credit: 4,697,353 RAC: 0 |
The Quadro NVS 135M is listed as a CUDA-enabled card and I do have 256MB of memory on mine: http://www.nvidia.com/object/cuda_learn_products.html Looks like maybe you have to install the beta Nvidia driver version 190.18 to get CUDA support on Ubuntu... |
skildude Send message Joined: 4 Oct 00 Posts: 9541 Credit: 50,759,529 RAC: 60 |
you may have to run a 3rd party app. I don't see the 6.08 listed for linux. I think Lunatics has one for linux In a rich man's house there is no place to spit but his face. Diogenes Of Sinope |
Chuck Gorish Send message Joined: 19 Jun 00 Posts: 156 Credit: 29,589,106 RAC: 0 |
i think you will find, if you have 256mb vidram and this is also your desktop display card you may not have enough vidram to run cuda. i had a 256mb card that was always out of memory for cuda. that however should not stop boinc from recognizing it. i shouldnt think you would have to use the 190x driver. i use 185.18.31 just fine on linux. os type should not matter other than matching the arch (32 or 64bit) (or running the cuda 2.3 toolkit then you need the 190x driver). what you do need is to download the nvidia-toolkit (i prefer v2.2) and install that and copy the libs into the project directory and the libcudart files into the main boinc directory making sure ldconfig knows where they are and it has been run. then download the matching cuda application from lunatics and install an app_info.xml with it. make sure you have the use_all_gpus set to 1 in cc_config.xml <options> <use_all_gpus>1</use_all_gpus> </options> and in the project directory a 'number_of_gpus' file containing a 1 i forget what boinc version started using that but i believe 6.6.36 does use it. i had trouble with cuda v2.3 and i am unclear if it is downward compatible or not. for me, going back to 2.2 solved everything. being fair, 2.3 does work for most people so it is your choice you just have to match the cuda app with the toolkit version. skildude is correct there still is not a linux app available in the download stream from seti (at least none i have been able to find). however lack of this will not stop boinc from recognizing your cuda device and reporting it in the message log. if all of the above is proper, boinc *shoud* report it in the log and should 'just work'. |
rob smith Send message Joined: 7 Mar 03 Posts: 22160 Credit: 416,307,556 RAC: 380 |
OK, not quite the same problem, but very similar: 64bit Jaunty, got that running well, so I added a GPU (EVGA GTS250 with 512MB, so it should be good to go). The GPU is workign (or at least the Nvidia x-server monitor says its working... Everything looks OK, but I get the following at startup Starting BOINC client version 6.6.36 for x86_64-pc-linux-gnu Configured to use all coprocessors log flags: task, file_xfer, sched_ops Libraries: libcurl/7.18.0 OpenSSL/0.9.8g zlib/1.2.3.3 c-ares/1.5.1 Data directory: /var/lib/boinc-client Processor: 1 AuthenticAMD AMD Athlon(tm) 64 Processor 3200+ [Family 15 Model 44 Stepping 2] Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt lm 3dnowext 3dnow up rep_good pni lahf_lm OS: Linux: 2.6.28-15-generic Memory: 988.60 MB physical, 2.38 GB virtual Disk: 54.03 GB total, 47.54 GB free Local time is UTC +1 hours No CUDA devices found No coprocessors Not using a proxy I've done all the checks I can think of, the mods suggested above, but still it sits there smiling sweetly at me :-( Bob Smith Member of Seti PIPPS (Pluto is a Planet Protest Society) Somewhere in the (un)known Universe? |
rob smith Send message Joined: 7 Mar 03 Posts: 22160 Credit: 416,307,556 RAC: 380 |
I should have added that I'm (or think I am) using Cuda 2.3, with NVIDIA driver version 190.18 Bob Smith Member of Seti PIPPS (Pluto is a Planet Protest Society) Somewhere in the (un)known Universe? |
rjfarmer Send message Joined: 7 Jan 04 Posts: 1 Credit: 2,149,618 RAC: 0 |
i found (after weeks of trying) that you need to set the owner permissions on your graphics card to the same as boinc, at least thats what i had to do on f11 then restart the boinc service. i tried adding boinc to the video group but that didnt seem to have any effect then also found that there appeared no way to set it permanently and had to reset it after each reboot |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.