Forum > GPU crunching
V10/11 of modified SETI MB CUDA + opt AP package for full multi-GPU+CPU use
The Grinch:
Don't know where are the Problem is .. may be the Browser?!? (try to use IE6/7 - i know, IE is not the favorit...)
I'm using the drivers from laptopvideo2go sometimes without any problems, only when playback BlueRay (CopyProteced) WHQL-driver is needed.
Jason00:
I've got a problem with my V10a x64 Cuda app, I believe it did it with the V10a x86 app too. Here's an example WU. http://setiathome.berkeley.edu/result.php?resultid=1173510764.
The message I get is this.
<message>
too many exit(0)s
</message>
Any idea on this error? It's not like I'm doing much else on this PC.
Raistmer:
--- Quote from: xbill on 27 Feb 2009, 09:41:25 am ---But starting the *GPU_CPU_team_V10.exe results in an application error popup from windows, no further output on the commandline, no stderr.txt. eventvwr is not helpful either: Fehlerhafte with nvidias stock drivers because they reference some files that are not contained in nvidias distribution.
--- End quote ---
Did you start it from command line?
Team builds don't support standalone work. The should run only under BOINC and only in SETI@home main project (hard link to particular layout for CUDA MB relatively to working path required).
Raistmer:
--- Quote from: Jason00 on 27 Feb 2009, 11:05:17 am ---I've got a problem with my V10a x64 Cuda app, I believe it did it with the V10a x86 app too. Here's an example WU. http://setiathome.berkeley.edu/result.php?resultid=1173510764.
The message I get is this.
<message>
too many exit(0)s
</message>
Any idea on this error? It's not like I'm doing much else on this PC.
--- End quote ---
Build features: Non-graphics CPU-GPU team mod IPP USE_SSSE3 x86
It's x86 build, not x64 one.
Update your config to V10a. V10 had rescheduling bug that could lead to such situation. So update REQUIRED.
Jason00:
--- Quote from: Raistmer on 27 Feb 2009, 11:11:12 am ---
--- Quote from: Jason00 on 27 Feb 2009, 11:05:17 am ---I've got a problem with my V10a x64 Cuda app, I believe it did it with the V10a x86 app too. Here's an example WU. http://setiathome.berkeley.edu/result.php?resultid=1173510764.
The message I get is this.
<message>
too many exit(0)s
</message>
Any idea on this error? It's not like I'm doing much else on this PC.
--- End quote ---
Build features: Non-graphics CPU-GPU team mod IPP USE_SSSE3 x86
It's x86 build, not x64 one.
Update your config to V10a. V10 had rescheduling bug that could lead to such situation. So update REQUIRED.
--- End quote ---
I started using the V10a app as soon as you posted them the other day. And last night I started with the V10a Intel x64 app.
After looking at my completed WU's it shows that for my CPU WU's its x64, and the GPU WU's it's x86.
CPU
http://setiathome.berkeley.edu/result.php?resultid=1173515610
GPU
http://setiathome.berkeley.edu/result.php?resultid=1173515613
Here are the tasks for my computer.
http://setiathome.berkeley.edu/results.php?hostid=4706608
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version