OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.10.0

[kano]

Edit: there's a later 4.3.2a update here: https://bitcointalk.org/index.php?topic=28402.msg6533537#msg6533537

Here's another new AntS1 binary.

An endian issue was found in the solo code for the ant (no issue for desktop computers), so this update includes the fix for that.
I've removed both old AntS1 binaries

This uses the same patch as before for the luci display.
My source for this version is here:
https://github.com/kanoi/cgminer/tree/ants1-4.2.0-00567a4

The binary and README are in my cgminer-binaries git here:
https://github.com/kanoi/cgminer-binaries/tree/master/AntS1  <-- Follow this link to get the new binary

Read the README on the screen there for how to replace the /usr/bin/cgminer binary in your AntS1 with the new one.

This binary includes all cgminer changes up to 4.2.0 and forward after that up to:
https://github.com/ckolivas/cgminer/commit/cec48cee5f1759e5996de5339537fab4aeff416c

The previous report of having trouble with running the binary turned out to be caused by incorrectly specifying cgminer options.

[1505873771]

1505873771

[1505873771]

1505873771

[canford]

Thank you kano for the S1 binary, running successfully on two S1s and using your luci pool password hack to pass temp params to cgminer.  Thank you artpego for the last share time fix, also working on both ants.  Thank you ckolivas for cgminer 4.2.0 working on win7 with 12 BE's and the Avalon 4.2.0 image running on a Mini.  The Mini is running at 59 gh/s clocked at 400, turns out miner 15 has failed, but 1-14 and 16 are working.  It might be a loose connection, but I'm not sure it's worth attempting to disassemble the Mini to check.   

[artpego]

Glad to help, was an easy tweak to grep out "lastsharetime" recursively down the lua/luci dir chain and work back from there. Like I said, I am new to all this (mining) and have 3 Antminer S1's running kano's great stuff (thanks mucho kano, i will be sending some coin your way), running real stable at low temps 200GH/s with nice low temps, but I am also a hacker at heart and these little rigs are proving fun for the interface side and cgminer side. This little test seems to be earning it's keep so-far (initial hardware costs and recurring electricity cost vs the payout I'm seeing)... but we'll see at the next difficulty increase... which is all too quickly approaching ... and the erratic bit-coin pricing. Anyway, long term investment, we'll see how it works out.

My "day job" these past 12 years has been writing enterprise software (shop floor controls, low level machine control for component placement, health system logs to pull/burn onto ROMS/B2B,ERP, web reporting & eCommerce) all day long for a PCBA fabrication facility, systems integration factory, engineering and program management site, our eCommerce group, and an a couple of RMA facilities (1 man "manager of 1", waaaaayyyyyy many hats)..... with a wife who designs the boards in the engineering wing of the same company (won't mention any names, but we make just about some percentage everyone's retail stuff they sell like servers, PC's, phones, etc... , they just have us design it and then re-brand or we build on their specs as a CM).... if anyone ever wants to design and build a "better ant", maybe we can figure something out and come up with a team... pretty sure I can do NPI's and get PCB's (since we own a PCB fab as well) without any hassles Weekdays suck for comms, but nights and weekends are usually free to mess around in my hardware lab all day.

[-ck]

New version: 4.2.1, 24th March 2014

Bugfixes.


Human readable changelog:

- Bitcoind did not like lots of persistent connections at once meaning it would fall over if more than one cgminer instance was trying to mine at the same time from the one bitcoind instance. Cgminer now opens and closes the connection every time it talks to bitcoind allowing any number of cgminer instances to mine solo from the one instance. Confirmed working with 200TH of miners aimed at the one bitcoind...
- Big endian hosts (like the antminer S1, avalon) did not work with solo mining.
- Solo mining setups will not mine unless a btc address is specified now, and the address is displayed on startup if it exists.
- Solo mining disconnections to bitcoind are handled better, not spawning more polling threads every failure.
- Low level optimisations for solo mining
- AntminerS1 fixes to decrease CPU usage and actually honour overheat conditions.
- Network diff when submitting a block is shown correctly on screen when >2billion.
- Build fixes for avalon2
- miner.php improvements


Full changelog:

- Fix various ava2 build issues generically
- Minimise the amount of heap memory allocations/frees when submitting gbt
shares.
- Make varint in gbt submission a stack object.
- Fix big endian problems with gbt submissions.
- Fix 32bit overflow on relative diff shown.
- ants1 - stop results read hard looping
- ants1 - slow down mining if overheat occurs
- miner.php allow gen before (bgen) and after (gen) grouping
- Change default solo mining to failing when no btc address is specified.
- Use upgrade cglock variants in get_gbt_curl
- Provide a cg_uilock to unlock the intermediate variant of cglocks.
- Use the one curl instance for all gbt solo operations, protecting its use with
a bool set under gbt lock.
- Only start block detection with gbt solo if setup succeeded
- One less block detection message
- Toss out the curl handle after each solo poll
- Don't reuse any curl handles for solo mining and break out of the lp thread if
the pool is removed.
- Make sure to only start the lognpoll thread once on gbt solo.
- Don't keep RPC connections open for solo mining since bitcoind doesn't like
having many persistent connections.
- GBT solo pools should be considered localgen pools.
- miner.php - speed up formatting and allow calc on gen fields
- Always show the address we're solo mining to to avoid confusion for when no
address is set.

[loshia]

Hello Con,

I have played with #define LOCK_TRACKING 1 - GREAT WORK THANK YOU!

Here are my findings:

First Issue
From the following code



static inline void _cg_wlock(cglock_t *lock, const char *file, const char *func, const int line)
{
   _mutex_lock(&lock->mutex, file, func, line);
   _wr_lock(&lock->rwlock, file, func, line);
}

static inline void _cg_rlock(cglock_t *lock, const char *file, const char *func, const int line)
{
   _mutex_lock(&lock->mutex, file, func, line);
   _rd_lock(&lock->rwlock, file, func, line);
   _mutex_unlock_noyield(&lock->mutex, file, func, line);
}

It seems that when a thread acquires a read lock (_cg_rlock) another thread can acquire a write lock (_cg_wlock)

Please take a look at the flowing peace of code

stale_work(struct work *work, bool share)   
.....
   cg_rlock(&pool->data_lock);
      if (strcmp(work->job_id, pool->swork.job_id))
         same_job = false;
      cg_runlock(&pool->data_lock)

It may turn that while we are performing strcmp
static bool parse_notify(struct pool *pool, json_t *val)
.......

   cg_wlock(&pool->data_lock);
   free(pool->swork.job_id);
   pool->swork.job_id = job_id;

frees pool->swork.job_id

Resulting in flowing line in BLOCKED gets (9) id=248038834 by cgminer.c stale_work()....
I have changed stale_work
      cg_rlock(&pool->data_lock);
      if (strcmp(work->job_id, pool->swork.job_id))
         same_job = false;
      cg_runlock(&pool->data_lock);
to
    cg_wlock(&pool->data_lock);
   
      if (strcmp(work->job_id, pool->swork.job_id))
         same_job = false;
      cg_wunlock(&pool->data_lock);
I have moved

gen_stratum_work.....

work->job_id = strdup(pool->swork.job_id); under
cg_wlock(&pool->data_lock);
Second:

   cg_wlock(&control_lock);
   local_work++;
   work->id = total_work++;
   cg_wunlock(&control_lock);

I do think that everywhere total_work++; and local_work++ shod be changed under &control_lock. This is not happening currently. I am digging to find all places to do it

[-ck]

Hello Con,

I have played with #define LOCK_TRACKING 1 - GREAT WORK THANK YOU!

Here are my findings:

First Issue
From the following code


[snip]

It seems that when a thread acquires a read lock (_cg_rlock) another thread can acquire a write lock (_cg_wlock)

Actually the unfortunate thing is that cglocks are unique upgradeable read write locks, and it is normal for a write lock to be able to grab the mutex component of the cglock while a read variant is holding the read lock - but it will not be able to grab the write lock. The same rules don't quite apply as per regular locks.

Yes they are an implementation of my own, originally developed for the linux kernel scheduler code I maintain. See:
http://ck-hack.blogspot.com/2012/06/upgradeable-rwlocks-and-bfs.html

[loshia]

Hello Con,

I have played with #define LOCK_TRACKING 1 - GREAT WORK THANK YOU!

Here are my findings:

First Issue
From the following code


[snip]

It seems that when a thread acquires a read lock (_cg_rlock) another thread can acquire a write lock (_cg_wlock)

Actually the unfortunate thing is that cglocks are unique upgradeable read write locks, and it is normal for a write lock to be able to grab the mutex component of the cglock while a read variant is holding the read lock - but it will not be able to grab the write lock. The same rules don't quite apply as per regular locks.

Yes they are an implementation of my own, originally developed for the linux kernel scheduler code I maintain. See:
http://ck-hack.blogspot.com/2012/06/upgradeable-rwlocks-and-bfs.html

So what will happen when  if (strcmp(work->job_id, pool->swork.job_id)) and free(pool->swork.job_id); are executed simultaneously?

[-ck]

Hello Con,

I have played with #define LOCK_TRACKING 1 - GREAT WORK THANK YOU!

Here are my findings:

First Issue
From the following code


[snip]

It seems that when a thread acquires a read lock (_cg_rlock) another thread can acquire a write lock (_cg_wlock)

Actually the unfortunate thing is that cglocks are unique upgradeable read write locks, and it is normal for a write lock to be able to grab the mutex component of the cglock while a read variant is holding the read lock - but it will not be able to grab the write lock. The same rules don't quite apply as per regular locks.

Yes they are an implementation of my own, originally developed for the linux kernel scheduler code I maintain. See:
http://ck-hack.blogspot.com/2012/06/upgradeable-rwlocks-and-bfs.html

So what will happen when  if (strcmp(work->job_id, pool->swork.job_id)) and free(pool->swork.job_id); are executed simultaneously?

That can't happen.

[loshia]

Hello Con,

I have played with #define LOCK_TRACKING 1 - GREAT WORK THANK YOU!

Here are my findings:

First Issue
From the following code


[snip]

It seems that when a thread acquires a read lock (_cg_rlock) another thread can acquire a write lock (_cg_wlock)

Actually the unfortunate thing is that cglocks are unique upgradeable read write locks, and it is normal for a write lock to be able to grab the mutex component of the cglock while a read variant is holding the read lock - but it will not be able to grab the write lock. The same rules don't quite apply as per regular locks.

Yes they are an implementation of my own, originally developed for the linux kernel scheduler code I maintain. See:
http://ck-hack.blogspot.com/2012/06/upgradeable-rwlocks-and-bfs.html

So what will happen when  if (strcmp(work->job_id, pool->swork.job_id)) and free(pool->swork.job_id); are executed simultaneously?

That can't happen.

Oki You are the boss..
Thank you for your comments.

Best

[-ck]

That can't happen.

Oki You are the boss..
Thank you for your comments.

Heh no problem Appreciate extra eyes on the code, always.

BTW if it wasn't obvious: The cg write lock variant would have grabbed the mutex successfully but be unable to grab the write lock while the other thread holds the read lock.

[kano]

...
I have played with #define LOCK_TRACKING 1 - GREAT WORK THANK YOU!
...

You're welcome

Yes Con designed all of the cglock code and wrote almost all of it.
I've had a few deadlocks I've coded in the past, so I wrote the lock tracking to be able to find them easily when I cause them.

[loshia]

...
I have played with #define LOCK_TRACKING 1 - GREAT WORK THANK YOU!
...

You're welcome

Yes Con designed all of the cglock code and wrote almost all of it.
I've had a few deadlocks I've coded in the past, so I wrote the lock tracking to be able to find them easily when I cause them.

Nice hack for lockstats to make them usable or at least for me api.c

#if LOCK_TRACKING

FILE * pFile;

#define LOCK_FMT_FFL " - called from %s %s():%d"

#define LOCKMSG(fmt, ...)   fprintf(pFile, "APILOCK: " fmt "\n", ##__VA_ARGS__)
#define LOCKMSGMORE(fmt, ...)   fprintf(pFile, "          " fmt "\n", ##__VA_ARGS__)
#define LOCKMSGFFL(fmt, ...) fprintf(pFile, "APILOCK: " fmt LOCK_FMT_FFL "\n", ##__VA_ARGS__, file, func, linenum)
#define LOCKMSGFLUSH() fflush(pFile)

then

void show_locks()
{
   pFile = fopen ("/tmp/cglocks","w");
..........


   fclose (pFile);

}

So no need to stare over console and catch the lines moving

PS:

Guy's
What about
   cg_wlock(&control_lock);
   .....local_work++;
   .....total_work++;
   cg_wunlock(&control_lock);
I think there is a need to lock them everywhere or ?

Thanks

[storm2k5]

Hashfast per die clock rate setting:

I have noticed that in driver-hashfast.c, there seems to be adaptive clock rate setting per die:

Code:

applog(LOG_INFO, "%s %d: Die temp below range %.1f, increasing die %d clock to %d",
hashfast->drv->name, hashfast->device_id, info->die_data[die].temp, die, hdd->hash_clock);
hfa_send_frame(hashfast, HF_USB_CMD(OP_WORK_RESTART), hdata, (uint8_t *)&diebit, 4);

Is there a way to set per die clock from command line or conf file? Reason I'm asking is one of my dies seems to work fine up to 150MHz then it completely stops working and I would like to clock dies 0-2 with normal clock and underclock die 3.

Edit: By the looks of your comments and the code it seems that per die clock setting will be possible for FW 0.5 and up. Do you already got FW 0.5 from hashfast by any chance?

[-ck]

PS:

Guy's
What about
   cg_wlock(&control_lock);
   .....local_work++;
   .....total_work++;
   cg_wunlock(&control_lock);
I think there is a need to lock them everywhere or ?

Thanks

Mostly harmless, but probably wouldn't hurt to protect them with the write lock for when mining at multiple different types of pools at once (eg GBT + stratum), yes, thanks.

[-ck]

Hashfast per die clock rate setting:

I have noticed that in driver-hashfast.c, there seems to be adaptive clock rate setting per die:

Code:

applog(LOG_INFO, "%s %d: Die temp below range %.1f, increasing die %d clock to %d",
hashfast->drv->name, hashfast->device_id, info->die_data[die].temp, die, hdd->hash_clock);
hfa_send_frame(hashfast, HF_USB_CMD(OP_WORK_RESTART), hdata, (uint8_t *)&diebit, 4);

Is there a way to set per die clock from command line or conf file? Reason I'm asking is one of my dies seems to work fine up to 150MHz then it completely stops working and I would like to clock dies 0-2 with normal clock and underclock die 3.

Edit: By the looks of your comments and the code it seems that per die clock setting will be possible for FW 0.5 and up. Do you already got FW 0.5 from hashfast by any chance?

Older firmware 0.3+ can do per die clockspeeds as well but when there is a large difference in the clocks it causes huge dips and peaks in the metering out of work which can present temperature and other issues. It is not possible to set clock speed per die on the command line yet but it is possible to add that feature.

[Sinturvy]

After patching the cgminer 4.0.0 patch (HEX16 by Technobit) I tried to "make" my cgminer-4.0.0 with MinGW/MSYS-Shell for the HEX16B. But it failed!

Code:

Sinturvy@SINNETWORK ~/cgminer-3.8.5
$ make
make  all-recursive
make[1]: Entering directory `/home/Sinturvy/cgminer-3.8.5'
Making all in lib
make[2]: Entering directory `/home/Sinturvy/cgminer-3.8.5/lib'
  GEN    arg-nonnull.h
  GEN    c++defs.h
  GEN    warn-on-use.h
  GEN    signal.h
  GEN    string.h
make  all-recursive
make[3]: Entering directory `/home/Sinturvy/cgminer-3.8.5/lib'
make[4]: Entering directory `/home/Sinturvy/cgminer-3.8.5/lib'
  CC     dummy.o
  CC     memmem.o
  CC     sigaction.o
  CC     sigprocmask.o
  AR     libgnu.a
make[4]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/lib'
make[3]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/lib'
make[2]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/lib'
Making all in compat
make[2]: Entering directory `/home/Sinturvy/cgminer-3.8.5/compat'
Making all in jansson-2.5
make[3]: Entering directory `/home/Sinturvy/cgminer-3.8.5/compat/jansson-2.5'
make  all-recursive
make[4]: Entering directory `/home/Sinturvy/cgminer-3.8.5/compat/jansson-2.5'
Making all in src
make[5]: Entering directory `/home/Sinturvy/cgminer-3.8.5/compat/jansson-2.5/src
'
  CC     dump.lo
  CC     error.lo
  CC     hashtable.lo
  CC     load.lo
  CC     memory.lo
  CC     pack_unpack.lo
  CC     strbuffer.lo
  CC     strconv.lo
  CC     utf.lo
  CC     value.lo
  CCLD   libjansson.la
Creating library file: .libs/libjansson.dll.a
make[5]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/compat/jansson-2.5/src'

make[5]: Entering directory `/home/Sinturvy/cgminer-3.8.5/compat/jansson-2.5'
make[5]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/compat/jansson-2.5'
make[4]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/compat/jansson-2.5'
make[3]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/compat/jansson-2.5'
Making all in libusb-1.0
make[3]: Entering directory `/home/Sinturvy/cgminer-3.8.5/compat/libusb-1.0'
make  all-recursive
make[4]: Entering directory `/home/Sinturvy/cgminer-3.8.5/compat/libusb-1.0'
Making all in libusb
make[5]: Entering directory `/home/Sinturvy/cgminer-3.8.5/compat/libusb-1.0/libu
sb'
  CC     libusb_1_0_la-core.lo
  CC     libusb_1_0_la-descriptor.lo
  CC     libusb_1_0_la-io.lo
  CC     libusb_1_0_la-sync.lo
  CC     os/libusb_1_0_la-poll_windows.lo
  CC     os/libusb_1_0_la-windows_usb.lo
  GEN    libusb-1.0.lo
  CC     libusb_1_0_la-hotplug.lo
  CC     os/libusb_1_0_la-threads_windows.lo
  CCLD   libusb-1.0.la
Creating library file: .libs/libusb-1.0.dll.a
make[5]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/compat/libusb-1.0/libus
b'
make[5]: Entering directory `/home/Sinturvy/cgminer-3.8.5/compat/libusb-1.0'
make[5]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/compat/libusb-1.0'
make[4]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/compat/libusb-1.0'
make[3]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/compat/libusb-1.0'
make[3]: Entering directory `/home/Sinturvy/cgminer-3.8.5/compat'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/compat'
make[2]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/compat'
Making all in ccan
make[2]: Entering directory `/home/Sinturvy/cgminer-3.8.5/ccan'
  CC     opt/libccan_a-helpers.o
  CC     opt/libccan_a-opt.o
  CC     opt/libccan_a-parse.o
  CC     opt/libccan_a-usage.o
  AR     libccan.a
make[2]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/ccan'
make[2]: Entering directory `/home/Sinturvy/cgminer-3.8.5'
  CC     cgminer-cgminer.o
  CC     cgminer-util.o
  CC     cgminer-sha2.o
  CC     cgminer-api.o
  CC     cgminer-logging.o
  CC     cgminer-usbutils.o
usbutils.c: In Funktion »_usb_init«:
usbutils.c:1760:5: Warnung: Unverträgliche implizite Deklaration der eingebauten
 Funktion »bzero« [standardmäßig aktiviert]
  CC     cgminer-driver-hexminera.o
driver-hexminera.c: In Funktion »hexminera_get_results«:
driver-hexminera.c:278:5: Warnung: Unverträgliche implizite Deklaration der eing
ebauten Funktion »bzero« [standardmäßig aktiviert]
  CC     cgminer-driver-hexminerb.o
driver-hexminerb.c: In Funktion »hexminerb_get_results«:
driver-hexminerb.c:290:3: Warnung: Unverträgliche implizite Deklaration der eing
ebauten Funktion »bzero« [standardmäßig aktiviert]
  CC     cgminer-driver-hexminerc.o
driver-hexminerc.c: In Funktion »hexminerc_get_results«:
driver-hexminerc.c:276:5: Warnung: Unverträgliche implizite Deklaration der eing
ebauten Funktion »bzero« [standardmäßig aktiviert]
  CCLD   cgminer.exe
make[2]: Leaving directory `/home/Sinturvy/cgminer-3.8.5'
make[1]: Leaving directory `/home/Sinturvy/cgminer-3.8.5'

Sinturvy@SINNETWORK ~/cgminer-3.8.5
$

CGminer.exe is compiled but I'm getting the following error:

Code:

USB init, open device failed, err -12, you need to install a WinUSB driver for - HEXb device 3:2
See README.txt file included for help
hexminerb detect (3:2) failed to initialise (incorrect device?)
No devices detected!
Waiting for USB hotplug devices or press q to quit

Would be awesome if anyone could help me!

[-ck]

After patching the cgminer 4.0.0 patch (HEX16 by Technobit) I tried to "make" my cgminer-4.0.0 with MinGW/MSYS-Shell for the HEX16B. But it failed!

Would be awesome if anyone could help me!

We do not support external patches on the cgminer code. Seek help from whoever provided those patches. Though it looks like you just need to do what it says: install a winusb driver.

[Sinturvy]

Yeah, would be a mess if you would do so.
I already installed the WinUSB Driver which is provided by Technobit. I'll ask their support.
Thanks ckolivas

Edit: Do you think the Compile-Error has something to do about the detection-error? I also can't find a *.cl File in my directory.

Edit II: Your WinUSB Devicepicker (http[Suspicious link removed]) worked. Thanks!

[-ck]

For those of you on windows who have devices that don't show up on USB3 slots, you can try the following binary (it is otherwise identical to the 4.2.1 release):

http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

If it turns out to fix the problems, I might just re-package 4.2.1 for windows.

[winit]

Hi Con,

Firstly thanks for all the updates aimed at Hashfast devices, 4.2 has helped a lot.

As all Sierra's are not born equal I need to run them at different clock speeds. I successfully used the '--hfa-name Slug --usb 4:42' to rename one device to later allow me to use '--hfa-options "rabbit:650,turtle:550"'
If I add more renaming to the string it simply doesn't find any device. Can you tell me what I have wrong with the below?

--hfa-name NS1 --usb 1:7 --hfa-name NS2 --usb 2:7 --hfa-name NS3 --usb 2:4

Thanks