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

[mutluit]

I think there is a big bug in cgminer's driver-icarus.c:

ICARUS_UNUSED_SIZE is defined as 16. IMO this should be 20.
ICARUS_WORK_DATA_OFFSET is defined as 64. IMO this should be 68.
(there are maybe even more wrong values)

Can you verify/confirm this?

So, have all the miners who use cgminer with icarus devices been misled?

BTW. the source code of this program is really a PITA to study :-(

[1713289537]

1713289537

[1713289537]

1713289537

[1713289537]

1713289537

[Larz952002]

I am a total noob when I comes to this miner, I tried to follow the instructions to the best of my ability but it tells me it is a 32bit program and I have win10 and 64 bit.  does anyone have this program completed and runs on a 64bit

[-ck]

I am a total noob when I comes to this miner, I tried to follow the instructions to the best of my ability but it tells me it is a 32bit program and I have win10 and 64 bit.  does anyone have this program completed and runs on a 64bit

All 32 bit programs run on 64 bit windows.

[Dropwise]

Dear CK,

I am experiencing a Segmentation Fault (core dumped) error when trying to write config file in version 4.10.0.   (I do not have this error with version 4.9.2).  

(it seems to write over cgminer.conf with an empty file, then crash)

I am running on R-PI, ARCH.    

Any advice?

Thanks!

[mutluit]

I need to compile the recent version to be run on AntMiner S1.
On the S1 there is not much space and also no gcc compiler installed.
I can compile it on the PC, but then I wonder if I need a cross-compiler since the target HW seems to be MIPS?

EDIT:
Ok, I finally figured it out: one of the methods is by using qemu and starting a linux mips distribution therein, and then the usual steps to build the binary...
Since qemu is an emulator, everything runs much slower, but no problem, I'm currently compiling it...

[mutluit]

Hi,
while solo mining I got this log entry:

 [2017-07-06 12:14:52] Share submissions: 1
 [2017-07-06 12:14:52] Accepted shares: 0
 [2017-07-06 12:14:52] Rejected shares: 1
 [2017-07-06 12:14:52] Accepted difficulty shares: 0
 [2017-07-06 12:14:52] Rejected difficulty shares: 708659466230

At 2017-07-06 19:56 UTC:
$ bin/bitcoin-cli getdifficulty
  708659466230.332

Does it mean I missed it by the decimals??? :-(


UPDATE: today again such a case happened:

Summary of runtime statistics:
                   
 [2017-07-09 17:31:41] Started at [2017-07-09 17:04:34]                   
 [2017-07-09 17:31:41] Pool: http://37.139.71.2:8332                   
 [2017-07-09 17:31:41] Runtime: 0 hrs : 27 mins : 6 secs                   
 [2017-07-09 17:31:41] Average hashrate: 177583.4 Mhash/s                   
 [2017-07-09 17:31:41] Solved blocks: 0                   
 [2017-07-09 17:31:41] Best share difficulty: 26.5K                   
 [2017-07-09 17:31:41] Share submissions: 1                   
 [2017-07-09 17:31:41] Accepted shares: 0                   
 [2017-07-09 17:31:41] Rejected shares: 1                   
 [2017-07-09 17:31:41] Accepted difficulty shares: 0                   
 [2017-07-09 17:31:41] Rejected difficulty shares: 708659466230                   
 [2017-07-09 17:31:41] Reject ratio: 100.0%                   
 [2017-07-09 17:31:41] Hardware errors: 30                   
 [2017-07-09 17:31:41] Utility (accepted shares / min): 0.00/min                   
 [2017-07-09 17:31:41] Work Utility (diff1 shares solved / min): 2480.90/min
                   
 [2017-07-09 17:31:41] Stale submissions discarded due to new blocks: 0                   
 [2017-07-09 17:31:41] Unable to get work from server occasions: 0                   
 [2017-07-09 17:31:41] Work items generated locally: 69978                   
 [2017-07-09 17:31:41] Submitting work remotely delay occasions: 0                   
 [2017-07-09 17:31:41] New blocks detected on network: 2
                   
 [2017-07-09 17:31:41] Summary of per device statistics:
                   
 [2017-07-09 17:31:41] S1A0 (30s):180.8G (avg):177.6Gh/s | A:0 R:708659466230 HW:30 WU:2480                   
 [2017-07-09 17:31:41]                     


# cat share.log
1499619895,reject:high-hash,000000000000000000000000000000000000000000308d010000000000000000,http://37.139.71.2:8332,S1A0,0,0000000000000000000000000000000000000000000000000000000000000000,200000020829b3bff0c10fd348e41756aea13ad0d504ba28003d3b630000000000000000af3e784c5bfedc4b79b6f07c32e663759b2a9fc9755887d283e893ba5d7343ea5962622618018d3000000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000


Can the author or anybody else please tell me why and what's going on here? Thx

[-ck]

while solo mining I got this log entry:

At 2017-07-06 19:56 UTC:
$ bin/bitcoin-cli getdifficulty
  708659466230.332

Does it mean I missed it by the decimals??? :-(

Summary of runtime statistics:
                   
 [2017-07-09 17:31:41] Started at [2017-07-09 17:04:34]                   
 [2017-07-09 17:31:41] Pool: http://37.139.71.2:8332                   
 [2017-07-09 17:31:41] Runtime: 0 hrs : 27 mins : 6 secs                   
 [2017-07-09 17:31:41] Average hashrate: 177583.4 Mhash/s                   
 [2017-07-09 17:31:41] Solved blocks: 0                   
 [2017-07-09 17:31:41] Best share difficulty: 26.5K                   
 [2017-07-09 17:31:41] Share submissions: 1                   
 [2017-07-09 17:31:41] Accepted shares: 0                   
 [2017-07-09 17:31:41] Rejected shares: 1                   
 [2017-07-09 17:31:41] Accepted difficulty shares: 0                   
 [2017-07-09 17:31:41] Rejected difficulty shares: 708659466230                   
 [2017-07-09 17:31:41] Reject ratio: 100.0%                   
 [2017-07-09 17:31:41] Hardware errors: 30                   
 [2017-07-09 17:31:41] Utility (accepted shares / min): 0.00/min                   
 [2017-07-09 17:31:41] Work Utility (diff1 shares solved / min): 2480.90/min
                   
 [2017-07-09 17:31:41] Stale submissions discarded due to new blocks: 0                   
 [2017-07-09 17:31:41] Unable to get work from server occasions: 0                   
 [2017-07-09 17:31:41] Work items generated locally: 69978                   
 [2017-07-09 17:31:41] Submitting work remotely delay occasions: 0                   
 [2017-07-09 17:31:41] New blocks detected on network: 2
                   
 [2017-07-09 17:31:41] Summary of per device statistics:
                   
 [2017-07-09 17:31:41] S1A0 (30s):180.8G (avg):177.6Gh/s | A:0 R:708659466230 HW:30 WU:2480                   
 [2017-07-09 17:31:41]                     


# cat share.log
1499619895,reject:high-hash,000000000000000000000000000000000000000000308d010000000000000000,http://37.139.71.2:8332,S1A0,0,0000000000000000000000000000000000000000000000000000000000000000,200000020829b3bff0c10fd348e41756aea13ad0d504ba28003d3b630000000000000000af3e784c5bfedc4b79b6f07c32e663759b2a9fc9755887d283e893ba5d7343ea5962622618018d3000000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000


Can the author or anybody else please tell me why and what's going on here? Thx

You are always mining at the current network diff when solo mining so any "shares" submitted are effectively considered the network diff so any rejects will be shown to be at the network diff as well. "Diff shares" is number of shares (in this case 1) multiplied by the difficulty you're mining at (in this case network diff). You definitely didn't even get close to the network diff but the software decided to try submitting a share anyway and it got rejected. You can see what your best share was, it was only 26,500 when network diff is 708 billion.

[mutluit]

You are always mining at the current network diff when solo mining so any "shares" submitted are effectively considered the network diff so any rejects will be shown to be at the network diff as well. "Diff shares" is number of shares (in this case 1) multiplied by the difficulty you're mining at (in this case network diff). You definitely didn't even get close to the network diff but the software decided to try submitting a share anyway and it got rejected. You can see what your best share was, it was only 26,500 when network diff is 708 billion.

But why did the software do that? Isn't that a bug?

[-ck]

You are always mining at the current network diff when solo mining so any "shares" submitted are effectively considered the network diff so any rejects will be shown to be at the network diff as well. "Diff shares" is number of shares (in this case 1) multiplied by the difficulty you're mining at (in this case network diff). You definitely didn't even get close to the network diff but the software decided to try submitting a share anyway and it got rejected. You can see what your best share was, it was only 26,500 when network diff is 708 billion.

But why did the software do that? Isn't that a bug?

A harmless bug, but a bug yes. Are you running the current version?

[mutluit]

You are always mining at the current network diff when solo mining so any "shares" submitted are effectively considered the network diff so any rejects will be shown to be at the network diff as well. "Diff shares" is number of shares (in this case 1) multiplied by the difficulty you're mining at (in this case network diff). You definitely didn't even get close to the network diff but the software decided to try submitting a share anyway and it got rejected. You can see what your best share was, it was only 26,500 when network diff is 708 billion.

But why did the software do that? Isn't that a bug?

A harmless bug, but a bug yes. Are you running the current version?

It's cgminer version 4.7.1
Is there a newer openwrt opkg version available?

[-ck]

It's cgminer version 4.7.1
Is there a newer openwrt opkg version available?

Well that would explain the breakage then. No idea about opkg versions, but additionally I don't believe any of the antminer forks remotely tried to stay in sync with the master cgminer.

[mutluit]

It's cgminer version 4.7.1
Is there a newer openwrt opkg version available?

Well that would explain the breakage then. No idea about opkg versions, but additionally I don't believe any of the antminer forks remotely tried to stay in sync with the master cgminer.

Maybe you got me wrong: I mean whether there is a newer binary version of cgminer available for the openwrt platform, ie. as a opkg-package.

[-ck]

It's cgminer version 4.7.1
Is there a newer openwrt opkg version available?

Well that would explain the breakage then. No idea about opkg versions, but additionally I don't believe any of the antminer forks remotely tried to stay in sync with the master cgminer.

Maybe you got me wrong: I mean whether there is a newer binary version of cgminer available for the openwrt platform, ie. as a opkg-package.

And as I said, I have no idea about opkg packages. I have nothing to do with their maintenance.

[bgibso01]

Anyone happen to know if I run CGMiner solo (w/ btc address) and point to a pruned node without a wallet, would the miner still receive the block rewards or is it based on bitcoind wallet address?

[mutluit]

It's cgminer version 4.7.1
Is there a newer openwrt opkg version available?

Well that would explain the breakage then. No idea about opkg versions, but additionally I don't believe any of the antminer forks remotely tried to stay in sync with the master cgminer.

Maybe you got me wrong: I mean whether there is a newer binary version of cgminer available for the openwrt platform, ie. as a opkg-package.

And as I said, I have no idea about opkg packages. I have nothing to do with their maintenance.

Ah, it seems that the said cgminer version for openwrt was created some years ago with this fork: https://github.com/kanoi/cgminer/tree/ants1-4.9.1c-e6ad32a
as was announced then here: https://bitcointalk.org/index.php?topic=1249569.0

[traderyo]

newb question so I apologise in advance:

What coins does CGminer actually support, where can I find this information? I cannot seem to find it anywhere?

[-ck]

newb question so I apologise in advance:

What coins does CGminer actually support, where can I find this information? I cannot seem to find it anywhere?

"Anywhere"? First line of the readme, last word.

[Dropwise]

Dear CK,

I am experiencing a Segmentation Fault (core dumped) error when trying to write config file in version 4.10.0.   (I do not have this error with version 4.9.2).  

(it seems to write over cgminer.conf with an empty file, then crash)

I am running on R-PI, ARCH.    

Any advice?

Thanks!

This didn't seem to get any kind of acknowledgement. I'm following it up here to see if anyone can help??

[-ck]

Dear CK,

I am experiencing a Segmentation Fault (core dumped) error when trying to write config file in version 4.10.0.   (I do not have this error with version 4.9.2).  

(it seems to write over cgminer.conf with an empty file, then crash)

I am running on R-PI, ARCH.    

Any advice?

Thanks!

This didn't seem to get any kind of acknowledgement. I'm following it up here to see if anyone can help??

Any chance you could get a backtrace? Google's gone crazy with blocking my website again so you may have to override security settings if you're on chrome.

http://ck.kolivas.org/apps/cgminer/debug/README-debug

[Dropwise]

Dear CK,

I am experiencing a Segmentation Fault (core dumped) error when trying to write config file in version 4.10.0.   (I do not have this error with version 4.9.2).  

(it seems to write over cgminer.conf with an empty file, then crash)

I am running on R-PI, ARCH.    

Any advice?

Thanks!

This didn't seem to get any kind of acknowledgement. I'm following it up here to see if anyone can help??

Any chance you could get a backtrace? Google's gone crazy with blocking my website again so you may have to override security settings if you're on chrome.

http://ck.kolivas.org/apps/cgminer/debug/README-debug

Sorry, not completely sure I follow you here.  You want me to rebuild with debugging and send you the logs, or you want me to sign up for backtrace service?  Can I please ask you to elaborate?