Hi,
What is the difference between miniZ v1.3n3 and miniZ v1.3n31?
What is the difference between miniZ v1.3n3 and miniZ v1.3n31?
where you see version v1.3n31 ?
Topic: miniZ v2.0a Equihash 144,5 125,4 210,9 150,5 192,7 BeamHash3 ProgPoW Ethash CFX - page 54. (Read 59767 times)
April 30, 2019, 01:23:22 PM
where you see version v1.3n31 ?
April 30, 2019, 01:20:46 PM
Hi,
What is the difference between miniZ v1.3n3 and miniZ v1.3n31?
What is the difference between miniZ v1.3n3 and miniZ v1.3n31?
April 30, 2019, 12:43:03 PM
Hi artful,
we have just updated the miniZ v1.3n3 Cuda 10 Linux file.
Could you download and try again? https://miniz.ch/download/
Thanks.
Cheers
we have just updated the miniZ v1.3n3 Cuda 10 Linux file.
Could you download and try again? https://miniz.ch/download/
Thanks.
Cheers
all work, new version is working on gtx 970
April 30, 2019, 12:05:26 PM
to GTX 970
log 50 minutes:
gtx 970 not working
Hi artful,log 50 minutes:
Code:
[ 0d 0h50m30s] 209(208.1)Sol/s 1158(1154.4)W
0>GTX 1080 Ti ` 100% [63°C/100%]*19.99 I/s 39.7(40.1)Sol/s 209(215.3)W clk=1695MHz mclk=5556MHz Sol/W=0.19
1>GTX 1080 Ti ` 100% [55°C/80%] 20.21 I/s 41.0(40.6)Sol/s 210(208.8)W clk=1683MHz mclk=5556MHz Sol/W=0.19
2>GTX 1080 Ti ` 100% [59°C/100%] 19.88 I/s 40.2(39.8)Sol/s 223(216.4)W clk=1657MHz mclk=5556MHz Sol/W=0.18
3>GTX 970 ` 100% [28°C/85%] 167927.09 I/s 0.0( 0.0)Sol/s 12( 11.6)W clk=135MHz mclk=324MHz Sol/W=0.00
4>GTX 1080 Ti ` 100% [66°C/100%] 19.84 I/s 39.7(39.5)Sol/s 226(217.7)W clk=1708MHz mclk=5556MHz Sol/W=0.18
5>GTX 1660 Ti ` 100% [57°C/70%] 8.45 I/s 16.6(16.8)Sol/s 95( 95.4)W clk=1860MHz mclk=6251MHz Sol/W=0.18
6>GTX 1660 ` 100% [59°C/70%] 8.11 I/s 16.5(16.3)Sol/s 96( 95.4)W clk=1950MHz mclk=4550MHz Sol/W=0.17
7>P106-100 ` 100% [58°C/70%] 7.63 I/s 14.6(15.0)Sol/s 87( 93.7)W clk=1759MHz mclk=4201MHz Sol/W=0.16
gtx 970 not working
For Maxwell GPUs try miniZ Cuda 8 version.
Sorry about that.
Let us know if miniZ Cuda 8 works for you. Let us know if runs slower in the other GPUs.
Cheers
No,No.No
miniZ v1.3n+ working in GTX 970 fine:
CUDA 10.1, drivers 418.56
and version v1.3n3 not working
we have just updated the miniZ v1.3n3 Cuda 10 Linux file.
Could you download and try again? https://miniz.ch/download/
Thanks.
Cheers
April 30, 2019, 11:26:11 AM
to GTX 970
log 50 minutes:
gtx 970 not working
Hi artful,log 50 minutes:
Code:
[ 0d 0h50m30s] 209(208.1)Sol/s 1158(1154.4)W
0>GTX 1080 Ti ` 100% [63°C/100%]*19.99 I/s 39.7(40.1)Sol/s 209(215.3)W clk=1695MHz mclk=5556MHz Sol/W=0.19
1>GTX 1080 Ti ` 100% [55°C/80%] 20.21 I/s 41.0(40.6)Sol/s 210(208.8)W clk=1683MHz mclk=5556MHz Sol/W=0.19
2>GTX 1080 Ti ` 100% [59°C/100%] 19.88 I/s 40.2(39.8)Sol/s 223(216.4)W clk=1657MHz mclk=5556MHz Sol/W=0.18
3>GTX 970 ` 100% [28°C/85%] 167927.09 I/s 0.0( 0.0)Sol/s 12( 11.6)W clk=135MHz mclk=324MHz Sol/W=0.00
4>GTX 1080 Ti ` 100% [66°C/100%] 19.84 I/s 39.7(39.5)Sol/s 226(217.7)W clk=1708MHz mclk=5556MHz Sol/W=0.18
5>GTX 1660 Ti ` 100% [57°C/70%] 8.45 I/s 16.6(16.8)Sol/s 95( 95.4)W clk=1860MHz mclk=6251MHz Sol/W=0.18
6>GTX 1660 ` 100% [59°C/70%] 8.11 I/s 16.5(16.3)Sol/s 96( 95.4)W clk=1950MHz mclk=4550MHz Sol/W=0.17
7>P106-100 ` 100% [58°C/70%] 7.63 I/s 14.6(15.0)Sol/s 87( 93.7)W clk=1759MHz mclk=4201MHz Sol/W=0.16
gtx 970 not working
For Maxwell GPUs try miniZ Cuda 8 version.
Sorry about that.
Let us know if miniZ Cuda 8 works for you. Let us know if runs slower in the other GPUs.
Cheers
No,No.No
miniZ v1.3n+ working in GTX 970 fine:
log:
Code:
************ miniZ v1.3n+ ************
miniZ,150,5[7:0:00]: Selecting GPU#3[0] GeForce GTX 970
Algo: EQ[150,5]
Pool#0: user[wallet.970]
server[beam.eu.nicehash.com] port[3370] ssl[no] pers[Beam-PoW]
Telemetry: [http://localhost:20000]
Temp. limit: [90°C]
[ 0d 0h 0m09s] 0>GTX 970 ` 100% [43°C/84%] 3.68 I/s 6.8( 6.8)Sol/s 93( 92.6)W clk=1328MHz mclk=3004MHz Sol/W=0.07
[ 0d 0h 0m19s] 0>GTX 970 ` 100% [50°C/85%] 3.82 I/s 7.2( 7.2)Sol/s 118(117.6)W clk=1417MHz mclk=3004MHz Sol/W=0.06
[ 0d 0h 0m29s] 0>GTX 970 ` 100% [52°C/85%] 3.85 I/s 6.9( 6.9)Sol/s 119(118.6)W clk=1417MHz mclk=3004MHz Sol/W=0.06
[ 0d 0h 0m39s] 0>GTX 970 ` 100% [51°C/85%] 3.86 I/s 7.4( 7.4)Sol/s 120(120.0)W clk=1440MHz mclk=3004MHz Sol/W=0.06
[ 0d 0h 0m49s] 0>GTX 970 ` 100% [53°C/85%] 3.87 I/s 7.5( 7.5)Sol/s 119(119.4)W clk=1440MHz mclk=3004MHz Sol/W=0.06
CUDA 10.1, drivers 418.56
and version v1.3n3 not working
April 30, 2019, 11:11:17 AM
Hi,
miner doesn't stop, he still writes the error. I have to stop it and restart it
Hi stzcze,miner doesn't stop, he still writes the error. I have to stop it and restart it
It seems that the miner cannot recover from these state, so we will make it exit for the next version.
Thank you for letting us know.
Cheer
April 30, 2019, 11:09:47 AM
to GTX 970
log 50 minutes:
gtx 970 not working
Hi artful,log 50 minutes:
Code:
[ 0d 0h50m30s] 209(208.1)Sol/s 1158(1154.4)W
0>GTX 1080 Ti ` 100% [63°C/100%]*19.99 I/s 39.7(40.1)Sol/s 209(215.3)W clk=1695MHz mclk=5556MHz Sol/W=0.19
1>GTX 1080 Ti ` 100% [55°C/80%] 20.21 I/s 41.0(40.6)Sol/s 210(208.8)W clk=1683MHz mclk=5556MHz Sol/W=0.19
2>GTX 1080 Ti ` 100% [59°C/100%] 19.88 I/s 40.2(39.8)Sol/s 223(216.4)W clk=1657MHz mclk=5556MHz Sol/W=0.18
3>GTX 970 ` 100% [28°C/85%] 167927.09 I/s 0.0( 0.0)Sol/s 12( 11.6)W clk=135MHz mclk=324MHz Sol/W=0.00
4>GTX 1080 Ti ` 100% [66°C/100%] 19.84 I/s 39.7(39.5)Sol/s 226(217.7)W clk=1708MHz mclk=5556MHz Sol/W=0.18
5>GTX 1660 Ti ` 100% [57°C/70%] 8.45 I/s 16.6(16.8)Sol/s 95( 95.4)W clk=1860MHz mclk=6251MHz Sol/W=0.18
6>GTX 1660 ` 100% [59°C/70%] 8.11 I/s 16.5(16.3)Sol/s 96( 95.4)W clk=1950MHz mclk=4550MHz Sol/W=0.17
7>P106-100 ` 100% [58°C/70%] 7.63 I/s 14.6(15.0)Sol/s 87( 93.7)W clk=1759MHz mclk=4201MHz Sol/W=0.16
gtx 970 not working
For Maxwell GPUs try miniZ Cuda 8 version.
Sorry about that.
Let us know if miniZ Cuda 8 works for you. Let us know if runs slower in the other GPUs.
Cheers
April 30, 2019, 11:03:49 AM
to GTX 970
log 50 minutes:
gtx 970 not working
log 50 minutes:
Code:
[ 0d 0h50m30s] 209(208.1)Sol/s 1158(1154.4)W
0>GTX 1080 Ti ` 100% [63°C/100%]*19.99 I/s 39.7(40.1)Sol/s 209(215.3)W clk=1695MHz mclk=5556MHz Sol/W=0.19
1>GTX 1080 Ti ` 100% [55°C/80%] 20.21 I/s 41.0(40.6)Sol/s 210(208.8)W clk=1683MHz mclk=5556MHz Sol/W=0.19
2>GTX 1080 Ti ` 100% [59°C/100%] 19.88 I/s 40.2(39.8)Sol/s 223(216.4)W clk=1657MHz mclk=5556MHz Sol/W=0.18
3>GTX 970 ` 100% [28°C/85%] 167927.09 I/s 0.0( 0.0)Sol/s 12( 11.6)W clk=135MHz mclk=324MHz Sol/W=0.00
4>GTX 1080 Ti ` 100% [66°C/100%] 19.84 I/s 39.7(39.5)Sol/s 226(217.7)W clk=1708MHz mclk=5556MHz Sol/W=0.18
5>GTX 1660 Ti ` 100% [57°C/70%] 8.45 I/s 16.6(16.8)Sol/s 95( 95.4)W clk=1860MHz mclk=6251MHz Sol/W=0.18
6>GTX 1660 ` 100% [59°C/70%] 8.11 I/s 16.5(16.3)Sol/s 96( 95.4)W clk=1950MHz mclk=4550MHz Sol/W=0.17
7>P106-100 ` 100% [58°C/70%] 7.63 I/s 14.6(15.0)Sol/s 87( 93.7)W clk=1759MHz mclk=4201MHz Sol/W=0.16
gtx 970 not working
April 30, 2019, 10:12:56 AM
algo 150,5 6x 1060 6GB, W10, driver 430.39
Code:
[ 0d 3h22m53s] S:1344/0 90(90.0)Sol/s 534(535.7)W [beam-eu.leafpool.com]- 110ms (97.8%) (2.2%)
[WARNING] GPU[3]: CUDA error 'unspecified launch failure' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
[WARNING] GPU[4]: CUDA error 'unspecified launch failure' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
A bunch of this in the newest version (v1.3n3)
algo 150,5
1070ti
Win7
algo 150,5
1060 3gb (mode=3)
Win7
Hi ltxminer, stzcze,algo 150,5
1070ti
Win7
Code:
[WARNING] GPU[0]: CUDA error 'an illegal memory access was encountered' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
[WARNING] GPU[1]: CUDA error 'an illegal memory access was encountered' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
algo 150,5
1060 3gb (mode=3)
Win7
Code:
[WARNING] GPU[0]: CUDA error 'unknown error' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
[WARNING] GPU[1]: CUDA error 'unknown error' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
thank you for the log.
This CUDA warning/error might be related to your OC settings.
The miner now outputs these errors. We suggest you to modify a bit the OCs and check if it helps.
But we would like to know whether the miner exits. Could you let us know if it exits or just keeps going?
Cheers
Hi,
miner doesn't stop, he still writes the error. I have to stop it and restart it
April 30, 2019, 10:11:48 AM
version v1.3n3 + drivers 418.56 + GTX 970 - mining not working
and 10 min working miner, only:
no log, no mining
Code:
nvidia-smi -i 3
Tue Apr 30 17:57:18 2019
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 418.56 Driver Version: 418.56 CUDA Version: 10.1 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 3 GeForce GTX 970 On | 00000000:06:00.0 Off | N/A |
| 85% 33C P2 37W / 120W | 3592MiB / 4043MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 3 1070 G /usr/lib/xorg/Xorg 4MiB |
| 3 25769 C ...ing/calcprofit/miners/miniz/1.3n3/miniZ 3574MiB |
+-----------------------------------------------------------------------------+
and 10 min working miner, only:
Code:
************ miniZ v1.3n3 ************
miniZ,150,5[7:0:00]: Selecting GPU#3[0] GeForce GTX 970
Algo: EQ[150,5]
Pool#0: user[wallet.v-004.970]
server[beam.eu.nicehash.com] port[3370] ssl[no] pers[Beam-PoW]
Telemetry: [http://localhost:20000]
Temp. limit: [90°C]
no log, no mining
April 30, 2019, 09:20:49 AM
n3 is much more stable, no crashes yet in almost 10 hours. All previous 1.3 mods crashed every few hours. I dont overclock cards and not power limiting them (1080ti, 105,5).
v1.3n3 fixed high cpu load on all my rigs. Thanks for resolving this quickly.
Hi RoninAlek, somaton,thanks for letting us know that it is working fine for you, but we will still try to improve a bit more
Cheers
April 30, 2019, 09:18:56 AM
algo 150,5 6x 1060 6GB, W10, driver 430.39
Code:
[ 0d 3h22m53s] S:1344/0 90(90.0)Sol/s 534(535.7)W [beam-eu.leafpool.com]- 110ms (97.8%) (2.2%)
[WARNING] GPU[3]: CUDA error 'unspecified launch failure' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
[WARNING] GPU[4]: CUDA error 'unspecified launch failure' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
A bunch of this in the newest version (v1.3n3)
algo 150,5
1070ti
Win7
algo 150,5
1060 3gb (mode=3)
Win7
Hi ltxminer, stzcze,algo 150,5
1070ti
Win7
Code:
[WARNING] GPU[0]: CUDA error 'an illegal memory access was encountered' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
[WARNING] GPU[1]: CUDA error 'an illegal memory access was encountered' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
algo 150,5
1060 3gb (mode=3)
Win7
Code:
[WARNING] GPU[0]: CUDA error 'unknown error' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
[WARNING] GPU[1]: CUDA error 'unknown error' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
thank you for the log.
This CUDA warning/error might be related to your OC settings.
The miner now outputs these errors. We suggest you to modify a bit the OCs and check if it helps.
But we would like to know whether the miner exits. Could you let us know if it exits or just keeps going?
Cheers
April 30, 2019, 06:16:16 AM
n3 is much more stable, no crashes yet in almost 10 hours. All previous 1.3 mods crashed every few hours. I dont overclock cards and not power limiting them (1080ti, 105,5).
April 30, 2019, 01:11:30 AM
algo 150,5 6x 1060 6GB, W10, driver 430.39
Code:
[ 0d 3h22m53s] S:1344/0 90(90.0)Sol/s 534(535.7)W [beam-eu.leafpool.com]- 110ms (97.8%) (2.2%)
0>GTX 1060 6GB ` 100% [57řC/75%] 7.53 I/s 15.1(15.0)Sol/s 90( 88.7)W clk=1645MHz mclk=4353MHz Sol/W=0.17
1>GTX 1060 6GB ` 100% [56řC/75%] 7.56 I/s 14.9(15.1)Sol/s 88( 89.3)W clk=1670MHz mclk=4353MHz Sol/W=0.17
2>GTX 1060 6GB ` 100% [57řC/75%] 7.57 I/s 15.4(15.0)Sol/s 90( 89.2)W clk=1645MHz mclk=4353MHz Sol/W=0.17
3>GTX 1060 6GB ` 100% [53řC/75%] 7.60 I/s 15.0(15.0)Sol/s 89( 89.1)W clk=1683MHz mclk=4353MHz Sol/W=0.17
4>GTX 1060 6GB ` 100% [55řC/75%] 7.49 I/s 14.9(14.9)Sol/s 88( 89.1)W clk=1620MHz mclk=4353MHz Sol/W=0.17
5>GTX 1060 6GB ` 100% [57řC/75%] 7.54 I/s 14.8(15.0)Sol/s 89( 89.2)W clk=1645MHz mclk=4353MHz Sol/W=0.17
[WARNING] GPU[1]: CUDA error 'unspecified launch failure' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
[WARNING] GPU[4]: CUDA error 'unspecified launch failure' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
[WARNING] GPU[1]: CUDA error 'unspecified launch failure' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
[WARNING] GPU[0]: CUDA error 'unspecified launch failure' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
[WARNING] GPU[4]: CUDA error 'unspecified launch failure' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
[WARNING] GPU[5]: CUDA error 'unspecified launch failure' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
[WARNING] GPU[2]: CUDA error 'unspecified launch failure' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
[WARNING] GPU[1]: CUDA error 'unspecified launch failure' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
[WARNING] GPU[0]: CUDA error 'unspecified launch failure' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
[WARNING] GPU[3]: CUDA error 'unspecified launch failure' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
[WARNING] GPU[4]: CUDA error 'unspecified launch failure' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
April 30, 2019, 12:49:15 AM
A bunch of this in the newest version (v1.3n3)
algo 150,5
1070ti
Win7
algo 150,5
1060 3gb (mode=3)
Win7
algo 150,5
1070ti
Win7
Code:
[WARNING] GPU[0]: CUDA error 'an illegal memory access was encountered' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
[WARNING] GPU[1]: CUDA error 'an illegal memory access was encountered' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
[WARNING] GPU[2]: CUDA error 'an illegal memory access was encountered' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
[WARNING] GPU[4]: CUDA error 'an illegal memory access was encountered' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
algo 150,5
1060 3gb (mode=3)
Win7
Code:
[WARNING] GPU[0]: CUDA error 'unknown error' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
[WARNING] GPU[1]: CUDA error 'unknown error' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
[WARNING] GPU[2]: CUDA error 'unknown error' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
[WARNING] GPU[4]: CUDA error 'unknown error' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
[WARNING] GPU[3]: CUDA error 'unknown error' in func 'eq_00.8[dx][[2;ba8<51B, SM, PS2>::solve' line 971
April 29, 2019, 08:41:38 PM
v1.3n3 fixed high cpu load on all my rigs. Thanks for resolving this quickly.
April 29, 2019, 07:53:12 PM
Hi everyone,
Big thanks for you amazing patience and cooperation!
We believe to have fixed a few major issues. Nevertheless, we will keep further testing.
We made available new files for both Windows and Linux.
You can find the miniZ v1.3n3 on our website https://miniz.ch/download/
* Improved high CPU load. (We keep testing)
* Fixed "offline" worker issue.
* Fixed problems with sparkpool
* Modified --localtime, added the possibility to show both local time and running time. (Ex. --localtime 11) Usage
* Other minor fixes.
For those who use Hive OS there is a new link for you:
http://miniz.ch/hiveos/miniZ-1.3n3.tar.gz
Cheers
Big thanks for you amazing patience and cooperation!
We believe to have fixed a few major issues. Nevertheless, we will keep further testing.
We made available new files for both Windows and Linux.
You can find the miniZ v1.3n3 on our website https://miniz.ch/download/
* Improved high CPU load. (We keep testing)
* Fixed "offline" worker issue.
* Fixed problems with sparkpool
* Modified --localtime, added the possibility to show both local time and running time. (Ex. --localtime 11) Usage
* Other minor fixes.
For those who use Hive OS there is a new link for you:
http://miniz.ch/hiveos/miniZ-1.3n3.tar.gz
Cheers
April 29, 2019, 06:58:53 PM
Hi MineOrDie,
I think the easiest fix for now is to just add --mode0 3 (this puts gpu 0 into mode 3), maybe you
are ok with this solution.
Also remember that if you are using power limit and OC, and it may help to get better performance if you add --oc1 (or less likely --oc2).
Thanks for giving miniZ a try :-)
Cheers
No problem, thank you for your hard work and try to get added into Hive by default. I hit them up, but they just said that you have a turtorial on your site how to run miniZ on Hive, so just to use that. More people would use miniZ if it's already there by default.I think the easiest fix for now is to just add --mode0 3 (this puts gpu 0 into mode 3), maybe you
are ok with this solution.
Also remember that if you are using power limit and OC, and it may help to get better performance if you add --oc1 (or less likely --oc2).
Thanks for giving miniZ a try :-)
Cheers
EDIT: So we fixed one problem, but now I have another.
My LA is 7+. On 144,5 everything was fine.
Thank you.
Yes that would be nice. Maybe, in the future they will add miniZ!
We will keep the tutorial online. (But now we are tempted to remove it
)We keep looking into the load issue.
Cheers
April 29, 2019, 05:07:31 PM
Hi MineOrDie,
I think the easiest fix for now is to just add --mode0 3 (this puts gpu 0 into mode 3), maybe you
are ok with this solution.
Also remember that if you are using power limit and OC, and it may help to get better performance if you add --oc1 (or less likely --oc2).
Thanks for giving miniZ a try :-)
Cheers
No problem, thank you for your hard work and try to get added into Hive by default. I hit them up, but they just said that you have a turtorial on your site how to run miniZ on Hive, so just to use that. More people would use miniZ if it's already there by default.I think the easiest fix for now is to just add --mode0 3 (this puts gpu 0 into mode 3), maybe you
are ok with this solution.
Also remember that if you are using power limit and OC, and it may help to get better performance if you add --oc1 (or less likely --oc2).
Thanks for giving miniZ a try :-)
Cheers
EDIT: So we fixed one problem, but now I have another.
My LA is 7+. On 144,5 everything was fine.
April 29, 2019, 04:59:59 PM
Hi MineOrDie,
It should run as it looks like there is enough memory to run it (3019-25=2994), but
maybe it is still too tight...
You still can try two things:
1. --mode=3 (it will be a bit slow, but just to see if it works)
2. exclude the first GPU (that has less free memory) with -cde 0
Then we can try to workout a solution for you :-)
Cheers
With all 12 GPUs I would have additional 2.5 GPUs worth of hashing power free compared to GMiner. Nice work!
Hi MineOrDie,
I think the easiest fix for now is to just add --mode0 3 (this puts gpu 0 into mode 3), maybe you
are ok with this solution.
Also remember that if you are using power limit and OC, and it may help to get better performance if you add --oc1 (or less likely --oc2).
Thanks for giving miniZ a try :-)
Cheers
Jump to: