GekkoScience NewPac / Terminus R606 (BM1387) Official Support Thread - page 85.

dnprock

member

Activity: 324

Merit: 17

Bitflate developer

Quote from: dnprock on April 30, 2019, 06:14:23 PM

I'm running a NewPac miner on a mac with cgminer. It creates a few blocks. Then it starts to give me: GSH 0 failure, disabling!... "failed to initialise" error. I'm running with a low frequency (--gekko-newpac-freq 50). I'm using vhoang/cgminer brew build. The command I use:

cgminer -o http://127.0.0.1:8332 -u user -p pw --btc-address ... --gekko-newpac-freq 50

Any pointer?

I'm updating on my failed-to-initialised issue. After a reboot of my mac, the problem goes away. It seems like there's an issue with driver initialization. But my current work around is to reboot my mac.

os2sam

legendary

Activity: 3583

Merit: 1094

Think for yourself

It's been quite a while since cgminer has been flagged for me. Of course it has been 3 or so years since I've used any version of CGMiner too.

I'm assuming that this version has some instrumentation code that may not be normal?

The hash checks out, as long as my dyslexia hasn't flared up

Thanks,
Sam

Wow, this new version just went straight to 700Mzh with no issues on voltage level 5. The other versions would only go to 575Mhz on level 5.

Edit: It did finally re-target to 631.25Mhz. But that is better than the 575Mhz my R606 got previously.

vh

hero member

Activity: 699

Merit: 666

Highly surprised any previous version didn't flag AV.

The safest path is to review the code and use the cross compile instruction in the first/second post.

The version I dropped into the 7z (a62385f) has this signature.

Code:

# sha1sum cgminer.exe
a4c65616886dff429dd01b4caac582cea32ab43b cgminer.exe

Code:

C:\AVExcludedPath\cgminer-4.11.1-windows-gekko>certutil -hashfile cgminer.exe
SHA1 hash of cgminer.exe:
a4c65616886dff429dd01b4caac582cea32ab43b

os2sam

legendary

Activity: 3583

Merit: 1094

Think for yourself

Quote from: vh on May 13, 2019, 09:49:08 PM

New build (a62385f)...

OK, whats different about this build that Security Essentials is flagging it as a trojan and not the previous versions?

minefarmbuy

full member

Activity: 1022

Merit: 221

We are not retail.

WinX is finicky. I get asic boost to work well on my desktop and surface but not laptop. I think I've voltage setting 5 averaging over 800gh/s poolside at ckpool. With a couple of zero hashing instances. Then I've been getting local IP disconnects through the middle of the night. So I'd say average is closer to 900gh/s. Smiles do ensue when I look at the blinky lights.

gt_addict

hero member

Activity: 2534

Merit: 623

Quote from: sidehack on May 14, 2019, 10:41:07 AM

The obvious solution is stop using Win10. That'll make literally everything better, not just mining.

But hey cool, good there are options. Thanks for the explanation.

mstrozier, good to see it's up and running well. ~700MHz on volt 5 is pretty good. Setting 3 is approximately the same as a NewPac's stock.

Yea i seem to have an issue with my pc. I would run off a pi but haven't got one anymore. The sticks and eventually an r606 when they are released for overseas will be running on my desk so its easier to run direct on the pc.

So far the “lowboost” midstate 2 is working great. 24hours at 600m and using 10w less than no boost at all. But I'm not fussed about the efficiency, just want to hit the magical 1Th on the r606. Really appreciate vh’s ongoing help with this. Ive tried all manner of things before I contacting him, disconnecting all usb devices apart from keyboard and mouse, enabling xhci handoff, closing down any and all programmes including security software but to no avail. The only thing I haven't tried is a better quality usb cable but not sure if that would make much difference.

sidehack

legendary

Activity: 3374

Merit: 1859

Curmudgeonly hardware guy

The obvious solution is stop using Win10. That'll make literally everything better, not just mining.

But hey cool, good there are options. Thanks for the explanation.

mstrozier, good to see it's up and running well. ~700MHz on volt 5 is pretty good. Setting 3 is approximately the same as a NewPac's stock.

vh

hero member

Activity: 699

Merit: 666

@sidehack

I'm working through an issue with gt_addict. The combination of his (WIN10) environment + four midstate packets appears to be causing mining to stall. I would like to later conclude it's not needed, but for the moment it's an alternative path to a form of AB that can approach 900+TH/s on the r606.

Extra Troubleshooting Path: (normal) -> (gekko-lowboost) -> (gekko-noboost)

philipma1957

legendary

Activity: 4256

Merit: 8551

'The right to privacy matters'

I did a video on youtube.

3 newpacs
1 r606

about 5 minutes long

Your video will be live at: https://youtu.be/3ANZPRnjCpA

the r606 is doing 1.035 th at 7 volt setting freq of 775 it tuned to 775 and does 98-100%

I added a fan basically I have a lot of loose fans so why not.

I am doing say

1035gh r606
   62gh newpac 1
   62gh newpac 2
   62gh newpac 3

1221gh total

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

mstrozier

member

Activity: 114

Merit: 151

It is on volt setting 5. I set the freq to 700 and didn't drop much with the autotune. With the updated miner I went ahead and pointed my newpacs also towards multipool since it's AB supported and bumped their freq to 400. Each stick running about 90Gh/s steady. No hiccups there either.

https://ibb.co/pjpTzTL <---- R606

https://ibb.co/c8xX0dy <---- Newpac's. I had to break them down in groups of 2 for this pool however. Some of the sticks wouldn't accept any shares when I ran them all together.

Later this week my 2nd pod should arrive. Looking forward to adding to the collection Cheesy

And later today I have a volt/watt meter arriving. As I've been curious how many watts this is putting out and also my small farm as a whole is using. I'll take those measurements later this evening.

philipma1957

legendary

Activity: 4256

Merit: 8551

'The right to privacy matters'

Quote from: sidehack on May 14, 2019, 09:32:25 AM

That's decent numbers. Volt 5, volt 6?

I might have to update all the testers to this one. We still have the occasional problem with a bad NewPac killing cgminer and stopping a 24-hour run on a whole hub.

VH, can you explain a bit more about 2-midstate AB? Why that option might be necessary or beneficial over regular (4-midstate) or no AB at all?

I went to volt 7 and freq 775 I also set 3 newpacs to 275

I am doing over 1.3th with this. I am going to post a short YouTube today.

sidehack

legendary

Activity: 3374

Merit: 1859

Curmudgeonly hardware guy

That's decent numbers. Volt 5, volt 6?

I might have to update all the testers to this one. We still have the occasional problem with a bad NewPac killing cgminer and stopping a 24-hour run on a whole hub.

VH, can you explain a bit more about 2-midstate AB? Why that option might be necessary or beneficial over regular (4-midstate) or no AB at all?

mstrozier

member

Activity: 114

Merit: 151

@vh thanks for working with me yesterday. These changes fixed the shutdown issues I was having (as far as I can tell). This is the first time my pod has ran all night without shutting down.

Current uptime: 12 hours autotuned itself to 694 at 98% and hashing 916Gh/s for an average. Awesome.

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: rockmoney on May 11, 2019, 02:33:16 AM

...
@kano - I currently have four R606 miners on your pool, all with R606 in their worker names. My newest one is averaging 1.10Th/s on the pool if you want to grab some stats. I'm back in PA now btw, and two additional R606 miners will be online soon! Wink

Quote from: rockmoney on May 11, 2019, 03:49:01 PM

Quote from: vh on May 11, 2019, 09:58:29 AM

New build (ef74c27)...

Thank you vh! I just switched all of my R606 miners to this latest version. First, those stray characters have disappeared now, which is good. Will let you know if I experience any problems, but all has been good so far! Thanks again! Wink

So the numbers for each of the 4 workers ... anything with a Finish time >= May 10
Each time a miner stops then reconnects it gets a new clientid, so gets a new line below.
So each worker I've shown the time of the first to last share then calculated the hash rate - ignoring the first share, since that's the start time.
As can be seen, all were over 1THs

I also excluded anything with less than 5000 shares since that was usually only a couple of hours or less and thus wasn't very reliable.

The switch to the new code, mentioned above, would be around 'Sat May 11 20:45 UTC 2019'

Code:

R606
  From 'Fri May 10 22:49:22 UTC 2019' to 'Sat May 11 20:44:33 UTC 2019' = 78911s
  Accepted Shares='24093' (including first)
  Hash rate 1.065THs

  From 'Sat May 11 20:49:54 UTC 2019' to 'Sun May 12 05:00:11 UTC 2019' = 29417s
  Accepted Shares='8336' (including first)
  Hash rate 1.032THs

  From 'Sun May 12 05:15:56 UTC 2019' to 'Tue May 14 01:59:55 UTC 2019' = 161039s
  Accepted Shares='43313' (including first)
  Hash rate 1.069THs

R606-2
  From 'Fri May 10 22:56:59 UTC 2019' to 'Sat May 11 20:44:39 UTC 2019' = 78460s
  Accepted Shares='23670' (including first)
  Hash rate 1.052THs

  From 'Sat May 11 20:50:33 UTC 2019' to 'Sun May 12 05:00:08 UTC 2019' = 29375s
  Accepted Shares='8297' (including first)
  Hash rate 1.028THs

  From 'Sun May 12 05:18:31 UTC 2019' to 'Tue May 14 01:59:58 UTC 2019' = 160887s
  Accepted Shares='41871' (including first)
  Hash rate 1.030THs

R606_CJ
  From 'Thu May 9 00:22:00 UTC 2019' to 'Sat May 11 00:32:37 UTC 2019' = 173437s
  Accepted Shares='50195' (including first)
  Hash rate 1.065THs

  From 'Sat May 11 00:42:51 UTC 2019' to 'Sun May 12 11:33:31 UTC 2019' = 125440s
  Accepted Shares='39682' (including first)
  Hash rate 1.036THs

  From 'Sun May 12 20:11:27 UTC 2019' to 'Mon May 13 01:35:20 UTC 2019' = 19433s
  Accepted Shares='5251' (including first)
  Hash rate 1.038THs

  From 'Mon May 13 01:37:22 UTC 2019' to 'Mon May 13 13:56:00 UTC 2019' = 44318s
  Accepted Shares='12423' (including first)
  Hash rate 1.039THs

  From 'Mon May 13 14:37:32 UTC 2019' to 'Mon May 13 19:37:58 UTC 2019' = 18026s
  Accepted Shares='5127' (including first)
  Hash rate 1.045THs

ROCKY-R606-3
  From 'Sun May 12 10:35:05 UTC 2019' to 'Sun May 12 19:27:02 UTC 2019' = 31917s
  Accepted Shares='9830' (including first)
  Hash rate 1.020THs

  From 'Sat May 11 20:45:46 UTC 2019' to 'Sun May 12 05:00:05 UTC 2019' = 29659s
  Accepted Shares='8971' (including first)
  Hash rate 1.009THs

vh

hero member

Activity: 699

Merit: 666

@evade_57

pool diff automatically changes upward toward the network diff to force you send less traffic depending on your worker hashrate. if you are allowed to take an initial guess (suggested-diff / pool side setting), aim anywhere between 2(min) to 5(max) times your hashrate (GHs).

New build (a62385f)

Linux instructions:
   rename (save), clone, build. (see first post)

Windows binary: cgminer-4.11.1-windows-gekko-a62385f.7z
sha1sum a4c65616886dff429dd01b4caac582cea32ab43b cgminer.exe

Fixed version mask negotiation.
   + AsicBoost now works for prohashing.com & slushpool.com

Added "--gekko-lowboost"
   + 2 midstate mode vs normal 4 midstate mode.
   + less efficient version of AB.

Add locking around some shared memory structures.
   + potential place for program fault.

evade_57

member

Activity: 93

Merit: 11

This doesn't make a lot of sense but I'll post anyway
Purpose is to obtain 12 more NewPac's & 2 GekkoScience hubs and add another Pi
Backed up my Kingston 8gb class 4 SD card from the current Pi 3+
Flashed img to a new Sandisk Class 10 card and installed to test on the same Pi
Difficulty performance on pool.ckpool more than doubled
Average was 425 difficulty and went up to 1100 or so
Frequency of NewPac's is set to a comfortable 250mhz with 682Gh/s in total with A/B
Possible change in the pool itself or traffic could be part of this I assume, coincidence Huh

Pi connection is wired to the router directly

mstrozier

member

Activity: 114

Merit: 151

How can I check for that? It's the only device connected to this linux PC. No other usb device is connected including keyboard or a mouse. As I remote desktop into this machine.

* edit *

I may just start with a fresh reinstall on this box. Right now I have it running on setting 7 and freq 700 and so far, been an hour in and no issues. And it's 700/700/700 at 99.1%.

sidehack

legendary

Activity: 3374

Merit: 1859

Curmudgeonly hardware guy

If one of the chips is not getting enough voltage to run at a set frequency, that's what causes the ASIC plateau or missing nonces, and the auto-tune does its thing. There is no "so it shuts down".

As mentioned already, nothing in the code makes it shutdown except a specific user command. What's likely happening is some noise or data on the USB bus being erroneously detected as that shutdown signal. It's not deliberate.

mstrozier

member

Activity: 114

Merit: 151

I am wondering if it's AB related. When I run this on a non-AB supported pool, it never gives me the random shutdown. It'll lower the frequency until it reaches a good % to reflect. However working on a AB supported pool I get this to happen.

1st test I had it at setting 6 and 700 for targeted freq. It reached the target freq as 700/700/698. Remained there for an hour and 45 minutes before it shutdown.

2nd test I dropped to setting 5 and tried again. Roughly same time limit before it shutdown.

3rd test I remained on setting 5 and dropped freq to 675. This time ran 2 hours 25 minutes before shut down.

The test I just ran this morning for vh, freq set to 700 voltage set to 5 and it ended in 20 minutes.

This makes me think one of the chips are possibly not getting enough voltage to run at a set freq possibly? So it shuts down?

sidehack

legendary

Activity: 3374

Merit: 1859

Curmudgeonly hardware guy

I have yet to see an issue similar to that with Terminus, but it happens occasionally on a NewPac testing station when there's a faulty stick dropped out and cycling. I am therefore not surprised to see a "shutdown signal received" adjacent to a "toggling to reset". I am surprised to see an R606 needing to be reset so frequently though.

Topic: GekkoScience NewPac / Terminus R606 (BM1387) Official Support Thread - page 85. (Read 61923 times)