FrEaKy
[H] Movie and TV Show Review Guy
- Joined
- Jan 31, 2003
- Messages
- 14,113
Things to know before you start attempting to do -bigadv
Some ideas on Bargain builds can be found in this thread.
(A wealth of other FAQ can be found here, written by Kassen)
1) To use -bigadv flag you will need an 8CPU core or better computer.
The cores can be virtual, so running on an i7 or a dual-quad core Xeon/Opteron setup should work.
1b) It is possible to run on a 4 core box, but the CPU must be overclocked to or over 4GHz in order to make the 4 day bonus deadline.
1c) Possible speeds to make it per CPU
2) The bigadv client will need 4.5GB or more ram to run, so a system with 6GB or more is recommended.
3) The client can be run on a 64bit Linux install or through a 8 core VM using VMWare Player 3.0 with 64-bit Windows OS
3b) If your system requires virtualization to be turned on through the bios to use more than 1 core, make sure you do so.
3c) If you plan on running 16 or 32 CPU cores OR MORE, than a 64-bit Linux install will be your only option in doing so, there is no free VM that will run with this many CPU cores at this time.
#note# With 4x 8 core VM's in Windows OS, there is a potential of 45K PpD, 32 cores on a Linux install, possibility of 85k PpD. Bonus calculator
4) In order to do -bigadv a passkey is required.
4b) In order to attain a passkey, please go here
5) You will not see the bonus kick in until after you complete 10 SMP units. (This is for verification purposes from Stanford)
5b) You need to have completed 10 Core A2 based SMP units against your passkey before you can get start getting a bonus. They can be normal SMP units or they can be -bigadv units but they must be recorded against your passkey
5c) You will notice a long pause at the end before the WU uploads at completion, this is a normal process, do not reset your client.
6) -bigadv WU's have a 4 day deadline.
6b) 2.7 days to make the 50K cutoff, 4 days for the 25K cutoff.
6c) To check and see if you will make the deadline, if a normal SMP WU is faster than 6.5K PpD, you should be able to make the deadline, obviously, the higher the better.
7) The WU's have an upload size of 95MB or more, this could make an upload time of 30-40 minutes on slower connections and will take an additional couple minutes to half an hour to clean up the work files at the end of the run. So add an addition hour to the end of the WU completion before you receive your next WU.
Link to foxtrotniner's -bigadv backup script
Installing the -bigadv client with Finstall for Linux;
Installing a VM client; (This is being updated continuously over at eVGA forums, so this information may no longer be up to date, I will try and refresh it as it is updated there.)
Quoted from linuxrouter on evga.com/forums
Information added from the following threads;
http://www.hardforum.com/showthread.php?t=1476242
http://www.hardforum.com/showthread.php?t=1467934
https://www.evga.com/forums/tm.aspx?m=4464
Contributors; Pocatello, Tigerbiten, nitrobass24, Tobit, Kendrak and newxperiment
*If anything is missing or incorrect, let me know I will fix it asap on this top link*
Add more as it comes my way!
Some ideas on Bargain builds can be found in this thread.
(A wealth of other FAQ can be found here, written by Kassen)
1) To use -bigadv flag you will need an 8CPU core or better computer.
The cores can be virtual, so running on an i7 or a dual-quad core Xeon/Opteron setup should work.
1b) It is possible to run on a 4 core box, but the CPU must be overclocked to or over 4GHz in order to make the 4 day bonus deadline.
1c) Possible speeds to make it per CPU
2) The bigadv client will need 4.5GB or more ram to run, so a system with 6GB or more is recommended.
3) The client can be run on a 64bit Linux install or through a 8 core VM using VMWare Player 3.0 with 64-bit Windows OS
3b) If your system requires virtualization to be turned on through the bios to use more than 1 core, make sure you do so.
3c) If you plan on running 16 or 32 CPU cores OR MORE, than a 64-bit Linux install will be your only option in doing so, there is no free VM that will run with this many CPU cores at this time.
#note# With 4x 8 core VM's in Windows OS, there is a potential of 45K PpD, 32 cores on a Linux install, possibility of 85k PpD. Bonus calculator
4) In order to do -bigadv a passkey is required.
4b) In order to attain a passkey, please go here
5) You will not see the bonus kick in until after you complete 10 SMP units. (This is for verification purposes from Stanford)
5b) You need to have completed 10 Core A2 based SMP units against your passkey before you can get start getting a bonus. They can be normal SMP units or they can be -bigadv units but they must be recorded against your passkey
5c) You will notice a long pause at the end before the WU uploads at completion, this is a normal process, do not reset your client.
6) -bigadv WU's have a 4 day deadline.
6b) 2.7 days to make the 50K cutoff, 4 days for the 25K cutoff.
6c) To check and see if you will make the deadline, if a normal SMP WU is faster than 6.5K PpD, you should be able to make the deadline, obviously, the higher the better.
7) The WU's have an upload size of 95MB or more, this could make an upload time of 30-40 minutes on slower connections and will take an additional couple minutes to half an hour to clean up the work files at the end of the run. So add an addition hour to the end of the WU completion before you receive your next WU.
Link to foxtrotniner's -bigadv backup script
Installing the -bigadv client with Finstall for Linux;
Installing the bigadv client with Finstall.
I always use Finstall to install the FaH client on Linux.
Its quick and easy.
If curl does not work try .........Code:curl -O http://ra.vendomar.ee/~ivo/finstall chmod +x finstall ./finstall smp
More Info on Finstall.Code:wget http://ra.vendomar.ee/%7Eivo/finstall
Once you have configured the client, make sure to add passkey, shut it down as you need to do a clouple more tweaks.
First:- you need to ddownload and drop in the new fah6 from http://www.stanford.edu/~kasson/folding/osx/fah6
If you dont do this you get a bad argument message when you add the -bigadv flag.
Second:- You need to change the default flags the client starts with.
Open the FaH file with an editor and find the line .....
Code:FAH_default_flags="-smp -verbosity 9"
If your just running standard work-unit change it to .......
Where X is the number of cores you want it to run on.Code:FAH_default_flags="-smp X -verbosity 9"
It can either be the number of cores on your computer or the number minus one if you want to save a core for something else.
If your running bigadv then change it to ......
Code:FAH_default_flags="-smp X -bigadv -verbosity 9"
If you want to install the client as a service just run .....
Code:./installService
To start, stop and restart the client use ........
To change to the folding directory.Code:CD ~/foldingathome
Then.......
To start,stop, restart it.Code:./folding start ./folding stop ./folding restart
Luck ..................
Installing a VM client; (This is being updated continuously over at eVGA forums, so this information may no longer be up to date, I will try and refresh it as it is updated there.)
Quoted from linuxrouter on evga.com/forums
This thread is dedicated to folding bigadv in VMware. Below is a screenshot of 7-core SMP folding of bigadv in Windows XP x64 using VMware 3.0 Player.
The TPF with 7-core folding is 34:52 with my i7 @ 3.8 GHz.
There are examples of systems, PPD, and bonus points at this forum thread:
http://foldingforum.org/viewtopic.php?f=55&t=11314
To calculate bonus points and PPD based on TPF, go here:
Bonus Point Calculator:
http://www.linuxforge.net/bonuscalc.php
Leaving one core unused is probably not the worst idea if GPU folding at the same time. This leaves a virtual core over for the GPU clients and other system resources.
Image and instructions
As requested, I have compressed a copy of my Linux image consisting of the necessary fah client. This image is for bigadv units and the bigadv folding requires an i7 or dual socket setup consisting of 8 or more cores. At least 6GB total memory is necessary. The bigadv Windows VMware folding is experimental and stability is unknown. Make sure your system, CPU, and memory are completely stable and all temps under load are normal before trying out these bigadv units. Also make sure your operating system has enough available resources including memory. This can be checked in Windows task manager. This image can also be used to run the regular 1920 pt Core A2 work units.
The image can be download here:
Linux FAH Image v0.7 (7z - 34.1MB) ; http://folding.braindancer.net/linuxrouter/VMWare-FAH-0.7.7z
Linux FAH Image v0.6 (Mirror 1) (Zip - 60.1MB) ; http://hotfile.com/dl/22198169/1abd201/VMWare-FAH-0.6.zip.html
Linux FAH Image v0.6 (Mirror 2) (Zip - 60.1MB) ; http://folding.braindancer.net/linuxrouter/VMWare-FAH-0.6.zip
Linux FAH Image v0.6 (Mirror 2) (7z - 37.2MB) ; http://folding.braindancer.net/linuxrouter/VMWare-FAH-0.6.7z
Linux FAH Image v0.6 (Torrent) (Zip - 60.1MB) ; http://drop.io/vmwarefah06
Linux FAH Image v0.4 (Mirror 1) ; http://hotfile.com/dl/18563526/e72bb21/VMWare-FAH-0.4.zip.html
Linux FAH Image v0.4 (Mirror 2) ; http://folding.braindancer.net/linuxrouter/VMWare-FAH-0.4.zip
Thanks to wb488641 and braindancer for providing file mirror locations. Thanks to gotspeed for making the torrent.
VMWare Player Download
VMWare Player 3.0:
http://downloads.vmware.com/d/details/player_3_0/ZGp0YmQlJSpiZGVkZA==
Folding backup scripts provided by TheCrazyCanuck (see further down the thread for more info)
Folding backup scripts:
http://www.evga.com/folding/files/FAH_SMP_BACKUP_v0_1.rar
Thanks to Shane @ EVGA for hosting the file and thanks to TheCrazyCanuck for spending the time writing the backup scripts and instructions.
Utilities
Qfix - Linux 64-bit build:
http://www.linuxforge.net/fah/img/qfix/qfix
Source:
Link 1: http://linuxminded.xs4all.nl/mirror/www.boston.quik.com/rph/fah.html
Link 2: http://linuxminded.nl/?target=software-qd-tools.plc#qd.c
7-Zip offers much better compression options than using Zip. The compression program can be found here:
7-zip:
http://www.7-zip.org/
Installation
1) Install VMWare Player 3.0 - default options
2) Download and unzip the image. Put the file anywhere you like as long as there is at least 4GB free storage.
3) Startup VMWare Player
4) Click File - Open a Virtual Machine
5) Go to the location where you put the image and double click on the Linux64_FAH.vmx file.
6) The VMX file is preconfigured to use 8 processors and 3600MB memory. Before starting the VM machine, you have the option to "Edit virtual machine settings" and adjust RAM. 3600MB seemed to work okay for me but you may want to allocate more memory just to make sure the client has what it needs. Double click on the name "Linux64_FAH" to start the virtual machine.
7) Wait for Linux to boot. You will see a command prompt. Just above, there are instructions on how to setup FahMon. The system will attempt to get an IP by DHCP and will tell you that IP address.
8) Login with the following:
FAH Login: fah
Password: fah1234
9a) This step is for web-based configuration. If you would rather configure with the fah6 client then skip this step and go to 9b.
When you first boot up the virtual machine it will tell you the HTTP address. The format should be:
http://ip/
where IP is the IP address assigned to the virtual machine.
Enter your username, team id, and passkey here. Optionally, you can change the hostname or enable auto-startup for the fah client with v0.6. Click submit when finished. You must reboot with the command reboot if you change the hostname or enable auto-startup for the changes to take effect.
To get a passkey:
http://fah-web.stanford.edu/cgi-bin/getpasskey.py
When you have done that, shutdown the web service with this command (unless you plan to use the web logs):
v0.4 or newer:
web disable
V0.2-0.3:
/etc/rc.d/rc.httpd stop; chmod 644 /etc/rc.d/rc.httpd
This will save some memory and also close down the web port for security.
Start fah6 with this command in the virtual machine:
./fah6 -bigadv -smp 7
9b) Command line configuration:
With this configuration, the web interface is not being used so this service can be turned off with this command:
v0.4 or newer:
web disable
v0.2-0.3:
/etc/rc.d/rc.httpd stop; chmod 644 /etc/rc.d/rc.httpd
To startup and configure the folding client:
./fah6 -bigadv -smp 7
For configuration, you will need your login, team (33), and passkey. To get a passkey:
http://fah-web.stanford.edu/cgi-bin/getpasskey.py
The only two options I change from default is I select "big" for the unit size when prompted and I enable advmethods under Advanced Options when prompted.
10) (Optional)
8-core bigadv folding may be possible if you allocate enough memory to the virtual machine. At least 4600MB will need to be allocated, if not more. Make sure that Windows has enough resources before trying this. Thanks goes to brentpresley over at foldingforum.org for the tip on setting a greater memory allocation to the virtual machine.
./fah6 -bigadv -smp 8
It is also possible to run the smaller 1920 pt work units via this system (replace with 8 with however many cores you like and your system supports):
./fah6 -smp 8
11) (Optional) With v0.6, you can now view the folding log file via the web:
http://IP/log.php
Additional Information and Configuration Options
Bonus point requirements
1) At least 10 Core A2 work units must be completed. (1920 or 25403 pt units qualify)
2) At least 80% of Core A2 work units must be completed in time.
3) A passkey must be used.
GNU License
The Linux image software is covered under the GNU General Public License Version 2:
http://www.gnu.org/licenses/gpl.html
ChangeLog
VMware Linux Folding ChangeLog:
http://www.linuxforge.net/fah/vmware-changelog.html
Folding backup scripts and instructions provided by TheCrazyCanuck
TheCrazyCanuck
These files will allow you to backup your FAH contents to your Windows machine every hour. Those of you who have real servers to backup files just tweak the username, password, and location accordingly. These files also take care of backing up the ramdrive if you happen to use it. The reason why you would want to backup every hour is because if the FAH client restarts early then you might loose days worth of work that is either not backed up or has been backed up and replaced by another backup.
The hourly backups also resync the clock just in case it was drifting over time. I give you the option of starting up the client with a RAM disk using what Linuxrouter has provided and I give you instructions on how you can retain those contents since they are volatile.
*Disclaimer: I expect anyone who uses this to read the instructions and not complain to me if they loose a WU because they were too lazy to follow instructions. I also take no responsibility for anything you manage to bugger up on the host or VM.*
View original IP configuration information
If you missed the original configuration information including the IP address, FahMon setup, and web configuration address, then you can run this command to see that information again:
info
Solution for client error "Could not connect to Primary Assignment Server for ID" (Credit to pgmoney for solution)
The virtual machine needs an IP on the network in order to access the Internet and the folding servers. If on startup the IP is missing in the notification, then this configuration change may give the virtual machine access to the network.
1) Open VMWare and select Linux64_FAH but do not start the virtual machine
2) Click "Edit virtual machine settings"
3) Click on Network Adapter
4) Change Network Connection from Bridged to NAT
5) Click OK and start the virtual machine
Shutting down or restarting
To shutdown the virtual machine, run this command:
shutdown -h now
To reboot the virtual machine, run this command:
reboot
Multiple Consoles
The image supports opening multiple consoles at once (max 6). Simply hit ALT+F2 through F6 and login. Then you can run other commands while folding at the same time.
Sample Configuration Screenshots
Config Screenshot 01:
http://www.linuxforge.net/fah/vmware-fah-config.jpg
Config Screenshot 02:
http://www.linuxforge.net/fah/webconfig03.jpg
-- Advanced Options --
SSH / Screen Session Setup (Optional)
For those familiar with SSH, there is also the option to access the virtual machine and FAH client remotely.
Only do this if you are familiar with SSH and feel that your network is adequately secure.
To enable SSH:
chmod 755 /etc/rc.d/rc.sshd; /etc/rc.d/rc.sshd start
You can now SSH into the virtual machine using the fah login. Make sure your network is secure first. I would highly recommend setting a new password for the fah account to something more secure using the command: passwd fah. Alternatively, setup a key pair. Use your favorite SSH client. I use Putty in Windows and OpenSSH in Linux.
Setup a screen session:
screen -R -D -S fah
Startup FAH:
./fah6 -bigadv -smp 7
Detach from screen session:
CTRL A + D
Reconnect to the screen session at a later time:
screen -rx fah
Using this method you can login to your virtual machine from another system on the same network or from another site if your network is configured for remote access (VPN) and then join into the screen session again to monitor your FAH client.
Ramdisk (v0.4 or greater)
v0.4 has support for setting up a Ramdisk. There is a script called buildramfs that you can run to set up the Ramdisk. This script creates a Ramdisk with a default size of 750000K to accommodate the bigadv work files. It also automatically copies the files from the work folder and mounts the Ramdisk to the work folder. You will need at least 500MB of available memory and allocated to the virtual machine for these files. The Ramdisk does grow and uses in memory what it needs up to the file system size. The script takes one argument of size where you can specify another size instead of the default 750000K.
Only do this if you have the available memory, have an adequate backup plan, and feel comfortable working with Linux. You will want to backup your files somewhere. These are several options you might consider:
1) Setup a batch file in Windows that copies the work folder and queue.dat file to the host OS on a scheduled time interval using scheduled tasks.
2) Mount a Windows shared folder in Linux using CIFS and copy the files to the Windows shared folder using a Cronjob.
3) Copy the files to a location on the Linux file system of your choosing using a Cronjob.
4) Copy the files manually.
Increase the resolution for the virtual machine
The default resolution is 1024x768x16 for the virtual machine. To set a higher resolution, on first boot when the red LILO bootloader shows up, hit the tab key. You only have 3-seconds to hit the tab key. Enter the following:
2.6.32.2-intel vga=0x346
This will set the resolution to 1600x1200x32 so that you can see a greater amount of information in the virtual machine at once. A couple other options:
0x344 - 1280x1024x32
0x355 - 2048x1536x32
Old Forum Thread
Link to old forum thread:
http://www.evga.com/forumsarchive/tm.asp?m=100994828
Information added from the following threads;
http://www.hardforum.com/showthread.php?t=1476242
http://www.hardforum.com/showthread.php?t=1467934
https://www.evga.com/forums/tm.aspx?m=4464
Contributors; Pocatello, Tigerbiten, nitrobass24, Tobit, Kendrak and newxperiment
*If anything is missing or incorrect, let me know I will fix it asap on this top link*
Add more as it comes my way!
Last edited: