v22.1 released.  - Add support for mining Swap (XWP). - Improve Grin29 & AEperformance. - Improve Windows compatibility on Grin & AE, significant boost on performance. |
|
|
|
Any chance you can add support for SWAP (cuckaroo29s)
Only real option is gminer at this point and would prefer not to use them for multiple reasons
Sure, considering add swap support in next version. Any detailed information for the difference between SWAP and Grin? |
|
|
|
|
New version v21.4:
- Improve Grin31 performance.
- Improve performance of Grin29 & AE on RTX cards.
- Fix Grin31 compatibility on Win7 with 8G cards.
- New option to reduce the range of power consumption by multi-gpu rig.
- Add miner Up Time print in cmd outputs.
|
|
|
|
Can anyone help me? I have the error "... check pool name" for Grin 31 f2pool. I have tried stratum and w/o but failed. Bminer and Gminer work fine.
Mining Grin on f2pool needs to add an arbitrary password at the end of username (f2pool requires that, don't know the reason). You can find the sample usage in readme: Grin31 sparkpool: nbminer -a cuckatoo -o stratum+tcp://grin.sparkpool.com:66667-u 123@qq.com/worker f2pool: nbminer -a cuckatoo -o stratum+tcp://grin31.f2pool.com:13654 -u username.worker:passwd nicehash: nbminer -a cuckatoo -o stratum+tcp://grincuckaroo31.eu.nicehash.com:3372 -u btc_address.worker |
|
|
|
BTM 1660,1660ti ?
Do not have these cards. Though the miner should work on those cards as NVIDIA claims their compute capability is 7.5, which is the same as RTX 20's. |
|
|
|
|
New version with bug fix.
1. Fix bug: Occasionlly lower local hashrate than previously version.
2. Do not run GPU if mining pool not connected when mining Grin & AE.
|
|
|
|
new version v21.2 with bug fixed.
Hash rate drops regulary on 2018 ti /undervolted/ on equal intervals - 10 seconds 2.03 g/s, 10 seconds 1.74 g/s wich is strange. No such drops with bminer or gminer. Have you tried with stock settings? |
|
|
|
|
new version v21.2 with bug fixed.
|
|
|
|
Hello thanks for your hard work seems like this is only miner win10 compatible with gtx1080ti on cuckto31 my hash rate stable 1,5 im using nicehash pool but when checking speed 80% time it shows 0 hashrate , 20 % of time it shows actual speed 1,2-1,6 when checked after 24hours of mining the reported speed is only around 0,6 becouse 80% of time its not reporting any hashing activity but miner sends shares but probably not enough ? Please let me know if this is normal on cucktoo
When you say "checking speed", do you mean checking on nicehash website? Nicehash gives a very high difficulty to miner due to large amount of miner rigs it connected. So the frequency of submitting found share to nicehash will be significantly lower than other pool (eg. sparkpool, f2pool). And the hashrate calculated on nicehash based on how much share the miner submitted, could be very different from local hashrate, caused by the high difficulty. I don't know how many 1080tis that you have, but if you got only 1 or 2 cards, then a relative big gap between nicehash reported hashrate and local hashrate could be normal, otherwise there's something wrong. Thank you for answer im using only 1 gtx1080ti (zotac) and im checking hashrates on nh website / nh mobile apk , this relative big gap coused by high dif stratum which u mention would affect every other algo i connect to on nicehash to but this is just ur miner and cucktoo 31 algo on which i get this gap, When im mining x16r , beam , lyra2rev3 and other algos supported by nicehash i get hashrate fluctuaction but nothing like this and the result by pool = miner hashrate atleast most of the time but on cucktoo the local hashrate just doesnt get near pool reported hashrate , not in hashrates not in profit thats why im asking coz i cant double check on other miners since there isnt any around working on windows.... I carefully checked the communications between miner and nicehash. There do exists a bug, when nicehash send a clean job, nbminer do not kill current job on GPU immediately. This bug has much lower effect on other Grin pools (1% as most), since there are typically only 1 or 2 clean jobs every minute on other mining pools. Things get different on Nicehash, the percentage of clean jobs is much higher, so this could be the reason that miner do not report any hashrate on nicehash for a certain amount of time. I'll fix this issue in the next version, hopefully in next few days. Thank you for your answer and keep the hard work GG Fixed in v21.1. |
|
|
|
Hello thanks for your hard work seems like this is only miner win10 compatible with gtx1080ti on cuckto31 my hash rate stable 1,5 im using nicehash pool but when checking speed 80% time it shows 0 hashrate , 20 % of time it shows actual speed 1,2-1,6 when checked after 24hours of mining the reported speed is only around 0,6 becouse 80% of time its not reporting any hashing activity but miner sends shares but probably not enough ? Please let me know if this is normal on cucktoo
When you say "checking speed", do you mean checking on nicehash website? Nicehash gives a very high difficulty to miner due to large amount of miner rigs it connected. So the frequency of submitting found share to nicehash will be significantly lower than other pool (eg. sparkpool, f2pool). And the hashrate calculated on nicehash based on how much share the miner submitted, could be very different from local hashrate, caused by the high difficulty. I don't know how many 1080tis that you have, but if you got only 1 or 2 cards, then a relative big gap between nicehash reported hashrate and local hashrate could be normal, otherwise there's something wrong. Thank you for answer im using only 1 gtx1080ti (zotac) and im checking hashrates on nh website / nh mobile apk , this relative big gap coused by high dif stratum which u mention would affect every other algo i connect to on nicehash to but this is just ur miner and cucktoo 31 algo on which i get this gap, When im mining x16r , beam , lyra2rev3 and other algos supported by nicehash i get hashrate fluctuaction but nothing like this and the result by pool = miner hashrate atleast most of the time but on cucktoo the local hashrate just doesnt get near pool reported hashrate , not in hashrates not in profit thats why im asking coz i cant double check on other miners since there isnt any around working on windows.... I carefully checked the communications between miner and nicehash. There do exists a bug, when nicehash send a clean job, nbminer do not kill current job on GPU immediately. This bug has much lower effect on other Grin pools (1% as most), since there are typically only 1 or 2 clean jobs every minute on other mining pools. Things get different on Nicehash, the percentage of clean jobs is much higher, so this could be the reason that miner do not report any hashrate on nicehash for a certain amount of time. I'll fix this issue in the next version, hopefully in next few days. |
|
|
|
Hello thanks for your hard work seems like this is only miner win10 compatible with gtx1080ti on cuckto31 my hash rate stable 1,5 im using nicehash pool but when checking speed 80% time it shows 0 hashrate , 20 % of time it shows actual speed 1,2-1,6 when checked after 24hours of mining the reported speed is only around 0,6 becouse 80% of time its not reporting any hashing activity but miner sends shares but probably not enough ? Please let me know if this is normal on cucktoo
When you say "checking speed", do you mean checking on nicehash website? Nicehash gives a very high difficulty to miner due to large amount of miner rigs it connected. So the frequency of submitting found share to nicehash will be significantly lower than other pool (eg. sparkpool, f2pool). And the hashrate calculated on nicehash based on how much share the miner submitted, could be very different from local hashrate, caused by the high difficulty. I don't know how many 1080tis that you have, but if you got only 1 or 2 cards, then a relative big gap between nicehash reported hashrate and local hashrate could be normal, otherwise there's something wrong. |
|
|
|
Hi,
I am trying to send you a PM but you has not chosen to allow messages from newbies. Please allow it or how can I reach you? Thanks.
Allowed. Also, you can send me email: nebutech@hotmail.com |
|
|
|
Hello I just found your miner. I have a 2080 ti Overclocking it I get about 18.70 kh/s for BTM This is really good. Any chance there will be further updates for BTM Tensority algo ? Edit: Using windows 10 and the latest nvidia driver available. Edit2: Also cuda 10.1 was released recently and there are updates for tensor cores in it which improve performance. https://news.developer.nvidia.com/cuda-10-1-now-available/Do not have an update plan for BTM recently. The main reason is Bitmain already launched a new ASIC miner for BTM (Antminer B7). Besides, thje price of BTM really do not encourage developer to do futher development, the difficulty to put Tensority algo near theoretical limit is actually much harder than most other algos. |
|
|
|
Comparison on hive os - current major public grin29 miners, both 3xx and 4xx nvidia drivers compared
This does NOT compare pool side hashrates!
Thanks for detailed information. Keep improving nbminer. |
|
|
|
More grin weirdness from me. I quickly tried on hiveos (mineros.cn registration still does not work) On rig - newer drivers and kernel does 2.9, other exact same, but i think stable hiveOS so bit older drivers and kernel (and also unbootable from usb on biostar with windows ssd present  ) 2.7 mostly. Do you think cuda version could be the issue or something else? Also second one does have bit higher mem oc, but lower g/s. On linux there is no undervolting for nvidia cards, at least no publicly known, so i do use power limit, but hiveOS is quite nice that it is easily readable from single screenshot. I will not post other miner performance on rig with lower performance in NB miner here as hiveos does not have gminer 1.15 which may fixed some hashrate issues. What is interesting is load average that is lowest in NBminer with no apparent negative effect on hashrate, so I would guess that CPU is not bottle neck after all. As far as I know, the driver version has big affect on mining Grin & AE, especially on windows. The recommend driver version for Win10 is 399.24 (the last 3xx driver version). |
|
|
|
What is the speed of 1060 6g?
Slightly lower than p106, cause p106 usually has higher freq than 1066. |
|
|
|
 often appear "No share accepted in 30 minutes...." Thanks for the report. I checked code, this is a bug which will happen when using backup mining pool urls. I will fix in the next version. Please use only one url for now. My apologies. |
|
|
|
new version shuts down 2 of my GPU for whatever reason i dont know. displays no error or msg. just stops using the memory and turns the gpu to min power i have decreased the memclock and it still happens. all the time. same GPUs. never happened before and never had problem with other miners or versions.  img shows gpu5 but it is gpu1 and 5 every time Cuckoo series algorithm implementations could cause an instant high power consumption, the peak power consumption could exceed the power limit of GPU (150W for 1070). This problem become more serious as the hashrate of miner goes higher. Check your power supply, make sure the power delivery has 20% more than what the average mining cost. |
|
|
|
BTW on linux i'm getting about same (well, pretty much EXACTLY SAME ) hashrate on 1060s as on win10. I guess I should be getting lower as other miner sw authors claim the win10 can't use all the gpu memory? But definitely can't get over 3 per GPU. Definitely not 3.15 - still better then bMiner thought as he claim 3.3 and I can get 2.6 or maybe 2.7 max. Can CPU be bottle neck? I do run the cheapest celerons that were available at the time. Maybe it is because of Micron and not Samsung memory cards? I think this performance is on par with gminer. Both gMiner and bMiner can't start on windows10 at all thought (because of the GPU memory limit they claim). What's your CPU usage when mining? There is an option '--cuckoo-intensity', you can try tune it up to lower CPU usage. |
|
|
|
|
Show Posts
