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

[derjanb]

It seems that the share diff calculation is somehow broken? Usually the diff is the higher the more zero bits are at the beginning of the share, right?

[2013-11-04 08:07:35] Accepted 36fbfe43 Diff 1.19K/2 AMU 2 pool 0
 [2013-11-04 08:42:49] Accepted 31ca6a09 Diff 1.32K/7 AMU 1 pool 1
 [2013-11-04 09:03:48] Accepted 050ce41f Diff 13K/2 AMU 1 pool 0
 [2013-11-04 09:05:12] Accepted 17ad04b5 Diff 2.77K/2 AMU 1 pool 0
 [2013-11-04 09:11:50] Accepted 7aef6014 Diff 533/2 AMU 0 pool 0

I'm using the git version 8b38d7fec8 (still 3.6.6) but there are only README and configure changes to 3.7.0.

[-ck]

It seems that the share diff calculation is somehow broken? Usually the diff is the higher the more zero bits are at the beginning of the share, right?

[2013-11-04 08:07:35] Accepted 36fbfe43 Diff 1.19K/2 AMU 2 pool 0
 [2013-11-04 08:42:49] Accepted 31ca6a09 Diff 1.32K/7 AMU 1 pool 1
 [2013-11-04 09:03:48] Accepted 050ce41f Diff 13K/2 AMU 1 pool 0
 [2013-11-04 09:05:12] Accepted 17ad04b5 Diff 2.77K/2 AMU 1 pool 0
 [2013-11-04 09:11:50] Accepted 7aef6014 Diff 533/2 AMU 0 pool 0

I'm using the git version 8b38d7fec8 (still 3.6.6) but there are only README and configure changes to 3.7.0.

- Accepted share will trim off all paired zeroes.

[derjanb]

- Accepted share will trim off all paired zeroes.

Phew! It seems I've over-read that. Thanks for all your hard work and your quick reply.

[pooler]

ckolivas

it is normal for 3.6.6-1?
in other versions there is no such
This is not a solo. So on any script coins. Not only at me.
3.6.4 works fine
 

Yeah I probably screwed that up for $scryptcoins when I fixed it for bitcoin.

I thought I'd confirm this, as more and more scrypt miners are getting confused.
Commits 3f6b9d67 and 36c6da8 introduce an inconsistency between share difficulty and network difficulty when cgminer is in scrypt mode. This causes many shares to be considered as blocks, even when they are not.
This doesn't seem to cause any real issue, but if you're getting annoyed by all those fake "Found block" messages, just use the stable version (tag v3.6.6).

If you could try latest git, I'd like to confirm that I've fixed the issue before releasing a new version.

Did you commit the fix? I cannot find it in the commit history.
I have tried the latest master (tag v3.7.0) from the git repo, and the bug is still there.

[-ck]

Did you commit the fix? I cannot find it in the commit history.
I have tried the latest master (tag v3.7.0) from the git repo, and the bug is still there.

Well, no one confirmed whether I had fixed it or not, so I had to run blind. Therefore the bug is still there.

[pooler]

Did you commit the fix? I cannot find it in the commit history.
I have tried the latest master (tag v3.7.0) from the git repo, and the bug is still there.

Well, no one confirmed whether I had fixed it or not, so I had to run blind. Therefore the bug is still there.

Sorry for the misunderstanding. When I posted my report, it was referred to the latest git master (that's why I suggested users to revert to v3.6.6 instead of just pulling the latest commits). Since no related commit appeared after my post, I thought you were working on a fix and you still had to push it to the git repo. My bad, I should probably have been more explicit.

[-ck]

Did you commit the fix? I cannot find it in the commit history.
I have tried the latest master (tag v3.7.0) from the git repo, and the bug is still there.

Well, no one confirmed whether I had fixed it or not, so I had to run blind. Therefore the bug is still there.

Sorry for the misunderstanding. When I posted my report, it was referred to the latest git master (that's why I suggested users to revert to v3.6.6 instead of just pulling the latest commits). Since no related commit appeared after my post, I thought you were working on a fix and you still had to push it to the git repo. My bad, I should probably have been more explicit.

In that case I suggest scrypt miners stick to 3.6.6 (not 3.6.6-1 or later).

[nitrox]

cgminer will officially supports HEH16A form technobit.eu ?

[kano]

cgminer will officially supports HEH16A form technobit.eu ?

Looking at their web site they have a collection of all sorts of low hashing devices and one 40GH/s device.
The 40GH/s device has it's own miner in it so obviously that one isn't relevant.
The others, no idea coz we haven't seen any of them and no one has sent them to us.

[jmc1517]

Next step after LOL has to be:

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

Skip that and go straight to

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

I'm getting itchy here with too much accumulated for a new release, so consider lmfao as the release candidate.

EDIT: Never mind,  v3.7.0 is out which is basically the same as lmfao. Just try that one.

Thank you for the generous comments in the changelog *blush*

Ran 3.5.1 overnight, no problems. Skipped "lol", "lmfao" etc as suggested and started 3.7.0 this morning, without logging.
Unfortunately got a zombie after no more than a minute. Re-plugged it and went off for breakfast. Came back to find a new zombie.

I've now made a clean start with 3.7.0 with logging. Broadband has been up and down, which it has coped with, so I'll just let it run and see what happens.  I assume it's of no benefit to go back and test "lol" etc.?

[-ck]

Next step after LOL has to be:

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

Skip that and go straight to

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

I'm getting itchy here with too much accumulated for a new release, so consider lmfao as the release candidate.

EDIT: Never mind,  v3.7.0 is out which is basically the same as lmfao. Just try that one.

Thank you for the generous comments in the changelog *blush*

Ran 3.5.1 overnight, no problems. Skipped "lol", "lmfao" etc as suggested and started 3.7.0 this morning, without logging.
Unfortunately got a zombie after no more than a minute. Re-plugged it and went off for breakfast. Came back to find a new zombie.

I've now made a clean start with 3.7.0 with logging. Broadband has been up and down, which it has coped with, so I'll just let it run and see what happens.  I assume it's of no benefit to go back and test "lol" etc.?

No point testing any of those earlier ones. Yours looks more resistant to being fixed than aigeezer's too. You have lots of problems... and I have nothing new for you to test at this time.

[Illutian]

Is there anyway to change the layout.

Currently my 18 erupters show up like this:
(Marked and pasted from the command prompt; no formatting changes made, except for adding a '.' in the brackets to avoid a forum post formatting issue)

[P.]ool management [S.]ettings [D.]isplay options [Q.]uit
AMU  0:                 | 335.7M/325.3Mh/s | A:16 R:0 HW:0 WU: 4.8/m
AMU  1:                 | 335.5M/340.3Mh/s | A:10 R:0 HW:0 WU: 3.2/m
AMU  2:                 | 335.5M/322.7Mh/s | A: 8 R:0 HW:0 WU: 4.0/m
AMU  3:                 | 335.5M/340.8Mh/s | A:16 R:0 HW:0 WU: 5.5/m
AMU  4:                 | 336.6M/341.4Mh/s | A:14 R:0 HW:2 WU: 6.7/m
AMU  5:                 | 335.4M/335.8Mh/s | A:12 R:0 HW:0 WU: 4.8/m
AMU  6:                 | 335.5M/331.3Mh/s | A: 8 R:0 HW:0 WU: 2.8/m
AMU  7:                 | 335.3M/315.4Mh/s | A: 8 R:0 HW:0 WU: 3.6/m
AMU  8:                 | 335.6M/341.7Mh/s | A: 8 R:0 HW:0 WU: 3.6/m
AMU  9:                 | 335.5M/341.5Mh/s | A: 4 R:0 HW:0 WU: 2.0/m
AMU 10:                 | 335.5M/326.0Mh/s | A: 6 R:0 HW:0 WU: 4.4/m
AMU 11:                 | 335.5M/332.3Mh/s | A:12 R:0 HW:0 WU: 4.4/m
AMU 12:                 | 335.4M/325.7Mh/s | A:10 R:0 HW:0 WU: 3.6/m
AMU 13:                 | 335.5M/340.7Mh/s | A:10 R:0 HW:0 WU: 4.0/m
AMU 14:                 | 335.6M/341.6Mh/s | A:10 R:0 HW:0 WU: 4.0/m AMU 15:  /

But all 18 are crunching away:

(5s):5.942G (avg):5.883Gh/s | A:252  R:0  HW:4  WU:76.0/m

[-Redacted-]

Try the up and down arrows...

[Illutian]

Try the up and down arrows...

That does nothing. Doesn't even most the blinking prompt line.

I should also mention that because of the formatting I can't see any of the 'Settings', 'Pool Management', or 'Display options' messages.

[jmc1517]

No point testing any of those earlier ones. Yours looks more resistant to being fixed than aigeezer's too. You have lots of problems... and I have nothing new for you to test at this time.

Well I could suggest going back to the code in 3.5.1 - which seems to work flawlessly for me - but I'm not good at dodging flying objects...!!!  Seriously, I do appreciate all the time and effort you've been putting into this, and if a solution is not forthcoming, then I can happily stay with 3.5.1 or even 3.3.1 for my particular setup.

Last run of 3.7.0 produced one zombie after 2 hours.  I came back after 4 hours, so just the one. Logfile here if required:
 https://dl.dropboxusercontent.com/u/44240170/logfile-3.7.0.txt

Edited to correct formatting.

[dlasher]

[snip comments about 'waiting for pool issue']

On further investigation, I've found how this can happen, and have committed a fix for this into git so it should go into the next version. The actual issue goes back quite a way so backtracking versions will not avoid it.

Thanks, heard more comments about people running into it over the weekend from KNC users, who, of course in 0.98 firmware, went to cgminer 3.6.6.

by the way, is this the fix:

- Use a non blocking connect with a 1 second select timeout when initiating
stratum to allow us to iterate over all IPs returned by getaddrinfo in round
robin DNS pools.

I know I haven't said it for at least 1-2 versions, but thank you again for your continued commitment to CGMINER. It only seems to get better and better over time.

It's a pity you didn't write a secret "send 0.1% to the author" into cgminer.. you'd be filthy rich by now from all of us mining with it. In all seriousness, perhaps you should put in a command-line switch.. don't make it default, but make it explicit, like --donate-author %

[-Redacted-]

Checkbox to do that, yes.  I'd check that.
Secretly do that - once discovered, that would be the end of cgminer.

[ksenter]

Could something that changed in 3.7.0 have broken mining on p2pool?  I just tried upgrading and it just closed immediately after I ran it.  

Edit: forgot to add log..

 [2013-11-04 11:29:34] Started cgminer 3.7.0
 [2013-11-04 11:29:36] Probing for an alive pool
 [2013-11-04 11:29:36] Switching pool 0 http://127.0.0.1:9332 to stratum+tcp://127.0.0.1:9332
 [2013-11-04 11:29:36] Pool 0 difficulty changed to 7.328747
 [2013-11-04 11:29:36] Network diff set to 391M
 [2013-11-04 11:29:36] Stratum from pool 0 requested work restart

Then it closed...

[Askit2]

Started 3.7.0 when it was released. I hadn't turned logging on so this won't likely be of much help. Plus it was already reported. Still here is what I came back to.

Code:

 cgminer version 3.7.0 - Started: [2013-11-04 05:15:39]
--------------------------------------------------------------------------------
 (5s):0.000 (avg):7.981Gh/s | A:32182  R:32  HW:276  WU:111.6/m
 ST: 0  SS: 0  NB: 4  LW: 33213  GF: 0  RF: 0
 Connected to multiple pools with block change notify
 Block: 7ac0fe1f...  Diff:391M  Started: [05:42:01]  Best share: 36.2K
--------------------------------------------------------------------------------
 [P]ool management [S]ettings [D]isplay options [Q]uit
 BAJ  0:  max 32C 3.43V | 4.862G/439.6Mh/s | A:1880 R:0 HW:  0 WU:  6.2/m
 BAJ  1:  max 32C 3.73V | 5.329G/466.7Mh/s | A:1990 R:0 HW:  0 WU:  6.4/m
 BAJ  2:  max 31C 3.65V | 5.354G/474.4Mh/s | A:1465 R:0 HW:  0 WU:  6.8/m
 BAJ  3:  max 33C 3.32V | 4.867G/433.3Mh/s | A:1922 R:0 HW:  7 WU:  6.0/m
 BAJ  4:  max 30C 4.04V | 5.874G/523.7Mh/s | A:2130 R:0 HW:  0 WU:  7.2/m
 BAJ  5:  max 30C 3.15V | 4.980G/435.7Mh/s | A:1753 R:0 HW: 52 WU:  5.7/m
 BAJ  6:  max 32C 3.33V | 5.078G/448.7Mh/s | A:1756 R:0 HW:  1 WU:  6.5/m
 BAJ  7:  max 31C 3.46V | 5.665G/501.1Mh/s | A:2073 R:0 HW:  0 WU:  7.1/m
 BAJ  8:  max 29C 3.86V | 5.552G/487.4Mh/s | A:1921 R:0 HW:  0 WU:  6.9/m
 BAJ  9:  max 31C 2.28V | 5.619G/502.1Mh/s | A:2042 R:0 HW:  0 WU:  6.8/m
 BAJ 10:  max 31C 3.73V | 5.661G/481.6Mh/s | A:2094 R:0 HW:  0 WU:  7.0/m
 BAJ 11:  max 26C 3.51V | 4.810G/426.9Mh/s | A:1601 R:0 HW: 40 WU:  5.9/m
 BAJ 12:  max 29C 3.52V | 5.086G/453.8Mh/s | A:1759 R:0 HW:  0 WU:  6.5/m
 BAJ 13:  max 30C 3.96V | 5.118G/455.7Mh/s | A:1984 R:0 HW:  0 WU:  6.4/m
 BAJ 14:  max 29C 2.99V | 5.246G/462.7Mh/s | A:2211 R:0 HW:  0 WU:  6.6/m
 BAJ 15:  max 30C 3.83V | 5.579G/497.3Mh/s | A:1949 R:0 HW:111 WU:  6.8/m
 BAJ 16:  max 29C 3.71V | 5.448G/490.8Mh/s | A:1653 R:0 HW: 65 WU:  6.7/m
--------------------------------------------------------------------------------

 [2013-11-04 05:41:10] Accepted 03a19249 Diff 71/37 BAJ 3 pool 2
 [2013-11-04 05:41:17] Accepted 038254a8 Diff 73/37 BAJ 13 pool 2
 [2013-11-04 05:41:21] Accepted 063654e9 Diff 41/32 BAJ 5 pool 3
 [2013-11-04 05:41:21] Accepted 01895d09 Diff 167/32 BAJ 12 pool 3
 [2013-11-04 05:41:23] Accepted ca03713b Diff 324/37 BAJ 12 pool 2
 [2013-11-04 05:41:25] Accepted 062fe1a4 Diff 41/32 BAJ 7 pool 3
 [2013-11-04 05:41:28] Accepted 0424011a Diff 62/37 BAJ 12 pool 2
 [2013-11-04 05:41:29] Accepted 06de4660 Diff 37/32 BAJ 4 pool 3
 [2013-11-04 05:41:30] Accepted 01a3620a Diff 156/32 BAJ 9 pool 3
 [2013-11-04 05:41:30] Accepted 05815bc9 Diff 46/37 BAJ 5 pool 2
 [2013-11-04 05:41:33] Accepted 03489a3f Diff 78/37 BAJ 3 pool 2
 [2013-11-04 05:41:35] Accepted 0473473c Diff 58/37 BAJ 7 pool 2
 [2013-11-04 05:41:39] Accepted 01c0d4f4 Diff 146/37 BAJ 12 pool 2
 [2013-11-04 05:41:40] Accepted 0557207a Diff 48/37 BAJ 16 pool 2
 [2013-11-04 05:41:42] Accepted 736fe14f Diff 568/32 BAJ 1 pool 3
 [2013-11-04 05:41:44] Accepted 014c91dc Diff 197/32 BAJ 4 pool 3
 [2013-11-04 05:41:44] Accepted 06bad42c Diff 38/32 BAJ 8 pool 3
 [2013-11-04 05:41:45] Accepted 02a756e8 Diff 96/32 BAJ 9 pool 3
 [2013-11-04 05:41:45] Accepted 069b8966 Diff 39/37 BAJ 11 pool 2
 [2013-11-04 05:41:47] Accepted 041775b3 Diff 63/32 BAJ 4 pool 3
 [2013-11-04 05:41:51] Accepted 04419a6b Diff 60/37 BAJ 11 pool 2
 [2013-11-04 05:41:53] Accepted 052bc753 Diff 50/37 BAJ 9 pool 2
 [2013-11-04 05:41:58] Accepted 5d6981d9 Diff 702/37 BAJ 15 pool 2
 [2013-11-04 05:41:59] Accepted 848fab84 Diff 494/32 BAJ 1 pool 3
 [2013-11-04 05:42:01] New block detected on network before longpoll
 [2013-11-04 05:42:01] Pool 3 stale share detected, submitting as user requested
 [2013-11-04 05:42:01] Accepted 0724f753 Diff 36/32 BAJ 4 pool 3
 [2013-11-04 05:42:04] Stratum from pool 1 requested work restart
 [2013-11-04 05:42:06] Stratum from pool 0 requested work restart
 [2013-11-04 05:42:06] Pool 2 difficulty changed to 32.949399
 [2013-11-04 05:42:06] Stratum from pool 2 requested work restart

I came back at 10:08 or really close to that. Odd that it stopped on a restart. Well a series of restarts.

Raspberry pi running arch and quotas to split hashing to 3 pools. Do the quota numbers matter? Failover only is also enabled so that the two backups should only work as backups.

[LB72]

HI


I use cgminer 3.7 and the message :

KnC spi: Can not open SPI device /dev/spidev1.0: No such file or directory

I don't use KNC Miner. How can I disable that ?

OS : Archlinux


Thank you