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

rainbowminer

jr. member

Activity: 95

Merit: 2

The new version v1.9z2 doesn't find any shares for 144,5 + LTZ on ZergPool (Windows 10, 6x GTX1070).

Quote

miniZ.exe -cd 0 1 2 3 4 5 [email protected]:2146 -p ID=wrk1,c=BTC,mc=LTZ --worker=wrk1 --pers=ZcashPoW --gpu-line --extra --latency --par=144,5

It all looks good, and the miner mines away, but shares, accepted and rejected, stay at 0 always and the miner is not detected at the pool. Also the hashrate is much much too high at the beginning at 830 for one GTX1070 and decreases down to 60 only slowly, over time.

For reference: all other miners (Gminer, MiniZ v1.8z3, ..) in fact do find shares with the equivalent parameter configuration.

Divinity666

jr. member

Activity: 312

Merit: 2

Quote from: miniZ on September 11, 2022, 07:28:31 PM

Cheers

Yes, thanks, it was wrong algo settings indeed.

ps. on RTX 3080\3070 there is also like .5 sol\s increasement on Zelhash with latest release Grin

raft888

newbie

Activity: 8

Merit: 1

I already tested miniz 1.9z2 now. hashrate gets increased up to 5 sol (from 58/59 sol to 63/64/65). any improvement is welcome. thank you

miniZ

member

Activity: 695

Merit: 17

Quote from: iRonNuke on September 10, 2022, 05:04:18 AM

Thanks for the replies! I have solved it by now, nothing wrong with your miner, maybe it was a little bit more sensitive. But it got worse and affected other algos like ETH, was a faulty PCIe power cable. When I replaced it, your miner worked fine!

Hi iRonNuke,
Thanks for letting us know.
Cheers

miniZ

member

Activity: 695

Merit: 17

Quote from: Divinity666 on September 10, 2022, 03:28:53 AM

It fixed card's naming, yes, but telemetry may still stop working after a wile and then all of a sudden it will fix itself and start working again....

Quote from: Divinity666 on September 10, 2022, 07:26:21 AM

Why won't it mine zano?

Quote

Number of miniZ CUDA>=[8.0] using driver CUDA[11.40] devices found: 1
Number of OpenCL[] devices found: 0
[WARNING] GPU[0]: NVIDIA GeForce GTX 1080 Ti does not have oc1 for this algo.
Driver:      471.11
Algo:      EQ[kawpow] [smart-pers]
Pool#0:    user[iZ2CFBHEsbjPYCWHns75LFT5NwNLc2i9hPTG1SwJjonyBnBUGCtdCdpKwBbo6KdZgH1Azg9vNcyLoBXBLEaz3HADLho9Qm6UAo11UmDDANCg.test]
      server[zano.luckypool.io] port[8877] ssl[no] pers[rAVENCOINKAWPOW]
