When the user pool falls during the fee time (or right before start mining to the fee), mining can get stuck with the fee.
I mine 125,4 on herominers and it didn't seem it has been down lately at all...
Topic: miniZ v2.0a Equihash 144,5 125,4 210,9 150,5 192,7 BeamHash3 ProgPoW Ethash CFX - page 8. (Read 60122 times)
October 27, 2022, 11:54:55 AM
Hm, never happened with z3 version... Anyway, since its only happening after 24hr+ of uptime I'll just keep restarting miner on each rig every day as a temporary workaround.
I mine 125,4 on herominers and it didn't seem it has been down lately at all...
I mine 125,4 on herominers and it didn't seem it has been down lately at all...
October 27, 2022, 11:24:07 AM
Hi Divinity666,
Thanks for the message.
This can happen once and a while, if the miner was mining for long time for the user. You can see that the %s are ok, possibly it was 1.9% for the fee for long time.
In any case we had a look at it, and although found no issue with this we added a limit to time mining for the fee without interruption. It will check more often when it is time to change for the user/fee.
Cheers
Still happening in z3 and z4, one windows miner and a hiveos miner. Stayed on dev pool for over 3 hours, percentage’s showed over 10%. I rolled back to z2 where I haven’t yet experienced the issue. Any logs or details which would help?
October 27, 2022, 10:45:40 AM
Found problem with not working ubqhash (CUDA Driver API error = 0001 from line 1100.). It does not like --ocx switch.
One more thing. Mining to same pool with different algo, i see diffent miner name. It is fine with 125,4, but with ubqhash i see totally different name and and for ubqhash with 144,5 my worker name is lost, my btc wallet is shown instead.
mining 125.4, pool shows this: miniZ/1.9z4 9600k c=BTC equihash125
mining 144.5, pool shows this: miniZ/1.9z4 1Lcx************************ c=BTC equihash144
mining ubqhash, pool shows this: EthDcrMiner64 1Lcx************************ c=BTC ubqhash
In all bat files i have worker name in this format --user 1Lcx************************.9600k
One more thing. Mining to same pool with different algo, i see diffent miner name. It is fine with 125,4, but with ubqhash i see totally different name and and for ubqhash with 144,5 my worker name is lost, my btc wallet is shown instead.
mining 125.4, pool shows this: miniZ/1.9z4 9600k c=BTC equihash125
mining 144.5, pool shows this: miniZ/1.9z4 1Lcx************************ c=BTC equihash144
mining ubqhash, pool shows this: EthDcrMiner64 1Lcx************************ c=BTC ubqhash
In all bat files i have worker name in this format --user 1Lcx************************.9600k
Hi somaton,
We fixed ocX with ubqhash. This should be working fine in the new release.
We'll have a look at worker names.
Thank you for the feedback!
Cheers
October 27, 2022, 10:32:22 AM
who cares this miner has been consistently 5% over 24hrs reported hashrate at the pool for me.
It's 0% if it's mining dev fee all the time. And it keeps happening again and again with this version.
ps ha-ha, I posted a comment about this matter on their support page. It was under "awaiting moderation" for a while, but visible to me, and now its deleted completely. Nice!
Hi Divinity666, everyone,
Thank you for your feedback.
We've been carefully looking into this, and finaly found the culprit.
When the user pool falls during the fee time (or right before start mining to the fee), mining can get stuck with the fee.
This seems to happen only in this situation, this is why we were not able to find it before.
We are deeply sorry about this, as you can imagine this is also very unconfortable for us.
For now, you can disconnect from the internet for about 3 minutes and reconnect again. This should bring the miner back to the user.
Once more, we would like to thank you for the feedback, which is precious for us. This way we can know about uncommon issues like this one, and improve the miner.
We're working to fix this asap!!
Cheers
ps: we're also answering to your message on the website.
October 27, 2022, 12:44:04 AM
who cares this miner has been consistently 5% over 24hrs reported hashrate at the pool for me.
It's 0% if it's mining dev fee all the time. And it keeps happening again and again with this version.
ps ha-ha, I posted a comment about this matter on their support page. It was under "awaiting moderation" for a while, but visible to me, and now its deleted completely. Nice!
October 26, 2022, 12:22:18 PM
Wtf, dev fee has been mining for 2 hours and wouldn't stop at all most likely. I went to 8.6% of dev fee already, while you usually that kind of % only after 1st dev fee session in the beginning simply because total miner run time is minimal. Than its just from 1.9% to 2.1% dev fee even after running miner for a week+ without crashes, at least it used to be. Just restarted miner as soon as I noticed it.
ps same shit just happened on my other rig, dev fee started and kept going on to 3.7% after 1 day and 7 hours until I stopped the miner.
ps same shit just happened on my other rig, dev fee started and kept going on to 3.7% after 1 day and 7 hours until I stopped the miner.
who cares this miner has been consistently 5% over 24hrs reported hashrate at the pool for me.
October 25, 2022, 09:53:49 PM
Wtf, dev fee has been mining for 2 hours and wouldn't stop at all most likely. I went to 8.6% of dev fee already, while you usually that kind of % only after 1st dev fee session in the beginning simply because total miner run time is minimal. Than its just from 1.9% to 2.1% dev fee even after running miner for a week+ without crashes, at least it used to be. Just restarted miner as soon as I noticed it.
ps same shit just happened on my other rig, dev fee started and kept going on to 3.7% after 1 day and 7 hours until I stopped the miner.
ps same shit just happened on my other rig, dev fee started and kept going on to 3.7% after 1 day and 7 hours until I stopped the miner.
October 25, 2022, 08:27:25 AM
Found problem with not working ubqhash (CUDA Driver API error = 0001 from line 1100.). It does not like --ocx switch.
One more thing. Mining to same pool with different algo, i see diffent miner name. It is fine with 125,4, but with ubqhash i see totally different name and and for ubqhash with 144,5 my worker name is lost, my btc wallet is shown instead.
mining 125.4, pool shows this: miniZ/1.9z4 9600k c=BTC equihash125
mining 144.5, pool shows this: miniZ/1.9z4 1Lcx************************ c=BTC equihash144
mining ubqhash, pool shows this: EthDcrMiner64 1Lcx************************ c=BTC ubqhash
In all bat files i have worker name in this format --user 1Lcx************************.9600k
One more thing. Mining to same pool with different algo, i see diffent miner name. It is fine with 125,4, but with ubqhash i see totally different name and and for ubqhash with 144,5 my worker name is lost, my btc wallet is shown instead.
mining 125.4, pool shows this: miniZ/1.9z4 9600k c=BTC equihash125
mining 144.5, pool shows this: miniZ/1.9z4 1Lcx************************ c=BTC equihash144
mining ubqhash, pool shows this: EthDcrMiner64 1Lcx************************ c=BTC ubqhash
In all bat files i have worker name in this format --user 1Lcx************************.9600k
October 24, 2022, 12:15:28 PM
Wow, major h\r improvements for on 125,4 with my 3080\3070-rig, but its like +1% with my 1080ti rigs 
Finally, thank you!
Hi Divinity666,
You can try option --fantemp with the new version v1.9z4.
Cheers
You can try option --fantemp with the new version v1.9z4.
Cheers
Finally, thank you!
October 21, 2022, 10:48:53 PM
Tried ubqhash. Does not work (windows 10, 466.77):
[INFO ] Mining fee set to 0.75%
miniZ[20:2:00.0: 9106]: Selecting GPU#0[0] MSI GeForce RTX 3080
[INFO ] GPU[0]: Generating DAG #97 [1799+28=1828MB]
[INFO ] GPU[0]: Generated DAG in 1.188
[FATAL ] CUDA Driver API error = 0001 from line 1100.
[INFO ] QUIT miniZ
[INFO ] Mining fee set to 0.75%
miniZ
[INFO ] GPU[0]: Generating DAG #97 [1799+28=1828MB]
[INFO ] GPU[0]: Generated DAG in 1.188
[FATAL ] CUDA Driver API error = 0001 from line 1100.
[INFO ] QUIT miniZ
October 21, 2022, 09:24:34 PM
Hi everyone,
A new miniZ v1.9z4 is out with performance improvements for 125,4 – FLUX – mining! Up to 20%!
Added ubqhash support, progpow (and variants) support for AMDs, fan control for AMDs, fan/temperature control option…
Please find miniZ v1.9z4 @ Download page.
Changelog:
* Performance improvements for 125,4 on all gpus. Up to 20%.
* Performance improvements for 150,5 on all gpus.
* Added ubqhash algorithm for Ubiq (UBQ) mining.
* Added AMD support for all progpow algos.
* Added fan/target temperature control option --fantemp.1
* Changed AMD GPU order to PCI order.
* Added AMD fan control.
* Added support for NVIDIA RTX 40XX GPUs.
* Fixed issue with Telemetry.
* Fixed Ampere modes that were not launching well on Aion mining.
* Fixed 96,5 support.
* Added reset value to power option. --power=1 will reset to stock value. (0 to ignore)
* Power option show range when trying to set different value.
1 Requires sudo (Linux)/administator privileges (Windows)
Works with:
Linux: AMDs; and NVIDAs w/ driver >515
Windows: Polaris AMDs; and NVIDIAs w/ driver >515
On exit --fantemp resets to auto on AMDs, and to 50% fan on NVIDIAs.
When using --fanspeed conjointly with --fantemp, the fan % defined with --fanspeed works as minimum fan speed.
Check our website here.
For additional information check our Usage or FAQ pages.
Follow us on Twitter
Let us know how it goes!
Happy mining!
A new miniZ v1.9z4 is out with performance improvements for 125,4 – FLUX – mining! Up to 20%!
Added ubqhash support, progpow (and variants) support for AMDs, fan control for AMDs, fan/temperature control option…
Please find miniZ v1.9z4 @ Download page.
Changelog:
* Performance improvements for 125,4 on all gpus. Up to 20%.
* Performance improvements for 150,5 on all gpus.
* Added ubqhash algorithm for Ubiq (UBQ) mining.
* Added AMD support for all progpow algos.
* Added fan/target temperature control option --fantemp.1
* Changed AMD GPU order to PCI order.
* Added AMD fan control.
* Added support for NVIDIA RTX 40XX GPUs.
* Fixed issue with Telemetry.
* Fixed Ampere modes that were not launching well on Aion mining.
* Fixed 96,5 support.
* Added reset value to power option. --power=1 will reset to stock value. (0 to ignore)
* Power option show range when trying to set different value.
1 Requires sudo (Linux)/administator privileges (Windows)
Works with:
Linux: AMDs; and NVIDAs w/ driver >515
Windows: Polaris AMDs; and NVIDIAs w/ driver >515
On exit --fantemp resets to auto on AMDs, and to 50% fan on NVIDIAs.
When using --fanspeed conjointly with --fantemp, the fan % defined with --fanspeed works as minimum fan speed.
Check our website here.
For additional information check our Usage or FAQ pages.
Follow us on Twitter
Let us know how it goes!
Happy mining!
October 21, 2022, 09:15:39 PM
Hi, mini Z seems to be not working correctly with Aion Equihash 210,9 for CMP 170HX cards. The cards don't use more than 50w or so and only does about 8-10kSol per card. I uploaded a screenshot to your website in the comments. Could you fix this? I mentioned CMP 170HX performance issues on other Equihash before also
Hi tswift,
Thanks for your messages.
This should be solved with the new version v1.9z4.
Let us know how it goes.
Cheers
October 21, 2022, 09:13:44 PM
Hello everyone,
I have a problem with the miniz miner to mine FLUX. I'm having this problem on one particular rig. I mine through hiveos.
************ miniZ v1.8y4rc2 ************
Number of CUDA[8.0] devices found: 13
/hive/miners/miniz/h-run.sh: line 20: 4392 Segmentation fault (core dumped) ./miniZ $(< ${MINER_NAME}.conf) --logfile $MINER_LOG_BASE
NAME.log --telemetry 127.0.0.1:${MINER_API_PORT} --gpu-line
How to solve this problem ? I tried with OC and without OC. On my other rigs, no problem with this flight sheet
Hi Cyb93,I have a problem with the miniz miner to mine FLUX. I'm having this problem on one particular rig. I mine through hiveos.
************ miniZ v1.8y4rc2 ************
Number of CUDA[8.0] devices found: 13
/hive/miners/miniz/h-run.sh: line 20: 4392 Segmentation fault (core dumped) ./miniZ $(< ${MINER_NAME}.conf) --logfile $MINER_LOG_BASE
NAME.log --telemetry 127.0.0.1:${MINER_API_PORT} --gpu-line
How to solve this problem ? I tried with OC and without OC. On my other rigs, no problem with this flight sheet
Thank for your message.
Was this also happening with version v1.9z3?
The new version v1.9z4 has various fixes. Could you try it out and see if this is solved?
Cheers
October 21, 2022, 09:12:16 PM
Hi everyone,
A new miniZ version v1.9z3 is out
A new miniZ version v1.9z3 is out
Please add fan control(target temperature), most of popular miners have it already!
You can try option --fantemp with the new version v1.9z4.
Cheers
October 17, 2022, 03:24:47 AM
Hi, mini Z seems to be not working correctly with Aion Equihash 210,9 for CMP 170HX cards. The cards don't use more than 50w or so and only does about 8-10kSol per card. I uploaded a screenshot to your website in the comments. Could you fix this? I mentioned CMP 170HX performance issues on other Equihash before also
October 15, 2022, 08:55:42 AM
Hello everyone,
I have a problem with the miniz miner to mine FLUX. I'm having this problem on one particular rig. I mine through hiveos.
************ miniZ v1.8y4rc2 ************
Number of CUDA[8.0] devices found: 13
/hive/miners/miniz/h-run.sh: line 20: 4392 Segmentation fault (core dumped) ./miniZ $(< ${MINER_NAME}.conf) --logfile $MINER_LOG_BASE
NAME.log --telemetry 127.0.0.1:${MINER_API_PORT} --gpu-line
How to solve this problem ? I tried with OC and without OC. On my other rigs, no problem with this flight sheet
I have a problem with the miniz miner to mine FLUX. I'm having this problem on one particular rig. I mine through hiveos.
************ miniZ v1.8y4rc2 ************
Number of CUDA[8.0] devices found: 13
/hive/miners/miniz/h-run.sh: line 20: 4392 Segmentation fault (core dumped) ./miniZ $(< ${MINER_NAME}.conf) --logfile $MINER_LOG_BASE
NAME.log --telemetry 127.0.0.1:${MINER_API_PORT} --gpu-line
How to solve this problem ? I tried with OC and without OC. On my other rigs, no problem with this flight sheet
October 08, 2022, 05:59:14 AM
Hi everyone,
A new miniZ version v1.9z3 is out
A new miniZ version v1.9z3 is out
Please add fan control(target temperature), most of popular miners have it already!
October 07, 2022, 02:16:59 PM
Hi everyone,
A new miniZ version v1.9z3 is out with new options for core and memory clocks offset.
Fixed a few issues with KawPow mining. Also, fixed issues with AMDs stats output.
Please find miniZ version v1.9z3 @ Download page.
Changelog:
* Added --gpuoffset and --memoffset for core/memory clocks offset. (Windows only)
* Fixed Ethash, on AMD's, on Windows.
* Fixed AMD temperatures, on Windows.
* Fixed AMD fan display, on Linux.
* Added --hideclocks option to hide clocks from output.
* Added socks information to console/file mining log.
* Improved invalid/stale shares on progpow/ethash/octopus.
* Fixed issues with KawPow mining.(Ravencoin, Sato, KawKaw, Neoxa, Arielcoin...)
* Improved stability.
Check our website here.
For additional information check our Usage or FAQ pages.
Follow us on Twitter
Let us know how it goes!
Happy mining!
A new miniZ version v1.9z3 is out with new options for core and memory clocks offset.
Fixed a few issues with KawPow mining. Also, fixed issues with AMDs stats output.
Please find miniZ version v1.9z3 @ Download page.
Changelog:
* Added --gpuoffset and --memoffset for core/memory clocks offset. (Windows only)
* Fixed Ethash, on AMD's, on Windows.
* Fixed AMD temperatures, on Windows.
* Fixed AMD fan display, on Linux.
* Added --hideclocks option to hide clocks from output.
* Added socks information to console/file mining log.
* Improved invalid/stale shares on progpow/ethash/octopus.
* Fixed issues with KawPow mining.(Ravencoin, Sato, KawKaw, Neoxa, Arielcoin...)
* Improved stability.
Check our website here.
For additional information check our Usage or FAQ pages.
Follow us on Twitter
Let us know how it goes!
Happy mining!
October 07, 2022, 02:08:49 PM
Thank you... i try it tomorrow and i post a feedback...
Have a nice day Miners
Have a nice day Miners
Uh, there is a mistake in setting card mode in my config, it should be --mode=03, not --mode 3. Since wrong settings are ignored you will probably run mode 8 for flux any way, which is the best(same as setting --oc2 I think)
Hi Divinity666, MrAlgo,
We expect --mode=03 and --mode 3 to work the same way
Thank you for sharing your settings/ideas here.
Let us know how it goes.
Cheers
October 07, 2022, 02:07:52 PM
What is the OC for the 3070 cards ?
Hi pit55,For Flux mining, with our 3070Ti on Linux, we use
core clock = +240; memory clock = 0; PL = 215 W
Maybe this can help as a reference for your 3070s.
Make small increases/decreases at a time.
Cheers
Jump to: