Pages:
Author

Topic: GekkoScience 2Pac/Compac BM1384 Stickminer Official Support Thread - page 84. (Read 177410 times)

legendary
Activity: 1109
Merit: 1000
Well yeah, with a pool diff of 33K.
Is that a tuneable parameter?
legendary
Activity: 3374
Merit: 1859
Curmudgeonly hardware guy
Well yeah, with a pool diff of 33K.
legendary
Activity: 1109
Merit: 1000
I guess I do have an issue after all, several hours and no accepted shares...
newbie
Activity: 37
Merit: 0
I have mine running weeks on end using windows 10 at 237.5mhz no zombie issues.

using cgminer 4.10 and a small fan.



legendary
Activity: 1109
Merit: 1000
Excellent instructions in OP. Got my 2Pac miners today and got them fired up and running right off the bat.
I probably need to do a bit more reading to figure out how to set/change frequency though. Happy customer.

Code:
cgminer version 4.10.0 - Started: [2017-07-20 15:06:54.599]
--------------------------------------------------------------------------------
 (5s):15.57G (1m):11.01G (5m):5.175G (15m):2.087G (avg):10.96Gh/s
 A:0  R:0  HW:0  WU:154.8/m
 Connected to sha256.usa.nicehash.com diff 32.8K with stratum as user xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 Block: ba3d0792...  Diff:805G  Started: [15:08:53.927]  Best share: 4.83K
--------------------------------------------------------------------------------
 [U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
 0: GSD 10012279: COMPAC-2 100.00MHz HW:0 | 17.80G / 11.08Gh/s WU:154.8/m
member
Activity: 82
Merit: 10
I did everything anorganix  said above

WinXP 32bit
I try at 225 and 200 and 175 freqs and get the same results.  sometimes 15mins,  sometimes 16hrs and anything above and inbetween

It goes OFF and then ZOMBIE shortly after

 [2017-07-13 15:18:01.288] GSD 0: No valid hashes recently, attempting to reset
 [2017-07-13 15:18:01.303] GSD 0 attempted reset got err:(0) LIBUSB_SUCCESS / LIBUSB_TRANSFER_COMPLETED
 [2017-07-13 15:18:29.038] Network diff set to 2.1G
 [2017-07-13 15:18:29.038] Stratum from pool 0 detected new block at height 0
 [2017-07-13 15:19:15.116] GSD 0: Device failed to respond to restart
 [2017-07-13 15:19:15.194] GSD 0 failure, disabling!     (<-----at this point it goes ZOMBIE)
 [2017-07-13 15:26:44.053] Stratum connection to pool 0 interrupted
 [2017-07-13 15:26:44.460] Pool 0 difficulty changed to 1024
 [2017-07-13 15:28:26.741] Network diff set to 2.1G
 [2017-07-13 15:28:26.741] Stratum from pool 0 detected new block at height 0
 [2017-07-13 15:28:29.131] Stratum connection to pool 0 interrupted
 [2017-07-13 15:28:31.913] Pool 0 difficulty changed to 1024
 [2017-07-13 15:28:31.913] Stratum from pool 0 requested work restart

If I catch it while it's OFF,  I just have to close cgminer and open it again and it resumes
If it gets to the ZOMBIE stage,  I have to close cgminer then unplug/plug the 2pac  and restart cgminer

EDIT====
This also happens  when it doesn't ZOMBIE,  it just goes OFF
[2017-07-13 15:56:52.788] Accepted 05d4763c Diff 44/30 GSD 0
[2017-07-13 15:56:56.975] Pool 0 difficulty changed to 70.7
[2017-07-13 15:58:13.881] GSD 0 failure, disabling!
member
Activity: 79
Merit: 18

hp# apt-get install winusb
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package winusb

On an amd64 Debian machine: Linux hp 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2 (2017-04-30) x86_64 GNU/Linux

I've always had to hotplug mine, either on Raspberry Pis or on my HP laptop with amd64 Debian.  I ran across a cgminer I had downloaded April 30 from http://gekkoscience.com/misc/cgminer-gekko.tar.gz so I just tried it.  I didn't fiddle enough to get it to recognize my 2pac, I just went back to the version I was running.
The new version:


The old version:


Same libusb, etc.  Also I see my "--gekko-2pac-freq 150" wasn't recognized anymore.
legendary
Activity: 3374
Merit: 1859
Curmudgeonly hardware guy
Ah okay, I missed that part. If it works as stated that'd be simpler for most people.
legendary
Activity: 966
Merit: 1003
That's why I stated if they all have the same operating instructions.
Its also the third suggestion in the usb part of the read me file...and the most basic. But it works well.
legendary
Activity: 3374
Merit: 1859
Curmudgeonly hardware guy
Yeah but, if you specify the device you want you can tune each one to an optimal frequency instead of forcing them all to run on the same speed.
legendary
Activity: 966
Merit: 1003
The third version
  --usb :10
means only use a maximum of 10 devices of any supported USB devices
Once cgminer has 10 devices it will not configure any more and hotplug will
not scan for any more
If one of the 10 devices stops working, hotplug - if enabled, as is default
- will scan normally again until it has 10 devices


^^^as copy and paste from the read me file^^^

You don't need to Specify each usb's specific location if they all have the same operating instructions.
 --usb :1
Would be all you need to start a single stick at the end of your start up instructions.
 Then you could wait a moment and click your desktop batch shortcut icon again and the next stick will start, so on and so on. If one of the sticks has a problem and hot plug puts the device in a different address the program will see it and keep going.

good lord...let's not over complicate things...MM..K!
newbie
Activity: 51
Merit: 0
Actually, the WinUSB drivers are a lot easier and less annoying than in windows... so perhaps I'll just stick with cgminer on *nix.
Heh, that's a funny thing to say. WinUSB drivers on linux... think about what you just said (hint WINusb.) There is no such thing on linux, cgminer just talks directly to the linux kernel usb interface and doesn't need any driver at all.

Yeah, I don't know how it works.  I do know that in order to build cgminer, I needed to apt-get install winusb to resolve a dependency.  I guess I'd say "I'm glad I don't have to worry about WinUSB drivers"? Smiley
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Actually, the WinUSB drivers are a lot easier and less annoying than in windows... so perhaps I'll just stick with cgminer on *nix.
Heh, that's a funny thing to say. WinUSB drivers on linux... think about what you just said (hint WINusb.) There is no such thing on linux, cgminer just talks directly to the linux kernel usb interface and doesn't need any driver at all.
newbie
Activity: 51
Merit: 0
FYI -  I was going crazy trying to figure out why my sticks were going zombie almost immediately.  Based on this thread, I definitely thought that it had to be something regarding my USB hub / power supply.  I decided to fire up a Ubuntu VM and compiled cgminer as per the instructions on the first page of this thread.  NO ISSUES!!  I'll be running cgminer on Ubuntu until something is resolved.  Actually, the WinUSB drivers are a lot easier and less annoying than in windows... so perhaps I'll just stick with cgminer on *nix.
copper member
Activity: 970
Merit: 287
Per aspera ad astra
For all those that are having issues with some sticks going zombie, you should check the troubleshooting / Q&A from the OP.
If you have followed the instructions (voltage adjutment etc) and you still have the zombie issue, continue reading (Windows only).

Important
By following the instructions below, you will end up using one instance of cgminer for each stick.

[1] Create a batch file in the cgminer folder (let's call it list-devices.bat)
Code:
@echo off
TITLE 2Pac - list devices
cgminer -n
pause

[2] Run it and you should see something like this
Code:
[2017-07-11 20:00:08.577] USB all: found 13 devices - listing known devices
.USB dev 0: Bus 4 Device 12 ID: 10c4:ea60
[...some more info here...]
.USB dev 1: Bus 4 Device 10 ID: 10c4:ea60
[...some more info here...]
.USB dev 2: Bus 4 Device 14 ID: 10c4:ea60
[...some more info here...]
 [2017-07-11 20:00:08.578] 3 known USB devices
Press any key to continue . . .

[3] Write down the bus number (in my case 4) and each device ID (in my case 10, 12 and 14)

[4] Create a batch file in the cgminer folder for the first stick with the following
Code:
@echo off
TITLE BTC - solo (ckpool) - 2Pac #1
cgminer -o stratum+tcp://de.ckpool.org:3333 -u YOUR-USERNAME -p x --gekko-2pac-freq YOUR-DESIRED-FREQ --suggest-diff YOUR-DESIRED-DIFF --usb 4:10
pause

[5] Create a batch file in the cgminer folder for the second stick with the following
Code:
@echo off
TITLE BTC - solo (ckpool) - 2Pac #2
cgminer -o stratum+tcp://de.ckpool.org:3333 -u YOUR-USERNAME -p x --gekko-2pac-freq YOUR-DESIRED-FREQ --suggest-diff YOUR-DESIRED-DIFF --usb 4:12
pause

[6] Create a batch file in the cgminer folder for the third stick with the following
Code:
@echo off
TITLE BTC - solo (ckpool) - 2Pac #3
cgminer -o stratum+tcp://de.ckpool.org:3333 -u YOUR-USERNAME -p x --gekko-2pac-freq YOUR-DESIRED-FREQ --suggest-diff YOUR-DESIRED-DIFF --usb 4:14
pause

[7] Repeat until you cover all devices

[8] Please note the --usb 4:14 added at the end of the command line which instructs cgminer to use only the device found on bus 4 with ID 14 (see step 3).

Final notes:
- my 3 sticks were running fine most of the time but every 2-3 days one of them was going zombie
- with this setup I'm running fine @ 200 Mhz since the 6th of July (0 HW errors, no zombies)
- the hub I use is the Plugable USB 2.0 version

HTH,
anorganix.
newbie
Activity: 19
Merit: 0
but you got accepteds after the error starts.  once I get that error they display OFF,   I haven't experienced ZOMBIE yet.
and sometimes I just have to restart cgminer, and sometimes I have to unplug/plug the stick and restart cgminer.
I did find that they run better when I have a separate cgminer for each stick.

I have the same here, when they go zombie, I quit and than restart and it works again, some times I have to turnoff the hub and turn on again.

I just have tried with 100 mhz, and the problem persists!
I'll try running different cgminer for each stick!

And actually I can run each one at 250mhz! working with no hardware errors!

So I did, running 2 sticks in different cgminers at 250mhz for more than 14 hours without a break, it´s definitely the solution. No problem here.

So my guess it´s the 2 pack stick going zombie or off, it´s a matter of driver or cgminer bug!

It´s definitely not a problem with the hub!

Interesting.   Looks like both cases are windows based.   I was previously looking into a write error issue with my hub that only happens in windows and not in linux.   I shelved it since it seemed isolated, but will revisit it in a bit to see if I can spot anything else.

I have also tested in a Virtual Machine with Linux, and I got the same problem, but in this case, I don't know if it´s valid for a Vmware Virtual Machine!
newbie
Activity: 19
Merit: 0
but you got accepteds after the error starts.  once I get that error they display OFF,   I haven't experienced ZOMBIE yet.
and sometimes I just have to restart cgminer, and sometimes I have to unplug/plug the stick and restart cgminer.
I did find that they run better when I have a separate cgminer for each stick.

I have the same here, when they go zombie, I quit and than restart and it works again, some times I have to turnoff the hub and turn on again.

I just have tried with 100 mhz, and the problem persists!
I'll try running different cgminer for each stick!

And actually I can run each one at 250mhz! working with no hardware errors!

So I did, running 2 sticks in different cgminers at 250mhz for more than 14 hours without a break, it´s definitely the solution. No problem here.

So my guess it´s the 2 pack stick going zombie or off, it´s a matter of driver or cgminer bug!

It´s definitely not a problem with the hub!


NICE!
what's your voltage at?
also what is your cgminer version?  I grabbed 2 of them, to see if there was a difference, so I have 495461c and b682468

I haven't checked the voltage, but I´m always changing it when I change the frequency.
I can't say either the version of mine, where do I check that? I have build my own using a Linux
vh
hero member
Activity: 699
Merit: 666
but you got accepteds after the error starts.  once I get that error they display OFF,   I haven't experienced ZOMBIE yet.
and sometimes I just have to restart cgminer, and sometimes I have to unplug/plug the stick and restart cgminer.
I did find that they run better when I have a separate cgminer for each stick.

I have the same here, when they go zombie, I quit and than restart and it works again, some times I have to turnoff the hub and turn on again.

I just have tried with 100 mhz, and the problem persists!
I'll try running different cgminer for each stick!

And actually I can run each one at 250mhz! working with no hardware errors!

So I did, running 2 sticks in different cgminers at 250mhz for more than 14 hours without a break, it´s definitely the solution. No problem here.

So my guess it´s the 2 pack stick going zombie or off, it´s a matter of driver or cgminer bug!

It´s definitely not a problem with the hub!

Interesting.   Looks like both cases are windows based.   I was previously looking into a write error issue with my hub that only happens in windows and not in linux.   I shelved it since it seemed isolated, but will revisit it in a bit to see if I can spot anything else.
member
Activity: 82
Merit: 10
but you got accepteds after the error starts.  once I get that error they display OFF,   I haven't experienced ZOMBIE yet.
and sometimes I just have to restart cgminer, and sometimes I have to unplug/plug the stick and restart cgminer.
I did find that they run better when I have a separate cgminer for each stick.

I have the same here, when they go zombie, I quit and than restart and it works again, some times I have to turnoff the hub and turn on again.

I just have tried with 100 mhz, and the problem persists!
I'll try running different cgminer for each stick!

And actually I can run each one at 250mhz! working with no hardware errors!

So I did, running 2 sticks in different cgminers at 250mhz for more than 14 hours without a break, it´s definitely the solution. No problem here.

So my guess it´s the 2 pack stick going zombie or off, it´s a matter of driver or cgminer bug!

It´s definitely not a problem with the hub!


NICE!
what's your voltage at?
also what is your cgminer version?  I grabbed 2 of them, to see if there was a difference, so I have 495461c and b682468
newbie
Activity: 19
Merit: 0
but you got accepteds after the error starts.  once I get that error they display OFF,   I haven't experienced ZOMBIE yet.
and sometimes I just have to restart cgminer, and sometimes I have to unplug/plug the stick and restart cgminer.
I did find that they run better when I have a separate cgminer for each stick.

I have the same here, when they go zombie, I quit and than restart and it works again, some times I have to turnoff the hub and turn on again.

I just have tried with 100 mhz, and the problem persists!
I'll try running different cgminer for each stick!

And actually I can run each one at 250mhz! working with no hardware errors!

So I did, running 2 sticks in different cgminers at 250mhz for more than 14 hours without a break, it´s definitely the solution. No problem here.

So my guess it´s the 2 pack stick going zombie or off, it´s a matter of driver or cgminer bug!

It´s definitely not a problem with the hub!
Pages:
Jump to: