Posts by lacdesmonts

1) Message boards : Number crunching : Dual GPUs - failed to calculate likelihood (Message 51755) Posted 21 Nov 2011 by lacdesmonts Post: I've checked the validation errors and only one applies to the rig in question. They appear infrequently and seem to have nothing to do with the likelihood error. I now find that the error always occurs with simultaneous MC and CC WUs. I should have mentioned that I am running the GPUs in Crossfire. This may not be significant but I have never been able to acccess the cards independently under Linux. This is (probably) a limitation in the Catalyst and/or AMD-APP-SDK-v2.5 (not really relevant here but I had that problem when mining.) So it's either a Linux problem or a Boinc / MW problem. If anyone is successfully running Linux / ATI Crossfire with multiple GPU WUs I would appreciate knowing how you did it. Thanks.
2) Message boards : Number crunching : Dual GPUs - failed to calculate likelihood (Message 51750) Posted 21 Nov 2011 by lacdesmonts Post: Thanks for the responses. Not sure what you mean by several validation errors. Fairly sure it's not a heat problem - currently running at 58c with CC WUs, MW sends it to about 62c. About a month ago I had this system set up with a Regor 250 running 2 cores at 3GHz. Had the same problem then with MW, presumably before the "mix" WUs were issued. Made a great CC only rig so I didn't bother any further Now I have the hex in it and it seems a shame to waste all those cores.
3) Message boards : Number crunching : Dual GPUs - failed to calculate likelihood (Message 51743) Posted 21 Nov 2011 by lacdesmonts Post: I'm running an AMD 1100 Hex with dual HD 5830s. Operating system is Ubuntu 10.10 - 2.6.35-30, Catalyst 11.9, Boinc 6.10.58 The system runs full Milkyway and Collatz GPU WUs only, timeslicing is at 30 minutes. Collatz has no problem running two GPU WUs simultaneously. On Milkyway some simultaneous WUs process OK and some fail with a "failed to calculate likelihood" error. The WUs in question are ps_separation_82_2s_mix4_ . . . Generally the first of a pair of processes fail and the second works. Sometimes it appears both work. I have yet to observe the system processing one MW and one CC WU at the same time, so don't know what will happen there. Any help would be appreciated. Thanks.
4) Message boards : Number crunching : GPU Requirements (Message 50986) Posted 8 Sep 2011 by lacdesmonts Post: . The other projects that support AMD/ATI GPUs that do not require DP math will recognize and use the A8-3850's integrated GPU, however. I've got an Asus F1A75-M Pro with an A8-3850 running Ubuntu 10.10 64 bit. I've tried MilkyWay, Moo and Prime - Boinc states no useable GPU in all cases. Running ATI 11.8 drivers. Using just the onboard graphics the Unigine Heaven benchmark runs great, can run 2 Nexius windows simultaneously with no significant load on the cores. However - can't run AMDOverdriveCtrl, which works with pretty well any discrete card. And Linux doesn't recognize the sensors, so I don't like to push the CPU without knowing what the temps are.
5) Message boards : News : Separation updated to 0.82 (Message 50237) Posted 19 Jul 2011 by lacdesmonts Post: System is Linux 64 - Catalyst 11.6 - HD5830 Last night was getting "maximum time limit elapsed" errors on all GPU WUs. Upgraded to 6.12.18 now I'm getting this - <core_client_version>6.12.18</core_client_version> <![CDATA[ <message> Maximum elapsed time exceeded </message> <stderr_txt> Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4' Error reading astronomy parameters from file 'astronomy_parameters.txt' Trying old parameters file Using SSE3 path Found 1 CAL devices Chose device 0 Device target: CAL_TARGET_CYPRESS Revision: 2 CAL Version: 1.4.1417 Engine clock: 825 Mhz Memory clock: 1050 Mhz GPU RAM: 1024 Wavefront size: 64 Double precision: CAL_TRUE Compute shader: CAL_TRUE Number SIMD: 14 Number shader engines: 2 Pitch alignment: 256 Surface alignment: 256 Max size 2D: { 16384, 16384 } Estimated iteration time 152.765152 ms Target frequency 30.000000 Hz, polling mode 1 Dividing into 4 chunks, initially sleeping for 0 ms Integration range: { nu_steps = 640, mu_steps = 1600, r_steps = 1400 } Using 4 chunk(s) with sizes: 400 400 400 400 Integration time = 127.293641 s, average per iteration = 198.896314 ms Integral 0 time = 130.222443 s Likelihood time = 5.456142 s <background_integral> 0.000125639127066 </background_integral> <stream_integral> 409.950098617738433 13.735900627600021 </stream_integral> <background_likelihood> -3.063023849357760 </background_likelihood> <stream_only_likelihood> -4.212400995965620 -173.914236733988474 </stream_only_likelihood> <search_likelihood> -3.026010903920815 </search_likelihood> <search_application> milkywayathome_client separation 0.82 Linux x86_64 double CAL++ </search_application> 01:31:06 (9368): called boinc_finish </stderr_txt> ]]>