Pages:
Author

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

member
Activity: 676
Merit: 17
Hello Team having an issue with MiniZ trying to mine Zelhash via Nicehash.  Getting all Stale: Above Target Level shares.  Have tested with Gminer and LolMiner both work without issue.  Using MiniZ via HiveOS any suggestions?

Hi bizcoin85,
Could you check if the miner is starting with correct algo and pers?
If not, then try adding the following to your command line:
Code:
--pers=ZelProof --par=125,4

If it doesn't help, could you paste here your command line?
Cheers
member
Activity: 676
Merit: 17
Кaк зaпycтить EvrProgPoW в cpeдe линeкc?
Hигдe никaкoгo oпиcaния нeт
Кaк выбpaть aлгopитм? eгo нeт в cпиcкe!

How to run EvrProgPoW in Linux environment?
There is no description anywhere
How to choose an algorithm? it's not on the list!


Hi Eujenvanino,
We made a FAQ - How to mine Evrmore?
Did you manage to make it work?
Let us know how it goes.
Cheers
newbie
Activity: 3
Merit: 0
i have an issue with BTG dual with Zill it's not working as well please advise.
newbie
Activity: 1
Merit: 0
Hello Team having an issue with MiniZ trying to mine Zelhash via Nicehash.  Getting all Stale: Above Target Level shares.  Have tested with Gminer and LolMiner both work without issue.  Using MiniZ via HiveOS any suggestions?
newbie
Activity: 46
Merit: 0
Кaк зaпycтить EvrProgPoW в cpeдe линeкc?
Hигдe никaкoгo oпиcaния нeт
Кaк выбpaть aлгopитм? eгo нeт в cпиcкe!

How to run EvrProgPoW in Linux environment?
There is no description anywhere
How to choose an algorithm? it's not on the list!
member
Activity: 676
Merit: 17
Hi everyone,

A new miniZ version v2.2c is out with support for EthashB3 and EvrProgPoW algorithms to mine Rethereum and Evrmore, respectively.

This new version also comes with important fixes, for example fixed issue when mining ProgPow/KawPoW that were causing miner error.

Please find miniZ version v2.2c @ Download page.
https://miniz.cc/download/





Changelog:

 * Added support for EthashB3 algorithm (Rethereum, RTH). Fee: 1%.
 * Added support for EvrProgPoW algorithm (Evrmore, EVR). Fee: 1%.
 * Removed DAG generation when mining ProgPow/Ethash fee, for most cases.
 * Fixed issue when mining ProgPow/KawPoW that caused miner error.
 * Fixed Zil issues when mining with Nicehash.


*** 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
https://twitter.com/miniZ_miner

Happy mining!
full member
Activity: 1148
Merit: 209
Due to the fact that there is a constant switching of orders to DaggerHashimoto on NiceHash, and the appearance of mining coins with an epoch of 0 (for example, PowBlocks - XPB), additional ZIL mining becomes impossible. Please add the ZIL API to determine the real ZIL mining round.
https://github.com/Zilliqa/apidocs/blob/master/source/index.html.md
POST Method GetNumTxBlocks to https://api.zilliqa.com
newbie
Activity: 1
Merit: 1
Hello. I have configured the miniz miner to dual mine flux with zil ( Version 2.1C ). in the begining of the miner, apperas the info that it will mine flux and zil to my adresses, but on crazypool theres no activity from this miner, and on the info show on the webshell of hiveos, the miniz never goes to mine zil . never ever..What is the problem with this version and how to solve it please?

In the extra settings i have this.

[email protected]:5005 --log --extra

Thankx
full member
Activity: 1148
Merit: 209
* Added support for new ZIL epoch #1.
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 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
still waiting for a fix for nicehash
jr. member
Activity: 312
Merit: 2
No its core voltage in my case. But whatever the cause the problem still remains - miner not gonna restart like on nvidia cards...
jr. member
Activity: 312
Merit: 2
On AMD card miner won't restart or shut down if card crashes, it will continue to work and produce invalid shares:

