Pages:
Author

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

legendary
Activity: 3583
Merit: 1094
Think for yourself
Hopefully you will have better luck than I did with the RPi.

That's kind of why I said hopefully.  Smiley

I read your post of issues after I already ordered my kit.  But hopefully it will work out.  It seemed like others were using Pi's successfully.  We'll see, the Pi thingy seems really cool anyway as I've never looked into one before.
hero member
Activity: 2534
Merit: 623
WilcoWi, I'm the unlucky git to have a PITA PC. But I'm glad someone else has benefited from my problems and also has a workaround for now.

vh, I'm still running the last version with "lowboost". I'm happy to carry on with any more iterations of your cgminer whenever you are. Shes been running over 48 hours and averaging a smidge under 670Ghs for the 5 sticks. I have ordered various different USB cables ($40 worth   Shocked) just to rule that out aswell. Even a USB2.0 Type B to USB C, which I was surprised to see. So will try them all out and see what happens when they arrive.
member
Activity: 88
Merit: 85
Results of switching the ports as asked:

Code:
0: GSH 10030648: BM1387:02+ 600/600/556 (38:31) [oo]  | 97.3% WU:^72% | 133.4G / 99.09Gh/s WU:1384.6/m A:27404 R:884 HW
 1: GSH 10030962: BM1387:02+ 594/600/544 (39:32) [oo]  | 90.6% WU:^71% | 126.2G / 96.64Gh/s WU:1350.2/m A:19890 R:  0 HW
 2: GSH 10031032: BM1387:02+ 444/600/385 (53:42) [oo]  | 86.3% WU:^80% | 85.13G / 80.92Gh/s WU:1130.8/m A:19006 R:884 HW
 3: GSH 10031051: BM1387:02+ 600/600/573 (38:31) [oo]  |  100% WU:^76% | 143.8G / 104.5Gh/s WU:1460.5/m A:28288 R:442 HW

So it's the miner not the port.

edit: i do not dare to turn voltage up, cause this miner is hotter @~450 Mhz than the others @600 Mhz
Soon i will see what the temperatures they are @. Making an arduino temp. measurement kit. Parts did arrive yesterday.
Now have to find the time to build it(my greatest challenge atm).
First version will only display it on LCD. in future i want to put it towards website with API or something like that. Busy mastering that last part.
vh
hero member
Activity: 699
Merit: 666
My altcoin source code is here...

These are bitcoin miners.   If they happen to work with non-bitcoins, that's neat.

Other than that, You should start up your own thread in the non-bitcoin sections of the forum.

Also, a quick general reminder that any long discussion leading in that direction will be actively removed.



Ok, lowboost seems to work better, just switched to latest version (a62385f).

That makes two now.   You can thank gt_addict for taking the time to help pinpoint that one workaround.

Since I haven't found a way to recreate the problem to investigate locally,
I'll go ahead and add a note about --gekko-lowboost to the first post's Q&A section.

edit: more
just to cross out the possibility of power from the ports being different:
leaving everything else the same, swap physical places on the hub for GS-10030648 & GS-10031032

Your next set of actions will depend on if the lower speed stays with the miner or with the port.   Smiley
member
Activity: 88
Merit: 85
@vh

Ok, lowboost seems to work better, just switched to latest version (a62385f).

@ start:

Code:
0: GSH 10030648: BM1387:02+ 244/600/217 (98:77) [oo]  | 91.7% WU:^89% | 60.18G / 49.36Gh/s WU:692.5/m A:0 R:884 HW:0
 1: GSH 10030962: BM1387:02+ 244/600/217 (98:77) [oo]  | 91.7% WU:^89% | 56.34G / 49.43Gh/s WU:692.5/m A:0 R:442 HW:0
 2: GSH 10031032: BM1387:02+ 231/600/206 (100:81) [oo] | 91.2% WU:^89% | 52.35G / 46.66Gh/s WU:655.7/m A:0 R:442 HW:0
 3: GSH 10031051: BM1387:02+ 244/600/215 (98:77) [oo]  | 90.9% WU:^88% | 64.26G / 49.22Gh/s WU:689.6/m A:0 R:884 HW:0

@ approx 5 mins:

Code:
0: GSH 10030648: BM1387:02+ 600/600/548 (39:31) [oo]  | 94.8% WU:^74% | 120.8G / 100.6Gh/s WU:1405.4/m A:20774 R:884 HW
 1: GSH 10030962: BM1387:02+ 600/600/548 (39:31) [oo]  | 99.6% WU:^73% | 144.3G / 99.22Gh/s WU:1386.3/m A:22100 R:442 HW
 2: GSH 10031032: BM1387:02+ 481/600/387 (48:39) [oo]  | 85.8% WU:^73% | 99.35G / 80.50Gh/s WU:1124.6/m A:17680 R:442 HW
 3: GSH 10031051: BM1387:02+ 600/600/555 (39:31) [oo]  | 98.9% WU:^75% | 132.7G / 102.8Gh/s WU:1435.6/m A:19890 R:884 HW

Its going up now, right away after start instead of down and no messages of " 0 chips". lowboost seems solving this all.

@Kano. i am @ 499 average with 4 newpac's and autotune (no asic boost at the moment, but testing asic boost again now).

@gt_addict: thx for the support on vh, so lowboost is option now.
member
Activity: 114
Merit: 151
631.25 is where it settled overnight.  It would never reach the 750Ghs mark before and last night it was stable over 800Ghs for the first time.  I'll do a run tonight at power level 4 just to verify that it reaches the 750Ghs mark.  BTW I'm running Win7.  My RPi should be in today and I'll get that setup over the weekend, hopefully.

Hopefully you will have better luck than I did with the RPi.  I originally had my R606 running off a RPi 3 B+, and with Asci boost off, worked decent.  Could never get it to hit 500 - 550MHz. It would settle at 481Mhz.   With Asic boost enabled, still had issues.  No matter what volt setting I had the unit on, low 500s for Mhz is what it would settle at.

The only thing I could think of was the lower processing power of the Pi being my weak link.   I then moved my R606 over to a AMD FX-6300 powered Ubuntu box, and it's been working better than I expected.  Volt setting 5 settling at ~700 Mhz.  And put the newpac's and moonlander 2's over on the Pi.  So far been working great on both systems.

All this was before the recent updates to the software that vh has worked hard on.  So it may have different results now on the Pi then when I originally tested.  Good luck, looking forward to seeing the results Smiley
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
...
@Kano: is your pool asic boost and are 4 newpac's @ high freq good enough for difficulty?
They can mine, and yes it's AB, but they'll probably gather dust which wont be paid out for quite a while ...
At the moment the dust limit is about 400-500GH but varies a lot since the pool hash rate varies a lot also.
legendary
Activity: 3583
Merit: 1094
Think for yourself
It will eventually settle near P: (Peak)

But it shouldn't have reached 700MHz, looks like I have another round of adjusting to do (note to self).

631.25 is where it settled overnight.  It would never reach the 750Ghs mark before and last night it was stable over 800Ghs for the first time.  I'll do a run tonight at power level 4 just to verify that it reaches the 750Ghs mark.  BTW I'm running Win7.  My RPi should be in today and I'll get that setup over the weekend, hopefully.
vh
hero member
Activity: 699
Merit: 666
is it normal with asic boost and newpac's, the freq goes down @first? With no asic boost i only see it going up. tried ckpool and now kano pool, but see same behaviour with asic boost...

https://bitcointalksearch.org/topic/m.51047754

hmm... just posted about it like a few hours ago.

There's a new option you might as well throw into your testing mix.

If it heads downward immediately from 200 with asicboost on try including --gekko-lowboost.
member
Activity: 88
Merit: 85
Yes, three fans, on two different Power suplies for backup. just want to be sure if one power supply fails they dont burn. Normally i run em on 600 Mhz (but that is with no asic boost enabled). @600 Mhz they stay cool.

