miniZv2.3c Equihash144,5 125,4 210,9 150,5 192,7 Beam ProgPoW Ethash CFX KLS PYI

[Porrit]

What does the —oc1 and —oc2 do? I’m mining Beam on Hiveos with 1080Ti’s. Allready applied oc and pl within hiveos. Do I still use -oc1 or —oc2?

Love miniz by the way 💪

[1715003448]

1715003448

[1715003448]

1715003448

[1715003448]

1715003448

[1715003448]

1715003448

[miniZ]

* Better mode detection 3GB cards. (150,5)

Can you give more details? Does this mean automatic --mode=3 even when flag not included in command line?

Hi ltxminer,
That was the ideia... did it work for you?
Cheers

[miniZ]

What does the —oc1 and —oc2 do? I’m mining Beam on Hiveos with 1080Ti’s. Allready applied oc and pl within hiveos. Do I still use -oc1 or —oc2?

Love miniz by the way 💪

Hi Porrit,
The --oc1 and the --oc2, just help miniZ to tune the algo according to
your overclock settings.
You first you should do the overclock/power limit like you usually do,
and only then try to start miniZ with --oc1 or --oc2 to see if you get an extra boost.
Thank you for using miniZ.
Cheers

[ltxminer]

* Better mode detection 3GB cards. (150,5)

Can you give more details? Does this mean automatic --mode=3 even when flag not included in command line?

Hi ltxminer,
That was the ideia... did it work for you?
Cheers

It did not.

My rig card #0 is 6gb, the rest is 3gb
Maybe that is the problem for your auto setting

[Porrit]

What does the —oc1 and —oc2 do? I’m mining Beam on Hiveos with 1080Ti’s. Allready applied oc and pl within hiveos. Do I still use -oc1 or —oc2?

Love miniz by the way 💪

Hi Porrit,
The --oc1 and the --oc2, just help miniZ to tune the algo according to
your overclock settings.
You first you should do the overclock/power limit like you usually do,
and only then try to start miniZ with --oc1 or --oc2 to see if you get an extra boost.
Thank you for using miniZ.
Cheers

Thanks, it does not make any difference for me. Oc1 gives worse hash and oc2 the same hash as none used.

[miniZ]

* Better mode detection 3GB cards. (150,5)

Can you give more details? Does this mean automatic --mode=3 even when flag not included in command line?

Hi ltxminer,
That was the ideia... did it work for you?
Cheers

It did not.

My rig card #0 is 6gb, the rest is 3gb
Maybe that is the problem for your auto setting

Hi ltxminer,
When you use --mode=3, the miner will apply this mode to all GPUs. This includes the 1060 6GB that will run slower since this (very likely) is  not the optimal mode for this GPU.
You can try running miniZ with --mode=3 --mode0 4 or --mode=3 --mode0 8, this will set mode=3 for all GPUs except for the GPU#0.
Sorry about the complicated settings. --mode is still an experimental setting, and we are going to try to improve automatic detection for the next release.
Cheers

[miniZ]

What does the —oc1 and —oc2 do? I’m mining Beam on Hiveos with 1080Ti’s. Allready applied oc and pl within hiveos. Do I still use -oc1 or —oc2?

Love miniz by the way 💪

Hi Porrit,
The --oc1 and the --oc2, just help miniZ to tune the algo according to
your overclock settings.
You first you should do the overclock/power limit like you usually do,
and only then try to start miniZ with --oc1 or --oc2 to see if you get an extra boost.
Thank you for using miniZ.
Cheers

Thanks, it does not make any difference for me. Oc1 gives worse hash and oc2 the same hash as none used.

Hi Porrit,
--oc1/2 may not improve performance, it really depends on the OCs and power limit you are using. This option is a way to make the miner more flexible and adaptable to each rig configuration.
Cheers

[MineOrDie]

Hey,

ZEL will have an upcoming algo change to ther unique algo, can you maybe reach out to them, offer your help and be the one who will provide the most optimized miner when they release their upgraded network?

Also n5 gives me a bit lower hashrate on 144,5 compared to n4.

[Yashnik]

Would be great to have Aion support for your miner, can this be done?

[hogwash.89m]

Hey,

ZEL will have an upcoming algo change to ther unique algo, can you maybe reach out to them, offer your help and be the one who will provide the most optimized miner when they release their upgraded network?

Also n5 gives me a bit lower hashrate on 144,5 compared to n4.

Spending some development time on new ZelHash algo (new ZEL antiFPGA/ASIC algo) would be nice, as it's promising coin.

[miniZ]

Hey,

ZEL will have an upcoming algo change to ther unique algo, can you maybe reach out to them, offer your help and be the one who will provide the most optimized miner when they release their upgraded network?

Also n5 gives me a bit lower hashrate on 144,5 compared to n4.

Spending some development time on new ZelHash algo (new ZEL antiFPGA/ASIC algo) would be nice, as it's promising coin.

Hi MineOrDie, hogwash.89m,
Thank you for your suggestion.
We will try to know more details about the new upcoming ZEL algo, but if they stay in the equihash domain it is likely that we will support
Cheers

[miniZ]

Would be great to have Aion support for your miner, can this be done?

Hi, Aion support is in the pipeline.
After ensuring 1.3n is stable we will work on it.
Cheers

[Yashnik]

Would be great to have Aion support for your miner, can this be done?

Hi, Aion support is in the pipeline.
After ensuring 1.3n is stable we will work on it.
Cheers

Please check your private messages.

[ltxminer]

Currently, when miner crashes, for example with these errors:

Code:

[FATAL ] GPU[0]: CUDA error 30 'unknown error' in func 'eq_:80C8>5_2~3]>4:e0aB, SM, PS2>::solve' line 1119 
[FATAL ] GPU[2]: CUDA error 30 'unknown error' in func 'eq_:80C8>5_2~3]>4:e0aB, SM, PS2>::solve' line 1119 
[FATAL ] GPU[4]: CUDA error 30 'unknown error' in func 'eq_:80C8>5_2~3]>4:e0aB, SM, PS2>::solve' line 1119 
[FATAL ] GPU[1]: CUDA error 30 'unknown error' in func 'eq_:80C8>5_2~3]>4:e0aB, SM, PS2>::solve' line 1119 
[FATAL ] GPU[3]: CUDA error 30 'unknown error' in func 'eq_:80C8>5_2~3]>4:e0aB, SM, PS2>::solve' line 1119 
[FATAL ] GPU[5]: CUDA error 30 'unknown error' in func 'eq_:80C8>5_2~3]>4:e0aB, SM, PS2>::solve' line 1119 

An error window pops up and miner halts

Can you make it so that the error window does not pop up?
Also, just make the miner restart?

[joseph32]

I've had similar experiences. See the picture below. If a card crashs or hangs for whatever reason (RTX cards, maybe this matters), miniZ just print these lines until restart, but does not mine anymore.

Can you please just ignore the faulty card(s) and continue mining with the rest?

[hogwash.89m]

Hi MineOrDie, hogwash.89m,
Thank you for your suggestion.
We will try to know more details about the new upcoming ZEL algo, but if they stay in the equihash domain it is likely that we will support
Cheers

@miniZ
It's definitely flavour of equihash, they are aiming to do something similarly as 150_5 (BEAM) Equihash with custom datapath, but will also focus on making modifications which would prevent FPGA to gain much performance advantage ove GPUs (or atleast as minimal as possible).
And they plan to release it on testnet soon.
That are only information which I have.
Have a nice day.

And can confirm that --oc1 on 1080 gives extra 1 Sol/s *
With following settings (topping to 25.5 - 26 Sol/s, with efficiency of 0.20 Sol/W) :

Code:

PL 72%
Core +180
Mem +340

Currently, when miner crashes, for example with these errors:

Code:

[FATAL ] GPU[0]: CUDA error 30 'unknown error' in func 'eq_:80C8>5_2~3]>4:e0aB, SM, PS2>::solve' line 1119 
[FATAL ] GPU[2]: CUDA error 30 'unknown error' in func 'eq_:80C8>5_2~3]>4:e0aB, SM, PS2>::solve' line 1119 
[FATAL ] GPU[4]: CUDA error 30 'unknown error' in func 'eq_:80C8>5_2~3]>4:e0aB, SM, PS2>::solve' line 1119 
[FATAL ] GPU[1]: CUDA error 30 'unknown error' in func 'eq_:80C8>5_2~3]>4:e0aB, SM, PS2>::solve' line 1119 
[FATAL ] GPU[3]: CUDA error 30 'unknown error' in func 'eq_:80C8>5_2~3]>4:e0aB, SM, PS2>::solve' line 1119 
[FATAL ] GPU[5]: CUDA error 30 'unknown error' in func 'eq_:80C8>5_2~3]>4:e0aB, SM, PS2>::solve' line 1119 

An error window pops up and miner halts

Can you make it so that the error window does not pop up?
Also, just make the miner restart?

@ltxminer
It's Windows Error reporting settings which shown that dialog, and blocks miner restart until user action.
Save this code in .reg file and execute it.
This is adding dword to registry (or add it manually, it's quite readable), and it disables showing Error Reporting dialog UI when program error happens, like when miner throws a error.

Code:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting]
"DontShowUI"=dword:00000001

Or same thing via elevated (admin) CMD reg command, result is same. Which ever you prefer.
https://superuser.com/a/715645

[miniZ]

Currently, when miner crashes, for example with these errors:

Code:

[FATAL ] GPU[0]: CUDA error 30 'unknown error' in func 'eq_:80C8>5_2~3]>4:e0aB, SM, PS2>::solve' line 1119 
[FATAL ] GPU[2]: CUDA error 30 'unknown error' in func 'eq_:80C8>5_2~3]>4:e0aB, SM, PS2>::solve' line 1119 
[FATAL ] GPU[4]: CUDA error 30 'unknown error' in func 'eq_:80C8>5_2~3]>4:e0aB, SM, PS2>::solve' line 1119 
[FATAL ] GPU[1]: CUDA error 30 'unknown error' in func 'eq_:80C8>5_2~3]>4:e0aB, SM, PS2>::solve' line 1119 
[FATAL ] GPU[3]: CUDA error 30 'unknown error' in func 'eq_:80C8>5_2~3]>4:e0aB, SM, PS2>::solve' line 1119 
[FATAL ] GPU[5]: CUDA error 30 'unknown error' in func 'eq_:80C8>5_2~3]>4:e0aB, SM, PS2>::solve' line 1119 

An error window pops up and miner halts

Can you make it so that the error window does not pop up?
Also, just make the miner restart?

I've had similar experiences. See the picture below. If a card crashs or hangs for whatever reason (RTX cards, maybe this matters), miniZ just print these lines until restart, but does not mine anymore.

Can you please just ignore the faulty card(s) and continue mining with the rest?

Hi ltxminer, joseph32,
Thank you for your feedback.
Which miniZ version are you using? If you are not using the 1.3n5, we suggest you to try it out. It should exit more gracefuly. But it is a good idea to follow hogwash.89m suggestion anyway.
If we ignore the faulty cards, the miner will crash again and eventually will not be able to recover. Normally this error is related to driver instability and this affects all the cards. The best is to adjust the OCs.
Cheers

[miniZ]

@miniZ
It's definitely flavour of equihash, they are aiming to do something similarly as 150_5 (BEAM) Equihash with custom datapath, but will also focus on making modifications which would prevent FPGA to gain much performance advantage ove GPUs (or atleast as minimal as possible).
And they plan to release it on testnet soon.
That are only information which I have.
Have a nice day.

And can confirm that --oc1 on 1080 gives extra 1 Sol/s *
With following settings (topping to 25.5 - 26 Sol/s, with efficiency of 0.20 Sol/W) :

Code:

PL 72%
Core +180
Mem +340

@ltxminer
It's Windows Error reporting settings which shown that dialog, and blocks miner restart until user action.
Save this code in .reg file and execute it.
This is adding dword to registry (or add it manually, it's quite readable), and it disables showing Error Reporting dialog UI when program error happens, like when miner throws a error.

Code:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting]
"DontShowUI"=dword:00000001

Or same thing via elevated (admin) CMD reg command, result is same. Which ever you prefer.
https://superuser.com/a/715645

Hi hogwash.89m,
Thank you for the information about the new ZEL algo. We will investigate more.
Also, thanks for sharing a few tips!
Cheers

[123sss]

please add your miner algo HoneyComb Beenode coin https://bitcointalk.org/index.php?topic=5131731.0

[miniZ]

please add your miner algo HoneyComb Beenode coin https://bitcointalk.org/index.php?topic=5131731.0

Hi 123sss, 
for now miniZ is an Equihash cuda miner and the effort to add a completly different algo would be too big.
Thank you for your suggestion!
Cheers