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

[-ck]

have anyone the same problem with the combination of these miners:

3 x BXM (BFx2)
1 x BXF (BiFury)

In the config i have these command, ("usb" : ":4",), but Cgminer doesn't recognized the BXF when i restart the Cgminer, theni must unplugged and then plug in the BiFury??

Then starts the BiFury the mining? No Hotplugin by the BXF?

No, that should work to hotplug the bifury. Is there a reason you're restricting it to 4 devices with that in your config?

[Buchi-88]

have anyone the same problem with the combination of these miners:

3 x BXM (BFx2)
1 x BXF (BiFury)

In the config i have these command, ("usb" : ":4",), but Cgminer doesn't recognized the BXF when i restart the Cgminer, theni must unplugged and then plug in the BiFury??

Then starts the BiFury the mining? No Hotplugin by the BXF?

No, that should work to hotplug the bifury. Is there a reason you're restricting it to 4 devices with that in your config?

Hi no there is no reason for the restriction, but at the Bfx2 miners has performed flawlessly? For the BiFury i must always make the Hotplug by hand? Then the Cgminer find the BXF Fury?

[-ck]

No, that should work to hotplug the bifury. Is there a reason you're restricting it to 4 devices with that in your config?

Hi no there is no reason for the restriction, but at the Bfx2 miners has performed flawlessly? For the BiFury i must always make the Hotplug by hand? Then the Cgminer find the BXF Fury?

No, as I said it should work. I have no idea why it doesn't, but it's also impossible to debug issues with deprecated hardware long out of commission unfortunately when there's no reason for them to start misbehaving when they didn't previously. Perhaps try an older cgminer.

[Buchi-88]

No, that should work to hotplug the bifury. Is there a reason you're restricting it to 4 devices with that in your config?

Hi no there is no reason for the restriction, but at the Bfx2 miners has performed flawlessly? For the BiFury i must always make the Hotplug by hand? Then the Cgminer find the BXF Fury?

No, as I said it should work. I have no idea why it doesn't, but it's also impossible to debug issues with deprecated hardware long out of commission unfortunately when there's no reason for them to start misbehaving when they didn't previously. Perhaps try an older cgminer.

THX, is the best Cgminer for the Bitfury sticks the 4.3.3?

regards

[-ck]

THX, is the best Cgminer for the Bitfury sticks the 4.3.3?

If that's the one that works best for you, probably unfortunately. The only stick I have left that still works is a BXM and that works fine with the latest, so I would be hoping that the latest is working best with the older hardware that I no longer have/use, but that's not always the case due to subtle interactions between drivers. It's very hard to maintain support for hardware that you no longer have (usually the hardware has died or it became so inefficient that no one was still running it).

[kano]

Update from my kano.is pool thread.

https://bitcointalk.org/index.php?topic=789369.msg11191279#msg11191279

Very interesting. I may point some has at this soon as I am currently back in "testing the waters mode". p2pool has been good to me and I've roi'd on 2 s1's but starting to see non-paying blocks. I'll be over shortly, have a beer waiting for me  

Well if I can update the S1/S2/S3 driver in a few days hopefully more of the S's will join too

I don't understand ? 

I have had s1 s2 and s3 s here and they work fine. Why do you need a new driver?

I still have s2s and s3s here.

Kano
Is there better software I should be running on Antminers?  I would like to make sure I'm getting the most from hardware.

at this point in mining anything that helps could make the difference of tuning them off or let them run . 

No, I asked bitmain to fund (10BTC) doing work on the S1/S2/S3 and they said no they are too old and wont waste money on them.
...

Wow, gotta say, totally awesome.

Bitmain of course dropped the ball on this and have given up on anyone who bought their S1/S2/S3 saying they don't care.

However, someone (who wants to remain anonymous) has sent me 10BTC and asked me to do the S1/S2/S3 work.

Guess I'll be spending the time on this over the next 2 weeks that I was asking to do and get the S1/S2 updated and sort out some p2pool issues, and also merge a working S3 into cgminer master
(and of course dust off my old S1/S2 and get them working again)

The kano.is pool problems (and a backend ckdb change I've been working on) have been taking a lot of my (and of course -ck's) time, but I think I can handle both (if I ignore everything else )

Good news

[JoseMendez]

Hi. Thank you for your effort developing cgminer. Im interested in working with cgminer to develop some programs (like a GUI) and I want to ask you to questions:

I just ordered today a Usb miner but I want to start right now to develop but I cant run Cgminer, there is part in code which I can rewrite or some other way to run 4.9.1 on testnet without a USB miner?

My next question is if I start to develop with an older version (which suports GPU mining) via API, my program would be compatible with 4.9.1 when I get my USB miner?

Thank you for your time.

[jonnybravo0311]

Hey -ck and kano... there's a version of cgminer floating around based on 4.7 with a patch by nicehash to support extranonce subscriptions.  it is described here: https://www.nicehash.com/index.jsp?p=software#cgminer

This is an excerpt from the README:

Bitmain AntMiner S3 binary with cgminer 4.7 and extranonce.subscribe

- sourced from: https://github.com/ckolivas/cgminer
- with patch from NiceHash https://github.com/nicehash/cgminer-ckolivas/commit/4e9c7ce68ed91ec9189d83c35b2237aca65f2b7f
- with Bitmaintech's AntMiner S3 driver

With extranonce.subscribe used with nicehash.com & westhash.com

My question is based on the part I bolded in the quote.  If I update my S3s to use this patch, does it also include the work you guys did to ensure the S3 doesn't throw away stale work that could solve blocks for p2pool?

Thanks in advance!

[-ck]

Hey -ck and kano... there's a version of cgminer floating around based on 4.7 with a patch by nicehash to support extranonce subscriptions.  it is described here: https://www.nicehash.com/index.jsp?p=software#cgminer

This is an excerpt from the README:

Bitmain AntMiner S3 binary with cgminer 4.7 and extranonce.subscribe

- sourced from: https://github.com/ckolivas/cgminer
- with patch from NiceHash https://github.com/nicehash/cgminer-ckolivas/commit/4e9c7ce68ed91ec9189d83c35b2237aca65f2b7f
- with Bitmaintech's AntMiner S3 driver

With extranonce.subscribe used with nicehash.com & westhash.com

My question is based on the part I bolded in the quote.  If I update my S3s to use this patch, does it also include the work you guys did to ensure the S3 doesn't throw away stale work that could solve blocks for p2pool?

Thanks in advance!

Extranonce support is a non standard stratum extension designed by nicehash just for nicehash to use to support their multicoin multipool proxy switching pseudo-pool. We have no interest in putting support for one service like that in mainline cgminer. Officially provided source and binaries by the cgminer team do not have extranonce support. Their patch also appears to introduce some kind of bug that prevents workers from switching away from a dead pool.

[kano]

Hi. Thank you for your effort developing cgminer. Im interested in working with cgminer to develop some programs (like a GUI) and I want to ask you to questions:

I just ordered today a Usb miner but I want to start right now to develop but I cant run Cgminer, there is part in code which I can rewrite or some other way to run 4.9.1 on testnet without a USB miner?

My next question is if I start to develop with an older version (which suports GPU mining) via API, my program would be compatible with 4.9.1 when I get my USB miner?

Thank you for your time.

All changes I have done to the API since I first wrote it have been backward compatible except when removing functionality no longer needed.
That was one of the big design issues I decided upon when I first completed writing the API.

Other have screwed with that compatibility so you may or may not get what you expect.

[twebit]

Hi, I see these errors once and a while with 800 Monarchs  BMA0: Ran out of queued IDs after 6 of 7.
What does it mean? Also sometimes I see  hex2bin str truncated.
And BMA0: incorrect result count 10 (INPROCESS:00x00) will try 10 (COUNT: 100x00)
I'm using 4.9.1 built from github on ubuntu x64
Thanks

[kano]

Hi, I see these errors once and a while with 800 Monarchs  BMA0: Ran out of queued IDs after 6 of 7.
What does it mean? Also sometimes I see  hex2bin str truncated.
And BMA0: incorrect result count 10 (INPROCESS:00x00) will try 10 (COUNT: 100x00)
I'm using 4.9.1 built from github on ubuntu x64
Thanks

USB hardware errors.
Try replacing the cables or your hub and make sure you are using USB2.0 port.

[kano]

I've put up a new AntS1 binary in my binaries git hub of latest 4.9.1a cgminer - of course with the cgminer git version with the fixes in it.

I've tested it on my pool https://kano.is/ and also on p2pool (fired up my home one for a while for testing)
For details and installing: https://github.com/kanoi/cgminer-binaries/tree/master/AntS1

[Mikestang]

I've put up a new AntS1 binary in my binaries git hub of latest 4.9.1a cgminer - of course with the cgminer git version with the fixes in it.

I've tested it on my pool https://kano.is/ and also on p2pool (fired up my home one for a while for testing)
For details and installing: https://github.com/kanoi/cgminer-binaries/tree/master/AntS1

Great, will update my S1 straight away.  Thank you!

[helipotte]

Installed the new binary on one of my underclocked ants and now the discard rate is much higher.  Averages around 6% now.  With the previous binary (4.3.2)

it was around  .2%.  Is this normal?   

Exact setting I am using:  [196.88  69 5f06] with latest firmware.

Thanks!

[Mikestang]

For details and installing: https://github.com/kanoi/cgminer-binaries/tree/master/AntS1

I really appreciate the easy to follow instructions.  They are perfect for someone like me who barely knows what each line is doing, thank you.

Installed the new binary on one of my underclocked ants and now the discard rate is much higher.  Averages around 6% now.  With the previous binary (4.3.2)

it was around  .2%.  Is this normal?  

Exact setting I am using:  [196.88  69 5f06] with latest firmware.

Thanks!

On my now updated to 4.9.1a overclocked (393 freq) S1 I see 0 rejects (used to be around 0.3%), error rate is about the same ~1%.  Hash rate is up a little, too, but we'll see how that levels out.  I had to do the fix for LST time, but no big deal.  I updated the monitor script, too.

Question, I verified the cgminer version via API, but is there a way to see the version from the web GUI, too?  Just curious.

Looking very much forward to updated cgminer for my S3+, keep up the solid work, ck & Kano!

[kano]

Installed the new binary on one of my underclocked ants and now the discard rate is much higher.  Averages around 6% now.  With the previous binary (4.3.2)

it was around  .2%.  Is this normal?  

Exact setting I am using:  [196.88  69 5f06] with latest firmware.

Thanks!

Discards do not matter.

Did you mean Rejects?
If so post the full set of relevant numbers:
Elasped, DiffA, DiffR

[helipotte]

Installed the new binary on one of my underclocked ants and now the discard rate is much higher.  Averages around 6% now.  With the previous binary (4.3.2)

it was around  .2%.  Is this normal?  

Exact setting I am using:  [196.88  69 5f06] with latest firmware.

Thanks!

Discards do not matter.

Did you mean Rejects?
If so post the full set of relevant numbers:
Elasped, DiffA, DiffR

Rejects are actually very low.  Just curious about the discards.

[kano]

Installed the new binary on one of my underclocked ants and now the discard rate is much higher.  Averages around 6% now.  With the previous binary (4.3.2)

it was around  .2%.  Is this normal?  

Exact setting I am using:  [196.88  69 5f06] with latest firmware.

Thanks!

Discards do not matter.

Did you mean Rejects?
If so post the full set of relevant numbers:
Elasped, DiffA, DiffR

Rejects are actually very low.  Just curious about the discards.

Discards are unused work - so they mean nothing in terms of shares or hash rate.

[kano]

For details and installing: https://github.com/kanoi/cgminer-binaries/tree/master/AntS1

I really appreciate the easy to follow instructions.  They are perfect for someone like me who barely knows what each line is doing, thank you.

Installed the new binary on one of my underclocked ants and now the discard rate is much higher.  Averages around 6% now.  With the previous binary (4.3.2)

it was around  .2%.  Is this normal?  

Exact setting I am using:  [196.88  69 5f06] with latest firmware.

Thanks!

On my now updated to 4.9.1a overclocked (393 freq) S1 I see 0 rejects (used to be around 0.3%), error rate is about the same ~1%.  Hash rate is up a little, too, but we'll see how that levels out.  I had to do the fix for LST time, but no big deal.  I updated the monitor script, too.

Question, I verified the cgminer version via API, but is there a way to see the version from the web GUI, too?  Just curious.

No, the web interface shows the package version, which of course doesn't change when you replace the cgminer binary.

Looking very much forward to updated cgminer for my S3+, keep up the solid work, ck & Kano!

S2 is in the works now, the S3 is after that and will be more effort than the S1 and S2 combined