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

[-ck]

8 BEs and Jala in Tecknet USB 3.0 hub connected to laptop. No zombies in 3.7.2 but often see this

Code:

 [2013-11-07 14:15:44] AMU0: GetResults (amt=0 err=-7 ern=34)
 [2013-11-07 14:15:44] Icarus Read: No data for 12633 ms

BEs has often light solid and HW errors increased in my estimates. Jala is OK.
3.5.1 is best for my setup yet.

That's not a bug. It means that work item had no shares in it. There's a reason it doesn't show that message except at higher logging levels.

[1714215859]

1714215859

[1714215859]

1714215859

[Askit2]

Hi one and all, just a quick couple of question I would like cleared up in my mind and a better understanding, as I have been mining some time now. Am just a small time miner here with just 8.3ghs total at my disposal which I have set between two pools.

Queue - Staged work.
When in writing your own batch file, the option to add --queue -Q has a maximum value allowed of 10, but by default this is 1 if not added into the batch file. In the settings menu in the UI, there is also the same option, does the option in the UI have the same upper bound limit of 10 ?, if not what is the maximum ?. I have been playing around with this for months and trying to find the right balance is not easy. I assume that this does relate to the amount of staged work ready (ST). Why would you leave it at a value of 1 which is the default ?

Total WU from version 3.6.4  -  3.7.2
Since moving from 3.6.4 to version 3.7.2, why does the work utility show a much lower figure than before ? as I mentioned earlier, I am multi pooled with a quota split between two pools of pool 0 at 64% and pool 1 at 36%. Minimum difficulty shares are pool 0 at 1 and pool 1 at 8. I do not have the fastest of internet connections and with pool 0 there is no option to change the difficulty.

I have found also that by changing the scantime to 90s and the expiry to 180s, this reduced greatly the number of rejected shares.

Any help most welcome.

Regards

I expect Kano on CK will correct me if I am wrong but I have mine set well above 10, in a configuration file and it loads just fine. Mine is currently set to 99 giving me an even 100 work units staged. Now I didn't pick this number arbitrarily. I worked up to it trying to eliminate 5-10 second waiting for work from all pools messages. I now only drop as low as about 5 staged at some points. That having been said my WU is currently 1247.8 so I have 5 seconds worth of staged work. Well less than that because it is 20.7966667 per second but close enough.

Moving my qued work to 100 has bumped my average up but staging large amount of work will cost CPU cycles and network load for items that get flushed at a new block. Realistically you want it about as low as you can run without running out of work. So I guess my advice is for 8 GH I wouldn't go very high Something like 10 would be more then enough.

[-ck]

You should never need to touch the queue setting when mining at a stratum pool no matter what the hashrate.

[Askit2]

You should never need to touch the queue setting when mining at a stratum pool no matter what the hashrate.

I should have pointed out that because I lack the additional hardware my local bitcoin daemon doesn't run stratum.

EDIT: It isn't technically true. I don't run stratum because I haven't seen a good way to work it on windows. I lack a suitable Linux system as I don't expect the raspberry pi will also run a stratum server setup. I only increased mine because I frequently had 0 staged work and semi often waiting for work to be available from all pools. Sometimes for many seconds. Even on 3.7.2. So I increased it. Even at 100 I occasionally see drops down below 50. Very rarely into the teens. After getting it up that high never to 0 and waiting for work.  Possibly the Quota version doesn't handle mixed technologies as well. By mixed I mean get work and stratum.

In my setup pools 0 and 1 are quota 0, pools 2 and 3 are quota 12 pool 4(local bitcoin) is quota 1. As I understand it any work not being available fast enough on any of 2, 3 or 4 should come from 0 or if that's dead or slow 1.

But Like I said before I expected my settings where a little high and likely very high for most people. With 17 jalapeno's some running the newer firmware I get calls for 25 work units just to get things working again. 9 running the older 1 job per board, 8 running the newer 1 job per chip. Stratum from 2 of the three pools should keep them busy without adding the extra work I thought. I did gain about 1% on my average hashrate. Again not much. I just didn't like them stopping mining. So I increased the que to deal with it by having more work ready at a moments notice in theory it shouldn't be any different with the default 1 staged work.

[jmc1517]

cgminer-ymmv still going strong.  I will be away for 1-2 weeks so no more testing from me during that time, but I will leave this test version running while I'm away.  Hope to see the fixes present in ymmv make it to the next release

Oh, and keep up the good work.  It's all very much appreciated.

[os2sam]

Do you have "usb" : ":60" in your conf file? That's been the best thing for keeping all my BEs running.

So are you over 60 BE's?  I had trouble with the 60th too.  Mining with 59 at the moment.

No, I only have 49 BEs, but, I have a dozen PC miners and I spread them over several so I can read the bottom of the cgminer screen. Leave no USB unplugged 

Just a thought, have you tried running 30 in one instance of cgminer and the other 30 in a second instance?

Not yet.  I was hoping to get another 49 port hub so that I wouldn't need to use my Rosewills and Ankers for mining anymore.  But I'm not so excited about that hub at the moment.  I'll give it a try though.  It's hard to tell where the problem is since those Ankers are so flaky and finicky.
Thanks,
Sam

[os2sam]

You should never need to touch the queue setting when mining at a stratum pool no matter what the hashrate.

Deepbit doesn't use stratum, yet.  Increasing the queue does seem to help there and with solo mining.

[os2sam]

Just a thought, have you tried running 30 in one instance of cgminer and the other 30 in a second instance?

60 USB Miners work 61 does not.  It doesn't matter how you split them up in multiple instances.  If I plug in 61 devices and start CGMiner it says no USB Devices found.  If I remove one then it takes off and starts mining.  So I seem to max out with 59 BE's in one instance and 1 Jalapeno in another.

Thanks,
Sam

[gnar1ta$]

Anyone know why KLN devices would show up but mine at 0 on latest Ubuntu?  Sometimes they work, but mostly not. I'll have a few up then restart cgminer or the computer and then different ones will be at 0. Annoying.

[-ck]

Anyone know why KLN devices would show up but mine at 0 on latest Ubuntu?  Sometimes they work, but mostly not. I'll have a few up then restart cgminer or the computer and then different ones will be at 0. Annoying.

Power?

[gnar1ta$]

Anyone know why KLN devices would show up but mine at 0 on latest Ubuntu?  Sometimes they work, but mostly not. I'll have a few up then restart cgminer or the computer and then different ones will be at 0. Annoying.

Power?

Yeah that would make sense, so I've tried with different hubs and power setups and get the same results. So, since they are in Florida, and there is always plenty of lightning, I'm going to try that as a power source next. At least that will be entertaining 

https://bitcointalk.org/index.php?topic=326985.0

[-ck]

Anyone know why KLN devices would show up but mine at 0 on latest Ubuntu?  Sometimes they work, but mostly not. I'll have a few up then restart cgminer or the computer and then different ones will be at 0. Annoying.

Power?

Yeah that would make sense, so I've tried with different hubs and power setups and get the same results. So, since they are in Florida, and there is always plenty of lightning, I'm going to try that as a power source next. At least that will be entertaining 

https://bitcointalk.org/index.php?topic=326985.0

Hmm that might just give them enough power to recoup their costs.

[Gixer1970]

So is it there fore possible to queue work independant to each pool in the bat file instead as a whole ? I was unaware this could be done. I will give it a go and see if it is possible.
Many thanks.

[-ck]

I keep getting asked about the HEX16A driver. At the risk of sounding like a broken record, neither I nor Kano have one so we're not writing drivers for them, and no active maintainer has stepped up to try to push code to us and have us audit that the code is satisfactory enough to include, so there will be no driver for it for the foreseeable future.

[Askit2]

So is it there fore possible to queue work independant to each pool in the bat file instead as a whole ? I was unaware this could be done. I will give it a go and see if it is possible.
Many thanks.

Sorry I mis-typed. I ment Quota. I am sorry for the confusion I will undoubtedly cause. The post was edited to fix my mistake.

[branehans]

Absolutely the best on the market for now

[fydel]

Does sgminer run with Nanofury NF1 USB-sticks?

If yes - how can i get it to work?

No

No chance you will implement nanofury support in the near future?

I really don't want to use the evil twin of cgminer. 

[-ck]

Does sgminer run with Nanofury NF1 USB-sticks?

If yes - how can i get it to work?

No

No chance you will implement nanofury support in the near future?

I really don't want to use the evil twin of cgminer. 

I'll be sent one in the future, and then a driver will be developed for it. No idea of timeframe.

[dragon695]

Thanks for the work on fixing scrypt share difficulty. For the most part, it has been working fine. However, I've been having issues with Novacoin p2pools.

I have been mining Novacoin through stratum p2pool at http://fsb4000.no-ip.biz:8336. It requires a public key (instead of the usual wallet address) for the username, check the Novacoin altcoin thread for further details.

I am using Xubuntu 13.10 on amd64 with 3 Sapphire 7950s using fglrx-updates 2:13.101-0ubuntu3 and gcc 4:4.8.1-2ubuntu3.

It more or less works nicely at git revision 8e5dc21ea68d3ec4198e577a1073a32fcddcbcb9, generating shares as expected and finally reporting >0 stats. However, it spams about finding blocks, which is wrong, but that is only a minor annoyance.

Pulling past that point results in core dumps, except in the case of the very latest pulls, which--for Novacoin p2pools only--results in 100% false positives for hardware errors on all GPUS. hard resetting back to 8e5dc21ea68d3ec4198e577a1073a32fcddcbcb9 yields a working cgminer for Novacoin p2pools).

Here is the output of cgminer compiled from the latest git pull on the aforementioned Novacoin p2pool:

Code:

 [2013-11-08 14:43:52] Started cgminer 3.7.2
 [2013-11-08 14:43:54] Probing for an alive pool
 [2013-11-08 14:43:55] Pool 0 difficulty changed to 0.000697
 [2013-11-08 14:43:56] Network diff set to 313
 [2013-11-08 14:43:56] Stratum from pool 0 requested work restart
 [2013-11-08 14:43:59] GPU2: invalid nonce count - HW error
 [2013-11-08 14:43:59] GPU1: invalid nonce count - HW error
 [2013-11-08 14:43:59] GPU0: invalid nonce count - HW error
 [2013-11-08 14:44:01] GPU2: invalid nonce count - HW error
 [2013-11-08 14:44:01] GPU0: invalid nonce count - HW error
 [2013-11-08 14:44:01] GPU1: invalid nonce count - HW error

The output continues with not a single good share being accepted.

I suspect the issue has to do with the share difficulty being very low, but that is how they (the Novacoin developers) want the p2pool configured. I will continue to use 8e5dc21ea68d3ec4198e577a1073a32fcddcbcb9 as it seems to work well enough, but hopefully this can be resolved in future cgminers.

[-ck]

Scrypt and opencl support is being deprecated in the near future, and development for other coins is not going to happen, so sorry but there is no plan for improving support for other coins.