GekkoScience 2Pac/Compac BM1384 Stickminer Official Support Thread

[sidehack]

Using the command-line flags given in the first post.

[vh]

I guess there's no point in retrying via software when we see "Found 0 chip(s) on GSD 0".
Let me see if I can get it to just display "OFF" to signal folks to unplug, adjust voltage, and plug it back in.

Hm, I'd be careful with that. I've seen, more than once, Found 0 chip(s) on cgminer startup and after one or two "restarts" stick is detected/reports correctly

For now, I'm going go with you've got a special stick.

[vh]

New build is available (4fc8783).   git pull and build as needed.

- slight adjustment to ticket_mask and ramping
- check device health before creating an actual driver thread
- tidy up resources on failure

http://23.108.83.14/images/cgminer-4.10.0-windows-gekko-4fc8783.7z

[vh]

Eh, just remembered one more thing (my last post for today, I promise )

If you reset the stick after a few rounds of Found 0 chip(s) - Disabling! and it's starts hashing, numbers in the device list and device number reported once a share is found are misaligned. Right now I have GSDs listed as 21 and 22 in device list and shares reported for devices 15 and 16

They actually represent two different things, top stats are global device id (digit to left).   Logs are per device type ids (digits to right).   
If you have mix devices the number will diverge more apparently.   

[gt_addict]

OK so ive cloned the old sd card and managed to get cgminer 4.10.0 running. My current stats line has the format:-

 "1:GSC 10000081  231mhs  12.89G / 12.72 Gh/s WU:   A:   HW:  "
 "2:BSC 10000566  231mhs  13.24G / 12.71 Gh/s WU:   A:   HW:  "  etc etc

So do I now run the flowing in the order its been written by Biodom?

it looks like you did not run the correct code for pi.
Look closer: you need to run the one that says Debian (a longer list of dependencies) and mentions pi few lines down:

Code:

sudo apt-get update
sudo apt-get upgrade -y

sudo apt-get install -y build-essential git libusb-1.0-0-dev libusb-1.0-0 libcurl4-openssl-dev libncurses5-dev libudev-dev screen libtool automake pkg-config libjansson-dev

mkdir -p git/vthoang; cd git/vthoang
git clone https://github.com/vthoang/cgminer.git
cd cgminer

CFLAGS="-O2" ./autogen.sh --enable-gekko
make -j 2

After this:

Code:

sudo reboot
cd ~/git/vthoang/cgminer/
sudo usermod -G plugdev -a `whoami` #whoami=pi if you did not change it
sudo cp 01-cgminer.rules /etc/udev/rules.d/
sudo reboot

then
cd ~/git/vthoang/cgminer/
./cgminer -o stratum+tcp://solo.ckpool.org:3333 -u 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr.yourworkername -p x --suggest-diff 32

[Biodom]

on pi: just do commands as indicated, it will build a new vh's version of the cgminer inside the git/vhoang folder.

there is a bit of the code in the first post as to how to run both Compac and 2pac (called Compac-2) simultaneously.
also, not to worry, if you messed up a folder, just

rm -rf foldername

that's all

[takagari]

One of mine seems to drop offline at random, unplug and replug fixes, but odd. any ideas how to figure out why?

Code:

 [U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
   0: GSD 10010318: COMPAC-2 100.00MHz HW:0 | 14.12G / 11.02Gh/s WU:77.0/m
   1: GSD 10010326: COMPAC-2 100.00MHz HW:0 | ZOMBIE
--------------------------------------------------------------------------------
 [2017-03-23 15:51:23.396] Found 0 chip(s) on GSD 606
 [2017-03-23 15:51:23.396] GSD 606 failure, disabling!

[philipma1957]

One of mine seems to drop offline at random, unplug and replug fixes, but odd. any ideas how to figure out why?

Code:

 [U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
   0: GSD 10010318: COMPAC-2 100.00MHz HW:0 | 14.12G / 11.02Gh/s WU:77.0/m
   1: GSD 10010326: COMPAC-2 100.00MHz HW:0 | ZOMBIE
--------------------------------------------------------------------------------
 [2017-03-23 15:51:23.396] Found 0 chip(s) on GSD 606
 [2017-03-23 15:51:23.396] GSD 606 failure, disabling!

weak usb hub?

[takagari]

Directly plugged in, but I figure the port can't handle it. will go out and look to buy a powered usb hub tomorrow.
It works, ran for nearly 18hrs before it dropped off.

[gt_addict]

OK so ive cloned the old sd card and managed to get cgminer 4.10.0 running. My current stats line has the format:-

 "1:GSC 10000081  231mhs  12.89G / 12.72 Gh/s WU:   A:   HW:  "
 "2:BSC 10000566  231mhs  13.24G / 12.71 Gh/s WU:   A:   HW:  "  etc etc

So do I now run the flowing in the order its been written by Biodom?

it looks like you did not run the correct code for pi.
Look closer: you need to run the one that says Debian (a longer list of dependencies) and mentions pi few lines down:

Code:

sudo apt-get update
sudo apt-get upgrade -y

sudo apt-get install -y build-essential git libusb-1.0-0-dev libusb-1.0-0 libcurl4-openssl-dev libncurses5-dev libudev-dev screen libtool automake pkg-config libjansson-dev

mkdir -p git/vthoang; cd git/vthoang
git clone https://github.com/vthoang/cgminer.git
cd cgminer

CFLAGS="-O2" ./autogen.sh --enable-gekko
make -j 2

So ive done the following and it will run the Green compac I have but does not recognise the bitshopper compacs. Just comes up with "usb init failed"  

[ppetrovic68]

The post on Plugable's 7-port charging hub power setup is from me
Possibly using Y-cables is contributing to the drop out?

I run 2x 2Pacs and 1 Compac on the Plugable 7-port 60w charging hub.
For form-factor and cooling I have a 2Pac on port-2, the other 2Pac on port-4, and the Compac on port-6. Nice and compact for cooling and each stick is on its own buck.

Tried running them without the y-cables, just plugged straight into the hub?

I did earlier, and again last night - they were dropping like flies :/ After only a few minutes one of the stick would drop and Found 0 chip(s) fun would begin. Also tried swapping cables - nothing changed. One would work, the other would drop out.

Then I decided to go back to basics. I connected only one stick, via Y-cable to the Pluggable hub, and just for fun of it I upped the frequency to 275, two original Compacs were on other hub, second 2Pac was taking a break. Started cgminer... 19 hours later, 2Pac still going strong, averages at 30Gh/s, 0 HWs. I guess 30Gh/s @ 275Mhz is expected - Compacs @275Mhz would give somewhere about 15Gh/s.

And to make things more interesting I've connected "special" stick to Pluggable, an hour ago, using Y-cable but connecting just one end to the hub and then I ran another instance of cgminer @ 150 Mhz.

Now I have one cgminer running 2Pac@275, 2 Compacs @250 and second cgminer running one 2Pac@150 - so far so good...

[sidehack]

It's possible VH's driver doesn't recognize the bitshopper product string. Reckon we'll need to get that fixed here directly since I'm working on bitshopper 2Pacs right now.

[gt_addict]

It's possible VH's driver doesn't recognize the bitshopper product string. Reckon we'll need to get that fixed here directly since I'm working on bitshopper 2Pacs right now.

Phew! Theres me thinking ive gone a f**ked it up for the third time   I even tried the "--enable-icarus" alongside "--enable-gekko" but it didn't like that.

[Biodom]

It's possible VH's driver doesn't recognize the bitshopper product string. Reckon we'll need to get that fixed here directly since I'm working on bitshopper 2Pacs right now.

not sure about the batch you work on right now, but whatever black sticks you sold in US (at least mine) are working on vh's driver just fine for me (two out of two).

It's possible VH's driver doesn't recognize the bitshopper product string. Reckon we'll need to get that fixed here directly since I'm working on bitshopper 2Pacs right now.

Phew! Theres me thinking ive gone a f**ked it up for the third time   I even tried the "--enable-icarus" alongside "--enable-gekko" but it didn't like that.

did you try to take it out and hotplug it again?
if not, restart the pi, then start cgminer again.

[sidehack]

The seconds black sticks got bench-test configs, which means the default Gekkoscience product string and an arbitrary serial number. MacEntyre had a bitshopper-specific config he used on his sticks and I'll be using it on the bitshopper proper batch. It's what gets flashed into the CP2102.

[Biodom]

So ive done the following and it will run the Green compac I have but does not recognise the bitshopper compacs. Just comes up with "usb init failed"  

did you do the following...

Code:

cd ~/git/vthoang/cgminer/
sudo usermod -G plugdev -a `whoami` #whoami=pi if you did not change it
sudo cp 01-cgminer.rules /etc/udev/rules.d/
sudo reboot

it is right there in my prior post.
I don't see you quoting this.
When I did not do this, I also got "usb init failed".
EDIT: this is only so if you are actually talking about 2pacs. Original black Compac (not 2pac) is a whole another situation that vh is fixing, apparently.

[Biodom]

The seconds black sticks got bench-test configs, which means the default Gekkoscience product string and an arbitrary serial number. MacEntyre had a bitshopper-specific config he used on his sticks and I'll be using it on the bitshopper proper batch. It's what gets flashed into the CP2102.

yes, but @gt_addict got the same as me.
most likely explanation is in my post above.
then, again, maybe he is talking about older bitshopper one chip sticks.
if so, sorry, my mistake.

[vh]

It's possible VH's driver doesn't recognize the bitshopper product string. Reckon we'll need to get that fixed here directly since I'm working on bitshopper 2Pacs right now.

hmm... yes it is very possible I didn't finish connecting the dots there.  99.2% likely.
I'll add it shortly.

[sidehack]

No, because he specifically said "bitshopper Compac", not black 2Pac.

VH do you have a bitshopper Compac config? I've got one I can plug in if you want to read it.

[vh]

No, because he specifically said "bitshopper Compac", not black 2Pac.

VH do you have a bitshopper Compac config? I've got one I can plug in if you want to read it.

Cool, leave it connected.   I won't be able to get to it for a few more hours.