GekkoScience 2Pac/Compac BM1384 Stickminer Support Thread

######################################## #GekkoScience 2Pac BM1384 Stickminer Support Thread# ######################################## ================= =Shoutout to the Community= ================= This project wouldn’t have happened without the awesome support from everyone. Big thanks to all who helped out, whether it was through signature campaigns, chats, or just ordering products. ================= =How to Get a 2Pac= ================= For the latest updates and news, check out the current product discussion thread. ================= =How to Run= ================= Right now, you'll need to set up cgminer with the newest gekko driver to mine using the 2Pac. This driver is being actively developed in a fork of ckolivas/cgminer. A pull request will be sent to the ckolivas/cgminer repo when the code is stable enough. Here’s how to run it: *nix [if you don’t have root privileges, see the Q&A] ./cgminer -o stratum+tcp://pool.ckpool.org:3333 -u 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr -p x suggest-diff 32 For Windows: cgminer.exe -o stratum+tcp://pool.ckpool.org:3333 -u 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr -p x suggest-diff 32 For OS X: cgminer -o stratum+tcp://pool.ckpool.org:3333 -u 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr -p x suggest-diff 32 Steps to build cgminer on Linux: Ubuntu 16.04.1 LTS fresh install. Default install (+ OpenSSH server) Debian 8.7.1 fresh install. Default install (No desktop environment, + SSH Server) (*don’t specify root password)

====================== = cgminer on Windows = ====================== (!)... If you have access to linux, use the mxe based cross compile example in the post above. (!)... If you just want the windows executable, read a little past the cross compile section in the post above for a pre-built cgminer.exe. Building the cgminer.exe binary for windows on windows can be a bit tricky (not for beginners). Follow the steps below in exact order.  If a step fails, most steps after it will fail also. Once you have a successful binary, zip up the whole C:\MinGW folder for safe keeping.   Chances are these instructions won't work, as is, a few months from now due to normal updates, but you might still be able to git pull and build updates. Environment Used: Windows 7, (should work for all WinOS supported by MinGW & Git) MinGW Installation Manager (0.6.2-beta-20131004-1 - Tested) Git for Windows (2.11.0 - Tested) MinGW Installation Manager http://www.mingw.org/ : Download installer : mingw-get-setup.exe     Install Options:     default all - "C:\MinGW\"     Mark for installation - "mingw-developer-toolkit", "mingw-base"     Installation -> "Apply Changes" From Windows Explorer: (or you'll get errors later) C:\MinGW << Security (Edit)<< Users << Full Control        Paste the following into Windows+R to get a MINGW32 shell and init the home directory: "C:\MinGW\msys\1.0\msys.bat" From MINGW32 shell: Install Git for Windows https://git-for-windows.github.io/     Install Options:     "C:\MinGW\msys\1.0\opt\git"     "Use Git from Git Bash only"     default everything else -->>>      Return to MINGW32 shell and complete the build. Install the zadig generic WinUSB drivers http://zadig.akeo.ie If all is well, you can list and see the stick from cgminer. cgminer.exe -n The cgminer.exe executable build can be located in windows explorer at: C:\MinGW\msys\1.0\home\<username>\git\vthoang\cgminer To transfer the executable for another system, you'll need the following dll(s) in the same folder as cgminer.exe C:\MinGW\bin\libcurl.dll C:\MinGW\bin\libeay32.dll C:\MinGW\bin\libgcc_s_dw2-1.dll C:\MinGW\bin\libidn-11.dll C:\MinGW\bin\libpdcurses.dll C:\MinGW\bin\pthreadGC-3.dll C:\MinGW\bin\ssleay32.dll C:\MinGW\bin\zlib1.dll C:\MinGW\bin\libusb-1.0.dll

ck has released a new version of cgminer this week, does this build include the latest code or the version prior?

Yes, it includes all the latest updates from ck's repository. Including some related to system libusb that has sent my windows build example back to the drawing board.      The entry page to my repository should say "This branch is N commits ahead of ckolivas:master. ". If it's ever "commits behind" just let me know.

It's not often that ck releases version bumps like he did this week. Even though he adds commits regularly.

Love the fact that this build reports HW for each individual stick.

Just to clarify. The new cgminer incorporates the compac like the novak "gekko" version used too but there isn't support yet for the 2pac until vh has finished?

That's correct. vh's clarification on Official cgminer 4.10.0 release: https://bitcointalk.org/index.php?topic=28402.msg17596575#msg17596575 cgminer 4.10.0 from vh's github does support 2pac.

I will be getting this built and running tonight when I get home from work.

Excellent! Might I suggest adding a note for Raspberry Pi users that is is EXTREMELY HIGHLY suggested to use a powered hub and not the Pi's USB ports directly....  They have trouble even supplying enough current to a portable USB self-powered HDD... let alone a stickminer =)   I don't want to see people with unnecessary troubles related to this =)

I don't know if it's in there yet, but yesterday I talked to VH about adding frequency support below 100MHz. I tested my stick at 3.8W at 100MHz, so about 75MHz and below should run on a 2.5W port. It is still definitely recommended to use a good powered hub, especially if you want to push higher frequencies.

Yes, the lower frequency options is available in the current build via git. Both the compac and 2Pac appears to be responding to it.   Bleeding edge right   I can't argue that a powered hub is definitely the long term way to go. The Pi3B might be a good starting device to use with the 2Pac.   https://www.raspberrypi.org/help/faqs/#powerReqs. You feed it a 2.5A power source, and it has a 1.2A current limiter out to the usb ports. That give the stick up to 6W of power to work with.     In the photo above, I have a 2.1A battery pack hooked up, drawing 3.88W @ 100MHz. New numbers while connected to the Pi3B: adjusting the potentiometer knob as low as it can go (not sure what that translates to on my stick prototype) Mining, no hwerror @ 75MHz = 2.7W Mining, no hwerror @ 50Mhz = 1.9W

On your stick I think I used different resistors that'll go to a bit lower voltage than the release model, probably 600mV flat instead of 630. I had trouble getting sticks to initialize stably in that low range so I decided to nix it. I'll run my test stick at those underclock numbers tomorrow and add to the efficiency chart.

Windows build instructions has been added: https://bitcointalk.org/index.php?topic=1764803.msg17624477#msg17624477

Why is this so hard to build? Not complaining but asking. If I go to ck his just zips open and I can run cgminer. I will play with it in a bit. Eyes are still too blurry I will wait a bit.

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

thank you.  I have ck's 4.10 build working with the compac. I should be able to get yours going with the TwoPac  thanks again.

I have mine setup and running on a fresh install of Ubuntu 16.04.1 LTS.  Thanks vh! Just a little thing, but you missed the step about installing git in the instructions, not a big one, but you could easily add it in the line where you are installing everything else. Thanks again.

I built it on an older Debian fresh install, needed libncurses5-dev and libusb-1.0-0-dev to compile and work properly.

Added.   Thanks for spotting that.