Telemetry:   [http://localhost:3333]
Logging::    file[miniZ.log] period[30] delay[0]
Optimisation:   oc1[0]
Temp. limit:   [90 C]
[INFO ] Mining fee set to 1.00%
miniZ[00:0:00.0: 9326]: Selecting GPU#0[0] MSI GeForce GTX 1080 Ti
[ERROR ] invalid method (rAVENCOINKAWPOW)
[ERROR ] Pool:zano.luckypool.io - worker not authorized: iZ2CFBHEsbjPYCWHns75LFT5NwNLc2i9hPTG1SwJjonyBnBUGCtdCdpKwBbo6KdZgH1Azg9vNcyLoBX BLEaz3HADLho9Qm6UAo11UmDDANCg.test
[ERROR ] invalid method (rAVENCOINKAWPOW)
[ERROR ] Pool:zano.luckypool.io - worker not authorized: iZ2CFBHEsbjPYCWHns75LFT5NwNLc2i9hPTG1SwJjonyBnBUGCtdCdpKwBbo6KdZgH1Azg9vNcyLoBX BLEaz3HADLho9Qm6UAo11UmDDANCg.test

And can this miner mine firo? I tried mining on 2miners and it connects ok and card is actually mining, but it gets 100% bad shares

Hi Divinity666,
We'll continue to have a look at telemetry. We didn't manage to replicate this behavior.
Regarding zano mining, it seems that miniZ started mining the wrong algo. Normally, you do not need to write --par=ProgPowZ or --pers=zano.
You do not need to specify the algo for this pool. Check the command line it looks that there is the wrong par or pers was specified.
For firo, maybe the same happened. We find no issue with mining firo to 2miners. To mine Firo on 2miners, you do not need to specify --par=ProgPow or --pers=firo. Please check also the wallet. Make sure you set a Firo wallet.
Let us know how it goes.
Cheers

raft888

newbie

Activity: 8

Merit: 1

hello thanks for adding amd to hiveos

now I can run it. but 1.9z2 not yet out on hiveos. and how is the sol/s on 6800xt now on 1.9z2? previously around 58-59 sol
and please add beamhash3 to amd gpus, thank you

Divinity666

jr. member

Activity: 312

Merit: 2

Why won't it mine zano?

Quote

Number of miniZ CUDA>=[8.0] using driver CUDA[11.40] devices found: 1
Number of OpenCL[] devices found: 0
[WARNING] GPU[0]: NVIDIA GeForce GTX 1080 Ti does not have oc1 for this algo.
Driver:      471.11
Algo:      EQ[kawpow] [smart-pers]
Pool#0:    user[iZ2CFBHEsbjPYCWHns75LFT5NwNLc2i9hPTG1SwJjonyBnBUGCtdCdpKwBbo6KdZgH1Azg9vNcyLoBXBLEaz3HADLho9Qm6UAo11UmDDANCg.test]
      server[zano.luckypool.io] port[8877] ssl[no] pers[rAVENCOINKAWPOW]
Telemetry:   [http://localhost:3333]
Logging::    file[miniZ.log] period[30] delay[0]
Optimisation:   oc1[0]
Temp. limit:   [90 C]
[INFO ] Mining fee set to 1.00%
miniZ[00:0:00.0: 9326]: Selecting GPU#0[0] MSI GeForce GTX 1080 Ti
[ERROR ] invalid method (rAVENCOINKAWPOW)
[ERROR ] Pool:zano.luckypool.io - worker not authorized: iZ2CFBHEsbjPYCWHns75LFT5NwNLc2i9hPTG1SwJjonyBnBUGCtdCdpKwBbo6KdZgH1Azg9vNcyLoBX BLEaz3HADLho9Qm6UAo11UmDDANCg.test
[ERROR ] invalid method (rAVENCOINKAWPOW)
[ERROR ] Pool:zano.luckypool.io - worker not authorized: iZ2CFBHEsbjPYCWHns75LFT5NwNLc2i9hPTG1SwJjonyBnBUGCtdCdpKwBbo6KdZgH1Azg9vNcyLoBX BLEaz3HADLho9Qm6UAo11UmDDANCg.test

And can this miner mine firo? I tried mining on 2miners and it connects ok and card is actually mining, but it gets 100% bad shares

iRonNuke

jr. member

Activity: 98

Merit: 6

Quote from: miniZ on August 29, 2022, 01:03:55 PM

Hi iRonNuke,
We do not understand why you're having this issue with two of your GPUs.
This is happening always with your EVGA 1080, and one of the 1070 Ti, right?
Have you tried the v1.9z version? Do you have the same problem?
Do you experience the same issue if you mine another algo?
Cheers

Thanks for the replies! I have solved it by now, nothing wrong with your miner, maybe it was a little bit more sensitive. But it got worse and affected other algos like ETH, was a faulty PCIe power cable. When I replaced it, your miner worked fine!

Divinity666

jr. member

Activity: 312

Merit: 2

Quote from: miniZ on September 08, 2022, 09:43:16 AM

Hi Divinity666,
Do you also have these issues with the latest version, v1.9z?
Cheers

It fixed card's naming, yes, but telemetry may still stop working after a wile and then all of a sudden it will fix itself and start working again....

miniZ

member

Activity: 695

Merit: 17

Hi everyone,

A new miniZ version v1.9z2 is out with improvements for FLUX, on AMD gpu. Also, fixed issues that were causing the miner not to start on Windows.

Please find miniZ version v1.9z2 @ Download page.

Changelog:
* Performance improvements for some AMD gpus, on Flux. Major improvement for the RX 6800 XT.
* Fixed issues that were causing the miner to fail start, on Windows.
* Fixed issue interfering with Zano mining.
* Removed 'automatic' clock reset, on exit. Except when they are changed on the command line.

(miniZ v1.9z changelog:)
* Added support for Conflux – Octopus algorithm (NVIDIA).
* Added --fanspeed option for fan control (NVIDIA, need recent drivers).
* Improved support for AMD gpus.
* Added socks options to configuration file.
* Added clock reset when miniZ exits. (Nvidia RTX only)
* Minor bug fixes.

Check our website here.

For additional information check our Usage or FAQ pages.

Follow us on Twitter

Let us know how it goes!
Happy mining!

miniZ

member

Activity: 695

Merit: 17

Quote from: somaton on September 09, 2022, 04:44:38 PM

1.9z2 is starting fine, but octopus is not working. GPU is 3060 ti under win10, hashrate is 3.74mh/s, power consumption only 42w. After runing for 5 min, started to get error "bad share, invalid nonce, is miner not compatible with Nicehash?" Second problem: --fanspeed is not working, saying that this driver version does not support fan speed ajusting. Driver version 471.96.

Hi somaton,
We're investigating what's going on with mining octopus to Nicehash.
It seems to work fine with other pools.
Regarding fan control, --fanspeed will only work with recent drivers. We're not sure we'll be able to make it work for older drivers.
Thanks for the feedback.
Cheers

somaton

jr. member

Activity: 212

Merit: 6

1.9z2 is starting fine, but octopus is not working. GPU is 3060 ti under win10, hashrate is 3.74mh/s, power consumption only 42w. After runing for 5 min, started to get error "bad share, invalid nonce, is miner not compatible with Nicehash?" Second problem: --fanspeed is not working, saying that this driver version does not support fan speed ajusting. Driver version 471.96.

miniZ

member

Activity: 695

Merit: 17

Quote from: somaton on September 04, 2022, 02:46:43 PM

There is something wrong with 1.9z, .bat files that works fine with 1.8z3, does not work with new 1.9z. Reverted back to z3.

Example: miniz.exe --par=144,5 --pers=auto --server mine.nlpool.nl --port 2146 --user wallet.intel --pass c=BTC --telemetry 0 --shares-detail --show-shares --gpu-line --localtime 11 --latency --show-pers --pci-order --show-mode --retries=2 --retrydelay=2 --fee-time=20 --ocx

Hi somaton,
We already tested your command line and it is working well.
Are you getting some error, or warning, on the console? Could you paste it here?
Cheers

*edit* We think we got this. There is an issue with the Windows version v1.9z. But it doesn't seem to afect all Windows systems...
We’re working to fix this asap.
Cheers

miniZ

member

Activity: 695

Merit: 17

Quote from: iRonNuke on September 01, 2022, 01:50:14 PM

Quote from: miniZ on August 29, 2022, 01:03:55 PM

Hi iRonNuke,

Sorry about that.
If you mine with only one of those GPUs, does it also happen?
We're unsure this is a miniZ issue. At the moment we're still trying to reproduce this error, with no success.

Could you check the power consumption? miniZ is a bit more optimized when mining 125,4, when compared to other miners, power (and OCs) requirements may differ. If your power supply is working on its limits, this could create instability.

Let us know how it goes.
Cheers

I tried to only mine with the problematic GPUs. It got the same error, even without any core clock but PL. But if I excluded 1 & 2 it worked without errors.

Hi iRonNuke,
We do not understand why you're having this issue with two of your GPUs.
This is happening always with your EVGA 1080, and one of the 1070 Ti, right?
Have you tried the v1.9z version? Do you have the same problem?
Do you experience the same issue if you mine another algo?
Cheers

miniZ

member

Activity: 695

Merit: 17

Quote from: Divinity666 on September 01, 2022, 06:43:02 AM

Why after some time web telemetry(api) stops working? And why MSI RTX 3070 Gaming X no-LHR cards are identified as MSI RTX 3060 Ti Gaming X 8GB LHR in it and in miners initial card list? But everything is correct in report section

Quote

Telemetry:   [http://localhost:3333]
Logging::    file[miniZ.log] period[30] delay[0]
Optimisation:   oc1[0 0 0 0]
Temp. limit:   [90 C]
[INFO ] Mining fee set to 2.00%
miniZ<125,4>[06:0:00.0: 7127]: Selecting GPU#3[3] MSI GeForce RTX 3060 Ti 8GB Gaming X Trio LHR
miniZ<125,4>[06:0:00.0: 7127]: Selecting GPU#2[2] MSI GeForce RTX 3060 Ti 8GB Gaming X Trio LHR
miniZ<125,4>[06:0:00.0: 7127]: Selecting GPU#1[1] ASUS GeForce RTX 3070
miniZ<125,4>[06:0:00.0: 9100]: Selecting GPU#0[0] Gigabyte GeForce RTX 3080
[ 0d 0h 0m02s] 244(243.8)Sol/s 201(201.4)W
0>RTX 3080 [06] S: 0/0 [56 C/ 0%] 39.76 I/s 79.31(79.31)Sol/s 89( 89.1)W clk=1604MHz mclk=8784MHz Sol/W=0.890
1>RTX 3070 [06] S: 0/0 [53 C/ 0%] 27.87 I/s 55.61(55.61)Sol/s 41( 40.6)W clk=1634MHz mclk=7288MHz Sol/W=1.370
2>RTX 3070 [06] S: 0/0 [51 C/31%] 27.57 I/s 55.00(55.00)Sol/s 36( 36.3)W clk=1589MHz mclk=6940MHz Sol/W=1.516
3>RTX 3070 [06] S: 0/0 [52 C/31%] 26.99 I/s 53.84(53.84)Sol/s 35( 35.4)W clk=1559MHz mclk=6927MHz Sol/W=1.521

Hi Divinity666,
Do you also have these issues with the latest version, v1.9z?
Cheers

miniZ

member

Activity: 695

Merit: 17

Quote from: Frmg on August 30, 2022, 06:51:33 PM

Is there any option to control power consumption on AMD cards in miner, without me having to resort to manual adjustment in Catalyst Driver or Bios Mod?
Mem clocks? Core Clocks? Power Limit?
Here, in my case, this is essential. Wink

Hi Frmg,
At the moment this is not possible with AMDs.
We'll see what we can do for future releases.
Thanks for your message!
Cheers

somaton

jr. member

Activity: 212

Merit: 6

There is something wrong with 1.9z, .bat files that works fine with 1.8z3, does not work with new 1.9z. Reverted back to z3.

Example: miniz.exe --par=144,5 --pers=auto --server mine.nlpool.nl --port 2146 --user wallet.intel --pass c=BTC --telemetry 0 --shares-detail --show-shares --gpu-line --localtime 11 --latency --show-pers --pci-order --show-mode --retries=2 --retrydelay=2 --fee-time=20 --ocx

iRonNuke

jr. member

Activity: 98

Merit: 6

Quote from: miniZ on August 29, 2022, 01:03:55 PM

Hi iRonNuke,

Sorry about that.
If you mine with only one of those GPUs, does it also happen?
We're unsure this is a miniZ issue. At the moment we're still trying to reproduce this error, with no success.

Could you check the power consumption? miniZ is a bit more optimized when mining 125,4, when compared to other miners, power (and OCs) requirements may differ. If your power supply is working on its limits, this could create instability.

Let us know how it goes.
Cheers

I tried to only mine with the problematic GPUs. It got the same error, even without any core clock but PL. But if I excluded 1 & 2 it worked without errors.

Divinity666

jr. member

Activity: 312

Merit: 2

Why after some time web telemetry(api) stops working? And why MSI RTX 3070 Gaming X no-LHR cards are identified as MSI RTX 3060 Ti Gaming X 8GB LHR in it and in miners initial card list? But everything is correct in report section

Quote

Telemetry:   [http://localhost:3333]
Logging::    file[miniZ.log] period[30] delay[0]
Optimisation:   oc1[0 0 0 0]
Temp. limit:   [90 C]
[INFO ] Mining fee set to 2.00%
miniZ<125,4>[06:0:00.0: 7127]: Selecting GPU#3[3] MSI GeForce RTX 3060 Ti 8GB Gaming X Trio LHR
miniZ<125,4>[06:0:00.0: 7127]: Selecting GPU#2[2] MSI GeForce RTX 3060 Ti 8GB Gaming X Trio LHR
miniZ<125,4>[06:0:00.0: 7127]: Selecting GPU#1[1] ASUS GeForce RTX 3070
miniZ<125,4>[06:0:00.0: 9100]: Selecting GPU#0[0] Gigabyte GeForce RTX 3080
[ 0d 0h 0m02s] 244(243.8)Sol/s 201(201.4)W
0>RTX 3080 [06] S: 0/0 [56 C/ 0%] 39.76 I/s 79.31(79.31)Sol/s 89( 89.1)W clk=1604MHz mclk=8784MHz Sol/W=0.890
1>RTX 3070 [06] S: 0/0 [53 C/ 0%] 27.87 I/s 55.61(55.61)Sol/s 41( 40.6)W clk=1634MHz mclk=7288MHz Sol/W=1.370
2>RTX 3070 [06] S: 0/0 [51 C/31%] 27.57 I/s 55.00(55.00)Sol/s 36( 36.3)W clk=1589MHz mclk=6940MHz Sol/W=1.516
3>RTX 3070 [06] S: 0/0 [52 C/31%] 26.99 I/s 53.84(53.84)Sol/s 35( 35.4)W clk=1559MHz mclk=6927MHz Sol/W=1.521

Frmg

newbie

Activity: 10

Merit: 0

Is there any option to control power consumption on AMD cards in miner, without me having to resort to manual adjustment in Catalyst Driver or Bios Mod?
Mem clocks? Core Clocks? Power Limit?
Here, in my case, this is essential. Wink

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