Yes, adjusted @ two sticks the voltage, because they stayed behind (not asic boost enabled). Just very very minor changes (between 1-5 degrees). But see the 0 chips messages appearing on all sticks, even the ones that are not adjusted.

Below with no asic boost:

Code:
0: GSH 10030648: BM1387:02  600/600/488 (19:31) [oo] | 97.5% WU:^63% | 137.9G / 85.78Gh/s WU:1198.7/m A:10166 R:  0 HW:0
 1: GSH 10030962: BM1387:02  600/600/512 (19:31) [oo] | 99.2% WU:^70% | 138.5G / 95.68Gh/s WU:1337.1/m A:15028 R:  0 HW:0
 2: GSH 10031032: BM1387:02  463/600/325 (26:41) [oo] | 75.7% WU:^70% | 79.70G / 74.06Gh/s WU:1035.1/m A:12376 R:442 HW:0
 3: GSH 10031051: BM1387:02  600/600/481 (19:31) [oo] | 96.4% WU:^61% | 134.8G / 83.40Gh/s WU:1165.2/m A:16354 R:  0 HW:0

and with asic boost:

Code:
0: GSH 10030648: BM1387:02+ 188/188/142 (179:100) [oo] | 57.3% WU:^54% | 28.93G / 22.92Gh/s WU:320.2/m A:442 R:0 HW:0
 1: GSH 10030962: BM1387:02+ 188/188/120 (188:100) [oo] | 54.7% WU:^46% | 34.90G / 19.74Gh/s WU:275.8/m A: 0 R:0 HW:0
 2: GSH 10031032: BM1387:02+ 181/181/ 93 (189:104) [oo] | 58.8% WU:^45% | 40.12G / 18.42Gh/s WU:257.8/m A: 0 R:0 HW:0
 3: GSH 10031051: BM1387:02+ 200/600/200 (174:94) [oo]  | 75.4% WU:^71% | 40.22G / 32.47Gh/s WU:454.1/m A: 0 R:0 HW:0
legendary
Activity: 3374
Merit: 1859
Curmudgeonly hardware guy
The obvious solution is stop using Win10. That'll make literally everything better, not just mining.

Windows 10 sucks forever. Unless you've messed with the stick voltages (or there's no fan on them), there's no electrical reason they'd run that poorly. Every stick is tested to 200MHz on stock before it ships, and most of 'em will do upwards of 400MHz on stock voltage if they're kept cool. That's why I put a fan header on the hubs.

Please tell me you got a fan on 'em.
member
Activity: 88
Merit: 85
Yes understand how plateu is working etc., but don't understand why it is tuning down with asic boost enabled, and yes u assume right i am hitting 600+ with asic boost off. i also see sometimes a reset with asic boost enabled, saying found 0 chips, but with no asic boost, i never get this message. Also tried tune option, but no difference there.

Setup: 4 newpac, HP 1000W PS, win10, GS 7 port hub, very good usb cable.
member
Activity: 114
Merit: 151
@WilcoWi   My understanding is that with autotune, it will detune your freq in order to reach 95% - 100% WU.   With the logic that 250Mhz hashing at 97% is better than 350MHz hashing at 65% if that makes sense.   I'm running 4 newpac's using the latest updates from vh and 3 of them are running on target of 400/400/400 and the other downtuned to 394/394/394.   All of which are running at 98% to 100%.

Unsure why your's at least isn't hitting 400.  As I assume you were hitting 600+ Mhz before?

**edit**

You can try and add --gekko-tune-down 90 to your script or .bat file and see if it makes a different.  That should set the tune % of then 90% or higher.  0 disables it if I understand it right.
member
Activity: 88
Merit: 85
is it normal with asic boost and newpac's, the freq goes down @first? With no asic boost i only see it going up. tried ckpool and now kano pool, but see same behaviour with asic boost.

Code:
0: GSH 10030648: BM1387:02+ 188/188/142 (179:100) [oo] | 57.3% WU:^54% | 28.93G / 22.92Gh/s WU:320.2/m A:442 R:0 HW:0
 1: GSH 10030962: BM1387:02+ 188/188/120 (188:100) [oo] | 54.7% WU:^46% | 34.90G / 19.74Gh/s WU:275.8/m A: 0 R:0 HW:0
 2: GSH 10031032: BM1387:02+ 181/181/ 93 (189:104) [oo] | 58.8% WU:^45% | 40.12G / 18.42Gh/s WU:257.8/m A: 0 R:0 HW:0
 3: GSH 10031051: BM1387:02+ 200/600/200 (174:94) [oo]  | 75.4% WU:^71% | 40.22G / 32.47Gh/s WU:454.1/m A: 0 R:0 HW:0
----------------------------------------------------------------------------------------------------
 [2019-05-15 05:30:17.299] 2: GSH 2 - asic plateau: (3/3) 193.75MHz
 [2019-05-15 05:30:17.299] 2: GSH 2 - plateau adjust: target frequency 600.00MHz -> 187.50MHz
 [2019-05-15 05:30:17.640] 2: GSH 2 - NewPac Bitcoin Miner (10031032)
 [2019-05-15 05:30:32.500] 3: GSH 3 - asic plateau: (2/3) 218.75MHz
 [2019-05-15 05:30:32.707] 2: GSH 2 - plateau adjust: target frequency 187.50MHz -> 181.25MHz
 [2019-05-15 05:30:32.817] 3: GSH 3 - NewPac Bitcoin Miner (10031051)
 [2019-05-15 05:30:33.016] 2: GSH 2 - NewPac Bitcoin Miner (10031032)
 [2019-05-15 05:30:34.717] 1: GSH 1 - asic plateau: (3/3) 193.75MHz
 [2019-05-15 05:30:34.717] 1: GSH 1 - plateau adjust: target frequency 600.00MHz -> 187.50MHz
 [2019-05-15 05:30:35.031] 1: GSH 1 - NewPac Bitcoin Miner (10030962)
 [2019-05-15 05:30:40.060] 0: GSH 0 - asic plateau: (3/3) 193.75MHz
 [2019-05-15 05:30:40.060] 0: GSH 0 - plateau adjust: target frequency 600.00MHz -> 187.50MHz
 [2019-05-15 05:30:40.359] 0: GSH 0 - NewPac Bitcoin Miner (10030648)
vh
hero member
Activity: 699
Merit: 666
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.

It will eventually settle near P: (Peak)

But it shouldn't have reached 700MHz, looks like I have another round of adjusting to do (note to self).
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
New build (a62385f)...

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

@my pc all previous versions are flagged too...

It has nothing to do with the code - it's to do with random flagging decisions by the so called 'virus checkers' on Winblows.
member
Activity: 88
Merit: 85
OK, whats different about this build that Security Essentials is flagging it as a trojan and not the previous versions?

@my pc all previous versions are flagged too.

Looking for asicboost pool/multipool, any tips?

@Kano: is your pool asic boost and are 4 newpac's @ high freq good enough for difficulty?
legendary
Activity: 3374
Merit: 1859
Curmudgeonly hardware guy
Solid green means it's getting power. Blinking white means it's hashing. All of my miners work that way - solid color for general power, flash of white while mining (and blink rate generally proportional to hashing speed).

On the R606, the power light is orange and the white blinks are timed more like 2Pacs.
newbie
Activity: 16
Merit: 6
Is there a guide to what the various light states mean on the NewPac USB miners?   I am trying to determine if a blinking white and solid green is the normal state? 
Currently my new single NewPac at 100 Mhz is running at 22.61Gh/s at pool.ckpool.org
A R606 is on the way.
Thanks!
vh
hero member
Activity: 699
Merit: 666
There's a hint in the first post's Q&A section that might work for you.
Pages:
Jump to: