GekkoScience NewPac / Terminus R606 (BM1387) Official Support Thread

[kano]

Do you think i can still use a few less sticks for now until it comes in? I also have an amazon basics hub but it is REALLY simple.

It depends on each single port limit.
Again, most of them max at around 1Amp per port (some rare ones may get close to 2Amps)
If the stick miner needs more than that (which it does), then expect issues.

[1715035921]

1715035921

[1715035921]

1715035921

[1715035921]

1715035921

[1715035921]

1715035921

[minefarmbuy]

Gekko Science makes one, we have a version of it if you check out the site.

[JohnDon87]

hey,

So I finally am up and running. How should I try to clock these? I have six sticks and each set to 200 Mhz with a throughput of only 201.9 Gh/z?

[vh]

Try setting them at 175MHz.    You might get another 10-25GH/s if you set it between 160MHz - 175MHz.

edit:

Drawing out a rough sketch to explain.

In the normal range, Hashrate = Frequency x 0.228  



If the formula doesn't work, there's not enough power to move forward with a higher frequency.

[JohnDon87]

Yes, this definitely seems to be the sweet spot for them. No nonces and none dropping down low and having to reset.

[gt_addict]

hey,

So I finally am up and running. How should I try to clock these? I have six sticks and each set to 200 Mhz with a throughput of only 201.9 Gh/z?

Thought you had six sticks running at 100mhz and were having problems? Whats changed to get them to run over the 100mhz you originally had them set at?

[philipma1957]

what is newest miner? for win 10

this one below?

Dec 13, 2018 @ 3339a51 - cgminer-4.11.1-windows-gekko-3339a51.7z

I felt lucky so I set set sticks to 100mhz

http://solo.ckpool.org/users/1JdC6Xg3ajT3rge3FgPNSYYFpmf53Vbtje

[minefarmbuy]

what is newest miner? for win 10

this one below?

Dec 13, 2018 @ 3339a51 - cgminer-4.11.1-windows-gekko-3339a51.7z

I felt lucky so I set set sticks to 100mhz

http://solo.ckpool.org/users/1JdC6Xg3ajT3rge3FgPNSYYFpmf53Vbtje

Page 1 for best results, but you know that.

[vh]

Yes, "Dec 13, 2018 @ 3339a51" is the latest version (for the NewPac).

While we're on the topic:

Here's info on an updated version of the cgminer gekko driver (363d879, branch: r606), prepping for the Terminus R606.

Opening to early adopters.   Neat new options, with lots of bugs pre-squashed, (but probably not fully bug free).

To install:

Code:

#rename the existing cgminer folder then...

git clone -b r606 https://github.com/vthoang/cgminer.git
cd cgminer

CFLAGS="-O2" ./autogen.sh --enable-gekko
make -j 2

Windows Binary: edit
April 8  @ 363d879 : cgminer-4.11.1-windows-gekko-363d879.7z
April 26 @ 5c757f5 : cgminer-4.11.1-windows-gekko-5c757f5.7z
April 30 @ 0d524aa - cgminer-4.11.1-windows-gekko-0d524aa.7z
May 11 @ ef74c27- cgminer-4.11.1-windows-gekko-ef74c27.7z
May 13 @ a62385f- cgminer-4.11.1-windows-gekko-a62385f.7z
May 26 @ 9e51f0b- cgminer-4.11.1-windows-gekko-9e51f0b.7z


Changes:

- Merged in upstream cgminer.

- Added initial support for Terminus R606

- Added self preservation / performance tuning code:  

  leverages the standard stages of hash performance as frequency increase:

  | normal | peak | pleateau (80-90% peak - stress or "no nonces") | no hashing |

  this code update will step back from pleateau into peak.

    + okay to slightly over estimate frequency, it will back down to best healthy hashrate.
    + 5-10% increase in hashrate as you return to peak
    + adjust with "--gekko-tune-down" to suit your needs.   [90-95]% is a healthy range, 95 is default, set to 0 to disable.

    
    
        1.  Adjusts frequency according to each miner's unique charateristics
        2.  To keep a hash performance above 95%.  
        3.  Based on the idea that (95% of 275MHz) hashes better than (80% of 300MHz)
    
- Modified asic-boost pool startup sequence.

  + cleared issue sending AB stratum message on non AB pools.  
  + if pool indicates AB is supported, AB will be enabled.
  + removed option "--gekko-newpac-boost", use "--gekko-noboost" to force non AB mode.
  + added [plus] flag after chip count to indicate asic-boost is functioning.

@0d524aa
  + tune rx buffer handling.
  + drop vmask param when noboost is enabled.   better support for non compatible vmask implementation (prohashing.com)

@ef74c27
  + fix statline overflow

@a62385f
  + works with all tested AB pools below
  + added lowboost mode

@9e51f0b
  + performance improvements
  + bug fixes

Asic Boost Pool notes:

okay - auto detected - Asic Boost Pool(s):

    stratum+tcp://solo.ckpool.org:3333
    stratum+tcp://stratum.kano.is:3333
    stratum+tcp://pool.ckpool.org:3333
    stratum+tcp://btc.viabtc.com:3333
    stratum+tcp://us1.bitminter.com:3333
    stratum+tcp://stratum.slushpool.com:3333
    stratum+tcp://us.ss.btc.com:1800
    stratum+tcp://prohashing.com:3335
    
okay - auto detect - Non Asic Boost Pool(s):

    stratum+tcp://mmpool.org:3333
    
not okay - detected but rejected ab work:  (use "--gekko-noboost")

     N/A

[WilcoWi]

Cool.
So if i am reading right this new version will handle optimal settings for each stick in one instance?
That would be a major improvement.
Can i just start it and it wil run in this optimizing way automatically, or do i need an option for it. Tried to read this quistion in your posting, but not getting 100% clear to me.

[419mining]

vh, you have out done yourself as always. Thank you for your amazing work with this project!

[gt_addict]

Great work VH. Im giving it a whirl now. Love the auto tuning, although after 10 minutes its only getting 55gh on 5 sticks. I was previously running at 500ghs.

How long does it take to "find its groove" and level out? Also it certainly disables and enables the sticks quite often and it says there are no chips on all the sticks (not simultaneously mind you) quite often.

[sidehack]

Instead of a specific time component for ramping, it uses a health component - if it's stable above a certain hashing percentage threshold it'll step up, and then once it reaches that equilibrium again, it steps up again.

I haven't tested it out on sticks, but I've seen it take 20 minutes to reach target frequency on a test pod.

What controller are you using? I've had good luck on a PC but the timings are still being tweaked to cooperate with a Pi so that might be causing some of your reset/zero-chips issues.

[vh]

Auto anything is usually too generic to accommodate every case.  
A little hesitant to pursue it much but it looked very promising while locally testing.
When the build finalizes for the R606 release, it may or may not be still there.

Anyways, It waits a little bit to check quality before moving up in frequency.

On my test area:
10 minutes to settle in at 200MHz, no adjustments, all ports are minimum 2A.
45 minutes when I targeted 700MHz to pass peak, then another 30 minutes to return to peak.

Setup 1:
Device : Dell Optiplex
OS     : Ubuntu 16.04
Miners : NewPac x 3, Compac x 3, 2Pac x 3
Hub    : Sipolar 30, + 1 Y Cable.

Setup 2:
Device : Pi3
OS     : Rasbian - Latest
Miners : NewPac(s)
Hub    : GekkoScience Hub.

Reset is normal, but reporting 0 chips I wasn't expecting either.

Along the same questioning as sidehack mentioned, can you include your more detail on your current setup, so I can reconfigure my test area to look similar?

[Gage-Miner]

I need help setting up my pi w/ rasbian

I dont understand how to make a .bat file like you would in windows.

[gt_addict]

Sorry guys. I'm running on a windows 10 Pro 1809 build pc, using the gekko hub, with 419Mining fan stand and 92mm fan.

Gave it a good hour and it only reached 61Gh for all five sticks combined.

I left the bat file standard, just pool, username etc no frequency settings. Do I still need to add a freq like the previous versions of your cgminer variant? As that may well be where I was going wrong.

I did see it try to run at 200m but consistently dropped back down to 100 or lower with the issues of zero chips and "failure" of various sticks.

EDIT:-

Added the freq option of 450m (as per what they were running at) and they immediately stepped down to 200m and pretty consistently drop to 100m with numerous "no nonce" which seems to coincide with the "0 Chips" at the top in the list of devices (where the serial number would reside) at which point it looks like it restarts and the cycle repeats.

[vh]

@Gage-Miner

(Re) Read the first post.

How far did you get in the build process?

@gt_addict

If you just launch the test file as is, the target frequency will set to 100MHz.  

200MHz is the chip's built in frequency when a reset is applied, so it will flash that value temporarily.

In normal cases it will start there and move up to the target.

Something seem off in the windows build.   The "no nonces" seems likely to be the underlying culprit.

The missing nonces could be software timing or hardware events hidden in the previous build.   This build is very sensitive to that.

Same todos items on the hardware side to check hardware interaction.
    Do you still get no nonces with just one miner on the hub?
    Try a different port to get onto usb2 if possible.

I'll switch to windows 10 this evening to check if it's repeatable and approach it from the software side.

[gt_addict]

@VH

I will give it a try on a single stick later, then on a different port (hub currently plugged direct into mobo IO usb2 port, i think) and report back  

Currently got them running on the other build as normal at 450m.

[Gage-Miner]

@VH

so its a brand new pi3 b+ and i tried following the steps on the 1st page of this thread.

I have the pi all set up - installed cgminer - i can get it to run but it will not detect the gekko's (newpac) nor do i know how to edit the file to manually set my freq.

To be honest my command line skills are below par and i am learning as i go.

I did install full win10 pro on the pi but when i run zadig it gets angry cause 32bit to 64bit conflict... plus it was slow as a mutha with only have 1gb ram

Just exploring all options and learning as i go (as i have no idea what i am doing

-Gage

[gt_addict]

Gage, you may well have better success using raspbian. Win10 on a pi is probably asking a bit much.