Hi, thank you.
But here this too prints some gigantic/unrealistic WU rates, and hash rates in the TH/s range, see below.
If we assume that the TH/s means GH/s then I observed that the hash rate after a few hours sinks down from 450 to about 200 GH/s. Does this not happen with your S3?
BTW, I think your binary has all drivers included as the size of the binary is about twice the size compared to mine that has only the code for S3 enabled.


^C [2017-07-24 09:58:30.888] Shutdown signal received.                    
 [2017-07-24 09:58:30.979]
Summary of runtime statistics:
                    
 [2017-07-24 09:58:30.979] Started at [2017-07-24 09:56:36.980]                    
 [2017-07-24 09:58:30.979] Pool: http://37.139.71.2:8332                    
 [2017-07-24 09:58:30.979] Runtime: 0 hrs : 1 mins : 53 secs                    
 [2017-07-24 09:58:30.979] Average hashrate: 416358026.8 Mhash/s                    
 [2017-07-24 09:58:30.979] Solved blocks: 0                    
 [2017-07-24 09:58:30.980] Best share difficulty: 1.36K                    
 [2017-07-24 09:58:30.980] Share submissions: 0                    
 [2017-07-24 09:58:30.980] Accepted shares: 0                    
 [2017-07-24 09:58:30.980] Rejected shares: 0                    
 [2017-07-24 09:58:30.980] Accepted difficulty shares: 0                    
 [2017-07-24 09:58:30.980] Rejected difficulty shares: 0                    
 [2017-07-24 09:58:30.980] Hardware errors: 0                    
 [2017-07-24 09:58:30.980] Utility (accepted shares / min): 0.00/min                    
 [2017-07-24 09:58:30.980] Work Utility (diff1 shares solved / min): 5816454.46/min
                    
 [2017-07-24 09:58:30.980] Stale submissions discarded due to new blocks: 0                    
 [2017-07-24 09:58:30.981] Unable to get work from server occasions: 0                    
 [2017-07-24 09:58:30.981] Work items generated locally: 9290                    
 [2017-07-24 09:58:30.981] Submitting work remotely delay occasions: 0                    
 [2017-07-24 09:58:30.981] New blocks detected on network: 2
                    
 [2017-07-24 09:58:30.981] Summary of per device statistics:
                    
 [2017-07-24 09:58:30.981] AS3 0 (10s):422.0T (avg):416.4Th/s | A:0 R:0 HW:0 WU:5816454.5/m                    
 [2017-07-24 09:58:30.981]                      


'''''''''''''''''''''''''''
UPDATE:
'''''''''''''''''''''''''''
It seems that since version 4.7.0 some of the bitmain parameters have changed.
So, after renaming the config file /etc/config/cgminer, and using the following params
now version 4.10.0 seems to work fine in the console:

     --bitmain-voltage 0725 \
     --bitmain-freq    16:250:0982 \
     --bitmain-options 115200:32:32:16:250:0982 \
     --bitmain-fan     20-100 \
     --bitmain-auto \
     --bitmain-notempoverctrl --bitmain-nobeeper --bitmain-checkn2diff --bitmain-hwerror \
     ...

So, then this case can be closed :-)


But I think the above given compiler warnings need to be fixed in the code. I had made the following modification in driver-bitmain.h to eliminate the warnings:

// #define BITMAIN_MAX_CHAIN_NUM      8
#define BITMAIN_MAX_CHAIN_NUM      16