It would really be nice to see "Best Share" added to the Miner Status page. Do you have any info on when that might be added?
  
In the mean time, is there a way I can add that value myself by digging into and editing the html/config files?

Thank you.

Too funny. I thought I had installed the 64bit version.   Burning the new .iso now...

I'm relatively new to Linux.  Is there a way I can direct it to compile as 64 bit?  I just assumed it would do that somehow on its own.



By the way, I've been using your cgminer on another machine and it's been rock solid for a couple years.  Nice work.

Could use a little help please.  I've been trying to compile/install ckpool, but it errors-out during 'make'.
I have tried on two separate machines with the same results.

Here's where it all ends:

make[3]: Entering directory '/home/v3/ckpool/ckpool/src'
  CC       libckpool.o
  CC       sha2.o
yasm -f x64 -f elf64 -X gnu -g dwarf2 -D LINUX -o sha256_code_release/sha256_sse4.A sha256_code_release/sha256_sse4.asm
  AR       libckpool.a
ar: `u' modifier ignored since `D' is the default (see `U')
  CC       ckpool.o
  CC       generator.o
  CC       bitcoin.o
  CC       stratifier.o
stratifier.c: In function ‘read_poolstats’:
stratifier.c:8512:17: warning: passing argument 1 of ‘json_get_int64’ from incompatible pointer type [-Wincompatible-pointer-types]
  json_get_int64(&last.tv_sec, val, "lastupdate");
                 ^
In file included from stratifier.c:23:0:
ckpool.h:369:6: note: expected ‘int64_t * {aka long long int *}’ but argument is of type ‘__time_t * {aka long int *}’
 bool json_get_int64(int64_t *store, const json_t *val, const char *res);
      ^~~~~~~~~~~~~~
  CC       connector.o
  CCLD     ckpool
/usr/bin/ld: i386:x86-64 architecture of input file `libckpool.a(sha256_sse4.A)' is incompatible with i386 output
collect2: error: ld returned 1 exit status
Makefile:502: recipe for target 'ckpool' failed
make[3]: *** [ckpool] Error 1
make[3]: Leaving directory '/home/v3/ckpool/ckpool/src'
Makefile:570: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/home/v3/ckpool/ckpool/src'
Makefile:410: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/v3/ckpool/ckpool'
Makefile:342: recipe for target 'all' failed
make: *** [all] Error 2


Can anyone please tell me what steps I should take to get this to work? Both machines are Intel 64 bit with Debian.
I'd be happy to donate some satoshi's for some help.  Thank you.

Oh, and I'm using the .zip file from:      https://bitbucket.org/ckolivas/ckpool/get/5d4dbe166c31.zip

Is the hub not working with the RSPI3, or do you mean a 2Pac miner in the hub doesn't work with the RSPI3?

Looks like the number 10 port on your hub allows the most power. Have you tried that one? Have you tried plugging one 2Pac directly into the RSPI3? If so, does that work?

Most consumer-grade USB hubs have voltage and current limiting built in.  When you plug in more than one 2-Pac miner, it becomes the active one and zombies the others.  To use more than one 2-Pac in the same hub requires closer attention to the hub's specs.  I would say you need a hub that will output (permit) at least 1 amp per port.  2+ amps per port would be better if you want higher than stock hash rates.

the documentation for your hub states:

"For a stable connection, the devices connected to the 13 Port hub must not exceed a combined current of 5 volt 2.5A. Each USB port on our 13 Port hub will only provide 5 volts 300 Milliamps. "


You need more power.

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.