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 soland please add beamhash3 to amd gpus, thank you
Topic: miniZ v2.0a Equihash 144,5 125,4 210,9 150,5 192,7 BeamHash3 ProgPoW Ethash CFX - page 9. (Read 59037 times)
September 11, 2022, 12:36:12 PM
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
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 soland please add beamhash3 to amd gpus, thank you
September 10, 2022, 08:26:21 AM
Why won't it mine zano?
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
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
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
[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
September 10, 2022, 06:04:18 AM
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
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!
September 10, 2022, 04:28:53 AM
Hi Divinity666,
Do you also have these issues with the latest version, v1.9z?
Cheers
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....
September 09, 2022, 07:00:07 PM
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!
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!
September 09, 2022, 06:46:46 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
September 09, 2022, 05: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.
September 08, 2022, 10:45:51 AM
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
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
September 08, 2022, 10:44:57 AM
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
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
September 08, 2022, 10:43:16 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
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
September 08, 2022, 10:42:26 AM
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.
Mem clocks? Core Clocks? Power Limit?
Here, in my case, this is essential.
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
September 04, 2022, 03: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
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
September 01, 2022, 02:50:14 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
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.
September 01, 2022, 07: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
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
August 30, 2022, 07: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.
Mem clocks? Core Clocks? Power Limit?
Here, in my case, this is essential.
August 30, 2022, 01:23:09 PM
hello can you please add "AMD" tag for HiveOS... I can't use my flightsheet...
Hi raft888,
Thank you for your message.
Unfortunately HiveOS marked miniZ as nvidia miner only.
We'll see what we can do about this.
Cheers
thank you, I will wait
August 29, 2022, 02:52:58 PM
hello can you please add "AMD" tag for HiveOS... I can't use my flightsheet...
Hi raft888,
Thank you for your message.
Unfortunately HiveOS marked miniZ as nvidia miner only.
We'll see what we can do about this.
Cheers
August 29, 2022, 02:03:55 PM
No that didn't fix it. Same as before, forgot to mention that when the miner crashes, HiveOS reports GPU 1 & 2 need attention and the rig needs to be restarted.
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
August 29, 2022, 10:58:55 AM
hello can you please add "AMD" tag for HiveOS... I can't use my flightsheet...
August 24, 2022, 09:51:29 AM
Hi iRonNuke,
Thanks for your message.
Try adding --nvidia to your command line.
This will be fixed in the next version.
Let us know how it goes.
Cheers
Thanks for your message.
Try adding --nvidia to your command line.
This will be fixed in the next version.
Let us know how it goes.
Cheers
No that didn't fix it. Same as before, forgot to mention that when the miner crashes, HiveOS reports GPU 1 & 2 need attention and the rig needs to be restarted.
Jump to: