GPU questions on behalf of Hamoodi

Soldato
Joined
2 Dec 2005
Posts
5,514
Location
Herts
Mr Hamoodi has just started folding on his x1900xt 256 for me, what a gent :)

Anyway, we've got a few questions and could do with tips, things you guys have found useful changing. For example:

Start automatically? Does the service option work nicely now?
Voltage and clocks to use?
Start/stop when gaming?
Edit: It's in a single core machine (a 3200 venice @ 2.8 :eek: :p ) so he can only fold on one or the other right?

Anything other bits of wisdom you can provide? Basically, a run though of the setup process with recommended values.
Cheers guys, fold on. Triple stomp this week... :cool:
 
Last edited:
Service still doesn't work. There is a work-around for it, it might be in the sticky.

Depends what mode you are folding in for voltages. In 2D mode you will want default 2D voltages. In 3D mode you want 3D voltages. If you are using ATi Tray Tools to change modes all the info you need is in Concorde's sticky in the Graphics card forum.

Some games will cause the GPU to stop folding, but not all. You are best turning it off yourself and back on again afterwards! Just don't forget or you could lose hours and hours of folding like I have done on a few occassions. :p

The GPU nicks a whole CPU core, so if it is only single core he can do only GPU OR CPU - not both. Well, he can, but both will take twice as long to crunch which isn't good for the PPD or the science.

My personal recommendation is if it is your own PC then run the GPU client, if not then leave your mate with the CPU client. The GPU client is in Beta still and your mate probably will forget to turn it back on and there aint nothing you can do about it - unless you ring him every hour asking if the GPU client is on :p

SiriusB
 
Joe42 said:
If you can point me in the right direction i can remedy that. :)
On this page: http://folding.stanford.edu/FAQ-ATI.html

Under bugs we have
Running the GPU client as a service is not a problem, you just have to give it desktop privileges. After installing the client as a service, open the service in computer manager, go to the Log On tab, keep it at "Local System account" and check "Allow service to interact with desktop". Then it crunches along just as usual. You probably shouldn't set it to start up automatically, though, since whichever program you use to increase clock speeds will load after the client service. Athough I haven't had any client crashes or EUEs when changing clock speeds on the fly, it's generally not recommended.
 
Do you think its worth putting in the sticky? It suggests theres a chance of getting eues...

The problem is as i don't have a gpu i can fold on i'm not keeping up to date with the gpu folding stuff so the guide doesn't get updated as it should. Better than nothing though i suppose.
 
While the lengthy version of a guide is in producton I've just placed a link to Stanford's GPU FAQ. I expect you could direct your readers to do the same if interested in running as a service.

I have the same problem with not having a FAH-able GPU. I was hoping that when they announced all X1k cards would work my X1300 would able to fold, at least for the production of a guide. It is not. :(

I'm really hesitant to buy something like a whole new rig just for FAH considering how broke I am at the moment and my current Xeon rig (that I built for FAH just last year) with its AGP X850 meets and exceeds all my expectations.
 
I suppose there's no great hurry as its still beta.

Doubt they'll release it for my ati 7000 :p
Its the only ati card i've got.

I'm going to update the quick guide at some point when i get round to it.
 
Code:
[13:57:19] Entering M.D.
[13:57:30] Working on 1258 GPUlambda
[13:57:30] Starting GUI Server
[14:10:12] Completed 1
[14:22:51] Completed 2
[14:25:56] mdrun_gpu returned 50
[14:25:56] GPU was interrupted
[14:25:56] Folding@home Core Shutdown: INTERRUPTED
[14:25:59] CoreStatus = 66 (102)
[14:25:59] + Shutdown requested by user. Exiting.
Folding@Home Client Shutdown.
What does that mean? How do I fix it? :)
Apparently could be a memory issue.
 
Back
Top Bottom