Welcome to MilkyWay@home

ATI GPU app 0.19f on Vista ulimate 64 + 4870 x2

Message boards : Number crunching : ATI GPU app 0.19f on Vista ulimate 64 + 4870 x2
Message board moderation

To post messages, you must log in.

1 · 2 · 3 · Next

AuthorMessage
Ross*

Send message
Joined: 17 May 09
Posts: 22
Credit: 161,135,083
RAC: 0
Message 26622 - Posted: 28 Jun 2009, 2:44:42 UTC

ATI GPU app 0.19f on Vista ulimate 64 + 4870 x2
I am using a i7 920 with the above
done all the usual things to get 0.19f going.
still no luck
rollback drivers 9.6 to 9.5 still no joy
anyone out there that is using Vista and is cruching MWs succesfully?
can some one suggest some fixs?
Ross
ID: 26622 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Divide Overflow
Avatar

Send message
Joined: 16 Feb 09
Posts: 109
Credit: 11,089,510
RAC: 0
Message 26623 - Posted: 28 Jun 2009, 2:56:52 UTC - in response to Message 26622.  

Catalyst 9.6 doesn't work well for crunching here. For Vista or Windows 7, 9.5 should work OK. Have you done your due diligence by recreating all the .dll files in your System32 folder?
ID: 26623 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile JerWA

Send message
Joined: 22 Jun 09
Posts: 52
Credit: 74,110,876
RAC: 0
Message 26624 - Posted: 28 Jun 2009, 2:57:25 UTC
Last modified: 28 Jun 2009, 2:58:06 UTC

If that's the 920 listed under your computers it's running the CPU app still it looks like.

Make sure to stop the BOINC manager (and all apps) completely, exit, then extract the GPU app in the folder for Milky Way (lemme know if you need help finding it). If you've done everything else and it's not even trying to run the app then it's likely you're not exiting all the way (especially in protected mode, where you may have to stop the service manually).

Did you copy the DLLs in System32 like the readme says?

If you're running in protected mode that causes problems too. I had to reinstall the manager w/o protected mode and then force-run it as administrator to get it running on mine. But even without that it was trying to run the GPU app at least, just failing to. Your tasks, on the other hand, don't look like they're coming through the GPU app at all.
ID: 26624 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Ross*

Send message
Joined: 17 May 09
Posts: 22
Credit: 161,135,083
RAC: 0
Message 26625 - Posted: 28 Jun 2009, 3:15:11 UTC - in response to Message 26624.  

I think I have done everything right .
closed B Manger , manualy turned off application on icon bar bottom right.
do not know about protcted mode , only see that when i installed Bonic. how do I find that out now ?
when app 0.19f runs get black box with cusor blinking for a couple of seconds. is this normal?
could reinstall Bonic and make certain it is not in protected mode??
thanks for the tips
Ross
ID: 26625 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Ross*

Send message
Joined: 17 May 09
Posts: 22
Credit: 161,135,083
RAC: 0
Message 26626 - Posted: 28 Jun 2009, 3:17:45 UTC - in response to Message 26623.  

Yes there all there
will try 9.5 drivers again as control centre still says 9.6 !
ROSS
ID: 26626 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile JerWA

Send message
Joined: 22 Jun 09
Posts: 52
Credit: 74,110,876
RAC: 0
Message 26627 - Posted: 28 Jun 2009, 3:28:21 UTC

The easiest way I know to check for protected mode is to open the Services msc (Start, Control Panel, Administrative Tools, Services or Start->Run->Services.msc) and look for BOINC. If it's there, that's protected mode.

The only way I know of to switch is to uninstall and reinstall, but you don't lose anything (projects or tasks) doing so. I've switched versions several times trying to get the MW GPU app to run happily with everything else.

You may also run into a lot of scheduler issues with 6.6.36, I did at least. So far I'm having the best luck with 6.4.7 but even that's pretty touchy (having to do a lot to keep it running predictably).

I did read from someone else on the forum here that the app should work with 9.6, it just crashes the video driver a lot. I don't think you're getting that far, the tasks reports don't show any output in stderr and it should.

