FAHClient V7.1.33 released (3rd Open-Beta)

Moderators: Site Moderators, PandeGroup

FAHClient V7.1.33 released (3rd Open-Beta)

Postby jcoffland » Mon Sep 19, 2011 8:58 pm

Beta Testers,

This release addresses many of the issues found during internal and beta testing. Some of the highlights of this release are improved GPU detection and support, improved networking communication, better OSX support and the addition of themes. There are many other minor tweaks and fixes which can be seen in the change logs below.

There is still much more work to do. Our next major goal is to get the v7 beta client ready to take over as the recommended download on the main Folding@home download page. We are hoping to achieve this by January, if not sooner. Before this will happen we plan to resolve all the tickets currently listed in the Open Beta Phase 2 milestone. To this end we, will be making more frequent open-beta releases over the next months.

Please continue to let us know which issues are most important to you. Our ticket triage is based mainly on three factors 1) severity, 2) implementation difficulty and 3) the importance to Folding@home donors. Although it's not always immediately obvious, your feedback is a huge factor in how we decide to allocate our development resources. The time you spend debugging and articulating your thoughts in these forums may not earn you folding points but improvements in the Folding@home software, which make it more effective, easier to use or just plain more fun, can have a huge impact on disease research.

Thank you for all your help thus far. Let's squash some bugs.

Joseph Coffland
Folding@home Developer
Cauldron Development LLC

Image

Documentation
Installation and user guides can be found here:
FAHControl -> The Graphical User Interface (GUI) what controls the Slots.
FAHViewer -> It shows the protein being folded, if applicable.
Pictorial Installation Guide (Windows) -> A detailed pictorial guide on the V7 installation.
Installation Guide (Windows) -> A brief guide on Windows installation.
Installation Guide (Linux) -> A guide for Linux installation.
Installation Guide (OSX) -> A guide for OSX installation that is in progress.
Client Remote Interface -> Documentation for 3rd party developers.
Main Page -> Main page of the V7.

Getting Help
Aside from the documentation the best place to get help is in this forum. If you do have a problem post a message. There are many knowledgeable people ready and willing to help. Keep in mind, we greatly appreciate thorough reports delivered by patient people who can keep a cool head even when things go wrong.

Bugs/Tickets
Open Tickets Ordered by Milestone and Priority
Active Tickets by Change Time
Note: Some tickets may be closed because they are fixed in an upcoming alpha release but are not yet fixed in the beta release.


Here are the change logs:

v7.1.25:
  • Hide 'Quit on window close' option in OSX.
  • Fixed some problems with WU assign time and time offset calculations.
  • Detect and ignore invalid assign time from older WS.
  • Log computed WS time offset.
  • Removed warning from Slot configuration about changing threads mid-run.
  • Catch and log error accessing battery info in /sys on Linux
  • Fix grayed out name and IP in client add after viewing local client. #640.
  • Remove 'RS480 PCI-X Root Port' from GPU whitelist. #635
  • Added a few new Radeon HD 6xxx cards.
  • Added Nvidia GTX 590 device ID 0x1088 to whitelist.
  • Increase Radeon HD 5xxxx and 6xxxx GPU type level by one. #653.
  • Don't fail WS connections if all data was recieved even on net error.
  • Print IP Address with 'Uploading' message.
  • Fixes for OSX minimize and quit bugs. #649 & #659.
  • Limit max CPUs per slot to system count. #652.
  • Attempt to fix #654.
  • Release system resources when querying OSX battery status. #650.
  • Don't send 'auth' command from FAHControl if empty. #658.
  • Fixed 'slot-add' NULL pointer exception. #666.
  • Fixed 'log-updates start' error. #671.
  • Fixed FAHClient script parsing bug. #676.
  • Show 'Remote Access' tab in advanced mode. #648.
  • Don't allow minimizing to sys-tray if it is not there. #670.
  • Also print core return code numbers in hex. #677.
  • Print times in ISO 8601 format. #664.
  • Expire WUs in sending status.

v7.1.26:
  • Correctly report client version to WS with WU return.
  • Failed upload attempt could cause WU to dump before it was expired. #679.
  • Added AMD Radeon HD 6600 Series to GPU white-list.
  • Fix failure to restart FAHControl in OSX when 'start minimized'. #649.
  • Fixed a socket bug that could cause the loss of the end of a message.
  • Build OSX client in 32-bit mode with Intel compiler.
  • Reduced socket send buffer size to 32KiB to try to solve #682.
  • Attempt to fix PCI detect crash in Windows. #695.
  • Whitelisted more GPUs.

v7.1.27:
  • Check shared info modification time in an attempt to fix #688.
  • More GPU whitelisting.
  • Fixed Windows PCI/GPU detection, broke in v7.1.26. #701.
  • Use WS UTC WU assign time in client wo/ computing offset #697, #681.
  • If running WU is dumped shutdown the core. #700.

v7.1.28:
  • Hopefully finally fixed the OSX on battery detection code.
  • More GPU whitelist changes.

v7.1.29:
  • Print UNSUPPORTED in front of unsupported GPUs in info.
  • Removed unsupported gpu-vendor-id and gpu-device-id options.
  • Allow auto-configuring both GPU and SMP. #629
  • Configure GPU & SMP by default in Windows.
  • Repaired OS description printing in info.
  • Use OS bits to determine 32 vs 64 rather than build bits. #703
  • Enabled GPU detection in OSX.
  • Removed 'gpu-id' and added 'cuda-index' and 'opencl-index' options.
  • GTX465 -> Fermi. #661
  • Automatically install themes in Windows installer.

v7.1.30:
  • Attempt to fix OSX PCI scan crash.

v7.1.31:
  • Another attempt to fix OSX PCI scan crash.

v7.1.32:
  • Added 'gpu-usage' option with default of 80%.
  • Added percent GPU usage slider in FAHControl.
  • Added 'opencl-index' and 'cuda-index' options to FAHControl.
  • 'gpu-id' -> 'gpu-index' in FAHControl.

v7.1.33:
  • Set default 'gpu-usage' to 100%, until GPU cores implement better throttle.
  • Fixed client connection rate limiting.
  • Fixed error reporting for bad slot configuration. #582.
  • Attempt to fix EUE reporting for WSv4. #615.
  • Fixed "Wrong architecture" bug on 32-bit Ubunut. #599.
  • Dropped "64-bit" Windows release. Use 32-bit on all systems.
Cauldron Development LLC
http://cauldrondevelopment.com/
User avatar
jcoffland
Pande Group Member
 
Posts: 1008
Joined: Fri Oct 10, 2008 6:42 pm
Location: San Jose, CA

Re: FAHClient V7.1.33 released (3rd Open-Beta)

Postby Rambler358 » Mon Sep 19, 2011 9:28 pm

Are the GTX590s now supported in this release?
Rambler358
 
Posts: 70
Joined: Fri Sep 19, 2008 4:40 pm
Location: Torrance, CA

Re: FAHClient V7.1.33 released (3rd Open-Beta)

Postby 7im » Mon Sep 19, 2011 9:32 pm

Release notes (i.e. change logs) are your friend...

jcoffland wrote:v7.1.25:

*
* Added Nvidia GTX 590 device ID 0x1088 to whitelist.
*
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
User avatar
7im
 
Posts: 14648
Joined: Thu Nov 29, 2007 4:30 pm
Location: Arizona

Re: FAHClient V7.1.33 released (3rd Open-Beta)

Postby Jesse_V » Mon Sep 19, 2011 9:36 pm

Amazing and impressive!

http://en.wikipedia.org/wiki/Folding@home updated.
Pen tester at Cigital/Synopsys
User avatar
Jesse_V
 
Posts: 2773
Joined: Mon Jul 18, 2011 4:44 am
Location: USA

Re: FAHClient V7.1.33 released (3rd Open-Beta)

Postby Rambler358 » Mon Sep 19, 2011 9:57 pm

7im wrote:Release notes (i.e. change logs) are your friend...

jcoffland wrote:v7.1.25:

*
* Added Nvidia GTX 590 device ID 0x1088 to whitelist.
*

Thank you sir. ;)
Rambler358
 
Posts: 70
Joined: Fri Sep 19, 2008 4:40 pm
Location: Torrance, CA

Re: FAHClient V7.1.33 released (3rd Open-Beta)

Postby Rambler358 » Mon Sep 19, 2011 10:18 pm

Using FAHControl is it possible to set the -bigadv flag for SMP projects? Or how can we see if it's automatically set?
Rambler358
 
Posts: 70
Joined: Fri Sep 19, 2008 4:40 pm
Location: Torrance, CA

Re: FAHClient V7.1.33 released (3rd Open-Beta)

Postby ChelseaOilman » Mon Sep 19, 2011 10:30 pm

Rambler358 wrote:Using FAHControl is it possible to set the -bigadv flag for SMP projects? Or how can we see if it's automatically set?

Yes, see Panthers sticky post in this section of the forum.
viewtopic.php?f=67&t=18187
User avatar
ChelseaOilman
 
Posts: 1646
Joined: Sun Dec 02, 2007 3:47 pm
Location: Colorado @ 10,000 feet

Re: FAHClient V7.1.33 released (3rd Open-Beta)

Postby Spongebob25 » Mon Sep 19, 2011 10:37 pm

Its not working for me. It goes from offline inactive to connecting inactive and back again. It just repeats the same process over and over. Please advise!
Image
Spongebob25
 
Posts: 113
Joined: Thu Jul 23, 2009 8:27 pm

Re: FAHClient V7.1.33 released (3rd Open-Beta)

Postby jcoffland » Mon Sep 19, 2011 10:48 pm

Spongebob25 wrote:Its not working for me. It goes from offline inactive to connecting inactive and back again. It just repeats the same process over and over. Please advise!

Sounds like the client is not starting. Can you try running FAHClient.exe from the command line and tell us what the output is? Let us know if you need help with this.
User avatar
jcoffland
Pande Group Member
 
Posts: 1008
Joined: Fri Oct 10, 2008 6:42 pm
Location: San Jose, CA

Re: FAHClient V7.1.33 released (3rd Open-Beta)

Postby daikerjohn » Mon Sep 19, 2011 10:49 pm

Any specific instructions for upgrading from 7.1.24 to 7.1.33? Presumably we should Finish any outstanding WUs.

Are we supposed to remove the previous install, then fresh install 7.1.33? Or can we upgrade over the top? Just looking for a best practice here. :)
Image
daikerjohn
 
Posts: 5
Joined: Fri May 30, 2008 10:07 pm

Re: FAHClient V7.1.33 released (3rd Open-Beta)

Postby jcoffland » Mon Sep 19, 2011 10:49 pm

@Spongebob25 Also please let us know how you installed, on what platform, what options you selected, etc.
User avatar
jcoffland
Pande Group Member
 
Posts: 1008
Joined: Fri Oct 10, 2008 6:42 pm
Location: San Jose, CA

Re: FAHClient V7.1.33 released (3rd Open-Beta)

Postby jcoffland » Mon Sep 19, 2011 10:52 pm

daikerjohn wrote:Any specific instructions for upgrading from 7.1.24 to 7.1.33? Presumably we should Finish any outstanding WUs.

Are we supposed to remove the previous install, then fresh install 7.1.33? Or can we upgrade over the top? Just looking for a best practice here. :)


You shouldn't have to finish the previous WUs and you should be able to install over the top. However, some bug fixes such as the expiration date problems can require a clean install. So if you have problems try a clean install but we are shooting for clean upgrades, mid run with out an uninstall so it's a good thing to test.
User avatar
jcoffland
Pande Group Member
 
Posts: 1008
Joined: Fri Oct 10, 2008 6:42 pm
Location: San Jose, CA

Re: FAHClient V7.1.33 released (3rd Open-Beta)

Postby barebear » Tue Sep 20, 2011 1:54 am

Re: FAHClient V7.1.33 released (3rd Open-Beta)

Post by jcoffland » Mon Sep 19, 2011 3:52 pm

daikerjohn wrote:Any specific instructions for upgrading from 7.1.24 to 7.1.33? Presumably we should Finish any outstanding WUs.

Are we supposed to remove the previous install, then fresh install 7.1.33? Or can we upgrade over the top? Just looking for a best practice here. :)



You shouldn't have to finish the previous WUs and you should be able to install over the top. However, some bug fixes such as the expiration date problems can require a clean install. So if you have problems try a clean install but we are shooting for clean upgrades, mid run with out an uninstall so it's a good thing to test.


Greetings to all from barebear :D --- I'm delighted to advise that 7.1.33 installed just fine over 7.1.24 ---- it picked up the work units just as they were , and everything seems to be merrily humming along --best regards to 7im who has helped me so much before, and jcoffland for such dedicated work :mrgreen: :eugeek:
GIGABYTE GA-P55A-UD3 LGA 1156 Intel P55 SATA 6Gb/s USB 3.0 ATX Intel MB
Intel Core i7-860 Lynnfield 2.8GHz 8MB L3 Cache LGA 1156 95W Quad-Core Proc.BX80605I7860
16Gb ram
barebear
 
Posts: 134
Joined: Fri Dec 28, 2007 7:11 pm

Re: FAHClient V7.1.33 released (3rd Open-Beta)

Postby Zagen30 » Tue Sep 20, 2011 2:17 am

I didn't see the latest comments, so I uninstalled 7.1.24 before installing 7.1.33. I'm getting a similar problem as Spongebob. I don't know if he got this as well, but when the client starts up it shows the following message:

Image

Uploaded with ImageShack.us

Hitting yes just brings up the same error window over and over again. Hitting no gets rid of the window but FAHControl never starts the client.

This is on Win7 Pro 64-bit. I've tried both quick installation and custom installation. I didn't change any settings from default on custom. I also tried rebooting at one point but that didn't help.

I tried running FAHclient.exe via the console, and it proceeded to download a new WU along with a new copy of the a4 core into the Program Files/FAHClient directory. The old work and cores are still present in /User/Appdata, by the way.
Image
Zagen30
 
Posts: 1589
Joined: Tue Mar 25, 2008 12:45 am

Re: FAHClient V7.1.33 released (3rd Open-Beta)

Postby Spongebob25 » Tue Sep 20, 2011 2:27 am

Got it working. Had to uninstall and remove everything related to fah. Then do a fresh install.
Spongebob25
 
Posts: 113
Joined: Thu Jul 23, 2009 8:27 pm

Next

Return to V7.1.52 Windows/Linux

Who is online

Users browsing this forum: No registered users and 2 guests

cron