Message boards :
Number crunching :
vlar running over 21hrs on cpu
Message board moderation
Previous · 1 · 2
Author | Message |
---|---|
Bernd Noessler Send message Joined: 15 Nov 09 Posts: 99 Credit: 52,635,434 RAC: 0 |
You should check the ownership and rights in the BOINC folder. (especially in the slots) |
BilBg Send message Joined: 27 May 07 Posts: 3720 Credit: 9,385,827 RAC: 0 |
I also have need of some instruction on these app_info.xml files. Is it just me or are these an absolute abomination? I don't see the order there. ... I tried to reorder it (but mind I don't use Linux) (empty lines in app_info.xml file are OK to use) (since you don't have setiathome_enhanced tasks I used only setiathome_v7) <app_info> <app> <name>setiathome_v7</name> </app> <file_info> <name>setiathome_7.01_x86_64-pc-linux-gnu</name> <executable/> </file_info> <app_version> <app_name>setiathome_v7</app_name> <version_num>701</version_num> <platform>x86_64-pc-linux-gnu</platform> <avg_ncpus>1.000000</avg_ncpus> <max_ncpus>1.000000</max_ncpus> <file_ref> <file_name>setiathome_7.01_x86_64-pc-linux-gnu</file_name> <main_program/> </file_ref> </app_version> <app> <name>setiathome_v7</name> </app> <file_info> <name>setiathome_x41g_x86_64-pc-linux-gnu_cuda32</name> <executable/> </file_info> <file_info> <name>libcudart.so.3</name> <executable/> </file_info> <file_info> <name>libcufft.so.3</name> <executable/> </file_info> <app_version> <app_name>setiathome_v7</app_name> <version_num>700</version_num> <platform>x86_64-pc-linux-gnu</platform> <plan_class>cuda32</plan_class> <avg_ncpus>0.05</avg_ncpus> <max_ncpus>1.0</max_ncpus> <coproc> <type>CUDA</type> <count>1.0</count> </coproc> <file_ref> <file_name>setiathome_x41g_x86_64-pc-linux-gnu_cuda32</file_name> <main_program/> </file_ref> <file_ref> <file_name>libcudart.so.3</file_name> </file_ref> <file_ref> <file_name>libcufft.so.3</file_name> </file_ref> </app_version> </app_info> Â - ALF - "Find out what you don't do well ..... then don't do it!" :) Â |
Eric B Send message Joined: 9 Mar 00 Posts: 88 Credit: 168,875,085 RAC: 762 |
God idea on ownership, but its all ok. Could it be a library outside of boinc that its using? BTW: I don’t have the ability to run native, so to speak, the change to use a new glibc 2.3.2 or higher really screwed me, its not practical to try to upgrade glibc either, too much depends on it. I have to compile boinc in order to use it. Maybe its related to that somehow. But, is ti boinc? or is it the seti executable? How far back can i go with boinc versions and still run seti v7? |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
God idea on ownership, but its all ok. Could it be a library outside of boinc that its using? BTW: I don’t have the ability to run native, so to speak, the change to use a new glibc 2.3.2 or higher really screwed me, its not practical to try to upgrade glibc either, too much depends on it. I have to compile boinc in order to use it. Maybe its related to that somehow. But, is ti boinc? or is it the seti executable? How far back can i go with boinc versions and still run seti v7? I looked into the glibc BOINC issue when I downgraded to Ubuntu 10.04. You're correct, updating it isn't really possible. I was surprised to find BOINC v7 is incompatible with about 95% of Linux systems, not good. I first tried BOINC 6.10.xx and it seemed to be missing the GPU section in the Activity Menu. I then found a precompiled version of 6.12.33. 6.12 seems to be very close to BOINC v7 and works fine for me using x41g with SETI version 7 tasks. The Ubuntu version I used is here, “Debian BOINC Maintainers†team Good Luck. |
Eric B Send message Joined: 9 Mar 00 Posts: 88 Credit: 168,875,085 RAC: 762 |
sorry its taken me so long t reply here. I ended up reformatting and re-installing. It didn’t help, the MB v7 stock app gets stuck. So, i am now running x41g cuda and MBv7_7.05r1848_sse3_linux64 which i just started up about 20 minutes ago. It looks promising, I'm crunching mb v7 cpu and nvidia cuda. I will know more in a day or so. The root cause of the previously posted problems is something in the stock seti app that just doesn’t sit well with this OpenSuse 12.3 installation. |
Eric B Send message Joined: 9 Mar 00 Posts: 88 Credit: 168,875,085 RAC: 762 |
Just a follow up - using my locally compiled version of boinc 7.0.65 and the 2 executable files: MBv7_7.05r1848_sse3_linux64 (Seti V7.05) setiathome_x41g_x86_64-pc-linux-gnu_cuda32 (seti v7.00 cuda32) has worked fine, I can crunch both CPU MB and NVidia Cuda WU's with no apparent issues. My OS is OpenSuse 12.3 kernel 3.7.10-1.16-desktop, on a SNB-E 6 Core/HT with Nvidia GTX-460 using the proprietary Nvidia Driver 319.32 I'm posting this info in case any one else has similar problems and could benefit from my resolution. |
©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.