miniZ v2.0a Equihash 144,5 125,4 210,9 150,5 192,7 BeamHash3 ProgPoW Ethash CFX - page 25.

rainbowminer

jr. member

Activity: 95

Merit: 2

There is a bug in the new v1.6v3 when mining on Nicehash. The miner seems to alter the selected algorithm from "--par=144,5s" to "150,5,3" causing 100% rejected shares on Nicehash:

This is the commandline:
miniZ.exe --telemetry 33000 -cd 0 1 4 --server beamv3.eu.nicehash.com --port 3387 --user 3M73gP6x55C7nws3ie7UwCHpy5tDDVLwHN.GTX1660TIs --pass x --pers Beam-PoW --gpu-line --extra --latency --nocolor --par=144,5s

This is what happens:

deskcube

newbie

Activity: 2

Merit: 0

Thank you very much, MiniZ. You guys are great. Its good advice too but i want to alt tab to my eve online and playstation emulator. LOL. i guess i should go and install some other OS soon.

miniZ

member

Activity: 690

Merit: 17

Hi everyone,

we released a new miniZ version with a few adjustments and fixes.

Please find miniZ version 1.6v3 @ Download page.

Changelog:

* removed autoswitch for Beam.
* no need to add --par when mining to pool.raskul.com or beamv3.nicehash.com.
* fixed --pers auto that was not working on NiceHash
* added support for GTX 1650 4GB, in BeamHash III.
* added a few corrections to 144,5 that we expect to benefit miners experiencing high cpu usage. (Let us know if this helped)

This was only possible with your feedback. Thank you!

We'll keep working to make miniZ better.

Happy mining!

miniZ

member

Activity: 690

Merit: 17

Quote from: Kringel on June 28, 2020, 09:38:48 PM

BeamV3 suddenly stopped working on Nicehash with --pers=auto (all shares are rejected); when --pers=Beam-PoW or is not specified at all miniZ still works fine.

Hi Kringel,
This is fixed now. We also spotted that issue and we just released version v1.6v3 with a few corrections. Are you using this version already? --pers auto is fine again on NiceHash.
Cheers

Kringel

jr. member

Activity: 151

Merit: 7

BeamV3 suddenly stopped working on Nicehash with --pers=auto (all shares are rejected); when --pers=Beam-PoW or is not specified at all miniZ still works fine.

miniZ

member

Activity: 690

Merit: 17

Quote from: deskcube on June 28, 2020, 05:46:19 PM

Quote from: miniZ on June 28, 2020, 08:22:59 AM

Hi Ziv1,
for Zel and 1060 3GB, the oc2 in the newest version uses a similar kernel to the one in version 1.5t.
If you experienced stability or latency issues with v1.5t then it is good to try the recent version. But if not, if the v1.5t is working well for you, and you are just mining ZEL, then there is no reason to do it.
We will try to reduce the kernel in future versions so that the 1060 3GB may also benefit in performance.

Thank you for your feedback!
Cheers

miniZ.exe --url=ssl://[email protected]:11005 --par=beam3 --pers=Beam-PoW --extra --latency --oc0 --show-mode

************ miniZ v1.6v2 ************
Number of CUDA[10.0] devices found: 1
Algo: EQ[beam3]
Pool#0: user[user]
server[127.0.0.1] port[11005] ssl[yes] pers[Beam-PoW]
Telemetry: [http://localhost:20000]
Optimisation: oc0[0]
Temp. limit: [90°C]
miniZ<144,5s>[00:0:00:3318]: Selecting GPU#0[0] GeForce GTX 1650
[FATAL ] GPU[0] has invalid mode 0.
[INFO ] Disconnecting from 127.0.0.1
[INFO ]127.0.0.1 Stopping miner

****************
GPU 0 HAS INVALID MODE 0!!!
--oc0 --oc1 --ocx all don't work.
I can't get this to work on GTX 1650 4GB , Win10 64, latest Nvidia drivers.
any ideas?

Hi deskcube,
sorry, we did not test on that GPU, but we understand what is the issue.
We are finalising a fix (1.6v3) and it will be out shortly.
Mind you that rgsnedds has a point - performance on Windows will not be as high, because the solver memory will be a bit tight for the 1650 4GB.
Thanks a lot for the feedback!
Cheers

miniZ

member

Activity: 690

Merit: 17

Quote from: Dark Oopa on June 28, 2020, 01:40:33 PM

Hello,

thanks for the answer.
I installed vc_redist.x64.exe of Visual Studio 2015, 2017 and 2019 from https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads but it didn't change anything :/

Hi Dark Oopa,
We will investigate this. However, we'll add a Cuda 8 for Windows very soon, version 1.6v3.
We stopped supporting Cuda 8 but it should be working. Maybe this will take care of your issue for now.

Cheers

rgsnedds

member

Activity: 952

Merit: 17

raskul

Quote from: deskcube on June 28, 2020, 05:46:19 PM

I can't get this to work on GTX 1650 4GB , Win10 64, latest Nvidia drivers.
any ideas?

install a mining OS

ditch windows.

deskcube

newbie

Activity: 2

Merit: 0

Quote from: miniZ on June 28, 2020, 08:22:59 AM

Hi Ziv1,
for Zel and 1060 3GB, the oc2 in the newest version uses a similar kernel to the one in version 1.5t.
If you experienced stability or latency issues with v1.5t then it is good to try the recent version. But if not, if the v1.5t is working well for you, and you are just mining ZEL, then there is no reason to do it.
We will try to reduce the kernel in future versions so that the 1060 3GB may also benefit in performance.

Thank you for your feedback!
Cheers

miniZ.exe --url=ssl://[email protected]:11005 --par=beam3 --pers=Beam-PoW --extra --latency --oc0 --show-mode

************ miniZ v1.6v2 ************
Number of CUDA[10.0] devices found: 1
Algo: EQ[beam3]
Pool#0: user[user]
server[127.0.0.1] port[11005] ssl[yes] pers[Beam-PoW]
Telemetry: [http://localhost:20000]
Optimisation: oc0[0]
Temp. limit: [90°C]
miniZ<144,5s>[00:0:00:3318]: Selecting GPU#0[0] GeForce GTX 1650
[FATAL ] GPU[0] has invalid mode 0.
[INFO ] Disconnecting from 127.0.0.1
[INFO ]127.0.0.1 Stopping miner

****************
GPU 0 HAS INVALID MODE 0!!!
--oc0 --oc1 --ocx all don't work.
I can't get this to work on GTX 1650 4GB , Win10 64, latest Nvidia drivers.
any ideas?

Dark Oopa

newbie

Activity: 83

Merit: 0

Quote from: miniZ on June 28, 2020, 01:18:29 PM

Quote from: Dark Oopa on June 28, 2020, 12:23:45 PM

Hello,

I was using 1.5t2 cuda 8 on windows 7 (with 1063s).

I wanted to tried the new version but 1.5u2 nor 1.6V works. I have a message telling in is not a valid Win32 application.
I installed last NVIDIA drivers to have cuda 10 but still same message.

is it still win7 compatible?

Hi Dark Oopa,
We had someone with an issue that might be similar to yours.
Maybe try to update this: Redistributable Packages for Visual Studio 2015 – 2019 from Microsoft.
Let us know if this helps, or we'll try to think of another possibility.
Cheers

Hello,

thanks for the answer.
I installed vc_redist.x64.exe of Visual Studio 2015, 2017 and 2019 from https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads but it didn't change anything :/

miniZ

member

Activity: 690

Merit: 17

Quote from: Dark Oopa on June 28, 2020, 12:23:45 PM

Hello,

I was using 1.5t2 cuda 8 on windows 7 (with 1063s).

I wanted to tried the new version but 1.5u2 nor 1.6V works. I have a message telling in is not a valid Win32 application.
I installed last NVIDIA drivers to have cuda 10 but still same message.

is it still win7 compatible?

Hi Dark Oopa,
We had someone with an issue that might be similar to yours.
Maybe try to update this: Redistributable Packages for Visual Studio 2015 – 2019 from Microsoft.
Let us know if this helps, or we'll try to think of another possibility.
Cheers

Dark Oopa

newbie

Activity: 83

Merit: 0

Hello,

I was using 1.5t2 cuda 8 on windows 7 (with 1063s).

I wanted to tried the new version but 1.5u2 nor 1.6V works. I have a message telling in is not a valid Win32 application.
I installed last NVIDIA drivers to have cuda 10 but still same message.

is it still win7 compatible?

miniZ

member

Activity: 690

Merit: 17

Quote from: Ziv1 on June 28, 2020, 07:38:22 AM

Hello miniZ.
W7 125.4 1063mb
- oc 2, works (2668mb).
Does it make sense to change the working version of 1.5t or wait for the version with a new smaller kernel (at least 2800mb)?
Thanks for the work.

Hi Ziv1,
for Zel and 1060 3GB, the oc2 in the newest version uses a similar kernel to the one in version 1.5t.
If you experienced stability or latency issues with v1.5t then it is good to try the recent version. But if not, if the v1.5t is working well for you, and you are just mining ZEL, then there is no reason to do it.
We will try to reduce the kernel in future versions so that the 1060 3GB may also benefit in performance.

Thank you for your feedback!
Cheers

Ziv1

newbie

Activity: 25

Merit: 1

Hello miniZ.
W7 125.4 1063mb
- oc 2, works (2668mb).
Does it make sense to change the working version of 1.5t or wait for the version with a new smaller kernel (at least 2800mb)?
Thanks for the work.

miniZ

member

Activity: 690

Merit: 17

Quote from: annapotpot on June 27, 2020, 04:52:37 PM

Does miniz uses the "forkheight2" value returned after logging in and then compare it to the returned block height on jobs or is it hardcoded for the 777777 blockheight for BEAM? I am testing it on a testnet pool and it is not using the correct algo for the testnet since the testnets blockheight is still below 777777.

Hi annapotpot,
Thank you for your question.
Because not all pools report the "forkheight2" value, we've decided to hardcode the blockheight.
In your case you'll need to add --par=144,5s or --par=beam3 to be able to test miniZ in the testnet pool.
Cheers

annapotpot

jr. member

Activity: 330

Merit: 1

Quote from: miniZ on November 03, 2018, 01:51:57 PM

Hi,

It is good to know!

For both speed and consumption there are differences, for that GPU. Although they are not the same, they look less dissimilar if one looks at efficiencies.

It is always better to let miniZ run for a bit, so that it can be closer to a steady state. The average tends to be pretty stable making it easier to compare.

Thank you for the feedback.

Does miniz uses the "forkheight2" value returned after logging in and then compare it to the returned block height on jobs or is it hardcoded for the 777777 blockheight for BEAM? I am testing it on a testnet pool and it is not using the correct algo for the testnet since the testnets blockheight is still below 777777.

miniZ

member

Activity: 690

Merit: 17

Quote from: MrPlus on June 27, 2020, 03:44:52 AM

Thanks for the great work!

All rejects on NiceHash for BeamV3 it seems.
Other miner working.

Hi MrPlus,
NiceHash does not provide blockheight information. In this case if the algo is not specified it will start mining 150,5,3 - BeamHash II.

If you are mining to stratum+tcp://beamv3.LOCATION.nicehash.com:3387 you will need to add --par=144,5s or --par=beam3.
In the next version miniZ should be able to detect the right algo.

Thank you for your support and feedback!

Cheers

miniZ

member

Activity: 690

Merit: 17

Quote from: somaton on June 26, 2020, 07:45:11 PM

miniZ: Hi, yep, 1.6v2 is working fine now, that was fast, thanks Wink

Hi somaton,
Great!
Thank you for letting us know. This could have been an issue for others too.
Cheers

MrPlus

member

Activity: 514

Merit: 11

Thanks for the great work!

All rejects on NiceHash for BeamV3 it seems.
Other miner working.

somaton

jr. member

Activity: 212

Merit: 6

miniZ: Hi, yep, 1.6v2 is working fine now, that was fast, thanks Wink

Topic: miniZ v2.0a Equihash 144,5 125,4 210,9 150,5 192,7 BeamHash3 ProgPoW Ethash CFX - page 25. (Read 60004 times)