- Joined
- Apr 1, 2002
Well, since there appears to be very little info around concerning multi-GPU folding I thought I'd share my experience.
The official FAQ is here: http://folding.stanford.edu/FAQ-ATI.html
This will be tailored towards ATi cards, as there is currently no nV GPU client available.
[#1]
First you'll need at least two cards (or one card with two GPUs). I have two Sapphire x1950pros, with 512MB each. I'm running them on a P5WD2-P, one at 16x and one at 4x. The X1950pros have internal Crossfire connectors, much like nV's SLI ribbon cables. You don't really have to connect the cables as FaH doesn't work in Crossfire mode, but if you want to use Crossfire for games you can leave them connected full time and just toggle Crossfire on & off using the ATi control panel.
When installing the cards I'd suggest:
- If replacing an older card remove all previous drivers and reboot (Windows should load in standard VGA mode)
- Shut down computer
- Install one card (don't forget power plug), restart, and let windows detect it (but don't install any drivers)
- Shut down computer and install 2nd card, restart, and let windows detect it
- Install latest ATi drivers (and restart)
You should now have four display adapters listed under Device Manager. If you don't try moving your screen plug (DVI/VGA) to the other card to force Windows to detect it. You can also use the "Detect Displays" button on the "Display Manager" page of ATi's CCC.
[#2]
On your hard drive make two folders - I call mine FaH1 and FaH2.
[#3]
Now you'll need to download the FaH GPU client (console version).
http://folding.stanford.edu/download.html
[#4]
Place a copy of the downloaded client into each folder that you just made.
[#5]
Open a command prompt and change to the first folder you made (ie: cd\FaH1).
Type "FAH5.91beta3-console.exe -local -configonly"
(without the quotes)
Note that the executable name will change as the client is updated over time. Just type "dir" if you can't remember what you saved it as.
Go through the configuration questions (team 32 )
[#6]
Change to the 2nd folder (ie: cd\FaH2) and do the same thing to set up the second client. Remember to use a different machine ID when it asks.
You can close the command prompt when you are done.
[#7]
Browse to the first folder (FaH1) using Windows Explorer.
Create a shortcut to the executable (FAH5.91beta3-console.exe or whatever). Rename the shortcut to "GPU0" for simplicity. Alt-click on the shortcut and go into the properties. On the "Shortcut" tab, in the "Target:" field, you want to add "- gpu 0 -local" (without quotes) after the executable file name. It should look something like: FAH5.91beta3-console.exe -gpu 0 -local
This will force the client to use GPU 0, and the local configuration file.
[#8]
Try launching the shortcut. FaH should run. If it exits and gives you an error about not finding the GPU then change the "- gpu 0" option in the shortcut properties to "-gpu 1". If that doesn't work try 2...
Windows labeled my first GPU #0, and I think it should for everybody.
When you get it working leave it running for now.
[#9]
Now browse to your other FaH folder (FaH2) and create a shortcut just like we did for FaH1. Rename it to "GPU1". Now the "-gpu" option needs to be different then it was for FaH1. If -gpu 0 worked for the first one try -gpu 1, then 2, then 3. Don't foget the -local part.
Since you will only have four GPU outputs (two primary, two secondary) you're just trying to figure out what IDs Windows gave to the two primaries. Unless you have more then two cards (or onboard). Then you'll have more.
Mine were #0 and #1.
If you get a Machine ID error then you probably didn't set a different machine ID in step #6.
[#10]
Now you should have two clients working
The official FAQ is here: http://folding.stanford.edu/FAQ-ATI.html
This will be tailored towards ATi cards, as there is currently no nV GPU client available.
[#1]
First you'll need at least two cards (or one card with two GPUs). I have two Sapphire x1950pros, with 512MB each. I'm running them on a P5WD2-P, one at 16x and one at 4x. The X1950pros have internal Crossfire connectors, much like nV's SLI ribbon cables. You don't really have to connect the cables as FaH doesn't work in Crossfire mode, but if you want to use Crossfire for games you can leave them connected full time and just toggle Crossfire on & off using the ATi control panel.
When installing the cards I'd suggest:
- If replacing an older card remove all previous drivers and reboot (Windows should load in standard VGA mode)
- Shut down computer
- Install one card (don't forget power plug), restart, and let windows detect it (but don't install any drivers)
- Shut down computer and install 2nd card, restart, and let windows detect it
- Install latest ATi drivers (and restart)
You should now have four display adapters listed under Device Manager. If you don't try moving your screen plug (DVI/VGA) to the other card to force Windows to detect it. You can also use the "Detect Displays" button on the "Display Manager" page of ATi's CCC.
[#2]
On your hard drive make two folders - I call mine FaH1 and FaH2.
[#3]
Now you'll need to download the FaH GPU client (console version).
http://folding.stanford.edu/download.html
[#4]
Place a copy of the downloaded client into each folder that you just made.
[#5]
Open a command prompt and change to the first folder you made (ie: cd\FaH1).
Type "FAH5.91beta3-console.exe -local -configonly"
(without the quotes)
Note that the executable name will change as the client is updated over time. Just type "dir" if you can't remember what you saved it as.
Go through the configuration questions (team 32 )
[#6]
Change to the 2nd folder (ie: cd\FaH2) and do the same thing to set up the second client. Remember to use a different machine ID when it asks.
You can close the command prompt when you are done.
[#7]
Browse to the first folder (FaH1) using Windows Explorer.
Create a shortcut to the executable (FAH5.91beta3-console.exe or whatever). Rename the shortcut to "GPU0" for simplicity. Alt-click on the shortcut and go into the properties. On the "Shortcut" tab, in the "Target:" field, you want to add "- gpu 0 -local" (without quotes) after the executable file name. It should look something like: FAH5.91beta3-console.exe -gpu 0 -local
This will force the client to use GPU 0, and the local configuration file.
[#8]
Try launching the shortcut. FaH should run. If it exits and gives you an error about not finding the GPU then change the "- gpu 0" option in the shortcut properties to "-gpu 1". If that doesn't work try 2...
Windows labeled my first GPU #0, and I think it should for everybody.
When you get it working leave it running for now.
[#9]
Now browse to your other FaH folder (FaH2) and create a shortcut just like we did for FaH1. Rename it to "GPU1". Now the "-gpu" option needs to be different then it was for FaH1. If -gpu 0 worked for the first one try -gpu 1, then 2, then 3. Don't foget the -local part.
Since you will only have four GPU outputs (two primary, two secondary) you're just trying to figure out what IDs Windows gave to the two primaries. Unless you have more then two cards (or onboard). Then you'll have more.
Mine were #0 and #1.
If you get a Machine ID error then you probably didn't set a different machine ID in step #6.
[#10]
Now you should have two clients working