Quote from: kakarot9000 on December 24, 2017, 08:59:56 AM

I answered your same post here: https://bitcoin.stackexchange.com/questions/66387/unable-to-run-the-miner-using-2pac-bm1384-usb-miner/66527#66527

I had a similar problem when I first started with the 2pac. You didn't mention if you are using a Windows or Linux platform, but the solution is similar either way.

Solution: Ensure your cgminer binary is compiled to support the Gekko Science 2Pac. It seems your BM1384 2Pac is not being recognized properly by cgminer.

This output you provided:

"0: AMU GS-10018: | 528.0M / 516.0Mh/s WU: 5.6/m"

...shows that it is being enumerated as an "AMU" (which is usually an ASICMINER block erupter) It should be "GSC" for a GekkoScience device. That's also why you are seeing the low hash rate and hardware errors.

So, be sure you have a gekko-enabled cgminer binary, and also ensure your batch file points to that same correct binary. (correct path)

When you try to run cgminer with the --gekko-freq XXX option, it will immediately fail. That's because your cgminer.exe is not compiled to support the gekko. It doesn't recognize any gekko options. (Compile cgminer with "--enable-gekko" to support the 2Pac) When you run cgminer without the --gekko-freq XXX option, it will work, but it doesn't identify the 2Pac properly, and enumerates the device incorrectly as "AMU" and therefore doesn't hash properly.

Your batch commands to run cgminer look correct, no problems there.

Here is a link to cgminer with gekko support that I am using: github.com/vthoang/cgminer

If you need more detailed help, please state whether you are on a Windows or Linux platform.

80sKid

Posts

Merits