Quote
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
) 
Topic: GekkoScience Terminus R808 Miner Official Support Thread - page 17. (Read 16917 times)
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
) 
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.
As for heat, these guys automatically kick off at 80C. Temp sensor's under the heatsink, down with the chips.
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
--------------------------------------------------------------------------------
(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
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.
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.
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
--------------------------------------------------------------------------------
(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 pods are having a lot more trouble than they should. Not sure what's up, but they kinda suck.
I'm happy with mine. My troubles are based on my incompetence with computer stuff, not the miners. I'm happy to keep chugging along figuring these out.
zachj00: Do they automatically go zombie as soon as you start them up in cgminer?
Computer has no problems seeing them, I have tried different usb cables, PSU & computer with no luck.
I have a few raspi, will grab one and set it up to see if it comes back to life.
When I started 2 on my MacBook, they ran great for about an hour then went one went into zombie and the other into off mode. I plugged them back in twice, each time running shorter (5ish minutes). After reading your post I didn't restart them for fear that they might become "permanent zombies". I used the older CGminer and the updated one. My rpi3 one running with my 2pacs is still trucking along with no errors.(using the older driver for my pi) Computer has no problems seeing them, I have tried different usb cables, PSU & computer with no luck.
I have a few raspi, will grab one and set it up to see if it comes back to life.
zachj00: Do they automatically go zombie as soon as you start them up in cgminer?
Computer has no problems seeing them, I have tried different usb cables, PSU & computer with no luck.
I have a few raspi, will grab one and set it up to see if it comes back to life.
Computer has no problems seeing them, I have tried different usb cables, PSU & computer with no luck.
I have a few raspi, will grab one and set it up to see if it comes back to life.
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.
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.
Goose - I'll be honest, cgminer logs are useless for the kind of diagnosing that'd help me solve a problem. If you don't have an O-scope or at least a decent multimeter you're probably better off sending it back for me to look at it myself.
These pods are having a lot more trouble than they should. Not sure what's up, but they kinda suck.
Dont say that! the pods are awesome! seems most people are having trouble running it off windows/mac. Is anybody with a rpi3 set up having any issues? These pods are having a lot more trouble than they should. Not sure what's up, but they kinda suck.
Goose - I'll be honest, cgminer logs are useless for the kind of diagnosing that'd help me solve a problem. If you don't have an O-scope or at least a decent multimeter you're probably better off sending it back for me to look at it myself.
These pods are having a lot more trouble than they should. Not sure what's up, but they kinda suck.
These pods are having a lot more trouble than they should. Not sure what's up, but they kinda suck.
I'm gonna say this again then.
Does your old laptop also have old USB (like 1.1 vs 2.0)? It's incredibly unlikely that power is costing you hashrate. Power's sort of an all-or-nothing deal. What could be costing you is trying to run too high a frequency for the voltage setting and the string trips out and resets
What about that part? That's what made me worried the power was insufficient or the voltage set too low.
As far as the USB, the ports are all usb 2, so I believe they should work. Is there a way to stress test the usb drives or troubleshoot if that is indeed the problem?
You ruled that part out when you tested them individually and they worked.
The way I'd see if USB throughput was the issue is by plugging one in, then a second, and so on until you start seeing trouble like the hashrate topping out at a certain level regardless how many miners are plugged in.
Sidehack,
I am having problem with 2 of the 4 Terminus I received.
I had them connected to a 750w PSU, all started with no issues.
then I had one go zombie, I powered it off and on and it didn't work.
Now I have 2 go zombie and I can't seem to get them to work again.
I have tried one at a time with no luck, have also tried on a freshly built windows machine with no luck.
No sure what steps to take, any help would be very much appreciated.
Here are a couple of logs I have from testing them.
Cgminer shuts down right after.
This is from the 2 that are currently working with no issues:
Thanks.
I am having problem with 2 of the 4 Terminus I received.
I had them connected to a 750w PSU, all started with no issues.
then I had one go zombie, I powered it off and on and it didn't work.
Now I have 2 go zombie and I can't seem to get them to work again.
I have tried one at a time with no luck, have also tried on a freshly built windows machine with no luck.
No sure what steps to take, any help would be very much appreciated.
Here are a couple of logs I have from testing them.
Code:
[2018-02-26 11:20:10.459] Started cgminer 4.10.0
[2018-02-26 11:20:10.816] GSE 0: Terminus BM1384 Bitcoin Miner (10030034)
[2018-02-26 11:20:11.020] Probing for an alive pool
[2018-02-26 11:20:11.305] Pool 0 difficulty changed to 524288
[2018-02-26 11:20:11.305] Network diff set to 8.66G
[2018-02-26 11:20:17.376] GSE 1: Terminus BM1384 Bitcoin Miner (10030034)
[2018-02-26 11:20:17.578] Hotplug: GekkoScience added GSE 1
[2018-02-26 11:20:23.134] GSE 2: Terminus BM1384 Bitcoin Miner (10030034)
[2018-02-26 11:20:23.337] Hotplug: GekkoScience added GSE 2
[2018-02-26 11:20:10.816] GSE 0: Terminus BM1384 Bitcoin Miner (10030034)
[2018-02-26 11:20:11.020] Probing for an alive pool
[2018-02-26 11:20:11.305] Pool 0 difficulty changed to 524288
[2018-02-26 11:20:11.305] Network diff set to 8.66G
[2018-02-26 11:20:17.376] GSE 1: Terminus BM1384 Bitcoin Miner (10030034)
[2018-02-26 11:20:17.578] Hotplug: GekkoScience added GSE 1
[2018-02-26 11:20:23.134] GSE 2: Terminus BM1384 Bitcoin Miner (10030034)
[2018-02-26 11:20:23.337] Hotplug: GekkoScience added GSE 2
Cgminer shuts down right after.
This is from the 2 that are currently working with no issues:
Code:
[2018-02-26 11:33:21.587] Started cgminer 4.10.0
[2018-02-26 11:33:21.949] GSE 0: Terminus BM1384 Bitcoin Miner (10030031)
[2018-02-26 11:33:22.011] GSE 1: Terminus BM1384 Bitcoin Miner (10030032)
[2018-02-26 11:33:22.434] Probing for an alive pool
[2018-02-26 11:33:22.444] GSE 0: setting frequency to 100.00MHz
[2018-02-26 11:33:22.456] GSE 0: open cores @ 100.00MHz
[2018-02-26 11:33:22.657] GSE 1: setting frequency to 100.00MHz
[2018-02-26 11:33:22.672] GSE 1: open cores @ 100.00MHz
[2018-02-26 11:33:22.757] Pool 0 difficulty changed to 524288
[2018-02-26 11:33:22.758] Network diff set to 8.66G
[2018-02-26 11:33:24.114] GSE 0: start work @ 100.00MHz
[2018-02-26 11:33:24.329] GSE 1: start work @ 100.00MHz
[2018-02-26 11:33:39.168] GSE 0: setting frequency to 125.00MHz
[2018-02-26 11:33:39.344] GSE 1: setting frequency to 125.00MHz
[2018-02-26 11:33:53.209] Stratum from pool 0 detected new block at height 505152
[2018-02-26 11:33:54.224] GSE 0: setting frequency to 150.00MHz
[2018-02-26 11:33:54.366] GSE 1: setting frequency to 150.00MHz
[2018-02-26 11:34:14.619] GSE 1: frequency changed 150.00MHz -> 200.00MHz
[2018-02-26 11:34:16.012] GSE 1: setting frequency to 200.00MHz
[2018-02-26 11:34:20.957] GSE 1: setting frequency to 200.00MHz
[2018-02-26 11:34:27.757] Stratum reconnect requested from pool 0 to sha256.usa.nicehash.com:3334
[2018-02-26 11:34:28.076] Pool 0 difficulty changed to 524288
[2018-02-26 11:34:28.077] Network diff set to 3.01T
[2018-02-26 11:34:28.077] Stratum from pool 0 detected new block at height 511017
[2018-02-26 11:34:35.974] GSE 1: setting frequency to 175.00MHz
[2018-02-26 11:34:48.313] Stratum connection to pool 0 interrupted
[2018-02-26 11:34:48.659] Pool 0 difficulty changed to 524288
[2018-02-26 11:34:48.661] Stratum from pool 0 requested work restart
[2018-02-26 11:34:51.050] Network diff set to 8.66G
[2018-02-26 11:34:51.050] Stratum from pool 0 detected new block at height 505153
[2018-02-26 11:34:53.770] GSE 1: setting frequency to 150.00MHz
[2018-02-26 11:36:05.255] Stratum reconnect requested from pool 0 to sha256.usa.nicehash.com:3334
[2018-02-26 11:36:05.556] Pool 0 difficulty changed to 524288
[2018-02-26 11:36:05.556] Stratum from pool 0 requested work restart
[2018-02-26 11:38:13.453] Stratum connection to pool 0 interrupted
[2018-02-26 11:38:13.741] Pool 0 difficulty changed to 524288
[2018-02-26 11:38:13.743] Stratum from pool 0 requested work restart
[2018-02-26 11:39:02.026] Stratum reconnect requested from pool 0 to sha256.usa.nicehash.com:3334
[2018-02-26 11:39:02.323] Pool 0 difficulty changed to 524288
[2018-02-26 11:39:02.324] Stratum from pool 0 requested work restart
[2018-02-26 11:39:40.015] Stratum connection to pool 0 interrupted
[2018-02-26 11:39:40.294] Pool 0 difficulty changed to 524288
[2018-02-26 11:33:21.949] GSE 0: Terminus BM1384 Bitcoin Miner (10030031)
[2018-02-26 11:33:22.011] GSE 1: Terminus BM1384 Bitcoin Miner (10030032)
[2018-02-26 11:33:22.434] Probing for an alive pool
[2018-02-26 11:33:22.444] GSE 0: setting frequency to 100.00MHz
[2018-02-26 11:33:22.456] GSE 0: open cores @ 100.00MHz
[2018-02-26 11:33:22.657] GSE 1: setting frequency to 100.00MHz
[2018-02-26 11:33:22.672] GSE 1: open cores @ 100.00MHz
[2018-02-26 11:33:22.757] Pool 0 difficulty changed to 524288
[2018-02-26 11:33:22.758] Network diff set to 8.66G
[2018-02-26 11:33:24.114] GSE 0: start work @ 100.00MHz
[2018-02-26 11:33:24.329] GSE 1: start work @ 100.00MHz
[2018-02-26 11:33:39.168] GSE 0: setting frequency to 125.00MHz
[2018-02-26 11:33:39.344] GSE 1: setting frequency to 125.00MHz
[2018-02-26 11:33:53.209] Stratum from pool 0 detected new block at height 505152
[2018-02-26 11:33:54.224] GSE 0: setting frequency to 150.00MHz
[2018-02-26 11:33:54.366] GSE 1: setting frequency to 150.00MHz
[2018-02-26 11:34:14.619] GSE 1: frequency changed 150.00MHz -> 200.00MHz
[2018-02-26 11:34:16.012] GSE 1: setting frequency to 200.00MHz
[2018-02-26 11:34:20.957] GSE 1: setting frequency to 200.00MHz
[2018-02-26 11:34:27.757] Stratum reconnect requested from pool 0 to sha256.usa.nicehash.com:3334
[2018-02-26 11:34:28.076] Pool 0 difficulty changed to 524288
[2018-02-26 11:34:28.077] Network diff set to 3.01T
[2018-02-26 11:34:28.077] Stratum from pool 0 detected new block at height 511017
[2018-02-26 11:34:35.974] GSE 1: setting frequency to 175.00MHz
[2018-02-26 11:34:48.313] Stratum connection to pool 0 interrupted
[2018-02-26 11:34:48.659] Pool 0 difficulty changed to 524288
[2018-02-26 11:34:48.661] Stratum from pool 0 requested work restart
[2018-02-26 11:34:51.050] Network diff set to 8.66G
[2018-02-26 11:34:51.050] Stratum from pool 0 detected new block at height 505153
[2018-02-26 11:34:53.770] GSE 1: setting frequency to 150.00MHz
[2018-02-26 11:36:05.255] Stratum reconnect requested from pool 0 to sha256.usa.nicehash.com:3334
[2018-02-26 11:36:05.556] Pool 0 difficulty changed to 524288
[2018-02-26 11:36:05.556] Stratum from pool 0 requested work restart
[2018-02-26 11:38:13.453] Stratum connection to pool 0 interrupted
[2018-02-26 11:38:13.741] Pool 0 difficulty changed to 524288
[2018-02-26 11:38:13.743] Stratum from pool 0 requested work restart
[2018-02-26 11:39:02.026] Stratum reconnect requested from pool 0 to sha256.usa.nicehash.com:3334
[2018-02-26 11:39:02.323] Pool 0 difficulty changed to 524288
[2018-02-26 11:39:02.324] Stratum from pool 0 requested work restart
[2018-02-26 11:39:40.015] Stratum connection to pool 0 interrupted
[2018-02-26 11:39:40.294] Pool 0 difficulty changed to 524288
Thanks.
I'm gonna say this again then.
Does your old laptop also have old USB (like 1.1 vs 2.0)? It's incredibly unlikely that power is costing you hashrate. Power's sort of an all-or-nothing deal. What could be costing you is trying to run too high a frequency for the voltage setting and the string trips out and resets
What about that part? That's what made me worried the power was insufficient or the voltage set too low.
As far as the USB, the ports are all usb 2, so I believe they should work. Is there a way to stress test the usb drives or troubleshoot if that is indeed the problem?
I'm gonna say this again then.
Does your old laptop also have old USB (like 1.1 vs 2.0)? It's incredibly unlikely that power is costing you hashrate. Power's sort of an all-or-nothing deal. What could be costing you is trying to run too high a frequency for the voltage setting and the string trips out and resets, or your USB throughput sucks and they're not getting enough work to stay busy.
What frequency are you trying to run at? Does your old laptop also have old USB (like 1.1 vs 2.0)? It's incredibly unlikely that power is costing you hashrate. Power's sort of an all-or-nothing deal. What could be costing you is trying to run too high a frequency for the voltage setting and the string trips out and resets, or your USB throughput sucks and they're not getting enough work to stay busy.
...I suspect it may indeed be the voltage setting. How do I adjust that? These didn't come with an instruction manual so I want to make sure I do this properly without potentially damaging the units...Bumping my own question to be more specific:
The voltage adjuster pictured above looks like what I need to address.
1) do I only adjust on the miner or do I also need to change software settings?
2) clockwise or counter clockwise?
3) how do I know it's been adjusted enough vs too much? There aren't any scales on the dial to titrate to...
Edit:
So I did some more fidgeting and tried each miner as a lone unit and they each can reach the 66ghash at 150 hz. So my problem is trying to run them together and most likely a power issue.
My setup is all 4 miners each with the AC adapter provided by sidehack and the power cord of the laptop running off a surge protector from a standard US 120V outlet. At a draw of 3 volts total for the highest setting from the chart above I should easily be able to do this.
What is wrong with this?
Thanks for that.
Your error means you need to update the driver for the miners. Use the zadig program linked in the 2pac thread... I'm on mobile so don't have it right now...
Your error means you need to update the driver for the miners. Use the zadig program linked in the 2pac thread... I'm on mobile so don't have it right now...
I tried that already, no luck.
Unless there is an update on zadig.
Going to try a freshly build laptop, fresh install of drivers and see what I get.
Jump to: