Posts by Senilix

\n studio-striking\n
1) Message boards : Number crunching : ATI 12.2 vs. BOINC (Message 2864)
Posted 9 Mar 2012 by Senilix
Post:
I think I found the answer. Driver version 12.2 for XP doesn't contain CAL anymore. So ATI 12.2 and BOINC is a big NO-GO with XP.
2) Message boards : Number crunching : ATI 12.2 vs. BOINC (Message 2859)
Posted 9 Mar 2012 by Senilix
Post:
Anyone else having trouble with the new ATI driver version 12.2 and BOINC?

I uninstalled 12.1, re-booted, installed 12.2, re-booted and got a no usable GPU found message. Upgraded to BOINC 7.0.20 : still the same.

After falling back to ATI 12.1 BOINC detected my GPU as it used to.

I'm running a single HD 5850 with Win XP 32.
3) Message boards : Number crunching : CPU app only - minor issue with checkpointing (Message 2180)
Posted 10 Jan 2012 by Senilix
Post:
I just noticed that every CPU-WU that is restarting from a checkpoint ends up with being marked as invalid - but granting some credits nonetheless.

Example

It looks like during the checkpoint 1 out of the 9 packets a CPU-WU consists of is lost. The WU is marked as invalid, but after been crunched by a wingman credit is granted for 8 packets.
4) Message boards : Number crunching : Validator Down ? (Message 2016)
Posted 31 Dec 2011 by Senilix
Post:
My work is getting validated, but very slowly and with 15% less credit. So it looks like Teemu is reducing credit step by step to the level before Santa's credit raise.
5) Message boards : Number crunching : Credits (Message 1980)
Posted 29 Dec 2011 by Senilix
Post:
Teemu decreased the base credit level from 9 to 8, I think, so we all are getting less credit than during the last 'Santa' days. But as far as I see work is still double credited, with a 20% extra for heavily fragmented units.
6) Message boards : Number crunching : ATI 12.1 - Preview (Message 1953)
Posted 28 Dec 2011 by Senilix
Post:
Good news for all ATI crunchers having problems with CPU hogging since driver version 11.6 (like myself):

I just installed the preview driver version of 12.1 (download link http://support.amd.com/us/kbarticles/Pages/Catalyst121Previewdriver.aspx) and guess what? CPU usage for Moo! was back below 0.1%!

So let's hope that this fix finds its way into the final release of 12.1.

7) Message boards : News : Happy Holidays! (Message 1897)
Posted 24 Dec 2011 by Senilix
Post:
TYVM Santa (with tears in my eyes)
8) Message boards : Number crunching : Faulty WUs (Message 1863)
Posted 22 Dec 2011 by Senilix
Post:
Same here ... am running v11.6 on a 5850 over/underclocked to 775/200 with CPU usage less than 1%.
I've tried v11.7 to v11.9 but all 3 versions consume a full CPU core.

Rumours say that v12.1 will cure the CPU usage problem but it's not released yet.
9) Message boards : Number crunching : Faulty WUs (Message 1737)
Posted 15 Dec 2011 by Senilix
Post:
Actually, it looks like Teemu is already working on a solution as I'm not getting any new GPU work: 
15.12.2011 01:25:05 | Moo! Wrapper | Requesting new tasks for ATI GPU
15.12.2011 01:25:07 | Moo! Wrapper | Scheduler request completed: got 0 new tasks
15.12.2011 01:25:07 | Moo! Wrapper | No tasks sent

Server Status page is showing plenty of available tasks but they seem to be CPU only...
10) Message boards : Number crunching : Faulty WUs (Message 1735)
Posted 15 Dec 2011 by Senilix
Post:
I'm now playing with a manual fix for that issue:

1. Request a cache of 1 day of Moo WUs.
2. Shutdown BOINC after all WUs have been downloaded.
3. Manually edit the file 'client_state.xml' and replace the line
<max_nbytes>51200.000000</max_nbytes>

by
<max_nbytes>61200.000000</max_nbytes>

for every Moo! <file_info> section in that file.
4. Restart BOINC.

I'm quite confident that this will fix the issue but of course only time will tell if it really does...
11) Message boards : Number crunching : Faulty WUs (Message 1733)
Posted 14 Dec 2011 by Senilix
Post:
Darn! 3 out of my last 5 WUs ended with error_code -131.

