Bitcoin Forum
June 18, 2018, 07:54:43 PM *
News: Latest stable version of Bitcoin Core: 0.16.1  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: « 1 [2] 3 4 5 6 7 8 9 10 11 12 13 14 15 »  All
  Print  
Author Topic: GekkoScience Terminus R808 Miner Official Support Thread  (Read 4080 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
goose1072
Full Member
***
Offline Offline

Activity: 236
Merit: 100


View Profile
February 25, 2018, 07:15:55 AM
 #21

Hey vh,

I am trying to run the new build for windows (eb57c34) and can't seem to make it work.

This comes up then closes:

 [2018-02-25 02:11:18.520] Started cgminer 4.10.0
 [2018-02-25 02:11:18.842] GSD 0: 2Pac BM1384 Bitcoin Miner (10019295)
 [2018-02-25 02:11:18.906] GSE 0: Terminus BM1384 Bitcoin Miner (10030031)
 [2018-02-25 02:11:18.970] GSE 1: Terminus BM1384 Bitcoin Miner (10030032)
 [2018-02-25 02:11:19.033] GSE 2: Terminus BM1384 Bitcoin Miner (10030033)
 [2018-02-25 02:11:19.097] GSE 3: Terminus BM1384 Bitcoin Miner (10030034)
 [2018-02-25 02:11:19.736] GSE 0: setting frequency to 100.00MHz
 [2018-02-25 02:11:19.748] GSE 0: open cores @ 100.00MHz
 [2018-02-25 02:11:19.946] GSE 1: setting frequency to 100.00MHz
 [2018-02-25 02:11:19.959] GSE 1: open cores @ 100.00MHz
 [2018-02-25 02:11:20.133] Probing for an alive pool
 [2018-02-25 02:11:20.409] Pool 0 difficulty changed to 524288
 [2018-02-25 02:11:20.409] Network diff set to 584M
 [2018-02-25 02:11:21.530] GSE 0: start work @ 100.00MHz
 [2018-02-25 02:11:21.738] GSE 1: start work @ 100.00MHz
 [2018-02-25 02:11:26.442] GSE 4: Terminus BM1384 Bitcoin Miner (10030033)
 [2018-02-25 02:11:26.507] GSE 5: Terminus BM1384 Bitcoin Miner (10030034)
 [2018-02-25 02:11:26.711] Hotplug: GekkoScience added GSE 4
 [2018-02-25 02:11:26.916] Hotplug: GekkoScience added GSE 5


not getting any on them working now, I can supply the log file if you like.
1529351683
Hero Member
*
Offline Offline

Posts: 1529351683

View Profile Personal Message (Offline)

Ignore
1529351683
Reply with quote  #2

1529351683
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1529351683
Hero Member
*
Offline Offline

Posts: 1529351683

View Profile Personal Message (Offline)

Ignore
1529351683
Reply with quote  #2

1529351683
Report to moderator
1529351683
Hero Member
*
Offline Offline

Posts: 1529351683

View Profile Personal Message (Offline)

Ignore
1529351683
Reply with quote  #2

1529351683
Report to moderator
1529351683
Hero Member
*
Offline Offline

Posts: 1529351683

View Profile Personal Message (Offline)

Ignore
1529351683
Reply with quote  #2

1529351683
Report to moderator
vh
Hero Member
*****
Offline Offline

Activity: 603
Merit: 552


View Profile
February 25, 2018, 02:42:48 PM
 #22

Hey vh,

I am trying to run the new build for windows (eb57c34) and can't seem to make it work.


I just read through your couple of posts.

In your case, I suspect sipolar + windows = usb write errors.

I have a Sipolar 30 and it's plagued with usb write errors in windows 7.
I haven't plugged it into windows since I bought it.

My sipolar works perfectly connected to a RPi3 though

minerbobbert
Member
**
Offline Offline

Activity: 149
Merit: 10


View Profile
February 25, 2018, 03:52:18 PM
 #23

How are you guys getting the log files of these errors?
goose1072
Full Member
***
Offline Offline

Activity: 236
Merit: 100


View Profile
February 25, 2018, 04:16:08 PM
 #24

Hey vh,

I am trying to run the new build for windows (eb57c34) and can't seem to make it work.


I just read through your couple of posts.

In your case, I suspect sipolar + windows = usb write errors.

I have a Sipolar 30 and it's plagued with usb write errors in windows 7.
I haven't plugged it into windows since I bought it.

My sipolar works perfectly connected to a RPi3 though

vh,

I am not using the Sipolar on these, it's a Plugable usb hub.

I have disabled the 2pac and the 2 zombie 808, I have the 2 running now but getting different errors.



Code:
[2018-02-25 11:14:35.946] Started cgminer 4.10.0
 [2018-02-25 11:14:35.950] Loaded configuration file cgminer.conf
 [2018-02-25 11:14:36.316] USB init, open device failed, err -12,
 [2018-02-25 11:14:36.316] You need to install a WinUSB driver for - BSC device 1:6
 [2018-02-25 11:14:36.316] And associate - BSC device 1:6 with WinUSB using zadig
 [2018-02-25 11:14:36.316] See README.txt file included for help
 [2018-02-25 11:14:36.316] GekkoScience detect (1:6) failed to initialise (incorrect device?), resetting
 [2018-02-25 11:14:36.316] failed usb_init
 [2018-02-25 11:14:36.386] GSE 0: Terminus BM1384 Bitcoin Miner (10030031)
 [2018-02-25 11:14:36.451] GSE 1: Terminus BM1384 Bitcoin Miner (10030032)
 [2018-02-25 11:14:36.501] USB init, open device failed, err -12,
 [2018-02-25 11:14:36.501] You need to install a WinUSB driver for - BSC device 1:11
 [2018-02-25 11:14:36.501] And associate - BSC device 1:11 with WinUSB using zadig
 [2018-02-25 11:14:36.501] See README.txt file included for help
 [2018-02-25 11:14:36.501] GekkoScience detect (1:11) failed to initialise (incorrect device?), resetting
 [2018-02-25 11:14:36.501] failed usb_init
 [2018-02-25 11:14:36.551] USB init, open device failed, err -12,
 [2018-02-25 11:14:36.551] You need to install a WinUSB driver for - BSC device 1:10
 [2018-02-25 11:14:36.551] And associate - BSC device 1:10 with WinUSB using zadig
 [2018-02-25 11:14:36.551] See README.txt file included for help
 [2018-02-25 11:14:36.552] GekkoScience detect (1:10) failed to initialise (incorrect device?), resetting
 [2018-02-25 11:14:36.552] failed usb_init
 [2018-02-25 11:14:36.973] Probing for an alive pool
 [2018-02-25 11:14:36.987] GSE 0: setting frequency to 100.00MHz
 [2018-02-25 11:14:36.999] GSE 0: open cores @ 100.00MHz
 [2018-02-25 11:14:37.196] GSE 1: setting frequency to 100.00MHz
 [2018-02-25 11:14:37.210] GSE 1: open cores @ 100.00MHz
 [2018-02-25 11:14:37.276] Pool 0 difficulty changed to 524288
 [2018-02-25 11:14:37.276] Network diff set to 819M
 [2018-02-25 11:14:38.658] GSE 0: start work @ 100.00MHz
 [2018-02-25 11:14:38.872] GSE 1: start work @ 100.00MHz
 [2018-02-25 11:14:41.373] Network diff set to 787M
 [2018-02-25 11:14:41.373] Stratum from pool 0 detected new block at height 6149082
 [2018-02-25 11:14:43.331] USB init, open device failed, err -12,
 [2018-02-25 11:14:43.332] You need to install a WinUSB driver for - BSC device 1:6
 [2018-02-25 11:14:43.332] And associate - BSC device 1:6 with WinUSB using zadig
 [2018-02-25 11:14:43.333] See README.txt file included for help
 [2018-02-25 11:14:43.334] GekkoScience detect (1:6) failed to initialise (incorrect device?), resetting
 [2018-02-25 11:14:43.334] failed usb_init
 [2018-02-25 11:14:43.385] USB init, open device failed, err -12,
 [2018-02-25 11:14:43.385] You need to install a WinUSB driver for - BSC device 1:11
 [2018-02-25 11:14:43.386] And associate - BSC device 1:11 with WinUSB using zadig
 [2018-02-25 11:14:43.386] See README.txt file included for help
 [2018-02-25 11:14:43.387] GekkoScience detect (1:11) failed to initialise (incorrect device?), resetting
 [2018-02-25 11:14:43.387] failed usb_init
 [2018-02-25 11:14:43.438] USB init, open device failed, err -12,
 [2018-02-25 11:14:43.438] You need to install a WinUSB driver for - BSC device 1:10
 [2018-02-25 11:14:43.439] And associate - BSC device 1:10 with WinUSB using zadig
 [2018-02-25 11:14:43.440] See README.txt file included for help
 [2018-02-25 11:14:43.440] GekkoScience detect (1:10) failed to initialise (incorrect device?), resetting
 [2018-02-25 11:14:43.441] failed usb_init
 [2018-02-25 11:14:47.854] Network diff set to 757M
 [2018-02-25 11:14:47.854] Stratum from pool 0 detected new block at height 6149083
 [2018-02-25 11:14:48.796] USB init, open device failed, err -12,
 [2018-02-25 11:14:48.797] You need to install a WinUSB driver for - BSC device 1:6
 [2018-02-25 11:14:48.798] And associate - BSC device 1:6 with WinUSB using zadig
 [2018-02-25 11:14:48.798] See README.txt file included for help
 [2018-02-25 11:14:48.799] GekkoScience detect (1:6) failed to initialise (incorrect device?), resetting
 [2018-02-25 11:14:48.800] failed usb_init
 [2018-02-25 11:14:48.856] USB init, open device failed, err -12,
 [2018-02-25 11:14:48.857] You need to install a WinUSB driver for - BSC device 1:11
 [2018-02-25 11:14:48.857] And associate - BSC device 1:11 with WinUSB using zadig
 [2018-02-25 11:14:48.858] See README.txt file included for help
 [2018-02-25 11:14:48.858] GekkoScience detect (1:11) failed to initialise (incorrect device?), resetting
 [2018-02-25 11:14:48.859] failed usb_init
 [2018-02-25 11:14:48.909] USB init, open device failed, err -12,
 [2018-02-25 11:14:48.909] You need to install a WinUSB driver for - BSC device 1:10
 [2018-02-25 11:14:48.910] And associate - BSC device 1:10 with WinUSB using zadig
 [2018-02-25 11:14:48.911] See README.txt file included for help
 [2018-02-25 11:14:48.911] GekkoScience detect (1:10) failed to initialise (incorrect device?), resetting
 [2018-02-25 11:14:48.912] failed usb_init
 [2018-02-25 11:14:53.714] GSE 0: setting frequency to 125.00MHz
 [2018-02-25 11:14:53.898] GSE 1: setting frequency to 125.00MHz
 [2018-02-25 11:14:54.271] USB init, open device failed, err -12,
 [2018-02-25 11:14:54.271] You need to install a WinUSB driver for - BSC device 1:6
 [2018-02-25 11:14:54.272] And associate - BSC device 1:6 with WinUSB using zadig
 [2018-02-25 11:14:54.272] See README.txt file included for help
 [2018-02-25 11:14:54.273] GekkoScience detect (1:6) failed to initialise (incorrect device?), resetting
 [2018-02-25 11:14:54.273] failed usb_init
 [2018-02-25 11:14:54.324] USB init, open device failed, err -12,
 [2018-02-25 11:14:54.324] You need to install a WinUSB driver for - BSC device 1:11
 [2018-02-25 11:14:54.325] And associate - BSC device 1:11 with WinUSB using zadig
 [2018-02-25 11:14:54.326] See README.txt file included for help
 [2018-02-25 11:14:54.327] GekkoScience detect (1:11) failed to initialise (incorrect device?), resetting
 [2018-02-25 11:14:54.327] failed usb_init
 [2018-02-25 11:14:54.378] USB init, open device failed, err -12,
 [2018-02-25 11:14:54.378] You need to install a WinUSB driver for - BSC device 1:10
 [2018-02-25 11:14:54.379] And associate - BSC device 1:10 with WinUSB using zadig
 [2018-02-25 11:14:54.383] See README.txt file included for help
 [2018-02-25 11:14:54.383] GekkoScience detect (1:10) failed to initialise (incorrect device?), resetting
 [2018-02-25 11:14:54.384] failed usb_init
 [2018-02-25 11:14:59.740] USB init, open device failed, err -12,
 [2018-02-25 11:14:59.740] You need to install a WinUSB driver for - BSC device 1:6
 [2018-02-25 11:14:59.741] And associate - BSC device 1:6 with WinUSB using zadig
 [2018-02-25 11:14:59.742] See README.txt file included for help
 [2018-02-25 11:14:59.743] GekkoScience detect (1:6) failed to initialise (incorrect device?), resetting
 [2018-02-25 11:14:59.743] failed usb_init
 [2018-02-25 11:14:59.795] USB init, open device failed, err -12,
 [2018-02-25 11:14:59.795] You need to install a WinUSB driver for - BSC device 1:11
 [2018-02-25 11:14:59.797] And associate - BSC device 1:11 with WinUSB using zadig
 [2018-02-25 11:14:59.798] See README.txt file included for help
 [2018-02-25 11:14:59.798] GekkoScience detect (1:11) failed to initialise (incorrect device?), resetting
 [2018-02-25 11:14:59.799] failed usb_init
 [2018-02-25 11:14:59.850] USB init, open device failed, err -12,
 [2018-02-25 11:14:59.850] You need to install a WinUSB driver for - BSC device 1:10
 [2018-02-25 11:14:59.851] And associate - BSC device 1:10 with WinUSB using zadig
 [2018-02-25 11:14:59.852] See README.txt file included for help
 [2018-02-25 11:14:59.852] GekkoScience detect (1:10) failed to initialise (incorrect device?), resetting
 [2018-02-25 11:14:59.853] failed usb_init
 [2018-02-25 11:15:04.574] Network diff set to 728M
 [2018-02-25 11:15:04.575] Stratum from pool 0 detected new block at height 6149084
 [2018-02-25 11:15:05.211] USB init, open device failed, err -12,
 [2018-02-25 11:15:05.212] You need to install a WinUSB driver for - BSC device 1:6
 [2018-02-25 11:15:05.213] And associate - BSC device 1:6 with WinUSB using zadig
 [2018-02-25 11:15:05.213] See README.txt file included for help
 [2018-02-25 11:15:05.214] GekkoScience detect (1:6) failed to initialise (incorrect device?), resetting
 [2018-02-25 11:15:05.215] failed usb_init
 [2018-02-25 11:15:05.266] USB init, open device failed, err -12,
 [2018-02-25 11:15:05.266] You need to install a WinUSB driver for - BSC device 1:11
 [2018-02-25 11:15:05.267] And associate - BSC device 1:11 with WinUSB using zadig
 [2018-02-25 11:15:05.267] See README.txt file included for help
 [2018-02-25 11:15:05.268] GekkoScience detect (1:11) failed to initialise (incorrect device?), resetting
 [2018-02-25 11:15:05.269] failed usb_init
 [2018-02-25 11:15:05.319] USB init, open device failed, err -12,
 [2018-02-25 11:15:05.319] You need to install a WinUSB driver for - BSC device 1:10
 [2018-02-25 11:15:05.320] And associate - BSC device 1:10 with WinUSB using zadig
 [2018-02-25 11:15:05.320] See README.txt file included for help
 [2018-02-25 11:15:05.321] GekkoScience detect (1:10) failed to initialise (incorrect device?), resetting
 [2018-02-25 11:15:05.321] failed usb_init
 [2018-02-25 11:15:08.749] GSE 0: setting frequency to 150.00MHz
 [2018-02-25 11:15:08.928] GSE 1: setting frequency to 150.00MHz
 [2018-02-25 11:15:10.679] USB init, open device failed, err -12,
 [2018-02-25 11:15:10.680] You need to install a WinUSB driver for - BSC device 1:6
 [2018-02-25 11:15:10.681] And associate - BSC device 1:6 with WinUSB using zadig
 [2018-02-25 11:15:10.681] See README.txt file included for help
 [2018-02-25 11:15:10.682] GekkoScience detect (1:6) failed to initialise (incorrect device?), resetting
 [2018-02-25 11:15:10.682] failed usb_init
 [2018-02-25 11:15:10.733] USB init, open device failed, err -12,
 [2018-02-25 11:15:10.734] You need to install a WinUSB driver for - BSC device 1:11
 [2018-02-25 11:15:10.734] And associate - BSC device 1:11 with WinUSB using zadig
 [2018-02-25 11:15:10.735] See README.txt file included for help
 [2018-02-25 11:15:10.735] GekkoScience detect (1:11) failed to initialise (incorrect device?), resetting
 [2018-02-25 11:15:10.736] failed usb_init
 [2018-02-25 11:15:10.787] USB init, open device failed, err -12,
 [2018-02-25 11:15:10.787] You need to install a WinUSB driver for - BSC device 1:10
 [2018-02-25 11:15:10.788] And associate - BSC device 1:10 with WinUSB using zadig
 [2018-02-25 11:15:10.789] See README.txt file included for help
 [2018-02-25 11:15:10.789] GekkoScience detect (1:10) failed to initialise (incorrect device?), resetting
 [2018-02-25 11:15:10.790] failed usb_init


minerbobbert,

you can add this comand to your bat command, on windows not sure how to do it for others:

cgminer.exe -o stratum+tcp://sha256.usa.nicehash.com:3334 -u xxxoooxxxxooooxxxx -p x 2>logfile.txt

this one has a lot of details:

cgminer.exe -o stratum+tcp://sha256.usa.nicehash.com:3334 -u xxxoooxxxxooooxxxx -p x -D -T --verbose 2>logfile3.txt

minerbobbert
Member
**
Offline Offline

Activity: 149
Merit: 10


View Profile
February 25, 2018, 07:59:05 PM
 #25

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...
goose1072
Full Member
***
Offline Offline

Activity: 236
Merit: 100


View Profile
February 25, 2018, 09:14:20 PM
 #26

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...

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.
minerbobbert
Member
**
Offline Offline

Activity: 149
Merit: 10


View Profile
February 26, 2018, 02:21:49 AM
 #27

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?
sidehack
Legendary
*
Offline Offline

Activity: 1722
Merit: 1098

Curmudgeonly hardware guy


View Profile
February 26, 2018, 07:34:57 PM
 #28

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.

minerbobbert
Member
**
Offline Offline

Activity: 149
Merit: 10


View Profile
February 26, 2018, 09:56:51 PM
 #29

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?
goose1072
Full Member
***
Offline Offline

Activity: 236
Merit: 100


View Profile
February 26, 2018, 10:04:02 PM
 #30

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.
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


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

Thanks.
sidehack
Legendary
*
Offline Offline

Activity: 1722
Merit: 1098

Curmudgeonly hardware guy


View Profile
February 26, 2018, 10:05:27 PM
 #31

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
Legendary
*
Offline Offline

Activity: 1722
Merit: 1098

Curmudgeonly hardware guy


View Profile
February 26, 2018, 10:09:30 PM
 #32

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.

zachj00
Jr. Member
*
Offline Offline

Activity: 93
Merit: 0


View Profile
February 26, 2018, 10:12:53 PM
 #33

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.
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


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

Thanks.

Having similar issues running 2 off my macbook air. the one on my rpi3 is doing fantastic though.
zachj00
Jr. Member
*
Offline Offline

Activity: 93
Merit: 0


View Profile
February 26, 2018, 10:17:30 PM
 #34

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?
sidehack
Legendary
*
Offline Offline

Activity: 1722
Merit: 1098

Curmudgeonly hardware guy


View Profile
February 26, 2018, 10:20:28 PM
 #35

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.

goose1072
Full Member
***
Offline Offline

Activity: 236
Merit: 100


View Profile
February 26, 2018, 10:21:10 PM
 #36

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.
zachj00
Jr. Member
*
Offline Offline

Activity: 93
Merit: 0


View Profile
February 26, 2018, 11:21:43 PM
 #37

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)
minerbobbert
Member
**
Offline Offline

Activity: 149
Merit: 10


View Profile
February 27, 2018, 12:01:10 AM
 #38


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.
kipper01
Full Member
***
Offline Offline

Activity: 205
Merit: 100

1KippERXwH1PdBxKNt1ksgqh89WBv6CtWQ


View Profile
February 27, 2018, 12:01:38 AM
 #39

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 Smiley

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

sidehack
Legendary
*
Offline Offline

Activity: 1722
Merit: 1098

Curmudgeonly hardware guy


View Profile
February 27, 2018, 12:05:00 AM
 #40

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.

Pages: « 1 [2] 3 4 5 6 7 8 9 10 11 12 13 14 15 »  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!