Let us know if the new version solved your issue with nicehash.
So far, so good, no hangups caused by authorization errors (but actually I don't know if there were such errors these days). If the problem emerges again, I'll let you know. Thanks for the stable release. 
Topic: miniZ v2.0a Equihash 144,5 125,4 210,9 150,5 192,7 BeamHash3 ProgPoW Ethash CFX - page 34. (Read 60004 times)
October 22, 2019, 09:00:09 AM
October 18, 2019, 12:59:21 PM
CUDA 10 version should be beneficial.
This was the cause, thanks. I somehow missed the CUDA 10 link and started to use the CUDA 8 version instead, probably because it has no clear "CUDA 8" designation neither in the URL nor in the program startup info.Sorry for the false alarm
thank you for your messsage.
No problem, your feedback helps improving miniZ.
We made a few modifications to the Download table that may help to distinguish CUDA versions. It is likely that others are also downloading CUDA 8 by mistake
In the next version we will also add this information to the log.
Thanks again. Let us know if the new version solved your issue with nicehash.
Cheers
October 18, 2019, 11:20:37 AM
CUDA 10 version should be beneficial.
This was the cause, thanks. I somehow missed the CUDA 10 link and started to use the CUDA 8 version instead, probably because it has no clear "CUDA 8" designation neither in the URL nor in the program startup info.Sorry for the false alarm
October 18, 2019, 08:38:35 AM
The new version shows instantaneous hashrate instead of the average (so both shown values are identical), at least on Beam. Is this intended?
Also Beam seems to become slower (can't say with certainty since there is no visible average hashrate anymore), at least on 1070.
Hi Kringel,Also Beam seems to become slower (can't say with certainty since there is no visible average hashrate anymore), at least on 1070.
thanks for your feedback.
In the new version you still have both short and long hashrate reports.
If you only run the miner for a couple of minutes it is likely that these values are identical.
Regardig Beam hashrate, it should be the same as previous version.
If you want to compare versions in a short run, it is best to compare the I/s values since these are stable in about 5 min (or less).
Also, if you have a recent nvidia driver, CUDA 10 version should be beneficial.
Cheers
October 18, 2019, 06:12:13 AM
The new version shows instantaneous hashrate instead of the average (so both shown values are identical), at least on Beam. Is this intended?
Also Beam seems to become slower (can't say with certainty since there is no visible average hashrate anymore), at least on 1070.
Also Beam seems to become slower (can't say with certainty since there is no visible average hashrate anymore), at least on 1070.
October 17, 2019, 05:57:21 PM
Hi everyone,
Thank you for your feedback and for staying with us!
You can find the new miniZ version v1.5r here.
* Major performance improvement for 210,9, for all GPUs. Up to 7%, depending on GPU.
* Improved stability. (This was mostly affecting Beam mining)
* miniZ updates the hashrate when not mining. It drops to zero when mining stops.
* Better handling of “worker not autorized” error.
If you are tuning your cards, do not forget to use --oc1 or --oc2 options to match your OC settings!
For additional information check our Usage or FAQ pages.
Let us know how it goes!
Happy mining!
Thank you for your feedback and for staying with us!
You can find the new miniZ version v1.5r here.
* Major performance improvement for 210,9, for all GPUs. Up to 7%, depending on GPU.
* Improved stability. (This was mostly affecting Beam mining)
* miniZ updates the hashrate when not mining. It drops to zero when mining stops.
* Better handling of “worker not autorized” error.
If you are tuning your cards, do not forget to use --oc1 or --oc2 options to match your OC settings!
For additional information check our Usage or FAQ pages.
Let us know how it goes!
Happy mining!
October 16, 2019, 09:33:06 AM
Does this error happens often? This looks like a bug on the pool side, we are working on a few possible workarounds for this.
That's definitely a Nicehash servers problem, sometimes they start to return authorization errors, which may last from seconds to hours; that happens irregularly, maybe once a week at average. However, a miner shouldn't handle the error like MiniZ currently does Thanks for scheduling a fix for this. October 16, 2019, 09:31:55 AM
So is there any connection issue with miniZ and Sparkpool again? Can someone confirm? I cannot connect my rigs to sparkpool mining BEAM.
Hi MineOrDie,we've just tested and it runs fine.
Could you paste here the error? Which miniZ version are you using?
Cheers
is it possible you forgot to add ssl?
Command line should be something like:
Code:
miniZ.exe --url=ssl://[email protected]:2222 --log --extra
Cheers
October 16, 2019, 09:06:29 AM
So is there any connection issue with miniZ and Sparkpool again? Can someone confirm? I cannot connect my rigs to sparkpool mining BEAM.
Hi MineOrDie,we've just tested and it runs fine.
Could you paste here the error? Which miniZ version are you using?
Cheers
October 16, 2019, 08:58:34 AM
So is there any connection issue with miniZ and Sparkpool again? Can someone confirm? I cannot connect my rigs to sparkpool mining BEAM.
Hi MineOrDie,we've just tested and it runs fine.
Could you paste here the error? Which miniZ version are you using?
Cheers
October 16, 2019, 08:34:29 AM
So is there any connection issue with miniZ and Sparkpool again? Can someone confirm? I cannot connect my rigs to sparkpool mining BEAM.
October 16, 2019, 08:13:32 AM
This happened on different rigs several times before, but only today I managed to catch the error details on my test rig:
https://ibb.co/t3zQ7k6
The annoying thing here is not the error itself (which, BTW, is not permanent and could be resolved just by continuing trying) but the fact that after stopping (but not exiting!) MiniZ keeps reporting the last average hashrate to the Nicehash client so the latter one thinks that all is fine and does not restart the miner to resolve the situation.
https://ibb.co/vZBNDP9
https://ibb.co/t3zQ7k6
The annoying thing here is not the error itself (which, BTW, is not permanent and could be resolved just by continuing trying) but the fact that after stopping (but not exiting!) MiniZ keeps reporting the last average hashrate to the Nicehash client so the latter one thinks that all is fine and does not restart the miner to resolve the situation.
https://ibb.co/vZBNDP9
Hi Kringel,
thanks for the feedback. We are working on this now.
We will make sure miniZ doesn't get stuck reporting the last average hashrate, when it stops mining.
Does this error happen often? This looks like a bug on the pool side, we are working on a few possible workarounds for this.
We plan to release a new version by the end of the week and this should be taken care of.
Cheers
October 15, 2019, 10:56:33 AM
This happened on different rigs several times before, but only today I managed to catch the error details on my test rig:
https://ibb.co/t3zQ7k6
The annoying thing here is not the error itself (which, BTW, is not permanent and could be resolved just by continuing trying) but the fact that after stopping (but not exiting!) MiniZ keeps reporting the last average hashrate to the Nicehash client so the latter one thinks that all is fine and does not restart the miner to resolve the situation.
https://ibb.co/vZBNDP9
https://ibb.co/t3zQ7k6
The annoying thing here is not the error itself (which, BTW, is not permanent and could be resolved just by continuing trying) but the fact that after stopping (but not exiting!) MiniZ keeps reporting the last average hashrate to the Nicehash client so the latter one thinks that all is fine and does not restart the miner to resolve the situation.
https://ibb.co/vZBNDP9
October 10, 2019, 07:51:41 PM
Hello guys,
I don't see miniZ listed on https://equihub.pro/. Too bad cause an Equihash-only mining pool seems like a perfect fit for you! 😉
They've got a Telegram and a discord if you want to contact them: https://t.me/EquiHub, https://discordapp.com/invite/CkbPGxs.
Cheers
Hi crypt_fr,I don't see miniZ listed on https://equihub.pro/. Too bad cause an Equihash-only mining pool seems like a perfect fit for you! 😉
They've got a Telegram and a discord if you want to contact them: https://t.me/EquiHub, https://discordapp.com/invite/CkbPGxs.
Cheers
thank you for your suggestion.
We've just contacted them.
Cheers
October 09, 2019, 07:05:04 PM
Hello guys,
I don't see miniZ listed on https://equihub.pro/. Too bad cause an Equihash-only mining pool seems like a perfect fit for you! 😉
They've got a Telegram and a discord if you want to contact them: https://t.me/EquiHub, https://discordapp.com/invite/CkbPGxs.
Cheers
I don't see miniZ listed on https://equihub.pro/. Too bad cause an Equihash-only mining pool seems like a perfect fit for you! 😉
They've got a Telegram and a discord if you want to contact them: https://t.me/EquiHub, https://discordapp.com/invite/CkbPGxs.
Cheers
October 06, 2019, 08:16:46 PM
The first minutes of the video card sequentially make short stops (not simultaneously). Miner does not stop and finds shares. The pool does not see the miner. Miner does not show the transition to another pool. After half an hour, everything is restored. --jobtimeout = 900 does not change anything. The last miner. Everything is perfect with the gminer
Hi filko,thanks for your message!
We're trying to replicate the error.
In case you run miniZ again, could you paste here the miner console/logfile output when it stops mining?
Cheers
miniZ.exe --url=ssl://[email protected]:3333 --par=150,5 --pers=Beam-PoW --templimit=70c --telemetry=0.0.0.0:42000 -cd 0 1 2 3 --jobtimeout=900 --log
thank you very much for your patience, and for this information,
We will analyze it and try to solve your issue.
Cheers
October 06, 2019, 07:30:50 AM
The first minutes of the video card sequentially make short stops (not simultaneously). Miner does not stop and finds shares. The pool does not see the miner. Miner does not show the transition to another pool. After half an hour, everything is restored. --jobtimeout = 900 does not change anything. The last miner. Everything is perfect with the gminer
Hi filko,thanks for your message!
We're trying to replicate the error.
In case you run miniZ again, could you paste here the miner console/logfile output when it stops mining?
Cheers
miniZ.exe --url=ssl://[email protected]:3333 --par=150,5 --pers=Beam-PoW --templimit=70c --telemetry=0.0.0.0:42000 -cd 0 1 2 3 --jobtimeout=900 --log
https://ibb.co/g9Vy7tZ
https://ibb.co/kKXpsrQ
https://my-files.ru/gqv3qn
October 05, 2019, 08:30:54 PM
The first minutes of the video card sequentially make short stops (not simultaneously). Miner does not stop and finds shares. The pool does not see the miner. Miner does not show the transition to another pool. After half an hour, everything is restored. --jobtimeout = 900 does not change anything. The last miner. Everything is perfect with the gminer
Hi filko,thanks for your message!
We're trying to replicate the error.
In case you run miniZ again, could you paste here the miner console/logfile output when it stops mining?
Cheers
October 05, 2019, 03:20:22 AM
You can restart the miner or wait half an hour. And so it was every day for a month. I returned to the Gminer - the problem is gone.
1060 - Win7. 1070 -Win10
Hi filko,1060 - Win7. 1070 -Win10
thanks for the information.
Do you mean that the miner stops mining?
Could you let us know which miniZ version are you using?
On the latest version you can adjust some connection parameters that may solve your issue (ex. --jobtimeout=900).
Others have reported that it helped: https://bitcointalksearch.org/topic/m.52453403.
Cheers
October 01, 2019, 07:21:28 PM
You can restart the miner or wait half an hour. And so it was every day for a month. I returned to the Gminer - the problem is gone.
1060 - Win7. 1070 -Win10
Hi filko,1060 - Win7. 1070 -Win10
thanks for the information.
Do you mean that the miner stops mining?
Could you let us know which miniZ version are you using?
On the latest version you can adjust some connection parameters that may solve your issue (ex. --jobtimeout=900).
Others have reported that it helped: https://bitcointalksearch.org/topic/m.52453403.
Cheers
Jump to: