Pages:
Author

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

full member
Activity: 211
Merit: 100
GTX 1060 3GB mining BEAM = Problem

[FATAL  ] CUDA: failed to alloc 2924 MB for main data

Segmentation fault.

I tested it on Gminer 1.49 and it worked.


miniZ is the best miner, if you can fix the bug, thank you.
member
Activity: 690
Merit: 17
Hi everyone,

ZelCash will undergo a mandatory network upgrade - Kamiooka - @ block 372 500, estimated: 3rd july 2019. More info here.
Check the block height: https://explorer.zel.cash/


miniZ just released version v1.4o that supports the new algo 125,4 - ZelHash. You need to update miniZ to get ready to mine ZEL! Smiley 
Download here.


Also, to mine 125,4 you need to add --par=125,4 to your command line.
miniZ will not switch automatically for the new algo. You will need to restart the miner. Be sure to add --par=125,4 to your command line!

Command line example, for Windows:
Code:
miniZ.exe --par-125,4 --url [email protected]:50053 --log --extra

For additional information check our Usage or FAQ pages.

In case you need any help, please leave us a message.

Happy mining!
member
Activity: 690
Merit: 17

Will the BeamHashII miner support auto-switching to new algo at pre-defined block height on pools that will also support the auto-switch?

Hi garak,

in principle yes, we will work on it.

We should have done that for ZEL.

Cheers
member
Activity: 690
Merit: 17

Hi garak,
We just tested (one more time  Smiley ) mining beam with the RTX270 and it works fine for us.
Are you using the miniZ compiled for cuda 10?
You can check the version like this:
Code:
miniz@rig2:/tmp$ ./miniZ --version
************ miniZ v1.4o ************
miniZ v1.4o @ cuda v10.0, Jun 30 2019 18:50:12

If you are using miniZ compiled for cuda 10, could you show us the beginning of the program output?

Cheers

My bad!  Had cuda 8 by mistake!

Sorry to waste your time.

Thank you.
Hi garak,
no problem at all.
Glad that you made it work.
We may reorder the download table. It seems that it can be confusing.
Cheers
member
Activity: 690
Merit: 17

Hi,

I'm using Cuda Version 10 on Linux (Ubuntu 18.04):

$ /usr/local/cuda/bin/nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2018 NVIDIA Corporation
Built on Sat_Aug_25_21:08:01_CDT_2018
Cuda compilation tools, release 10.0, V10.0.130
$

This is what nvidia-smi shows:
Driver Version: 430.26       CUDA Version: 10.2



Hi garak,
We just tested (one more time  Smiley ) mining beam with the RTX270 and it works fine for us.
Are you using the miniZ compiled for cuda 10?
You can check the version like this:
Code:
miniz@rig2:/tmp$ ./miniZ --version
************ miniZ v1.4o ************
miniZ v1.4o @ cuda v10.0, Jun 30 2019 18:50:12

If you are using miniZ compiled for cuda 10, could you show us the beginning of the program output?

Cheers
member
Activity: 690
Merit: 17
Hi everyone,

Thank you all for your support!

miniZ version v1.4o is out! You can find new miniZ v1.4o v1.4o here.

Main new features are:
 * Added support for 125,4 (ZelCash).
 * Added support for 210,9 (Aion). (Testing!)

Equihash 125,4:
 * GTX 1050 Ti 4GB ~ 12 Sol/s
 * GTX 1060 3GB ~ 20.3 Sol/s
 * GTX 1070 Ti 8GB ~ 39.3 Sol/s
 * GTX 1080 8GB ~ 40.0 Sol/s
 * GTX 1080 Ti 11GB ~ 54.2 Sol/s
 * RTX 2070 8GB ~ 44.8 Sol/s

Equihash 210,9 (Testing):
 * GTX 1050 2GB ~ 72.2 Sol/s
 * GTX 1050 Ti 4GB ~ 79.7 Sol/s
 * GTX 1060 3GB ~ 134.1 Sol/s
 * GTX 1070 Ti 8GB ~ 210.7 Sol/s
 * GTX 1080 8GB ~ 229.5 Sol/s
 * RTX 2070 8GB ~ 254.8 Sol/s

Keep in mind that 210,9 (Aion) is still not fully tested and optimized. We will keep working on it.

For the next release we will
 * work on the support for the new Beam algo/fork;
 * revise all the currently supported algos to see if we can add some improvements; Smiley
 * start looking at VDS support.

Download Here
Support: FAQ and Usage
Additional information https://miniz.ch

Happy mining!

Just upgraded from 1.3n5 to 1.4o... Mining BEAM with GTX and RTX cards.  Mining does not start on the RTX 2070 cards now with the new version.  Can anyone replicate?
Hi garak,
Are you using Cuda 10 version? RTX require Cuda 10.
If you are, which OS are you using?
Cheers
member
Activity: 690
Merit: 17
Nice job!

Just your download link does not work.

Hi MineOrDie,
Thanks!
Link is working now.
Cheers
 
jr. member
Activity: 75
Merit: 1
Nice job!

Just your download link does not work.
member
Activity: 690
Merit: 17
Hi everyone,

Thank you all for your support!

miniZ version v1.4o is out! You can find new miniZ v1.4o v1.4o here.

Main new features are:
 * Added support for 125,4 (ZelCash).
 * Added support for 210,9 (Aion). (Testing!)

Equihash 125,4:
 * GTX 1050 Ti 4GB ~ 12 Sol/s
 * GTX 1060 3GB ~ 20.3 Sol/s
 * GTX 1070 Ti 8GB ~ 39.3 Sol/s
 * GTX 1080 8GB ~ 40.0 Sol/s
 * GTX 1080 Ti 11GB ~ 54.2 Sol/s
 * RTX 2070 8GB ~ 44.8 Sol/s

Equihash 210,9 (Testing):
 * GTX 1050 2GB ~ 72.2 Sol/s
 * GTX 1050 Ti 4GB ~ 79.7 Sol/s
 * GTX 1060 3GB ~ 134.1 Sol/s
 * GTX 1070 Ti 8GB ~ 210.7 Sol/s
 * GTX 1080 8GB ~ 229.5 Sol/s
 * RTX 2070 8GB ~ 254.8 Sol/s

Keep in mind that 210,9 (Aion) is still not fully tested and optimized. We will keep working on it.

For the next release we will
 * work on the support for the new Beam algo/fork;
 * revise all the currently supported algos to see if we can add some improvements; Smiley
 * start looking at VDS support.

Download here
Support: FAQ and Usage
Additional information https://miniz.ch

Happy mining!
member
Activity: 690
Merit: 17
Does 150,5 works on 1060 3gb?

I have 1063x12 rig, it does the 150,5 flawlessy.
Solutions: 1) check that your integrated graphics is turned on 2) or swap your gpu0 to the larger VRAM one.

Thanks, yes this was the problem but as they were remotely located i cant change the bios, i just excluded gpu0 from the miner. Is it possible devs to fix this and to work with no igpu?
Hi zorvalth,
as 2h4u suggested, 3GB memory is tight for our solver. When there are other programs using GPU memory, it can happen that there is no sufficient memory available for miniZ to run 150,5 on 3GB.

In this case you can add --mode0 3 to your command line. This will run GPU 0 in mode 3 (change 0 to n, being n the GPU that is having memory problem). The GPU will run a bit slower than the others but it should work.
You can try first with --mode0 10, it may not work but it is worth to try.

Let us know if this helps.
Cheers

ps: thanks 2h4u for your help!

Thnak you both! mode0 10 didnt work but mode0 3 worked just fine. There is about 13-15% hash lost on first card but thats not a problem.

What does mode do? I dont see it in the website?
Hi zorvalth,
Great that you managed to get it running.
mode option tunes the algo for the GPU memory and model. It is only useful on special cases. We may improve it in the future and add it to the website.
Cheers
full member
Activity: 223
Merit: 100
Does 150,5 works on 1060 3gb?

I have 1063x12 rig, it does the 150,5 flawlessy.
Solutions: 1) check that your integrated graphics is turned on 2) or swap your gpu0 to the larger VRAM one.

Thanks, yes this was the problem but as they were remotely located i cant change the bios, i just excluded gpu0 from the miner. Is it possible devs to fix this and to work with no igpu?
Hi zorvalth,
as 2h4u suggested, 3GB memory is tight for our solver. When there are other programs using GPU memory, it can happen that there is no sufficient memory available for miniZ to run 150,5 on 3GB.

In this case you can add --mode0 3 to your command line. This will run GPU 0 in mode 3 (change 0 to n, being n the GPU that is having memory problem). The GPU will run a bit slower than the others but it should work.
You can try first with --mode0 10, it may not work but it is worth to try.

Let us know if this helps.
Cheers

ps: thanks 2h4u for your help!

Thnak you both! mode0 10 didnt work but mode0 3 worked just fine. There is about 13-15% hash lost on first card but thats not a problem.

What does mode do? I dont see it in the website?
member
Activity: 690
Merit: 17
Does 150,5 works on 1060 3gb?

I have 1063x12 rig, it does the 150,5 flawlessy.
Solutions: 1) check that your integrated graphics is turned on 2) or swap your gpu0 to the larger VRAM one.

Thanks, yes this was the problem but as they were remotely located i cant change the bios, i just excluded gpu0 from the miner. Is it possible devs to fix this and to work with no igpu?
Hi zorvalth,
as 2h4u suggested, 3GB memory is tight for our solver. When there are other programs using GPU memory, it can happen that there is no sufficient memory available for miniZ to run 150,5 on 3GB.

In this case you can add --mode0 3 to your command line. This will run GPU 0 in mode 3 (change 0 to n, being n the GPU that is having memory problem). The GPU will run a bit slower than the others but it should work.
You can try first with --mode0 10, it may not work but it is worth to try.

Let us know if this helps.
Cheers

ps: thanks 2h4u for your help!
full member
Activity: 223
Merit: 100
Does 150,5 works on 1060 3gb?

I have 1063x12 rig, it does the 150,5 flawlessy.
Solutions: 1) check that your integrated graphics is turned on 2) or swap your gpu0 to the larger VRAM one.

Thanks, yes this was the problem but as they were remotely located i cant change the bios, i just excluded gpu0 from the miner. Is it possible devs to fix this and to work with no igpu?
newbie
Activity: 55
Merit: 0
Does 150,5 works on 1060 3gb?

I have 1063x12 rig, it does the 150,5 flawlessy.
Solutions: 1) check that your integrated graphics is turned on 2) or swap your gpu0 to the larger VRAM one.
full member
Activity: 223
Merit: 100
Does 150,5 works on 1060 3gb?

when i try it looks like the memory is not enough but you have a results in first post for 150,5...

HiveOS  1.3n5 80 and 100 the same result



Any tips?
jr. member
Activity: 200
Merit: 3
MiniZ.exe --par=192,7 --telemetry 0.0.0.0:4001 --server mine.nlpool.nl --port 2144 --user ********************************** --pass Blackbox,c=BTC --intensity 50 --latency --cuda-devices 1 --show-shares --all-shares --show-pers
************ miniZ v1.3n5 ************
miniZ,192,7[0:0:50]: Selecting GPU#1[0] GeForce GTX 1060 6GB
Algo:           EQ[192,7]
Pool#0:         user[**********************************]
                server[mine.nlpool.nl] port[2144] ssl[no] pers[BgoldPoW]
Telemetry:      [http://localhost:4001]
Intensity:      [50]
Temp. limit:    [90°C]
[ 0d 0h 0m09s] S:  0/0 0>GTX 1060 6GB ` 100% [62°C/28%]  6.27 I/s 11.0(11.0)Sol/s  50( 50.2)W clk=1936MHz mclk=4551MHz Sol/W=0.22 [BgoldPoW]- 47ms
[ 0d 0h 0m19s] S:  0/0 0>GTX 1060 6GB ` 100% [63°C/29%]  6.13 I/s 11.2(11.2)Sol/s  41( 41.2)W clk=1936MHz mclk=4551MHz Sol/W=0.27 [BgoldPoW]- 47ms
[ 0d 0h 0m29s] S:  0/0 0>GTX 1060 6GB ` 100% [64°C/29%]  6.03 I/s 11.4(11.4)Sol/s  93( 92.6)W clk=1936MHz mclk=4551MHz Sol/W=0.12 [BgoldPoW]- 14024ms
[ 0d 0h 0m39s] S:  0/0 0>GTX 1060 6GB ` 100% [64°C/29%]  6.13 I/s 12.6(12.6)Sol/s 108(107.4)W clk=1936MHz mclk=4551MHz Sol/W=0.12 [BgoldPoW]- 14024ms
[ 0d 0h 0m49s] S:  0/0 0>GTX 1060 6GB ` 100% [65°C/29%]  6.24 I/s 13.3(13.3)Sol/s  74( 81.2)W clk=1936MHz mclk=4551MHz Sol/W=0.16 [BgoldPoW]- 14024ms
[ 0d 0h 0m59s] S:  0/0 0>GTX 1060 6GB ` 100% [66°C/30%]  6.37 I/s 13.6(13.6)Sol/s  78( 81.4)W clk=1936MHz mclk=4551MHz Sol/W=0.17 [BgoldPoW]- 14024ms
[ 0d 0h 1m09s] S:  0/1 0>GTX 1060 6GB `0.00% [66°C/30%]* 6.37 I/s 13.0(13.0)Sol/s 102( 93.8)W clk=1936MHz mclk=4551MHz Sol/W=0.14 [BgoldPoW]- 9822ms
[ 0d 0h 1m20s] S:  0/1 0>GTX 1060 6GB `0.00% [66°C/30%]  6.44 I/s 12.8(12.8)Sol/s 112(100.7)W clk=1936MHz mclk=4551MHz Sol/W=0.13 [BgoldPoW]- 9822ms
[ 0d 0h 1m30s] S:  0/3 0>GTX 1060 6GB `0.00% [67°C/31%]* 6.45 I/s 12.9(12.9)Sol/s 116(105.2)W clk=1936MHz mclk=4551MHz Sol/W=0.12 [BgoldPoW]- 4822ms
[ 0d 0h 1m40s] S:  0/4 0>GTX 1060 6GB `0.00% [67°C/31%]* 6.46 I/s 12.6(12.6)Sol/s  80( 92.8)W clk=1936MHz mclk=4551MHz Sol/W=0.14 [BgoldPoW]- 3381ms
[ 0d 0h 1m50s] S:  0/4 0>GTX 1060 6GB `0.00% [67°C/31%]  6.47 I/s 12.7(12.7)Sol/s 106( 99.9)W clk=1936MHz mclk=4551MHz Sol/W=0.13 [BgoldPoW]- 3381ms

Miner fails at random and does not recover.... same issue with GTX1080ti
Hi UselessGuru,
we see that your personalisation string does not look right.

In this case, you need to add --pers auto or --smart-pers:
Code:
miniZ.exe --par=192,7 --telemetry 0.0.0.0:4001 --server mine.nlpool.nl --port 2144 --user ********************************** --pass Blackbox,c=BTC --intensity 50 --latency --cuda-devices 1 --show-shares --all-shares --show-pers --smart-pers
Let us know how it goes.
Cheers
> In this case, you need to add --pers auto or --smart-pers:

That did the trick. --pers auto works like a charm. Thank you very much for your help!
member
Activity: 690
Merit: 17
Hi,

In equihash algorithms average number of solutions per iteration is 2.
However number of solutions per iteration in miniz log is always close to 2.3, I mine equihash 96,5, is it mistake in hash rate calculations?
Can you please comment it.

Best Regards.

Hi Zminer777,

Thanks for your remark.
You are right, for 96,5 the average number of solutions per iterations should be closer to 2.
We will investigate and fix this.
It is good to cross check with values given by the pool.
It seems not many people are mining MNX with miniZ... Smiley Good that you did and report back.

Cheers
member
Activity: 488
Merit: 37
Why would you use miniZ instead of your own miner? Smiley
just for testing/comparison purpose
jr. member
Activity: 75
Merit: 1
Hi,

In equihash algorithms average number of solutions per iteration is 2.
However number of solutions per iteration in miniz log is always close to 2.3, I mine equihash 96,5, is it mistake in hash rate calculations?
Can you please comment it.

Best Regards.

Code:
[ 0d 0h 2m40s] 0>GTX 1070 Ti ` 100% [69°C/50%] 10799.04 I/s 24901.4(24901.4)Sol/s 163(164.0)W clk=1847MHz mclk=3802MHz Sol/W=151.88
[ 0d 0h 2m50s] 0>GTX 1070 Ti ` 100% [69°C/50%] 10796.81 I/s 24878.9(24878.9)Sol/s 170(165.4)W clk=1847MHz mclk=3802MHz Sol/W=150.43
[ 0d 0h 3m00s] 0>GTX 1070 Ti ` 100% [69°C/50%] 10793.15 I/s 24874.0(24874.0)Sol/s 159(163.4)W clk=1847MHz mclk=3802MHz Sol/W=152.21
[ 0d 0h 3m11s] 0>GTX 1070 Ti ` 100% [69°C/50%] 10791.12 I/s 24880.3(24880.1)Sol/s 155(162.2)W clk=1835MHz mclk=3802MHz Sol/W=153.38
[ 0d 0h 3m21s] 0>GTX 1070 Ti ` 100% [69°C/50%] 10790.08 I/s 24873.2(24873.6)Sol/s 164(163.3)W clk=1847MHz mclk=3802MHz Sol/W=152.35
[ 0d 0h 3m31s] 0>GTX 1070 Ti ` 100% [69°C/50%] 10786.53 I/s 24864.8(24866.2)Sol/s 170(164.2)W clk=1847MHz mclk=3802MHz Sol/W=151.47
[ 0d 0h 3m41s] 0>GTX 1070 Ti ` 100% [69°C/50%] 10784.79 I/s 24865.5(24866.7)Sol/s 167(164.2)W clk=1847MHz mclk=3802MHz Sol/W=151.44
[ 0d 0h 3m51s] 0>GTX 1070 Ti ` 100% [69°C/50%] 10782.77 I/s 24857.5(24860.1)Sol/s 166(164.2)W clk=1847MHz mclk=3802MHz Sol/W=151.42
Why would you use miniZ instead of your own miner? Smiley
member
Activity: 488
Merit: 37
Hi,

In equihash algorithms average number of solutions per iteration is 2.
However number of solutions per iteration in miniz log is always close to 2.3, I mine equihash 96,5, is it mistake in hash rate calculations?
Can you please comment it.

Best Regards.

Code:
[ 0d 0h 2m40s] 0>GTX 1070 Ti ` 100% [69°C/50%] 10799.04 I/s 24901.4(24901.4)Sol/s 163(164.0)W clk=1847MHz mclk=3802MHz Sol/W=151.88
[ 0d 0h 2m50s] 0>GTX 1070 Ti ` 100% [69°C/50%] 10796.81 I/s 24878.9(24878.9)Sol/s 170(165.4)W clk=1847MHz mclk=3802MHz Sol/W=150.43
[ 0d 0h 3m00s] 0>GTX 1070 Ti ` 100% [69°C/50%] 10793.15 I/s 24874.0(24874.0)Sol/s 159(163.4)W clk=1847MHz mclk=3802MHz Sol/W=152.21
[ 0d 0h 3m11s] 0>GTX 1070 Ti ` 100% [69°C/50%] 10791.12 I/s 24880.3(24880.1)Sol/s 155(162.2)W clk=1835MHz mclk=3802MHz Sol/W=153.38
[ 0d 0h 3m21s] 0>GTX 1070 Ti ` 100% [69°C/50%] 10790.08 I/s 24873.2(24873.6)Sol/s 164(163.3)W clk=1847MHz mclk=3802MHz Sol/W=152.35
[ 0d 0h 3m31s] 0>GTX 1070 Ti ` 100% [69°C/50%] 10786.53 I/s 24864.8(24866.2)Sol/s 170(164.2)W clk=1847MHz mclk=3802MHz Sol/W=151.47
[ 0d 0h 3m41s] 0>GTX 1070 Ti ` 100% [69°C/50%] 10784.79 I/s 24865.5(24866.7)Sol/s 167(164.2)W clk=1847MHz mclk=3802MHz Sol/W=151.44
[ 0d 0h 3m51s] 0>GTX 1070 Ti ` 100% [69°C/50%] 10782.77 I/s 24857.5(24860.1)Sol/s 166(164.2)W clk=1847MHz mclk=3802MHz Sol/W=151.42
Pages:
Jump to: