The Folding@Home GPU Thread

[CupCak3]

A new version of the GPU folding@home clients have been released
YOU MUST INSTALL THE NEW VERSION. THE BETA CLIENT IS SET TO EXPIRE ON DEC 1
x1600 and x1800 cards now supported!!!


The dual core client for those w/ dual (or more) pci-e 8x or 16x setups
Download
Configuration

Work units are now 330 points each! The x1900xt running at 2D speeds should now be able to fetch 660 points per day!


I will be updating this thread frequently with updates. The big release is set to be in the afternoon, PST.

Feel free to post any questions or comments you may have.

Hardware Requirements:
1.) ATI Radeon X1600, X1800, and X1900 Series
2.) Just in case you haven't heard, no NVIDIA support at this time. But will be sometime in the future with G80+ cores

Installation
1.) Drivers need to be updated to min 6.10 drivers. 6.10. If have issues with drivers, use DRIVERCLEANER then reinstall drivers.
2.) Install DirectX: 9.0c (4.09.0000.0904) or later. Download
3.) Install the Windows GPU Folding@Home client. Download. Both GUI and console options are available. It looks like better performance will come from the console version. They are currently working on the linux GPU client. No ETA.

Configuration
1.) Follow the on-screen prompts.
2.) Just keep in mind we are team 198
3.) Should not run as a service for now.
4.) Say yes to allowing workunits above 5mb
5.) Adv settings you want CPU usage to low and the next option to 100.
6.) Set the Machine ID to 2 or 3 as to not worry about causing issues with other cores. (if you have them)

Running the Client
1.) You are not "suppose" to run multiple clients with the GPU as of now. If you have a dual core machine you may run one GPU client and one CPU client. Just make sure they have different machine IDs! This can be done during setup or by editing the client.cfg
2.) The PPD on a normally clocked x1900xt look to be around 660 PPD.

Maximizing Performance
Force 3D This looks to be about a 1/3 increase in performance from the defualt settings! <-- Thank to HardOCP for these.
1.) Disable ATI Pooling Service LINK
2.) Force 3D mode with ATITool Download
Maximize Results on a Dual Core System
1.) Install ONE service of the console cpu client
2.) Set to 100% utilization at idle.
3.) Setup the GPU client to use 100% at low priority. Remember, do not install as service for now.

Notes
1.) This project is still in ?beta? but the Pande Group (the ones behind F@H) said everything should run go smoothly; only polishing of the client needs to be done.
2.) Shut down F@H for your GPU before opening any 3D apps. The switch from 3D to 2D mode can crash your machine.

Notes for running

1. The GUI client will slow down the scientific core (since both use the GPU heavily). We do not recommend the GUI client for long term use, unless you have two graphics cards.
2. Multiple GPUs are currently not supported (but will be supported in future releases); Crossfire is also not supported -- Crossfire will make FAH run more slowly than using a single GPU (this isn't a bug as much as a fundamental issue regarding the nature of a Crossfire/SLI type architecture).
3. The GPU client is not meant to be run in the background while one uses the computer for applications with heavy GPU usage -- it will greatly slow down the response of programs which make heavy use of a GPU
4. Do not run multiple GPU clients simultaneously -- there will be a huge (non-linear) slow down in performance. We currently do not support multiple GPU configurations, although a second GPU can help speed up the graphics of the GUI.
5. Client looks like it is using lots of CPU time: Graphics drivers must poll the GPU to see if it is done. This will look like a lot of CPU time being used, but nothing is really being done, so one can run other relatively CPU heavy code at the same time. However, we do not recommend running multiple FAH clients, as this can significantly slow down the GPU client.

Known Bugs

The GUI pause core command doesn't work
The GUI Client will automatically quit when running fullscreen directx apps (games), it may be a little slow at doing this though
In some rare situations, one needs to set the Hardware acceleration to max if the Catalyst install didn't do this. To do this, go into the Display Properties/Settings/Advanced/TroubleShoot tab and double check that the Hardware acceleration was set to "Max".
Known compatibility issues

One must use specific Catalyst drivers (6.5 or 6.10) and a recent DX version-- see the HOW TO above
The GPU core does not run under WINE in linux (nor do we have plans to support WINE)
Notes for running

The GUI client will slow down the scientific core (since both use the GPU heavily). We do not recommend the GUI client for long term use, unless you have two graphics cards.
Multiple GPUs are currently not supported (but will be supported in future releases); Crossfire is also not supported -- Crossfire will make FAH run more slowly than using a single GPU (this isn't a bug as much as a fundamental issue regarding the nature of a Crossfire/SLI type architecture).
The GPU client is not meant to be run in the background while one uses the computer for applications with heavy GPU usage -- it will greatly slow down the response of programs which make heavy use of a GPU
Do not run multiple GPU clients simultaneously -- there will be a huge (non-linear) slow down in performance. We currently do not support multiple GPU configurations, although a second GPU can help speed up the graphics of the GUI.
Client looks like it is using lots of CPU time: Graphics drivers must poll the GPU to see if it is done. This will look like a lot of CPU time being used, but nothing is really being done, so one can run other relatively CPU heavy code at the same time. However, we do not recommend running multiple FAH clients, as this can significantly slow down the GPU client.
Trouble shooting EUE's

Some Alpha testers have found an excessive number of Early Unit End's (EUE's) -- we have not reproduced that at Stanford or ATI and we need help from beta testers to help track this down. If you see many EUE's (i.e. more than 20%), please make a post in the GPU section of the forum with your system configuration (ATI driver version, DX version, OS) and hardware (card, CPU, motherboard type). With the help of beta testers, we hope to nail down what's going on.
If you are seeing lots of EUE's, please download the ATItool application and check that your core voltage is set to 1.4V. This has been shown to lead to problems.
Policy Notes

The client will stop working after 2 months (this is a limited release beta -- new clients will be available before the current version ends its test period)
Deadlines will be set to be much shorter than normal, as we need to get data back quickly in this beta test and we are releasing to a very specific set of hardware. This will likely change in time, as we move from a beta test and as we move towards supporting other graphics cards.

Cards
I only have cards listed that are in stock. If you have found better prices, please let me know!


Overclocking your X1900 Series
Nothing like squeezing out the last bit of juice...

Great Article with lots of good info: Here
Database for overclocking results: Database

Cooling
Not much here yet but I'm tired...

Arctic Cooling Accelero Coolers X1/X2 Link
Zalman VF900 Cu GPU Cooler Link
I may do some looking into lapping the stock heatsink...


Let me know if you would like to see anything else here which could be of benefit to all.

Thank you for not only supporting TeAm AnandTech but also the wonderful science behind Folding@Home!

 

[BobDaMenkey]

I am eagerly awaiting more info on this. My credit card, not so much, but I'm rather enthusastic about it.

 

[sswingle]

Call me when my X800 can do something useful. Sure, I'm not going to get this 40x increase, but why let it go to waste?

 

[caferace]

Thanks for this, CupCak3!

-jim

 

[Dulanic]

No go so far, the downloads for the client just link to the standard 5.02 Console client.

 

[Neurodog]

Thanks for the info.

Can't wait to try it out.

 

[lyssword]

Give me x800 f@h or give me death! (lol jk, but I think x800 should be faster than x1600, right? )

 

[Bateluer]

Originally posted by: lyssword
Give me x800 f@h or give me death! (lol jk, but I think x800 should be faster than x1600, right? )

Dunno, the 1600s have the ringbus memory design don't they?

 

[lyssword]

Originally posted by: Bateluer

Originally posted by: lyssword
Give me x800 f@h or give me death! (lol jk, but I think x800 should be faster than x1600, right? )

Dunno, the 1600s have the ringbus memory design don't they?

yeah but its still only 128bit wide vs 256 on x800.. But I don't know if f@h will work better on it or not, since neither work on it yet..

 

[Kinslayer777]

X1900XT 256 on my new comp list

Well, it was going to be on anyway, but this is 10x cooler now =p

 

[Dulanic]

Originally posted by: Kinslayer777
X1900XT 256 on my new comp list

Well, it was going to be on anyway, but this is 10x cooler now =p

Maybe LOL My X1900XT gets loud if it gets really hot, and this program may do that.

 

[Dulanic]

Its up and I'm running it now, will let ya know.

 

[BobDaMenkey]

Originally posted by: Dulanic
Its up and I'm running it now, will let ya know.

I would imagine it'll get quite hot, it'll probably be pegged at 100% utilization while it's crunching.

 

[Dulanic]

I dont know that this is working right..... the console version is using my CPU.... the GUI version crashes and crap...

 

[apiotrow]

You can download it right now !
http://folding.stanford.edu/release/FAH5.05beta1-console.exe
http://folding.stanford.edu/release/FAH5.05beta1-GUI.exe (GUI)
http://folding.stanford.edu/release/FAH5.05beta1-GUI-ATI.zip (Fancy GUI)

You need Catalyst Beta 6.10 Display Driver for Folding@Home Client
http://support.ati.com/ics/support/KBAnswer.asp?questionID=23354

 

[Dulanic]

Im gonna reinstall the new ATI drivers, this thing has done nothing but crash with the GUI version, and the console version uses my CPU instead.

 

[apiotrow]

You need Catalyst Beta 6.10 Display Driver for Folding@Home Client
http://support.ati.com/ics/support/KBAnswer.asp?questionID=23354

 

[MDE]

Anyone else stuck at "Starting GUI Server" on the CLI version?

EDIT: I'll probably pick up one of these for my X1900XT:
Link

 

[Dulanic]

The GUI client is buggy as hell, I deleted it. The console version seems to be working fine, but it is still using the CPU also which I dislike, I want to use the CPU for R@H not F@H

 

[Bateluer]

I'm having some issues gettng the 6.10s installed, they keep hard locking my system.

Gonna reinstall the Cat 6.9s and try the GPU client after the next version is released. Opinion seems to be that its super buggy at the moment.

 

[Dulanic]

Im very unsure about this so far, it seems it needs both the CPU and GPU at the same time. If I run R@H my GPU temps drop like a rock so it seems it HAS to use both the CPU and GPU. 2nd the GUI version is buggy I gave up on that. 3rd ATITool seems to crash with these new drivers and cause a hard lock so I cant overclock the GPU because the ATI drivers dont recognize it as a 3D application so it only runs at 2D speeds. I will probably let it run for a little while just to see the scores, but then uninstall it until they work out all these bugs.

 

[caferace]

Here is the ATI F@H FAQ, which should help some people get set up...

http://folding.stanford.edu/FAQ-ATI.html

from the FAQ:

Notes for running

1. The GUI client will slow down the scientific core (since both use the GPU heavily). We do not recommend the GUI client for long term use, unless you have two graphics cards.
2. Multiple GPUs are currently not supported (but will be supported in future releases); Crossfire is also not supported -- Crossfire will make FAH run more slowly than using a single GPU (this isn't a bug as much as a fundamental issue regarding the nature of a Crossfire/SLI type architecture).
3. The GPU client is not meant to be run in the background while one uses the computer for applications with heavy GPU usage -- it will greatly slow down the response of programs which make heavy use of a GPU
4. Do not run multiple GPU clients simultaneously -- there will be a huge (non-linear) slow down in performance. We currently do not support multiple GPU configurations, although a second GPU can help speed up the graphics of the GUI.
5. Client looks like it is using lots of CPU time: Graphics drivers must poll the GPU to see if it is done. This will look like a lot of CPU time being used, but nothing is really being done, so one can run other relatively CPU heavy code at the same time. However, we do not recommend running multiple FAH clients, as this can significantly slow down the GPU client.

-jim

 

[CupCak3]

thanks jim! I just added your stuff from teh FAQ onto the op. I'm at work so I haven't really been able to consolidate everything yet. Hopefully in another hour or so I can start getting everything together.

it also looks like drivers b/t 6.5 and 6.10 may work. I've updated the OP.


looks like it may be a long night

 

[MDE]

Looks like you still have to dedicate a CPU (or CPU core) to each copy of F@H, even if you use the GPU client. Oh well, just means I can still run two clients at a time so I can hold off on a RAM upgrade.

 

[Golgatha]

http://forums.anandtech.com/messageview.aspx?catid=40&threadid=1937045

If anyone lives in the KC, Metro area, please grab a $280 X1900XTX while you can.