yodap
CLASSIFIED Member
- Total Posts : 4668
- Reward points : 0
- Joined: 2011/05/15 06:13:40
- Location: NY, Upstate
- Status: offline
- Ribbons : 8
Re: New beta version of core 17 might fix GK104 - can someone test?
2014/04/18 04:10:56
(permalink)
Check your log and make sure you got version 0.0.55. It took me 2 tries.
|
mGuyA
New Member
- Total Posts : 45
- Reward points : 0
- Joined: 2006/02/04 20:51:52
- Status: offline
- Ribbons : 0
Re: New beta version of core 17 might fix GK104 - can someone test?
2014/04/18 07:18:57
(permalink)
Core 17 0.0.055 is a beta core. I think you need the beta flag to get it and to use it.
First post in this thread has good instructions for how to get it.
Using pause/fold you can download core 17 0.0.055 and install a new nVidia driver without waiting for wu to end.
 EVGA Affiliate Code CR6GOPQR5H
|
robbysites
FTW Member
- Total Posts : 1978
- Reward points : 0
- Joined: 2009/01/12 10:29:41
- Location: 51°10?43.84?N 1°49?34.28?W
- Status: offline
- Ribbons : 2
|
the_Scarlet_one
formerly Scarlet-tech
- Total Posts : 24079
- Reward points : 0
- Joined: 2013/11/13 02:48:57
- Location: East Coast
- Status: offline
- Ribbons : 79
Re: New beta version of core 17 might fix GK104 - can someone test?
2014/04/18 17:54:56
(permalink)
yodap
Check your log and make sure you got version 0.0.55. It took me 2 tries.
Found them in the log, and one shows that the long one is 0.0.52, and I have tried updating it multiple times. It shows 12 hours left, and once that is complete, I will try to force the update again. Should big brother get an Advanced flag for the Classifieds? I am wondering, for the challenge, if that would help out at all?
|
Zagen30
SSC Member
- Total Posts : 528
- Reward points : 0
- Joined: 2009/11/27 12:21:01
- Location: Laguna Niguel, CA
- Status: offline
- Ribbons : 3
Re: New beta version of core 17 might fix GK104 - can someone test?
2014/04/18 22:42:16
(permalink)
Just to confirm, you do have the GPU slots set to client-type:beta, correct? Could you double-check the configuration in case you entered that but it didn't save? This step is vitally important right now since the new version is still in beta.
Also, are you definitely deleting the beta core 17 folder (C:\Users\<your name>\AppData\Roaming\FAHClient\cores\www.stanford.edu\~pande\Win32\AMD64\NVIDIA\Fermi\beta\Core_17.fah)? Deleting the non-beta core 17 folder (NVIDIA\Fermi\Core_17.fah, note the lack of \beta between \Fermi and \Core_17.fah) won't do what you're looking to do.
If both of the above are as they should be, then you may just have to wait for the next WU. I don't know if this is the case, but it might be that WUs assigned on a non-beta flag will only use a copy of the core found in the non-beta core directory.
As to Big Brother, is it currently running no flag, or beta? With the new core 17 projects, I've once again been getting all core 17 with the beta flag (almost all have been project 9101, with two 9406's mixed in). All three of the new projects have been moved to advanced, but it's likely that advanced will still get you a mix of core 15 and core 17. For the purposes of TZC, I think you'd want to stick to beta. If it's currently running no flag, I guess advanced might have a slightly higher chance of getting core 17 work since there are more core 17 projects on it than full-FAH, but I'd still go with beta.
 Core i7 3770K @4.3 GHz, 8 GB DDR3 @2133 MHz, 2xGTX 970 SSC @1379 MHz, Windows 7 Pro 64-bit Affiliate code: K4BJ4FHUX5