As for the black box that's definitely not happening on mine. Are you putting the x86 or x64 app in?
ID: 26627 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Ross*

Send message
Joined: 17 May 09
Posts: 22
Credit: 161,135,083
RAC: 0
Message 26628 - Posted: 28 Jun 2009, 7:40:52 UTC - in response to Message 26627.  

finally it is going
most WUs take 2 to 3 mins, up to 10 WUs running at one time.
problem will be the server keeping up
Thanks for your help
Ross
ID: 26628 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile JerWA

Send message
Joined: 22 Jun 09
Posts: 52
Credit: 74,110,876
RAC: 0
Message 26630 - Posted: 28 Jun 2009, 7:51:22 UTC

Actually depending on how many "normal" (i.e. CPU apps) projects you're running you'll probably have more issues keeping the scheduler running right than getting work from the server.

See my thread about tripping MW cycles for more info on all the stuff I've been doing trying to keep mine going. Can't wait for the manager to play nice with GPU apps that aren't CUDA based.
ID: 26630 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Ross*

Send message
Joined: 17 May 09
Posts: 22
Credit: 161,135,083
RAC: 0
Message 26631 - Posted: 28 Jun 2009, 8:05:23 UTC - in response to Message 26630.  

only running WCG on this computer as well
only getting 1 or 2 WUs at a time and they get dealt to in less than 2 mins
What are the best prefences to get the best feed from the sever?
Ross
ID: 26631 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile JerWA

Send message
Joined: 22 Jun 09
Posts: 52
Credit: 74,110,876
RAC: 0
Message 26633 - Posted: 28 Jun 2009, 8:30:38 UTC
Last modified: 28 Jun 2009, 8:31:02 UTC

I've had to weight the project (200 vs 100 for everything else), set connect every to 0, queue 2 days worth, AND setup an automated task to reset project debt every hour or it stops getting work.

How much it downloads each time seems to be based on debt and predicted run-times. As both go totally haywire seemingly at random (most WUs finish under 90 seconds for me, but every once in awhile I'll check and they're all predicting 10 minutes or something similarly outrageous) it's hard to keep it running smoothly. Likewise, even when properly predicting the 1:00-1:30 time-to-finish "2 days" of queued work for the project is never more than 20 WUs, or just about 30 minutes. Go figure.

Mine right now is usually doing a cycle something like this:
20 WUs Waiting, Complete 4 WUs, report, Download 2 WUs.
16 WUs Waiting, Complete 8 WUs, report, Download 4 WUs.
10 WUs Waiting, Complete 4 WUs, report, Download 2 WUs.
6 WUs Waiting, Complete 2 WUs, report, Download *

Now, depending on when in this cycle my debt reset runs it will either continue to shrink until it runs dry and then it spends the rest of the hour downloading 2 every time 2 finish (not friendly to the server for sure), or it will realize it's outrunning the pace at which it's requesting work and with clear debts will happily reload up to 20 WUs or so.

Unfortunately this is my main system and I use it for other things and suspend applications every now and then. Once you do that all bets are off, the managers response has yet to be predictable. Sometimes it comes back fine and everything goes back to what it was doing, sometimes the MW app gets stuck in a wait loop (i.e. they say running but aren't getting any GPU time) and I have to restart the manager.
ID: 26633 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Ross*

Send message
Joined: 17 May 09
Posts: 22
Credit: 161,135,083
RAC: 0
Message 26636 - Posted: 28 Jun 2009, 11:09:52 UTC - in response to Message 26633.  

getting 10 to 12 WUs every 15 mins now
how do you allocate 1 core to MW so only 2 WUs get done at a time?
they then get done in less than 2 mins and reduces temp GPU and CPU
I have had to slow GPU down as was getting over heated.
Ross
ID: 26636 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Ross*

Send message
Joined: 17 May 09
Posts: 22
Credit: 161,135,083
RAC: 0
Message 26639 - Posted: 28 Jun 2009, 11:38:04 UTC - in response to Message 26633.  

further on
suspended WCG, immeditly got 50 WUs
CPU limit is 2 active but 21 are running time
will resume WCG and see what happens
Ross
ID: 26639 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile JerWA

Send message
Joined: 22 Jun 09
Posts: 52
Credit: 74,110,876
RAC: 0
Message 26642 - Posted: 28 Jun 2009, 12:14:12 UTC

You can tweak the GPU app in the folder you extracted it to by editing the app_info.xml file, in between the <cmdline></cmdline> tags.

n# is the max # of units (per GPU) actually getting GPU time at once. It's default value is 3. You will see lots marked "Running" but only this many should actually be running. 6.6.36 is bugged in that all of them marked running are counting time even when not getting any GPU time (did for me anyways). This was actually fixed in .19f but 6.6.36 seems to have unfixed it for them.

I run n2, and will show up to 3 "Running," and will sometimes only have 1 Running real or otherwise, but never more than 2 actually getting GPU time. Your 4870X2 counts as 2 GPUs (from your task logs: Found 2 CAL devices), so it should be running 6 at once which should be ok on a 2GB card which yours is (also from the task logs: Device 0: ATI Radeon HD 4800 (RV770) 1024 MB local RAM, and the other device also shows 1024).

w# sets the wait time on the CPU thread between GPU WUs. In effect it's the app trying to be nice and not tie up the CPU while doing GPU work. Default is 1.0. If you see too little GPU load decrease this. If you see too much CPU load increase it. In your case if you're intentionally trying to slow it down a bit you could try increasing this very slowly (i.e. add w1.1 and let it run awhile to see if that unloads the GPUs any).

x# excludes a GPU from processing entirely. They start at 0, so yours are 0 and 1. While this could be used to drop all load from one of the GPUs I'd actually recommend against it if you're trying to control heat because this will push all load onto just one GPU, localizing heat and not the whole card so the fan profiles would probably not spin up as much, leading to more heat, etc. You'd probably be better off dropping the n# and increasing the w# so that both cores are loaded relatively evenly, just less than 100%.

I'm a newbie here, so hopefully someone with more in-depth tweaking experience will chime in, but I'd think a safe place to start would be...

<cmdline>n1 w1.1</cmdline>

Then let it run awhile and see what that does. On my 4870 n1 gets me 75-85% load, may be lower on yours (Control Center will tell you), and the slightly increased wait should slow it down a bit too. With my fan locked at 55% my load temps are below my stock idle temps. You may want to bounce your fans up too if you haven't, as this whole family of cards is notorious for running hot (within design spec but way too high for me to be happy). 55% is a bit extreme, and very loud (it's audible over my 133cfm 3k RPM 120mm CPU and exhaust fans), but on my card 40% was quite livable and dropped temps over 20C.

For any change to the app_info.xml file you'll need to stop BOINC and exit it completely, make your change, then start BOINC back up.

If you don't have one already I'd highly recommend an app to monitor temps. GPU-Z works well with 9.5 (http://www.techpowerup.com/gpuz) but makes my system very cranky (long GPU pauses) while actually running so it's kind've open it, check temps and load, and close it. I also use the Everest Ultimate Vista sidebar app to monitor temps (CPU, MB, Case and GPU) which doesn't cause the same issue as GPU-Z.

Hope this helps, I'm still learning it all myself. :-)
ID: 26642 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Ross*

Send message
Joined: 17 May 09
Posts: 22
Credit: 161,135,083
RAC: 0
Message 26690 - Posted: 29 Jun 2009, 9:58:02 UTC - in response to Message 26642.  

Well just over a day and 60k cridts later
only problem is when more than 6 WUs run @ a time They count as going but don't
I am getting 50 at a time now so thats not a problem.
some time the system does go haywire and WUs have to be suspended
once i have used up all these WCG WUS i may go to climate predication , rn 7 threads and leave 1 thread to do MWs
will try editing that file if i get into trouble. will try to restrict to ^ WUs at a time
Ross
ID: 26690 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
STE\/E

Send message
Joined: 29 Aug 07
Posts: 486
Credit: 576,523,040
RAC: 34,701
Message 26696 - Posted: 29 Jun 2009, 19:27:09 UTC
Last modified: 29 Jun 2009, 20:12:50 UTC

I have the same problems Ross & the settings KWSN - JerWA pointed out do absolutely nothing to improve my 4870 Cards into running the Wu's like they should, at times they seem to do everything but run the Wu's. That's not to say his Settings don't work but they don't work on any of my Box's. That waiting to run State drives me nut's, just what the heck are they waiting for when none of the available MWay Wu's are running ???

Persistent Problems with the ATI 4870 (Single Core) Cards I have using the .19f Application:

1. They have no work & ain't even calling for work.
2. They have no work but are calling for work but ain't getting any.
3. Their waiting to run the work they have on board.
4. Their waiting to run the work they have already started but now are waiting again.
5. Their in a Hung State, not waiting & not running the Wu's that are shown as running & with a % of the Wu done already.
6. VPU Recovery has kicked out the Video Card until you Reboot, this can happen at any setting, even slightly under clocked settings.

PS: Right now my i7 with 2 Single Core 4870's has 48 MWay Wu's on it, 1 Wu is running, it was running 6 which it should do but then all of a sudden just decided to run only 1 & that's what it's been doing for the last 15 minutes.
ID: 26696 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Simplex0
Avatar

Send message
Joined: 11 Nov 07
Posts: 232
Credit: 178,229,009
RAC: 0
Message 26700 - Posted: 29 Jun 2009, 20:27:43 UTC

I have the same problem as you PoorBoy but on my
i7\4870 box the whole computer stop running and I have to reboot
to regain contol.

This happend even when I under clock my 4870 card to 500\700 and
have the side open on my box so the problem should not be heat related.

I wonder if it is caused by some of the wu's or if BOINC is the
caus of the problem.
ID: 26700 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Ross*

Send message
Joined: 17 May 09
Posts: 22
Credit: 161,135,083
RAC: 0
Message 26721 - Posted: 30 Jun 2009, 1:54:07 UTC - in response to Message 26700.  

I have the same problem as you PoorBoy but on my
i7\4870 box the whole computer stop running and I have to reboot
to regain contol.

This happend even when I under clock my 4870 card to 500\700 and
have the side open on my box so the problem should not be heat related.

I wonder if it is caused by some of the wu's or if BOINC is the
caus of the problem.


I have come to the conclusion that it does't mater how running but not running happens.
Exiting BIOMIC Manger will stop the counting but not fix the problem.
I still have 5 WUs going and about 20 counting.
Don't know if it ties up resources!
Hope some smart programmer some where can suggest a solution
I find that if I only run MW apps the system overloads and progreess of WUs grind down.
If I could make the software only take on 5 WUs at a time it would be great . All done in 2 mins , then move on to the next 5
looking seriously into doing Climate predication on 7 threads leaving 1 thread to do 5 MW WUs at a time
apart from that no crashes of system but I do Reboot eery day .
i7 920 oc to 3.4 6 gig of 1600 dr3 Ram and 2 300 GIG Raptors in raid 0 plus
1 Terbit back up
Ross
ID: 26721 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
STE\/E

Send message
Joined: 29 Aug 07
Posts: 486
Credit: 576,523,040
RAC: 34,701
Message 26722 - Posted: 30 Jun 2009, 2:02:54 UTC

It's a combination of the Application, the Wu itself & the BOINC Client all not wanting to Play nice with each other ...
ID: 26722 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile JerWA

Send message
Joined: 22 Jun 09
Posts: 52
Credit: 74,110,876
RAC: 0
Message 26750 - Posted: 30 Jun 2009, 14:16:45 UTC

PoorBoy you're running 6.5.0, which I haven't tested. The settings I'm using are all for 6.4.7. Have you tried that manager yet?
ID: 26750 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
STE\/E

Send message
Joined: 29 Aug 07
Posts: 486
Credit: 576,523,040
RAC: 34,701
Message 26752 - Posted: 30 Jun 2009, 14:57:11 UTC

I'm trying the 6.4.7 on a couple of Box's now to see how it works for me ...
ID: 26752 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
1 · 2 · 3 · Next

Message boards : Number crunching : ATI GPU app 0.19f on Vista ulimate 64 + 4870 x2

©2024 Astroinformatics Group