Pages:
Author

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

newbie
Activity: 32
Merit: 0
One question @miniZ,
Do you have implemented some anti-hacking solution, as Gminer released "optimized" miner for 150_5?

He (or they) become famous as thieves of other miner code, probably they spend some time reverse engineering competitors miners and stealing ideas.

They released beta now which improves 150_5, and previously they updated kernel months ago.

So be aware.


PS: I like your miner, especially --oc2 option can be handy when power limit needs to go down through summer.

Also I noticed that "templimit" option isn't readed from config file.


member
Activity: 690
Merit: 17
Hi,

What is the difference between miniZ v1.3n3  and miniZ v1.3n31?
Hi AcharyaOne,
there is no difference.
We updated the files about an hour ago with support for Maxwell GPUs.

In HiveOS, after creating the flightsheet and uploading the miner, if you want to update the same miner file with exaclty the same name, you need to delete the old one first from the system (or you will get stuck with the old one).

Because it may be difficult to delete this manually for some, we just added a new file with that extra '1' in case of someone needs it for a Maxwell and was using the v1.3n3 from yesterday.

Thanks.
Cheers

I get that what you are saying but there's a way to do it.
Maybe stop miner first but after that you can run the following command even from the dashboard (Run Command): /hive/miners/custom/custom-get http://miniz.ch/hiveos/miniZ-1.3n3.tar.gz -f
-f will reinstall miner

Thanks for your work, just wish it was a 1% fee :p

Cheers
Hi AcharyaOne,
Some people have difficulties using the command line, and to be honest we did not notice the dashboard (when we test on HiveOS we mostly to use the bash shell). Thanks a lot for the tip!

You may not believe this but 2% is very very little. At the moment is really not possible to change this, we still cannot even pay our current expenses from what we earn. If the situation changes we might reconsider Smiley

Thanks for using miniZ!
Cheers
newbie
Activity: 36
Merit: 0
Hi,

What is the difference between miniZ v1.3n3  and miniZ v1.3n31?
Hi AcharyaOne,
there is no difference.
We updated the files about an hour ago with support for Maxwell GPUs.

In HiveOS, after creating the flightsheet and uploading the miner, if you want to update the same miner file with exaclty the same name, you need to delete the old one first from the system (or you will get stuck with the old one).

Because it may be difficult to delete this manually for some, we just added a new file with that extra '1' in case of someone needs it for a Maxwell and was using the v1.3n3 from yesterday.

Thanks.
Cheers

I get that what you are saying but there's a way to do it.
Maybe stop miner first but after that you can run the following command even from the dashboard (Run Command): /hive/miners/custom/custom-get http://miniz.ch/hiveos/miniZ-1.3n3.tar.gz -f
-f will reinstall miner

Thanks for your work, just wish it was a 1% fee :p

Cheers
newbie
Activity: 59
Merit: 0
HiveOS.... brrrr,   ubuntu rulezzz
member
Activity: 690
Merit: 17
Hi,

What is the difference between miniZ v1.3n3  and miniZ v1.3n31?

where you see version v1.3n31 ?
Hi artful,

this is just for Hive OS users.
Because miniZ was not added yet to Hive OS, we always make available exactly the same files from a different address for ease of use.
They are exactly the same. Smiley
Cheers
member
Activity: 690
Merit: 17
Hi,

What is the difference between miniZ v1.3n3  and miniZ v1.3n31?
Hi AcharyaOne,
there is no difference.
We updated the files about an hour ago with support for Maxwell GPUs.

In HiveOS, after creating the flightsheet and uploading the miner, if you want to update the same miner file with exaclty the same name, you need to delete the old one first from the system (or you will get stuck with the old one).

Because it may be difficult to delete this manually for some, we just added a new file with that extra '1' in case of someone needs it for a Maxwell and was using the v1.3n3 from yesterday.

Thanks.
Cheers
newbie
Activity: 59
Merit: 0
Hi,

What is the difference between miniZ v1.3n3  and miniZ v1.3n31?

where you see version v1.3n31 ?
newbie
Activity: 36
Merit: 0
Hi,

What is the difference between miniZ v1.3n3  and miniZ v1.3n31?
newbie
Activity: 59
Merit: 0
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

all work, new version is working on gtx 970
member
Activity: 690
Merit: 17
to GTX 970

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
Hi artful,
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
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
newbie
Activity: 59
Merit: 0
to GTX 970

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
Hi artful,
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
member
Activity: 690
Merit: 17
Hi,
miner doesn't stop, he still writes the error. I have to stop it and restart it
Hi stzcze,
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
member
Activity: 690
Merit: 17
to GTX 970

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
Hi artful,
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
 
newbie
Activity: 59
Merit: 0
to GTX 970

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
jr. member
Activity: 109
Merit: 1
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

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
Hi ltxminer, stzcze,
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
newbie
Activity: 59
Merit: 0
version v1.3n3 + drivers 418.56 + GTX 970 - mining not working

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
member
Activity: 690
Merit: 17
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 Smiley
Cheers
member
Activity: 690
Merit: 17
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

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
Hi ltxminer, stzcze,
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
jr. member
Activity: 212
Merit: 6
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).
jr. member
Activity: 109
Merit: 1
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
Pages:
Jump to: