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

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

install a mining OS ditch windows.

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?

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 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,

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 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

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 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

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 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

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

Thanks for the great work!

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

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

Hi somaton,
We've added a check to v1.6v version that looks like it is not working for you.
Because this is not essencial, we decided to remove it. Please find a fix for you on Download page (v1.6v2).

Let us know if this is OK now. Thank you for your feedback!
Cheers

1.6v is broken, not working here at all, all previous versions are fine. Back to 1.5u2:

************ miniZ v1.6v ************
Number of CUDA[10.0] devices found: 4
Config:         [192.7.conf]
Algo:           EQ[192,7]
Pool#0:         user[user] server[equihash192.mine.zergpool.com] port[2144] ssl[no] pers[auto]
Pool#1:         user[user] server[equihash192.eu.mine.zpool.ca] port[2192] ssl[no] pers[auto]
Temp. limit:    [90°C]
[FATAL  ] No capable GPUs found for this algo.
[INFO   ] Disconnecting from equihash192.mine.zergpool.com
[INFO   ]equihash192.mine.zergpool.com Stopping miner
[INFO   ] Miner monitor exited.
miniZ<192,7>[6:0:00:7855]: Selecting GPU#3[3] GeForce RTX 2080 SUPER
miniZ<192,7>[6:0:00:7855]: Selecting GPU#0[0] GeForce RTX 2080 SUPER
miniZ<192,7>[6:0:00:10848]: Selecting GPU#1[1] GeForce RTX 2080 Ti
miniZ<192,7>[8:0:00:10953]: Selecting GPU#2[2] GeForce GTX 1080 Ti
[INFO   ] Exited GPU#3
[INFO   ] Exited GPU#0
[INFO   ] Exited GPU#1
[INFO   ] Exited GPU#2
[INFO   ] Disconnecting from equihash192.eu.mine.zpool.ca
************ miniZ v1.6v ************
Number of CUDA[10.0] devices found: 4
Config:         [192.7.conf]
Algo:           EQ[192,7]
Pool#0:         user[user] server[equihash192.mine.zergpool.com] port[2144] ssl[no] pers[auto]
Pool#1:         user[user] server[equihash192.eu.mine.zpool.ca] port[2192] ssl[no] pers[auto]
Temp. limit:    [90°C]
[FATAL  ] No capable GPUs found for this algo.
[INFO   ] Disconnecting from equihash192.mine.zergpool.com
[INFO   ]equihash192.mine.zergpool.com Stopping miner
[INFO   ] Miner monitor exited.
miniZ<192,7>[6:0:00:7855]: Selecting GPU#0[0] GeForce RTX 2080 SUPER
miniZ<192,7>[6:0:00:7855]: Selecting GPU#3[3] GeForce RTX 2080 SUPER
miniZ<192,7>[8:0:00:10953]: Selecting GPU#2[2] GeForce GTX 1080 Ti
miniZ<192,7>[6:0:00:10848]: Selecting GPU#1[1] GeForce RTX 2080 Ti
[INFO   ] Exited GPU#0
[INFO   ] Exited GPU#3
[INFO   ] Exited GPU#2
[INFO   ] Exited GPU#1
[INFO   ] Disconnecting from equihash192.eu.mine.zpool.ca

Hi rgsnedds,
Thank you for your trust and support!
Cheers

Hi cryptosize,
Your batch file looks fine for the autoswitch to work, however to avoid confusion we recommend that you remove the --par option. In any case, it should work both ways.
Cheers

Is there any special parameter that we need to use for the BEAM algo auto-switch to work properly?

Currently my batch file looks like this:

now that's exceptional dev work!

well done.