GekkoScience Terminus R808 Miner Official Support Thread

[zachj00]

Okay I will say though, if you see a note that the frequency unexpectedly changed to 200MHz, that means the hardware controls detected a string dropout and forced a reset. If you have turned the voltage down, you might turn it back up a bit.

No, the pods are awesome when they work and garbage when they don't. You haven't seen all the work I've had to do just to get some out the door, only to have an embarassingly high percentage of reported issues.

I have had three of mine running fine with no issues on Windows 10 PC for 24 hours.  I initially had one go into zombie mode and plugged into a different USB port and it has been working fine.  I thought I have had an abundance of USB 2.0 adapters for my other three but I can't find any and I forget to grab some while at work.

I also have them running with the original USB stick

Code:

 cgminer version 4.10.0 - Started: [2018-02-25 19:39:38.887]
--------------------------------------------------------------------------------
 (5s):136.4G (1m):140.0G (5m):134.7G (15m):126.0G (avg):111.6Gh/s
 A:2141877  R:4844  HW:1290  WU:1557.1/m
 Connected to solo.ckpool.org diff 111 with stratum as user kipper01
 Block: 5bc6cd36...  Diff:3.01T  Started: [18:47:02.957]  Best share: 74.1M
--------------------------------------------------------------------------------
 [U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
  0: GSC 10000175: BM1384:1 162.50MHz HW:0 | 4.085G / 4.458Gh/s WU: 62.3/m
  1: GSC 10000176: BM1384:1 162.50MHz HW:2 | 7.573G / 4.375Gh/s WU: 61.1/m
  2: GSC 10000177: BM1384:1 162.50MHz HW:4 | 5.760G / 4.351Gh/s WU: 60.8/m
  3: GSC 10000178: BM1384:1 162.50MHz HW:1 | 10.59G / 4.399Gh/s WU: 61.5/m
  4: GSC 10000181: BM1384:1 162.50MHz HW:0 | 2.277G / 4.384Gh/s WU: 61.3/m
  5: GSC 10000390: BM1384:1 162.50MHz HW:3 | 4.925G / 4.411Gh/s WU: 61.6/m
  6: GSC 10000391: BM1384:1 162.50MHz HW:4 | 4.357G / 4.393Gh/s WU: 61.4/m
  7: GSC 10000392: BM1384:1 162.50MHz HW:1262 | 6.917G / 4.330Gh/s WU: 58.7/m
  8: GSC 10000393: BM1384:1 162.50MHz HW:0 | 4.488G / 4.329Gh/s WU: 60.5/m
  9: GSE 10030018: BM1384:8 175.00MHz HW:13 | 21.07G / 10.64Gh/s WU:148.5/m
 10: GSE 10030022: BM1384:8 175.00MHz HW:0 | 54.51G / 30.86Gh/s WU:431.2/m
 11: GSE 10030023: BM1384:8 175.00MHz HW:1 | 42.21G / 30.66Gh/s WU:428.3/m
--------------------------------------------------------------------------------
 [2018-02-26 18:55:35.721] Accepted 01e6b264 Diff 135/111 GSE 2 pool 0
 [2018-02-26 18:55:44.686] Accepted 0209af42 Diff 126/111 GSE 1 pool 0
 [2018-02-26 18:55:44.898] Accepted 77e509c6 Diff 547/111 GSE 1 pool 0
 [2018-02-26 18:55:45.598] Accepted 01c7ad38 Diff 144/111 GSE 0 pool 0
 [2018-02-26 18:55:59.431] Accepted 02117e61 Diff 124/111 GSE 2 pool 0
 [2018-02-26 18:56:05.205] Accepted 011b4858 Diff 231/111 GSE 1 pool 0
 [2018-02-26 18:56:06.377] Accepted 019313c4 Diff 163/111 GSE 1 pool 0
 [2018-02-26 18:56:06.845] Accepted 020a417e Diff 125/111 GSE 0 pool 0

These are the hash rates you should be seeing. Btw, is anybody else's pod extremely hot on the bottom under the heat sink? I couldnt touch it for half a second it was so hot. I Have a USB fan cooling the bottom of it now and it seems to work well cooling it down.
https://ibb.co/jixgQx
https://ibb.co/c1sgQx

[lok8nusa]

Okay I will say though, if you see a note that the frequency unexpectedly changed to 200MHz, that means the hardware controls detected a string dropout and forced a reset. If you have turned the voltage down, you might turn it back up a bit.

No, the pods are awesome when they work and garbage when they don't. You haven't seen all the work I've had to do just to get some out the door, only to have an embarassingly high percentage of reported issues.

I have had three of mine running fine with no issues on Windows 10 PC for 24 hours.  I initially had one go into zombie mode and plugged into a different USB port and it has been working fine.  I thought I have had an abundance of USB 2.0 adapters for my other three but I can't find any and I forget to grab some while at work.

I also have them running with the original USB stick

Code:

 cgminer version 4.10.0 - Started: [2018-02-25 19:39:38.887]
--------------------------------------------------------------------------------
 (5s):136.4G (1m):140.0G (5m):134.7G (15m):126.0G (avg):111.6Gh/s
 A:2141877  R:4844  HW:1290  WU:1557.1/m
 Connected to solo.ckpool.org diff 111 with stratum as user kipper01
 Block: 5bc6cd36...  Diff:3.01T  Started: [18:47:02.957]  Best share: 74.1M
--------------------------------------------------------------------------------
 [U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
  0: GSC 10000175: BM1384:1 162.50MHz HW:0 | 4.085G / 4.458Gh/s WU: 62.3/m
  1: GSC 10000176: BM1384:1 162.50MHz HW:2 | 7.573G / 4.375Gh/s WU: 61.1/m
  2: GSC 10000177: BM1384:1 162.50MHz HW:4 | 5.760G / 4.351Gh/s WU: 60.8/m
  3: GSC 10000178: BM1384:1 162.50MHz HW:1 | 10.59G / 4.399Gh/s WU: 61.5/m
  4: GSC 10000181: BM1384:1 162.50MHz HW:0 | 2.277G / 4.384Gh/s WU: 61.3/m
  5: GSC 10000390: BM1384:1 162.50MHz HW:3 | 4.925G / 4.411Gh/s WU: 61.6/m
  6: GSC 10000391: BM1384:1 162.50MHz HW:4 | 4.357G / 4.393Gh/s WU: 61.4/m
  7: GSC 10000392: BM1384:1 162.50MHz HW:1262 | 6.917G / 4.330Gh/s WU: 58.7/m
  8: GSC 10000393: BM1384:1 162.50MHz HW:0 | 4.488G / 4.329Gh/s WU: 60.5/m
  9: GSE 10030018: BM1384:8 175.00MHz HW:13 | 21.07G / 10.64Gh/s WU:148.5/m
 10: GSE 10030022: BM1384:8 175.00MHz HW:0 | 54.51G / 30.86Gh/s WU:431.2/m
 11: GSE 10030023: BM1384:8 175.00MHz HW:1 | 42.21G / 30.66Gh/s WU:428.3/m
--------------------------------------------------------------------------------
 [2018-02-26 18:55:35.721] Accepted 01e6b264 Diff 135/111 GSE 2 pool 0
 [2018-02-26 18:55:44.686] Accepted 0209af42 Diff 126/111 GSE 1 pool 0
 [2018-02-26 18:55:44.898] Accepted 77e509c6 Diff 547/111 GSE 1 pool 0
 [2018-02-26 18:55:45.598] Accepted 01c7ad38 Diff 144/111 GSE 0 pool 0
 [2018-02-26 18:55:59.431] Accepted 02117e61 Diff 124/111 GSE 2 pool 0
 [2018-02-26 18:56:05.205] Accepted 011b4858 Diff 231/111 GSE 1 pool 0
 [2018-02-26 18:56:06.377] Accepted 019313c4 Diff 163/111 GSE 1 pool 0
 [2018-02-26 18:56:06.845] Accepted 020a417e Diff 125/111 GSE 0 pool 0

Are those 2Pacs, or Compacs?

[kipper01]

There's something seriously wrong with your setup, if those hashrates are to be trusted. Nothing's running more than about half as fast as it should.

I removed all the USB sticks out of the equation.  Adjusted the voltage.  Short sampling but here it is now.

Code:

 cgminer version 4.10.0 - Started: [2018-02-26 19:41:12.178]
--------------------------------------------------------------------------------
 (5s):279.0G (1m):219.6G (5m):164.3G (15m):81.16G (avg):212.9Gh/s
 A:16000  R:0  HW:1  WU:2979.1/m
 Connected to solo.ckpool.org diff 4K with stratum as user 1PxBdtknPdMuikQfbP497L8jXF85RhozSx.kipper01
 Block: 2b0ea6dc...  Diff:3.01T  Started: [19:43:32.008]  Best share: 18.5K
--------------------------------------------------------------------------------
 [U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
 0: GSE 10030018: BM1384:8 175.00MHz HW:1 | 97.08G / 71.00Gh/s WU: 990.8/m
 1: GSE 10030022: BM1384:8 175.00MHz HW:0 | 89.78G / 70.92Gh/s WU: 990.8/m
 2: GSE 10030023: BM1384:8 175.00MHz HW:0 | 88.66G / 71.40Gh/s WU: 997.5/m
--------------------------------------------------------------------------------
 [2018-02-26 19:41:19.036] Stratum from pool 1 detected new block at height 511076
 [2018-02-26 19:41:19.041] Stratum from pool 0 requested work restart
 [2018-02-26 19:41:27.776] GSE 0: setting frequency to 125.00MHz
 [2018-02-26 19:41:27.994] GSE 1: setting frequency to 125.00MHz
 [2018-02-26 19:41:28.200] GSE 2: setting frequency to 125.00MHz
 [2018-02-26 19:41:42.825] GSE 0: setting frequency to 150.00MHz
 [2018-02-26 19:41:43.023] GSE 1: setting frequency to 150.00MHz
 [2018-02-26 19:41:43.218] GSE 2: setting frequency to 150.00MHz
 [2018-02-26 19:41:57.848] GSE 0: setting frequency to 175.00MHz
 [2018-02-26 19:41:58.045] GSE 1: setting frequency to 175.00MHz
 [2018-02-26 19:41:58.241] GSE 2: setting frequency to 175.00MHz
 [2018-02-26 19:43:32.008] Stratum from pool 0 detected new block at height 511077
 [2018-02-26 19:43:33.589] Accepted 084be823 Diff 7.9K/4000 GSE 1 pool 0
 [2018-02-26 19:44:32.027] Accepted 0a467312 Diff 6.38K/4000 GSE 1 pool 0
 [2018-02-26 19:48:10.852] Pool 0 difficulty changed to 126
 [2018-02-26 19:48:10.853] Accepted 038bb3f9 Diff 18.5K/4000 GSE 0 pool 0
 [2018-02-26 19:48:18.936] Accepted 103b9b04 Diff 4.04K/4000 GSE 1 pool 0

[sidehack]

175MHz should run you 77GH

As for heat, these guys automatically kick off at 80C. Temp sensor's under the heatsink, down with the chips.

[kipper01]

Are those 2Pacs, or Compacs?

10 compacs
3 terminus

I removed the compacs till I get everything stabilized.  (I hooked up everything to look at the pretty blinking lights  )

[lok8nusa]

Are those 2Pacs, or Compacs?

10 compacs
3 terminus

I removed the compacs till I get everything stabilized.  (I hooked up everything to look at the pretty blinking lights  )

So, the hash rate might be a little low, but it's about where it needs to be on those, right?

[sidehack]

I bet if you only run 2 you'll get the full hashrate out of 'em. Could be a USB traffic limitation, same as several other people are running into.

[minerbobbert]

I bet if you only run 2 you'll get the full hashrate out of 'em. Could be a USB traffic limitation, same as several other people are running into.

Any work around to this USB issue? Such as buying a better quality USB hub?

I did some finagling and I think sidehack is right, at least in my case. I powered up all the miners and serially added them and subtracted them to the computer, each time I added a new one there was a drop in hash rate.  Makes me worried as that happened even without using the USB splitter and plugging each one into a USB 2.0 hub on my computer.

If there is no work around, am I going to need a new controller? I have an old raspberry pi 3 laying around I could dig up.  That has 4 USB ports. Has anyone had success setting up multiple termini on a raspberry pi?

Lastly - how do I turn up the frequency on these? If I can only run one for now I'd like to experiment with the higher hash rate than the default 150hz.  This is what my bat file includes but they don't go above 150.  Any ideas?

-gekko-start-freq 100 -gekko-step-freq 25 -gekko-step-delay 15 -gekko-terminus-freq 200

[sidehack]

--gekko-terminus-freq should do it.

I test them 2 at a time to a Pi at 200MHz. 3 started having issues, but 2 was okay.

Part of it is, these are run straight of a USB/UART so all work is sent straight off the USB bus. There's timing and packet count limitations that put a ceiling on effective hashrate. VH has already told me we need to conjure up a means of buffering or generating work packets onboard and save some bandwidth on the new stuff.

How many Terminus can be run off a single machine probably depends on how USB controllers are set up internally.

[vh]

I haven't spent a lot of time testing in windows.   Just catching up now.

Also keep as a testing option: running multiple cgminer with "--usb :1" or "--usb :2",
It has been reported to work in the past for windows "slower than expected speed".

This scenario is still on my to recreate list.


New build is available (d5fba8e).  Git pull and build on *unix for latest.

- fix crash in windows when detecting zero chips from 2Pac. 
  ^ does not fix low power hub issue, just prevents crash from low powered hub in windows.

windows binary:
http://23.108.83.14/images/cgminer-4.10.0-windows-gekko-d5fba8e.7z

[minerbobbert]

Also keep as a testing option: running multiple cgminer with "--usb :1" or "--usb :2",
It has been reported to work in the past for windows "slower than expected speed".

This scenario is still on my to recreate list.

In laymen's terms - does this mean the USB transfer issue is something you think is fixable and you are getting to it?

I'm currently deciding if I should be happy with one functioning unit and sell the rest, or keep working on getting all four working.

1) For the USB transfer rate, do we know the actual load that one miner demands? I think getting something with a USB 3.0 may work for multiple miners but would like to verify prior to buying a new used dedicated laptop for this.

2) I still can't run these higher than 150mhz with the bat file lines above. I'm using vh's build - will his settings supercede the settings on my bat file?

3) is it possible to mine different pools off the same control unit? Or will I need a new unit? I'd like to point one of these and my old USB miners at ck's solo pool for "hey, why not??" reasons and haven't been able to get two instances of cgminer up at the same time...

[sidehack]

1) USB 3.0 is irrelevant, this is a USB 2.0 device.

2) Did you generate a config file? Pretty sure VH said somewhere that a config file will override command-line flags, so that's something to look into. Also "the bat file lines above" have only a single leading hyphen so either you transcribed them inaccurately or there should be a syntax error being thrown somewhere. Problems are easier to diagnose when all the data is correct.

3) One cgminer instance means one pool. It's possible to run multiple pools from a single controller if you run multiple instances, which is exactly what VH states how to do in the portion you quoted. Not sure why it wouldn't work, unless there's conflicting config issues or a hardware limitation (not enough RAM, etc).

The USB transfer issue has to do with the limitations of USB 2.0 itself, possibly exacerbated by the hardware or software configuration of whatever you're using as a controller. Additionally, why sell units that aren't working? If it's the miner itself that doesn't work, take advantage of the warranty. That's irrelevant if they do in fact work and the issue is your controller setup.

[minerbobbert]

1) USB 3.0 is irrelevant, this is a USB 2.0 device.

2) Did you generate a config file? Pretty sure VH said somewhere that a config file will override command-line flags, so that's something to look into. Also "the bat file lines above" have only a single leading hyphen so either you transcribed them inaccurately or there should be a syntax error being thrown somewhere. Problems are easier to diagnose when all the data is correct.

3) One cgminer instance means one pool. It's possible to run multiple pools from a single controller if you run multiple instances, which is exactly what VH states how to do in the portion you quoted. Not sure why it wouldn't work, unless there's conflicting config issues or a hardware limitation (not enough RAM, etc).

The USB transfer issue has to do with the limitations of USB 2.0 itself, possibly exacerbated by the hardware or software configuration of whatever you're using as a controller. Additionally, why sell units that aren't working? If it's the miner itself that doesn't work, take advantage of the warranty. That's irrelevant if they do in fact work and the issue is your controller setup.

1) So even if we plugged these into a USB 3.0 splitter into a USB 3.0 drive that can handle faster data transfer, it wouldn't solve the issue. Drat.

2) Yup. That was it. I didn't have the double hyphen. I fixed that and it worked. Is the .bat file the same as the config file you mention? If not, then no I didn't. I don't know how to build my own cgminer and I'm using the updates VH is providing here. I'm not a computer science dude, I don't know how to code. I got these miners because I believe in bitcoin and I wanted to learn how to do this. I pretty much follow the instructions here to the best of my ability but most of it seems to be written for people that already have a baseline knowledge of this stuff and that means I'm pretty slow catching up.

3) He explained how to do that? Where? He said something about USB 1 and 2 commands, but going from there to different pools wasn't explained well.

Please don't misunderstand, I'm not at all worried these are defective units. I'm just not a computer literate guy who can figure this out easily. I'm perfectly happy with the pods and I am pretty sure it is just me having difficulty setting them up. I'd only sell them if I can't get them working, and I'd do that regretfully. Nothing to return under warranty because I'm pretty sure they work fine and the issues are on my end.

If any of you can explain how to set these up in simple step by step instructions, I'm pretty sure I could follow along. For now, I'm asking questions where I think I am getting stuck.

Here is the last log file of the instance I ran when trying 3 miners at 175.

 [2018-02-27 20:10:48.015] Started cgminer 4.10.0
 [2018-02-27 20:10:48.687] GSE 0: Terminus BM1384 Bitcoin Miner (10030015)
 [2018-02-27 20:10:48.953] GSE 1: Terminus BM1384 Bitcoin Miner (10030016)
 [2018-02-27 20:10:49.312] GSE 2: Terminus BM1384 Bitcoin Miner (10030017)
 [2018-02-27 20:10:49.828] GSE 0: setting frequency to 100.00MHz
 [2018-02-27 20:10:50.015] Probing for an alive pool
 [2018-02-27 20:10:50.078] GSE 1: setting frequency to 100.00MHz
 [2018-02-27 20:10:50.296] GSE 2: setting frequency to 100.00MHz
 [2018-02-27 20:10:50.296] GSE 0: open cores @ 100.00MHz
 [2018-02-27 20:10:51.078] GSE 2: open cores @ 100.00MHz
 [2018-02-27 20:10:51.078] GSE 1: open cores @ 100.00MHz
 [2018-02-27 20:10:51.296] Pool 0 difficulty changed to 4000
 [2018-02-27 20:10:51.359] Pool 0 message: Authorised, welcome to solo.ckpool.org
 [2018-02-27 20:10:51.906] Network diff set to 3.01T
 [2018-02-27 20:10:53.031] GSE 0: start work @ 100.00MHz
 [2018-02-27 20:10:53.078] GSE 1: start work @ 100.00MHz
 [2018-02-27 20:10:53.140] GSE 2: start work @ 100.00MHz
 [2018-02-27 20:11:14.484] GSE 0: setting frequency to 125.00MHz
 [2018-02-27 20:11:15.875] GSE 2: setting frequency to 125.00MHz
 [2018-02-27 20:11:16.812] GSE 1: setting frequency to 125.00MHz
 [2018-02-27 20:11:29.546] GSE 0: setting frequency to 150.00MHz
 [2018-02-27 20:11:30.937] GSE 2: setting frequency to 150.00MHz
 [2018-02-27 20:11:31.906] GSE 1: setting frequency to 150.00MHz
 [2018-02-27 20:11:44.593] GSE 0: setting frequency to 175.00MHz
 [2018-02-27 20:11:46.000] GSE 2: setting frequency to 175.00MHz
 [2018-02-27 20:11:55.671] GSE 1: setting frequency to 175.00MHz
 [2018-02-27 20:11:56.906] Stratum from pool 0 detected new block at height 511262
 [2018-02-27 20:12:22.453] GSE 1: usb failure (-9)
 [2018-02-27 20:12:22.453] GSE 1 failure, disabling!
 [2018-02-27 20:12:22.453] GSE 1: setting frequency to 100.00MHz
 [2018-02-27 20:12:24.250] GSE 3: Terminus BM1384 Bitcoin Miner (10030016)
 [2018-02-27 20:12:24.484] Hotplug: GekkoScience added GSE 3
 [2018-02-27 20:12:24.703] GSE 3: setting frequency to 100.00MHz
 [2018-02-27 20:12:24.765] GSE 3: open cores @ 100.00MHz
 [2018-02-27 20:12:26.515] GSE 3: start work @ 100.00MHz
 [2018-02-27 20:12:43.781] GSE 3: setting frequency to 125.00MHz
 [2018-02-27 20:13:02.187] GSE 3: setting frequency to 150.00MHz
 [2018-02-27 20:13:18.421] GSE 3: setting frequency to 175.00MHz
 [2018-02-27 20:14:09.312] Accepted 0b6e8269 Diff 5.73K/4000 GSE 0
 [2018-02-27 20:14:34.140] GSE 0: usb failure (-9)
 [2018-02-27 20:14:34.140] GSE 0 failure, disabling!
 [2018-02-27 20:14:34.140] GSE 0: setting frequency to 100.00MHz
 [2018-02-27 20:14:38.921] GSE 4: Terminus BM1384 Bitcoin Miner (10030015)
 [2018-02-27 20:14:39.140] Hotplug: GekkoScience added GSE 4
 [2018-02-27 20:14:39.359] GSE 4: setting frequency to 100.00MHz
 [2018-02-27 20:14:39.421] GSE 4: open cores @ 100.00MHz
 [2018-02-27 20:14:41.187] GSE 4: start work @ 100.00MHz
 [2018-02-27 20:14:48.218] GSE 2: setting frequency to 100.00MHz
 [2018-02-27 20:14:48.218] GSE 3: setting frequency to 100.00MHz
 [2018-02-27 20:14:49.281] Shutdown signal received.
 [2018-02-27 20:14:49.328]
Summary of runtime statistics:

 [2018-02-27 20:14:49.328] Started at [2018-02-27 20:10:51.890]
 [2018-02-27 20:14:49.343] Pool: stratum+tcp://solo.ckpool.org:3333
 [2018-02-27 20:14:49.343] Runtime: 0 hrs : 3 mins : 57 secs
 [2018-02-27 20:14:49.343] Average hashrate: 120120.2 Mhash/s
 [2018-02-27 20:14:49.343] Solved blocks: 0
 [2018-02-27 20:14:49.343] Best share difficulty: 5.73K
 [2018-02-27 20:14:49.343] Share submissions: 1
 [2018-02-27 20:14:49.343] Accepted shares: 1
 [2018-02-27 20:14:49.343] Rejected shares: 0
 [2018-02-27 20:14:49.343] Accepted difficulty shares: 4000
 [2018-02-27 20:14:49.359] Rejected difficulty shares: 0
 [2018-02-27 20:14:49.359] Reject ratio: 0.0%
 [2018-02-27 20:14:49.359] Hardware errors: 0
 [2018-02-27 20:14:49.359] Utility (accepted shares / min): 0.25/min
 [2018-02-27 20:14:49.359] Work Utility (diff1 shares solved / min): 1678.08/min

 [2018-02-27 20:14:49.359] Stale submissions discarded due to new blocks: 0
 [2018-02-27 20:14:49.359] Unable to get work from server occasions: 0
 [2018-02-27 20:14:49.375] Work items generated locally: 18585
 [2018-02-27 20:14:49.375] Submitting work remotely delay occasions: 0
 [2018-02-27 20:14:49.375] New blocks detected on network: 2

 [2018-02-27 20:14:49.375] Summary of per device statistics:

 [2018-02-27 20:14:49.375] GSE 0 (5s):15.58G (avg):42.95Gh/s | A:4000 R:0 HW:0 WU:600.0/m
 [2018-02-27 20:14:49.375] GSE 1 (5s):35.59M (avg):10.19Gh/s | A:0 R:0 HW:0 WU:142.4/m
 [2018-02-27 20:14:49.390] GSE 2 (5s):41.09G (avg):45.43Gh/s | A:0 R:0 HW:0 WU:634.6/m
 [2018-02-27 20:14:49.390] GSE 3 (5s):37.18G (avg):32.91Gh/s | A:0 R:0 HW:0 WU:459.7/m
 [2018-02-27 20:14:49.390] GSE 4 (5s):30.38G (avg):29.54Gh/s | A:0 R:0 HW:0 WU:412.7/m
 [2018-02-27 20:14:49.390]  

[sidehack]

Also keep as a testing option: running multiple cgminer with "--usb :1" or "--usb :2",
It has been reported to work in the past for windows "slower than expected speed".

This scenario is still on my to recreate list.

...

3) is it possible to mine different pools off the same control unit? Or will I need a new unit? I'd like to point one of these and my old USB miners at ck's solo pool for "hey, why not??" reasons and haven't been able to get two instances of cgminer up at the same time...

3) One cgminer instance means one pool. It's possible to run multiple pools from a single controller if you run multiple instances, which is exactly what VH states how to do in the portion you quoted. Not sure why it wouldn't work, unless there's conflicting config issues or a hardware limitation (not enough RAM, etc).

3) He explained how to do that? Where? He said something about USB 1 and 2 commands, but going from there to different pools wasn't explained well.

I'll give you a hint. The --usb :1 command is explained in cgminer's README file. Basically, the number tells cgminer how many USB devices to use. So you start a cgminer instance to run one device pointed at one pool, then start a second running one device and configured for a different pool.

Based on your log there, it looks like the miners are detected and trying to run. I'd run each one individually for an hour or so and see how they behave on their own.

[jdesarro]

Just cloned VH's latest from git and recompiled.  Running CGMINER with only pool and sugg-diff 40 switches.  All cmd line, no config file (need to work the JSON fail at start up sometime in the future).

Really grateful at how frequent the versions and potential solutions are coming, but problem hasn't changed for my single Terminus, Ubuntu PC, supplied 12V brick, 1 ea Terminus, 2PAC and COMPAC, pot turned to max CW (5:00) position.

Terminus runs error free for about 15 minutes when starting cold, then there are about 4-5 of these a minute:

[2018-02-27 21:54:05.405] GSE 0 failure, disabling!                    
 [2018-02-27 21:54:06.338] GSE 1: Terminus BM1384 Bitcoin Miner (10030035)                    
 [2018-02-27 21:54:06.548] Hotplug: GekkoScience added GSE 1                    
 [2018-02-27 21:54:06.771] GSE 1: setting frequency to 100.00MHz                    
 [2018-02-27 21:54:06.792] GSE 1: open cores @ 100.00MHz                    
 [2018-02-27 21:54:08.488] GSE 1: start work @ 100.00MHz                    
 [2018-02-27 21:54:13.104] GSE 1 failure, disabling!                    
 [2018-02-27 21:54:17.023] GSE 2: Terminus BM1384 Bitcoin Miner (10030035)                    
 [2018-02-27 21:54:17.233] Hotplug: GekkoScience added GSE 2                    
 [2018-02-27 21:54:17.456] GSE 2: setting frequency to 100.00MHz                    
 [2018-02-27 21:54:17.477] GSE 2: open cores @ 100.00MHz                    
 [2018-02-27 21:54:19.168] GSE 2: start work @ 100.00MHz                    
 [2018-02-27 21:54:20.735] GSE 2 failure, disabling!                    
 [2018-02-27 21:54:22.544] GSE 3: Terminus BM1384 Bitcoin Miner (10030035)                    
 [2018-02-27 21:54:22.754] Hotplug: GekkoScience added GSE 3                    
 [2018-02-27 21:54:22.977] GSE 3: setting frequency to 100.00MHz                    
 [2018-02-27 21:54:22.998] GSE 3: open cores @ 100.00MHz                    
 [2018-02-27 21:54:24.692] GSE 3: start work @ 100.00MHz                    
 [2018-02-27 21:54:39.846] GSE 3: setting frequency to 125.00MHz                    
 [2018-02-27 21:54:45.419] GSE 3 failure, disabling!                    
 [2018-02-27 21:54:45.419] GSE 3: setting frequency to 100.00MHz                    

Questions:
- There are chips that look like the ASICS on the 2PAC on the Terminus, would voltage readings across those be of any value?
- How long can it run with these restarts without damage?  I'm hashing faster than with just the two little brothers, but I don't want to release the magic smoke from the 808 as I try the s/w updates.
- How high can the serial after GSE (i.e. GSE 1, GSE 2,...) go?  I've seen as high as a 100 or so, but generally restart after that.

Many many thanks, if I ever get the herp to clear dust, and power through my postponements, I'll gladly split that massive payday.  If I hit a block I've never heard of any of you ha ha

[vh]

3) He explained how to do that? Where? He said something about USB 1 and 2 commands, but going from there to different pools wasn't explained well.

open up a command prompt.
navigate to the folder that you unzipped (d5fba8e) to.
run "cgminer.exe -o stratum+tcp://pool.ckpool.org:3333 -u 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr -p x --usb :1"

wait to see if miner can reach 66Gh/s...

open up a new command prompt.
navigate to the folder that you unzipped (d5fba8e) to.
run "cgminer.exe -o stratum+tcp://pool.ckpool.org:3333 -u 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr -p x --usb :1"

wait to see if miner can reach 66Gh/s...

open up a new command prompt.
navigate to the folder that you unzipped (d5fba8e) to.
run "cgminer.exe -o stratum+tcp://solo.ckpool.org:3333 -u 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr -p x --usb :1"


wait and don't change anything else (that third one is a different pool).



^note that there is only 3 miners in the example above that are on.

don't add that forth one for at least 24 hours and don't use your "splitter" or hub.   
leave that hub and any usb extension cables out of this setup.

[vh]

Just cloned VH's latest from git and recompiled.  Running CGMINER with only pool and sugg-diff 40 switches.  All cmd line, no config file
...
 [2018-02-27 21:54:08.488] GSE 1: start work @ 100.00MHz                    
 [2018-02-27 21:54:13.104] GSE 1 failure, disabling!                    
 [2018-02-27 21:54:17.023] GSE 2: Terminus BM1384 Bitcoin Miner (10030035)                    
 [2018-02-27 21:54:17.233] Hotplug: GekkoScience added GSE 2                    

You might not be on the latest code.   The latest code will have this extra line.

...
 [2018-02-27 20:12:22.453] GSE 1: usb failure (-9)
 [2018-02-27 20:12:22.453] GSE 1 failure, disabling!
 [2018-02-27 20:12:22.453] GSE 1: setting frequency to 100.00MHz
 [2018-02-27 20:12:24.250] GSE 3: Terminus BM1384 Bitcoin Miner (10030016)
 [2018-02-27 20:12:24.484] Hotplug: GekkoScience added GSE 3

That might point to an issue GSE 1: usb failure (-9) = a wiring or hub problem.

[sidehack]

Ooh handy, error codes. Gonna have to update my testing station.

Yes, voltages across the different nodes would be handy. Maybe on the reset pin also.

Wait, you're looking at the chips? You pulled off the heatsink?

When it re-enumerates, does it tell you how many chips are detected? VH, I don't know if updated version of your software mention how many chips are detected (the old version on my bench computer does) but that's useful diagnostic info.

[vh]

I tucked it down at a different log level away from general public.    
Just updated and check into master branch.

It should display again now without needing to enable verbose.
I can see it being useful enough to stay there.

edit:
windows binary for update above:
cgminer-4.10.0-windows-gekko-4746da4.7z
cgminer-4.10.0-windows-gekko-1fccd3d.7z

[goose1072]

Just tried the latest code on one of my troubled Terminus, still having issues and still does not come out of Zombie no matter what I try.

This is what it shows when I start up:

Code:

 [2018-02-27 23:44:58.731] GSE 1: Terminus BM1384 Bitcoin Miner (10030033)
 [2018-02-27 23:44:58.934] Hotplug: GekkoScience added GSE 1
 [2018-02-27 23:44:58.934] GSE 1 failure, disabling!
 [2018-02-27 23:44:58.935] GSE 1: setting frequency to 100.00MHz
 [2018-02-27 23:45:04.466] GSE 2: Terminus BM1384 Bitcoin Miner (10030033)
 [2018-02-27 23:45:04.669] Hotplug: GekkoScience added GSE 2
 [2018-02-27 23:45:04.670] GSE 2 failure, disabling!
 [2018-02-27 23:45:04.670] GSE 2: setting frequency to 100.00MHz
 [2018-02-27 23:45:10.203] GSE 3: Terminus BM1384 Bitcoin Miner (10030033)
 [2018-02-27 23:45:10.408] Hotplug: GekkoScience added GSE 3
 [2018-02-27 23:45:10.409] GSE 3 failure, disabling!
 [2018-02-27 23:45:10.409] GSE 3: setting frequency to 100.00MHz
 [2018-02-27 23:45:15.940] GSE 4: Terminus BM1384 Bitcoin Miner (10030033)
 [2018-02-27 23:45:16.143] Hotplug: GekkoScience added GSE 4
 [2018-02-27 23:45:16.143] GSE 4 failure, disabling!
 [2018-02-27 23:45:16.143] GSE 4: setting frequency to 100.00MHz

It just continues to count up on the GSE

Sidehack will be shipping them tomorrow hopefully you can figure these two out.