|
robbysites
FTW Member
- Total Posts : 1978
- Reward points : 0
- Joined: 2009/01/12 10:29:41
- Location: 51°10?43.84?N 1°49?34.28?W
- Status: offline
- Ribbons : 2
Re: New beta version of core 17 might fix GK104 - can someone test?
2014/04/18 23:57:32
(permalink)
Zagen30
Just to confirm, you do have the GPU slots set to client-type:beta, correct? Could you double-check the configuration in case you entered that but it didn't save? This step is vitally important right now since the new version is still in beta.
Also, are you definitely deleting the beta core 17 folder (C:\Users\<your name>\AppData\Roaming\FAHClient\cores\www.stanford.edu\~pande\Win32\AMD64\NVIDIA\Fermi\beta\Core_17.fah)? Deleting the non-beta core 17 folder (NVIDIA\Fermi\Core_17.fah, note the lack of \beta between \Fermi and \Core_17.fah) won't do what you're looking to do.
If both of the above are as they should be, then you may just have to wait for the next WU. I don't know if this is the case, but it might be that WUs assigned on a non-beta flag will only use a copy of the core found in the non-beta core directory.
As to Big Brother, is it currently running no flag, or beta? With the new core 17 projects, I've once again been getting all core 17 with the beta flag (almost all have been project 9101, with two 9406's mixed in). All three of the new projects have been moved to advanced, but it's likely that advanced will still get you a mix of core 15 and core 17. For the purposes of TZC, I think you'd want to stick to beta. If it's currently running no flag, I guess advanced might have a slightly higher chance of getting core 17 work since there are more core 17 projects on it than full-FAH, but I'd still go with beta.
For this test to be valid - the second paragraph is critical.I have seen the identical results following your instructions. (I did not follow it to the letter the first two times) RTFP right?!!! Anyway, the more testing this whether it works or not would prove to be a success. As for shaving seconds on the TPF - no benefit in the short runs - but over three to six months it is a net gain. I am not getting the 1300x like before, but my ppd output is fine. Beta for me is nothing but core 17 following your instructions. The more folders that try this and report your results to this thread will result in a more accurate assessment of your test. rs
post edited by robbysites - 2014/04/18 23:58:40
 MY AFFILIATE CODE-000H94333W  
|
the_Scarlet_one
formerly Scarlet-tech
- Total Posts : 24079
- Reward points : 0
- Joined: 2013/11/13 02:48:57
- Location: East Coast
- Status: offline
- Ribbons : 79
Re: New beta version of core 17 might fix GK104 - can someone test?
2014/04/19 05:10:09
(permalink)
I will be able to provide Updated information in about 45 minutes... I just pulled the system up again, and this work unit is almost complete. I will set it to finish, and once it does, I will pause the second Unit, and delete the folder again, to hopefully force the newest one to run on 0.0.55 and yes, Client-Type Beta is populated. *Little Brother* Just picked up new Core 17 Version 0.0.55 after completing the one that took 2 days. This one has an 8 Hour Completion time..... up to 120k PPD from 75k... *Big Brother* is Running at 338k PPD with the 750Ti plugging away at a Core 15 (8018). Maybe when the new MoBo gets here and can run everything at x8, the little one will work faster. I have no idea how that will work.
post edited by Scarlet-Tech - 2014/04/19 06:12:00
|
b-morgan
New Member
- Total Posts : 11
- Reward points : 0
- Joined: 2009/06/20 08:10:11
- Status: offline
- Ribbons : 0
Re: New beta version of core 17 fixes GK104 - tested and confirmed
2014/06/03 19:00:28
(permalink)
Zagen30If someone could test this on their own GK104, that'd be useful. You'd need to set the slot to client-type:beta if you haven't already. None of the beta core 17 projects have this set as the minimum version, so you'd need to manually force an update by deleting the beta core 17 folder when the slot is paused (default C:\Users\<yourname>\AppData\Roaming\FAHClient\cores\www.stanford.edu\~pande\Win32\AMD64\NVIDIA\Fermi\beta\Core_17.fah) and then restarting the slot. Can someone elaborate on how to "set the slot to client-type:beta"? I have both a GTX 660 (GK106) and a GTX 660 Ti (GK104) and I'd be happy to test the beta if the instructions can be made "simple" enough for me to follow.
|
bison88
Superclocked Member
- Total Posts : 136
- Reward points : 0
- Joined: 2013/10/28 17:44:21
- Status: offline
- Ribbons : 0
Re: New beta version of core 17 fixes GK104 - tested and confirmed
2014/06/03 19:07:10
(permalink)
b-morgan
Zagen30If someone could test this on their own GK104, that'd be useful. You'd need to set the slot to client-type:beta if you haven't already. None of the beta core 17 projects have this set as the minimum version, so you'd need to manually force an update by deleting the beta core 17 folder when the slot is paused (default C:\Users\<yourname>\AppData\Roaming\FAHClient\cores\www.stanford.edu\~pande\Win32\AMD64\NVIDIA\Fermi\beta\Core_17.fah) and then restarting the slot.
Can someone elaborate on how to "set the slot to client-type:beta"? I have both a GTX 660 (GK106) and a GTX 660 Ti (GK104) and I'd be happy to test the beta if the instructions can be made "simple" enough for me to follow.
Open up the FAH Advanced Control. Go into Configure. Next select the Slots tab. Select the first GPU you want to change to "client-type beta" and select the button at the bottom named "Edit". Scroll down to the "Extra Slot options" on the window that pops up and select "Add". For the name put: "client-type" and for the value put "beta", no quotations. Click OK and the pop up window should disappear. Make sure to select "Save" at the bottom of the menu that you're now on. Do that for each GPU. The next WU should now try and download the latest FAH Core 17 build and grab a beta unit.
|
b-morgan
New Member
- Total Posts : 11
- Reward points : 0
- Joined: 2009/06/20 08:10:11
- Status: offline
- Ribbons : 0
Re: New beta version of core 17 fixes GK104 - tested and confirmed
2014/06/04 09:22:37
(permalink)
|
Seadog
New Member
- Total Posts : 16
- Reward points : 0
- Joined: 2008/03/01 15:48:12
- Status: offline
- Ribbons : 0
Re: New beta version of core 17 might fix GK104 - can someone test?
2014/06/18 14:22:40
(permalink)
So I have the beta flags on my 670's, but I don't have a beta folder in the Fermi directory. I am assuming that i'm missing something here. Any ideas? Edit: never mind, i believe i figured it out. :D
post edited by Seadog - 2014/06/18 14:26:07
|
robbysites
FTW Member
- Total Posts : 1978
- Reward points : 0
- Joined: 2009/01/12 10:29:41
- Location: 51°10?43.84?N 1°49?34.28?W
- Status: offline
- Ribbons : 2
Re: New beta version of core 17 might fix GK104 - can someone test?
2014/06/18 18:17:57
(permalink)
Glad you got it figured out. Not too long ago you had to change your client-type flag between "beta", "advanced", or just no flag to get the CORE 17 projects. I have had mine set to "advanced" for several weeks and I get nothing but core 17 projects - mostly 130001s. Fold on!
post edited by robbysites - 2014/06/18 18:19:09
MY AFFILIATE CODE-000H94333W
|
Mcnugget
New Member
- Total Posts : 31
- Reward points : 0
- Joined: 2007/10/15 21:37:04
- Status: offline
- Ribbons : 0
Re: New beta version of core 17 might fix GK104 - can someone test?
2014/06/19 14:10:13
(permalink)
I did this as well and raised the PPD on my 760 by over 50%. Thanks for the post. I also rolled my drivers back to 326.80. Many other 760 owners posted that they saw a big change in points all any more current drivers. Hope this helps anyone else that is having issues.
  i7-3770k @4.2 w/Cooler Master Hyper 212 EVO, EVGA GTX 760 FTW 4gb, 16bg G.Skill Z Series ram, MSI z77 MPower MoBo, 1TB WD black drive, 120gb Kingston HyperX SSD, EVGA SuperNOVA 1300 G2 Power Supply, All in a Thermaltake Level 10 GT
|
Seadog
New Member
- Total Posts : 16
- Reward points : 0
- Joined: 2008/03/01 15:48:12
- Status: offline
- Ribbons : 0
Re: New beta version of core 17 might fix GK104 - can someone test?
2014/06/20 04:00:43
(permalink)
Yeah, my overall PPD on my rig of 2 x 670 FTW and 1 i7 4770k went from 96K to 168K. Worth at least giving it a shot. I didn't even delete the current jobs. Just waited for them to complete and pick up the .55 beta on it's own. Thanks again for this info.
|
menace33
New Member
- Total Posts : 38
- Reward points : 0
- Joined: 2013/01/06 12:34:11
- Location: Tennessee
- Status: offline
- Ribbons : 0
Re: New beta version of core 17 might fix GK104 - can someone test?
2014/06/22 08:43:58
(permalink)
I've updated my drivers to 337.88 for my 660 Ti FTW, 670, and 770 and all are functioning at the same levels or a lil better, but not worse. Back on beta from advanced and all looks good right now.
|