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

Hi angelbbs,
Thanks for your message.
We had a look and already fixed this.
It will be OK in the next version.
The current version 2.1c runs with the correct epoch on shardpool and on crazypool.
Cheers

Wrong ZIL epoch detection

************ miniZ v2.1c ************
Number of miniZ CUDA>=[.] using driver CUDA[12.20] devices found: 4
miniZ: Excluding GPU#0 Nvidia GeForce RTX 3060
miniZ: Excluding GPU#3 Gigabyte RTX2070S Gaming OC 3X
Driver:         536.40
Algo:           EQ[144,5] [smart-pers]
Pool#0:         user[**************] server[zhash.auto.nicehash.com] port[9200] ssl[no] pers[auto]
Pool#1:         user[**************] server[daggerhashimoto.auto.nicehash.com] port[9200] ssl[no] pers[zil]
Telemetry:      [http://localhost:4002]
Temp. limit:    [90 C]
[INFO   ] Mining fee set to 2.00%
miniZ<144,5>[10:0:00.0: 6786]: Selecting GPU#1[0] Nvidia GeForce GTX 1070
miniZ<144,5>[10:0:00.0: 6786]: Selecting GPU#2[1] Gigabyte GeForce GTX 1070
[ 0d 0h 0m09s] 106(106.3)Sol/s 186(185.7)W
 1>GTX 1070      ` 100% [62 C/40%] 25.00 I/s 49.87(49.87)Sol/s  79( 79.0)W clk=1531MHz mclk=4303MHz Sol/W=0.631
 2>GTX 1070      ` 100% [52 C/26%] 28.26 I/s 56.38(56.38)Sol/s 107(106.7)W clk=1518MHz mclk=4303MHz Sol/W=0.528
[ 0d 0h 0m10s] 106(106.2)Sol/s 186(185.7)W
 1>GTX 1070      ` 100% [62 C/40%] 25.00 I/s 49.88(49.88)Sol/s  79( 79.0)W clk=1531MHz mclk=4303MHz Sol/W=0.631
 2>GTX 1070      ` 100% [52 C/26%] 28.25 I/s 56.35(56.35)Sol/s 107(106.7)W clk=1518MHz mclk=4303MHz Sol/W=0.528
miniZ<2nd>[84:0:00.0: 6786]: Selecting GPU#2[1] Gigabyte GeForce GTX 1070
miniZ<2nd>[84:0:00.0: 6786]: Selecting GPU#1[0] Nvidia GeForce GTX 1070
[INFO   ] GPU[2]: Generating DAG #87 [1719+26=1746MB]
[INFO   ] GPU[1]: Generating DAG #87 [1719+26=1746MB]
[ 0d 0h 0m20s]  1( 1.1)H/s 111(111.0)W
 1>GTX 1070      ` 100% [60 C/40%]  0.21(0.21)H/s  52( 51.7)W clk=1708MHz mclk=4303MHz H/W=0.004
 2>GTX 1070      ` 100% [50 C/28%]  1.18(1.18)H/s  59( 59.3)W clk=1556MHz mclk=4303MHz H/W=0.020
[INFO   ] GPU[2]: Generated DAG in 3.897

Hi everyone,

A new miniZ version v2.1c is out with support for kHeavyHash algorithm to mine KASPA, and support for new ZIL eppoch.

Please find miniZ version v2.1c @ Download page.



Changelog:

* Added support for kHeavyHash algorithm (KASPA). Fee: 0.8%.
* Added support for new ZIL epoch #1.
* Improvements for CFX, for some NVIDIA gpus.
* Improved invalid shares on CFX.

*** Thank you all for the feedback! ***

Remember to try --oc1/--oc2/--ocX options for optimum performance. (NVIDIA only)

For additional information check our Usage or FAQ pages.

Download miniZ latest version here.

Follow us on Twitter

Happy mining!

Hi somaton,
We've looked into this before, and it seems to be on the pool side.
However we'll have another look for the next release.
Cheers

Hi Coinx0x,
We'll have a look, and see what we can do for the next release.
Cheers

Hi Mr.merson,
Sorry for the late reply.
How much ram do you have on gpu? Possibly there is a better kernel to run btg+zil with low ram.

Maybe you could try adding --mode=14, or --mode=15.

Let us know how it goes.
Cheers

Hi Divinity666, somaton,
We'll look into this over the next few days, and see if we can replicate the issues.
Thank you for your messages.
Cheers

yep, autofan is not very good compared to other miners.

one more bug: --gpuoffset is not working at all with 3070 ti, but working fine with 3060 ti, 3070, 3080, driver 528.49.

Will you ever fix fan control I wonder? If miner stays on maximum % set in config(e.g. --fanmax 60) for too long it won't change it anymore when temperature will actually go down...

With zerg/192.7 worker name in format wallet.worker sometimes works, sometimes not. Showing btc wallet instead of worker name when not.

intensity not working only for the first few second

hi, 144/5 seems to be broken on dual (btg+zil) mining on vram adjusted cards

I've tested low values simply out of curiosity - I need high values(to work). Ping is 50-60ms but even 200ms shouldn't cause anything. Haven't tried other pools.

upd. So after a bit of testing I can confirm that values above 999 don't work.

Just read that --jobtimeout 300 is the default and that decreasing n below 80-100 may cause instabilities, depends also on the pool. Out of curiosity what is your ping to the pool and did you try if another pool gives the same issue?

Well its basically same as not using --jobtimeout at all. Unless you use small values(like 0-120 or so) that it happens sooner - so they work. Really high values seem not to work though.

Do yu actually need to use --jobtimeout? Just curious.
As it is with the videocard in your PC have you tried a different miner(s) or pool(s) just to see if  it still happens.
It might be a driver issue or something else, I know its a bummer to troubleshoot but I have no experience with mining flux and my last use of miniZ is abt a year ago.

Hope this triggers some other people with more miniZ experience to help you.

I'm mostly encounter it with my 6800xt in my PC, because in rigs I've got 6-8 cards so share rate is higher, but it can be any videocard. Im mining flux at Herominiers and use big share size(24ksol) because overall it gives higher h\r, but sometimes when it's taking too long to find a share it would disconnect\reconnect from pool. I tried settings like 0 or 60 - and they work, with 0 you disconnect\reconnect after 10-15 seconds and then it starts doing it constantly. With 60 its like the same 10-15 second buffer + 60, but if I use like 999 or 9999 or something in between it seems it doesn't work because I get disconnect\reconnect sooner than it's supposed to. And I mean even with 999 seconds setting it shouldn't get any disconnects because single 6800xt finds a share sooner than that with 24ksol sharediff.

It would be more helpfull if you would give some more details, like videocard, pool and settings used.

What is --jobtimeout max setting? Tried =999 but it certainly doesn't work because I had message(in pool's stats stream) that I was reconnected to the pool in less than 15 minutes if there is not a single share submitted.

Hi everyone,

A new miniZ version v2.0c5 is out with fix for OC/power options that were having a few issues.

Please find the miniZ v2.0c5 version @ Download page.
 



Changelog:
 * Fixed gpuoffset/memoffset/power options that were not working properly.
 * Fixed gpuoffset2/memoffset2/power2 options for dual mining.


Check if the option --autoclocks works for you, it can be very useful for changing OC settings during dual mining.

For additional information check our Usage or FAQ pages.

Download miniZ latest version here.

Engage, feedback and support:

Because your feedback is very important, miniZ kindly encourages you to use the comment box on the website or this forum for feedback (questions, suggestions, requests...).

We wish you a fast and friendly mining experience!