I'm putting the project to 'no new work' now ...
12) Message boards : Number crunching : Calculation errors (Message 1721)
Posted 14 Dec 2011 by Senilix
Post:
The header of your stderr file is okay. The reason for the calculation error is showing in the last lines of the file : err_code -131.

See this thread for further details.

Not much you can do atm. We all are waiting for Teemu to fix the issue.
13) Message boards : Number crunching : Faulty WUs (Message 1684)
Posted 12 Dec 2011 by Senilix
Post:
I was experiencing a couple of computation errors on my rig during the last two days. As all of my wingmen are getting the same error, there seems to be something wrong with the corresponding WUs. Here's some examples:
http://moowrap.net/workunit.php?wuid=4382462
http://moowrap.net/workunit.php?wuid=4440517
http://moowrap.net/workunit.php?wuid=4415816
All are showing the same error code:
</stderr_txt>
<message>
upload failure: <file_xfer_error>
  <file_name>dnetc_r72_1323456479_401_768_2_0</file_name>
  <error_code>-131</error_code>
</file_xfer_error>

</message>
14) Message boards : Number crunching : Huge WUs crunching time on an HD5850 (Message 1158)
Posted 6 Oct 2011 by Senilix
Post:
My HD5850 is OC'd to GPU 855MHz / Mem 1180MHz
Another thing I forgot to mention is the ATI/AMD's CAL version
I found with Win 32 bit anything over CAL 11.5 runs at a very high CPU (25%) where it should run at only 2%
I use CAL 11.4 on all my PCs
This happens only here at Moo!
DNETC is OK with the later CAL releases

Keep in mind WU size vary - look at the last 5 digets of the WU name


If you are running only Moo! on that HD5850 then you should consider downclocking the mem speed as Moo! doesn't depend on a high memory bandwidth. Downclocking mem speed to e.g. 500 or even 300 MHz will keep your card much cooler without impact on your RAC.
15) Message boards : Number crunching : AMD 11.7 - Observations and Issues (Message 967)
Posted 1 Sep 2011 by Senilix
Post:
I can confirm that downgrading to 11.6 solved the issue for me.
16) Message boards : Number crunching : AMD 11.8 - Observations and Issues (Message 917)
Posted 20 Aug 2011 by Senilix
Post:
There is a massive issue with 11.8 and Moo! WUs.

see http://moowrap.net/forum_thread.php?id=100
17) Message boards : Number crunching : AMD 11.7 - Observations and Issues (Message 913)
Posted 18 Aug 2011 by Senilix
Post:
The 5850 WU results reacted to the change. The CPU time(secs) now shows nearly the same as the GPU time(secs). Markedly different from showing (presumeably) the actual CPU time used when under 11.6. Thats a significant change as such, and for some reason the reporting mechanism for the WU reports differently under 11.7 than under 11.6.


I experienced the same with my 5850 when I switched from 11.6 to 11.8. But the bad thing is that Windows' task manager is showing each WU is really consuming this increased CPU time. So with the actual driver version every Moo! WU is consuming 1 GPU and 1 CPU - in contrast to the 0.05 CPU indicated by BOINC.

That's an issue for me because on my dual core every CPU WU is now running twice as long as before the driver change.

So it's back to 11.6 ...
18) Questions and Answers : Windows : Does memory speed matter? (Message 596)
Posted 4 Jun 2011 by Senilix
Post:
Thank you very much Zy, it's working like a charm. Temp dropped another 2-3° C, fan ditto :)
19) Questions and Answers : Windows : Does memory speed matter? (Message 591)
Posted 4 Jun 2011 by Senilix
Post:
May well be able to do this with NVidia, dont know, but if you are AMD, you can access the configuration file for the card (works for 58XX and 5970, no idea about the others). The limitation is purely the software for CC, the card is easily capable of setting the memory lower, there is no hardware limitation in that regard. I run my 5970s at 300 here. Afterburner sometimes lets you go that low, but its a pain and most times doesnt play.

If you want to give it a go, shout, happy to post directions for it, easily done - I dont want to post screen shots et al on spec.

Regards
Zy


I'd be very interested in instructions how to down clock mem speed for my 5850. Am now using 500 MHz - the lowest CCC allows - but would give 300 MHz a go to see how it affects temp, fan speed and noise.
20) Questions and Answers : Windows : Error while computing ALL THE TIME (Message 497)
Posted 27 May 2011 by Senilix
Post:
Looks like the CPU app is crashing too, so his issue might not be GPU related.


Next 20


 
Copyright © 2011-2024 Moo! Wrapper Project