Welcome to MilkyWay@home

Posts by nanoprobe

1) Message boards : Number crunching : R9 285 (Message 64205)
Posted 30 Dec 2015 by nanoprobe
Post:
NM: Figured out it needed an app_info.xml to run. Crunching away.
2) Message boards : Number crunching : R9 285 (Message 64204)
Posted 30 Dec 2015 by nanoprobe
Post:
Just received an R9 285 as an RMA replacement for an R9 270X. For some reason I can't get any tasks for it from MW. Runs POEM fine and my 7970 receives work. Is this card somehow not supported at MW? It does have DP capabilities. Log says:

29966 Milkyway@Home 12/30/2015 3:25:40 PM Sending scheduler request: To fetch work.
29967 Milkyway@Home 12/30/2015 3:25:40 PM Requesting new tasks for AMD/ATI GPU
29968 Milkyway@Home 12/30/2015 3:25:41 PM Scheduler request completed: got 0 new tasks
3) Message boards : Number crunching : Linux Has Massively Superior AMD OpenCL Performance to Windows (Message 60260)
Posted 31 Oct 2013 by nanoprobe
Post:
Can someone post step by step instructions for installing ATI drivers in Linux Mint 13 64 bit. I've just started giving Linux a try and can't seem to get this driver thing going. Thanks! (I'm sure a face palm is coming)
4) Message boards : Number crunching : tasks (Message 60232)
Posted 27 Oct 2013 by nanoprobe
Post:
Are there no more de_separation_09_2s_sSgrFree_1, de_separation_10_2s_sSgrFree_1 tasks left to send out?
5) Message boards : News : New Separation Runs Started (Message 57453)
Posted 8 Mar 2013 by nanoprobe
Post:
Yesterday everything ran fine. Today I can't get any tasks. Get this error message. Tried detaching and reattaching, same error.

3/8/2013 5:00:51 PM | Milkyway@Home | Sending scheduler request: Requested by user.
3/8/2013 5:00:51 PM | Milkyway@Home | Requesting new tasks for ATI
3/8/2013 5:00:52 PM | Milkyway@Home | [error] Can't parse workunit in scheduler reply: unexpected XML tag or syntax
3/8/2013 5:00:52 PM | Milkyway@Home | [error] No close tag in scheduler reply

I found the problem. It's with the latest BOINC client 7.0.54. Went back to 7.0.52 and all is working again.
6) Message boards : Cafe MilkyWay : TLPTPW #14 (Message 55464)
Posted 3 Sep 2012 by nanoprobe
Post:
I'm winning again!


You were but now I AM!!! NOT

FTW
7) Message boards : Number crunching : Throttling GPU performance (Message 55162)
Posted 17 Jul 2012 by nanoprobe
Post:
There are many threads here that GPUs are not getting enough work. Well I have kind of the opposite problem.
Up to now I have used my HD4850 to crunch Moo, the card's fan would rev to about 10k rpm, which I cannot hear too much (or I've gotten used to), temp to 90°C.
I actived GPU on MW recently, and now the fan has to spin to 14k rpm to maintain 108°C. In both cases the GPU load is reported to 100%, so I guess MW is using more of it.
Now I can clearly hear the fan, the case's fans have to blow more air too, so it's all quite noisy when MW runs. I am a little worried of the temp level too.

-> Is it possible to throttle down the GPU calculations?
Not cycling, that kind of noise is even worse.

I use an app_info file to throttle back my GPU when running MW. I'm at work now but I'll post it for you when I get home this evening. And FWIW I agree with Link. Running your card @ 100+ will probably kill it quickly
8) Message boards : Cafe MilkyWay : TLPTPW #11 (Message 54818)
Posted 18 Jun 2012 by nanoprobe
Post:
I'm gonna miss FS.

FTW


What or who is FS?

WINNING!!!


I wonder that also.

Winning in free field!

BladeD knows. :-)

FTW

9) Message boards : Cafe MilkyWay : TLPTPW #11 (Message 54800)
Posted 17 Jun 2012 by nanoprobe
Post:
I'm gonna miss FS.

FTW
10) Message boards : News : testing work generation with 'ps_separation_14_2s_null_3' (Message 54798)
Posted 16 Jun 2012 by nanoprobe
Post:
Here is what i was referring to with the wattage fluctuations on 1.02 app. Is this normal and if so why?

11) Message boards : News : testing work generation with 'ps_separation_14_2s_null_3' (Message 54791)
Posted 16 Jun 2012 by nanoprobe
Post:
I've been trying to get some new tasks for my XP 32 bit machine without success. Here's the message log.

6/16/2012 10:03:38 AM | Milkyway@Home | work fetch resumed by user
6/16/2012 10:03:40 AM | Milkyway@Home | update requested by user
6/16/2012 10:03:45 AM | Milkyway@Home | Sending scheduler request: Requested by user.
6/16/2012 10:03:45 AM | Milkyway@Home | Not reporting or requesting tasks
6/16/2012 10:03:46 AM | Milkyway@Home | Scheduler request completed

Tried a reset, didn't help.

NM: Got it working.
FWIW I still find that the 1.02 app causes my kill-a-watt meter to fluctuate by as much as 60 watts on 64 bit and 25 watts on 32 bit while I never noticed the 0.82 app fluctuate by more than 5 watts.
12) Message boards : News : testing work generation with 'ps_separation_14_2s_null_3' (Message 54788)
Posted 15 Jun 2012 by nanoprobe
Post:
I just tried a couple of WU on a 5870 I acquired. Both ran to 100% and then went computation error. New/old problem again?

Are you still using the v0.82 CAL app? The current WUs seem to be incompatible with it on 64-bit systems, but your GPU is OpenCL capable, so you could try that.

I've stuck with the 0.82 because the later ones caused the GPU usage and power draw to be all over the place which I was not comfortable with. Even with an app_info to try and control GPU% didn't help. I may try the later app but I hope they can solve this 64 bit issue.
13) Message boards : News : testing work generation with 'ps_separation_14_2s_null_3' (Message 54785)
Posted 15 Jun 2012 by nanoprobe
Post:
I just tried a couple of WU on a 5870 I acquired. Both ran to 100% and then went computation error. New/old problem again?
14) Message boards : Number crunching : HD5450 not recognized with double precision (Message 53507)
Posted 1 Mar 2012 by nanoprobe
Post:
I don't think the 5450 is double precision. 58xx is the first DP card in the 5000 series.
15) Message boards : Cafe MilkyWay : TLPTPW #9 (Message 53277)
Posted 18 Feb 2012 by nanoprobe
Post:
FTW backwards=***
16) Message boards : Number crunching : Buy AMD Bulldozer or Intel Sandy Bridge for crunching BOINC? (Message 53242)
Posted 17 Feb 2012 by nanoprobe
Post:
Good choice IMHO. Not only is Bulldozer slower, its' power draw is considerably higher.
17) Message boards : Number crunching : HIGH CPU USAGE with new 1.02 OpenCL tasks (Message 53241)
Posted 17 Feb 2012 by nanoprobe
Post:
FWIW I had issues with 1.02 on all 3 of my 5830s on 3 different machines. I had to switch back to .82 to get things running smoothly again. I'm not currently running M@H so I don't know if the .82 app will still work. If it doesn't then I will not be able to run M@H on my current hardware.
18) Message boards : Cafe MilkyWay : TLPTPW #9 (Message 53228)
Posted 17 Feb 2012 by nanoprobe
Post:
GNINNIW
19) Message boards : Cafe MilkyWay : TLPTPW #9 (Message 53163)
Posted 14 Feb 2012 by nanoprobe
Post:
Win...

Have I?

Nope, but maybe I have.


Oh so close but no cigar! Please keep playing as the game continues!

Next.
20) Message boards : News : Separation updated to 1.00 (Message 53107)
Posted 12 Feb 2012 by nanoprobe
Post:
What command would be added to the the app-info file to throttle back GPU usage? It's currently at 99% and I'd like to pull it back to 80-85%.
Win7 64 bit. Radeon 5830.


With the new app you don't need the app_info-file to control GPU load - it's now only necessary if you want to run multiple instances on one GPU. If you want to use it anyway the command line parameter apparently wasn't changed from the old app:
--gpu-target-frequency XX

Raising XX lessens the GPU load and increases the run time (default is now 60).

With the new app it's easier controlled in the Milkyway@home preferences: Frequency (in Hz) that should try to complete individual work chunks

For some reason the frequency setting in the M@H preferences is ignored. The GPU runs @ 99% no matter what the setting. I tried a target frequency in the app-info file with separation 1.02 and it caused the GPU frequency and power draw to be all over the place. Had to switch back to 0.82 to get things running smoothly again. Only thing I can figure is it must be some kind of a hardware thing on my setup.


Next 20

©2024 Astroinformatics Group