Quote
[INFO   ] GPU[00]: Found share with difficulty=  4.81 /810.42  pool:  4.00  net: 31.47k
[ 0d 9h45m00s|05:47:17] S: 80/0/0 0>RX 6800 XT  100% [52 C/44%]*36.91 I/s 74.21(73.53)Sol/s 110(112.1)W clk=1864MHz mclk=2120MHz Sol/W=0.656 (96.1%) (3.9%)
[INFO   ] GPU[00]: Found share with difficulty=  5.43 /810.42  pool:  4.00  net: 35.33k
[INFO   ] GPU[00]: Found share with difficulty=  5.05 /810.42  pool:  4.00  net: 35.33k
[INFO   ] GPU[00]: Found share with difficulty=  4.65 /810.42  pool:  4.00  net: 35.17k
[ 0d 9h50m00s|05:52:17] S: 83/0/0 0>RX 6800 XT  100% [52 C/44%]*36.91 I/s 73.28(73.53)Sol/s 110(112.1)W clk=1859MHz mclk=2120MHz Sol/W=0.656 (96.2%) (3.8%)
[ 0d 9h55m00s|05:57:17] S: 83/0/0 0>RX 6800 XT  100% [52 C/44%] 36.91 I/s 73.26(73.52)Sol/s 110(112.1)W clk=1865MHz mclk=2120MHz Sol/W=0.656 (96.2%) (3.8%)
[INFO   ] GPU[00]: Found share with difficulty= 10.32 /810.42  pool:  4.00  net: 36.17k
[ 0d10h 0m00s|06:02:17] S: 84/0/0 0>RX 6800 XT  100% [52 C/44%]*36.90 I/s 73.56(73.52)Sol/s 112(112.0)W clk=1841MHz mclk=2120MHz Sol/W=0.656 (96.3%) (3.7%)
[INFO   ] GPU[00]: Found share with difficulty=  4.24 /810.42  pool:  4.00  net: 36.53k
[ 0d10h 5m00s|06:07:17] S: 85/0/0 0>RX 6800 XT  100% [52 C/44%]*36.91 I/s 72.81(73.54)Sol/s 110(112.0)W clk=1859MHz mclk=2120MHz Sol/W=0.656 (96.3%) (3.7%)
[ 0d10h10m00s|06:12:17] S: 85/0/0 0>RX 6800 XT  100% [52 C/44%] 36.90 I/s 73.58(73.54)Sol/s 110(112.0)W clk=1864MHz mclk=2120MHz Sol/W=0.657 (96.3%) (3.7%)
[ 0d10h15m00s|06:17:17] S: 85/0/0 0>RX 6800 XT  100% [51 C/44%] 36.90 I/s 73.82(73.55)Sol/s 112(112.0)W clk=1853MHz mclk=2120MHz Sol/W=0.657 (96.4%) (3.6%)
[ 0d10h20m00s|06:22:17] S: 85/0/0 0>RX 6800 XT  100% [51 C/44%] 36.90 I/s 73.97(73.57)Sol/s 110(112.0)W clk=1858MHz mclk=2120MHz Sol/W=0.657 (96.4%) (3.6%)
[ 0d10h25m00s|06:27:17] S: 85/0/0 0>RX 6800 XT  100% [52 C/44%] 36.94 I/s 73.74(73.51)Sol/s 109(111.9)W clk=1855MHz mclk=2122MHz Sol/W=0.657 (96.4%) (3.6%)
[ 0d10h30m00s|06:32:17] S: 85/0/0 0>RX 6800 XT  100% [52 C/44%] 36.90 I/s 72.50(73.47)Sol/s 113(111.9)W clk=1858MHz mclk=2120MHz Sol/W=0.657 (96.4%) (3.6%)
[INFO   ] GPU[00]: Found share with difficulty=  5.04 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty= 12.02 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty= 16.76 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty=  7.03 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty= 17.45 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty= 52.51 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty= 11.70 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty= 16.93 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty=  6.34 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty=  4.92 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty=  7.87 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty=414.72 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty=  4.02 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty=  9.32 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty=  8.81 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty=  4.95 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty=  5.67 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty=  4.30 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty=  5.09 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty=  5.10 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty= 13.57 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty=  5.60 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty=  4.74 /810.42  pool:  4.00  net: 39.83k
[INFO   ] GPU[00]: Found share with difficulty=  6.75 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty= 13.38 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty=  8.77 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty= 10.44 /810.42  pool:  4.00  net: 39.83k
[WARNING] Bad share: Invalid share
[INFO   ] GPU[00]: Found share with difficulty= 26.44 /810.42  pool:  4.00  net: 39.83k
jr. member
Activity: 312
Merit: 2
Why do I get miner crashing every 24 hours or so with error 77 on random GPU when I run all 8 cards with 1 instance(1 window) of miner + some invalid shares(3-4 per 1500 or 1 day), but if I run each card with separate instance of miner(8 windows) I don't get any crashes for 2 weeks(and I simply didn't mine longer that until I close miners myself) and may be 1-2 invalid share during that time from all cards combined? It's not that convenient to run 8 miners from monitoring point of view, but I guess I'll have to because these crashes just irritate me(+ more invalid shares)... Plz fix this if possible, tnx!
ps Im minig Flux btw.
full member
Activity: 200
Merit: 100
hi, 144/5 seems to be broken on dual (btg+zil) mining on vram adjusted cards

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

gp106-3GB. Haven't you thought about the need to do a memtweak rework? GDDR5 memories also benefit from "memory timing" one of the few miners that applied correctly this function was t-rex and nbminer reached speeds of 24-26 mhs on ethehash based algorithm, it would be beneficial for mining zil and pascal series https://imgur.com/a/TdV52Rg
member
Activity: 676
Merit: 17
* Added support for new ZIL epoch #1.
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 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
full member
Activity: 1148
Merit: 209
* Added support for new ZIL epoch #1.
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
member
Activity: 676
Merit: 17
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!
member
Activity: 676
Merit: 17
With zerg/192.7 worker name in format wallet.worker sometimes works, sometimes not. Showing btc wallet instead of worker name when not.

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
member
Activity: 676
Merit: 17
intensity not working only for the first few second

Hi Coinx0x,
We'll have a look, and see what we can do for the next release.
Cheers
member
Activity: 676
Merit: 17
hi, 144/5 seems to be broken on dual (btg+zil) mining on vram adjusted cards

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
Pages:
Jump to: