Questions and Answers :
Unix/Linux :
boinc 6.10.17 requests CUDA tasks but cant get any
Message board moderation
Author | Message |
---|---|
Eric B Send message Joined: 9 Mar 00 Posts: 88 Credit: 168,875,085 RAC: 762 |
I installed boinc yesterday on a newly built system. Boinc seems to recognize my nvidia card is cuda capable, it even requests CUDA tasks but i never get any. Its been trying for the last 20 hours. I do get regular seti MB tasks ok I'm running mandriva 64 bit 2010 with a slightly modified kernel. This fresh boinc install shows: ~/BOINC >file libcudart.so libcudart.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, stripped and from the Messages tab i see: Thu 04 Mar 2010 11:30:53 PM PST OS: Linux: 2.6.31.12-1mnbX Thu 04 Mar 2010 11:30:53 PM PST Memory: 3.87 GB physical, 0 bytes virtual Thu 04 Mar 2010 11:30:53 PM PST Disk: 70.33 GB total, 59.15 GB free Thu 04 Mar 2010 11:30:53 PM PST Local time is UTC -8 hours Thu 04 Mar 2010 11:30:53 PM PST NVIDIA GPU 0: GeForce GT 220 (driver version unknown, CUDA version 2030, compute capability 1.2, 1024MB, 131 GFLOPS peak) [snip] Fri 05 Mar 2010 07:14:04 PM PST SETI@home Requesting new tasks for GPU Fri 05 Mar 2010 07:14:09 PM PST SETI@home Scheduler request completed: got 0 new tasks Fri 05 Mar 2010 07:14:09 PM PST SETI@home Message from server: No work sent I'm running this nvidia driver; NVIDIA-Linux-x86_64-190.53-pkg2.run |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
Even while everything may work out there for you, Seti does not have a CUDA application for Linux. So you will have to manually install a 3rd party application with the anonymous platform. So check here at Crunch3r's site for the CUDA 6.08 app for 64bit Linux. How to install it is in readme's inside the tar file. |
Eric B Send message Joined: 9 Mar 00 Posts: 88 Credit: 168,875,085 RAC: 762 |
I installed crunch3r's app and now CUDA is processing happily away. HOWEVER. . . on first boinc run all my WU's got discarded. Boinc downloaded some cuda work and has been trying to get CPU work now for awhile, but like before with CUDA, now the CPU cant ever get work. Here's some selected output: Sat 06 Mar 2010 11:46:02 AM PST SETI@home Sending scheduler request: To fetch work. Sat 06 Mar 2010 11:46:02 AM PST SETI@home Requesting new tasks for CPU Sat 06 Mar 2010 11:46:07 AM PST SETI@home Scheduler request completed: got 0 new tasks Sat 06 Mar 2010 11:46:07 AM PST SETI@home Message from server: No work sent Sat 06 Mar 2010 11:47:22 AM PST SETI@home Sending scheduler request: To fetch work. Sat 06 Mar 2010 11:47:22 AM PST SETI@home Requesting new tasks for CPU Sat 06 Mar 2010 11:47:25 AM PST Project communication failed: attempting access to reference site Sat 06 Mar 2010 11:47:27 AM PST SETI@home Scheduler request failed: Server returned nothing (no headers, no data) Sat 06 Mar 2010 11:47:31 AM PST Internet access OK - project servers may be temporarily down. Sat 06 Mar 2010 11:48:27 AM PST SETI@home Sending scheduler request: To fetch work. Sat 06 Mar 2010 11:48:27 AM PST SETI@home Requesting new tasks for CPU Sat 06 Mar 2010 11:48:30 AM PST Project communication failed: attempting access to reference site Sat 06 Mar 2010 11:48:32 AM PST SETI@home Scheduler request failed: Server returned nothing (no headers, no data) Sat 06 Mar 2010 11:48:36 AM PST Internet access OK - project servers may be temporarily down. Sat 06 Mar 2010 11:49:32 AM PST SETI@home Sending scheduler request: To fetch work. Sat 06 Mar 2010 11:49:32 AM PST SETI@home Requesting new tasks for CPU Sat 06 Mar 2010 11:49:37 AM PST SETI@home Scheduler request completed: got 0 new tasks Sat 06 Mar 2010 11:49:37 AM PST SETI@home Message from server: No work sent |
Eric B Send message Joined: 9 Mar 00 Posts: 88 Credit: 168,875,085 RAC: 762 |
The problem was in app_info.xml, and contributing to the confusion were the very misleading behavior/error messages from BOINC, they are almost meaningless. it wasnt calling for gpu & cpu apps to run, now I have setiathome-CUDA-6.08.x86_64-pc-linux-gnu running the CUDA stuff and AK_V8_linux64_ssse3 running Seti MB. The app_info.xml below works. anyone know where the app_info.xml is documented? I'd like to understand why the file_info information has to be repeated in the app_name section. I can think of a much simpler format, anyway, I'm running. app_info> <app> <name>setiathome_enhanced</name> </app> <file_info> <name>AK_V8_linux64_ssse3</name> <executable/> </file_info> <app_version> <app_name>setiathome_enhanced</app_name> <version_num>603</version_num> <file_ref> <file_name>AK_V8_linux64_ssse3</file_name> <main_program/> </file_ref> </app_version> <app> <name>setiathome_enhanced</name> </app> <file_info> <name>setiathome-CUDA-6.08.x86_64-pc-linux-gnu</name> <executable/> </file_info> <file_info> <name>libcudart.so.2</name> <executable/> </file_info> <file_info> <name>libcufft.so.2</name> <executable/> </file_info> <app_version> <app_name>setiathome_enhanced</app_name> <version_num>608</version_num> <plan_class>cuda</plan_class> <avg_ncpus>0.350000</avg_ncpus> <max_ncpus>0.350000</max_ncpus> <coproc> <type>CUDA</type> <count>1</count> </coproc> <file_ref> <file_name>setiathome-CUDA-6.08.x86_64-pc-linux-gnu</file_name> <main_program/> </file_ref> <file_ref> <file_name>libcudart.so.2</file_name> </file_ref> <file_ref> <file_name>libcufft.so.2</file_name> </file_ref> </app_version> </app_info>[/code] |
Gundolf Jahn Send message Joined: 19 Sep 00 Posts: 3184 Credit: 446,358 RAC: 0 |
anyone know where the app_info.xml is documented? I don't know how complete the BOINC wiki entry for Anonymous platform is, but the format should be pretty similar to that of client_state.xml. Gruß, Gundolf Computer sind nicht alles im Leben. (Kleiner Scherz) SETI@home classic workunits 3,758 SETI@home classic CPU time 66,520 hours |
©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.