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

2h4u

newbie

Activity: 55

Merit: 0

Quote from: miniZ on August 24, 2019, 06:32:52 PM

* (Hopefully!) Fixed slow start for some GPUs/rigs.

Hmm... With rhminer as 2nd miner:

Code:

************ miniZ v1.5q2 ************
Number of CUDA[10.0] devices found: 12
Algo: EQ[150,5,3]
Pool#0: user[32K5Fu9b6uK3Gjk6vtqjo1y1c1iLDi54ub.ch3]
server[beamv2.eu-new.nicehash.com] port[3378] ssl[no] pers[Beam-PoW]
Telemetry: [http://localhost:20000]
Logging:: file[/var/log/miner/miniz/miniz.log] period[10] delay[0]
Optimisation: oc2[0 1 2 3 4 5 6 7 8 9 10 11]
Temp. limit: [75°C]
miniZ<150,5,3>[0:1:00:2933]: Selecting GPU#1[1] GeForce GTX 1060 3GB
miniZ<150,5,3>[0:1:00:2933]: Selecting GPU#11[11] GeForce GTX 1060 3GB
[ 0d 0h 0m02s|12:38:31 25/08/2019] S: 0/0 6( 6.2)Sol/s 0( 0.0)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 140ms (100.0%) (0.0%)
1>GTX 1060 3GB `S: 0/0 [0°C/ 0%] 3.51 I/s 6.1( 6.1)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf
11>GTX 1060 3GB `S: 0/0 [NA°C/NA%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=2081792MHz mclk=30868253MHz Sol/W=-nan
[ 0d 0h 0m12s|12:38:41 25/08/2019] S: 0/0 22(21.6)Sol/s 128(127.8)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 140ms (100.0%) (0.0%)
1>GTX 1060 3GB `S: 0/0 [60°C/82%] 10.43 I/s 21.6(21.6)Sol/s 99( 98.8)W clk=1911MHz mclk=4544MHz Sol/W=0.22
11>GTX 1060 3GB `S: 0/0 [57°C/53%] 0.00 I/s 0.0( 0.0)Sol/s 29( 29.0)W clk=1544MHz mclk=4414MHz Sol/W=0.00
[ 0d 0h 0m22s|12:38:51 25/08/2019] S: 2/0 22(21.9)Sol/s 133(132.5)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 121ms (100.0%) (0.0%)
1>GTX 1060 3GB `S: 2/0 [61°C/82%]*10.89 I/s 21.9(21.9)Sol/s 104(103.5)W clk=1911MHz mclk=4544MHz Sol/W=0.21
11>GTX 1060 3GB `S: 0/0 [55°C/53%] 0.00 I/s 0.0( 0.0)Sol/s 29( 29.0)W clk=1544MHz mclk=4414MHz Sol/W=0.00
miniZ<150,5,3>[0:1:00:2933]: Selecting GPU#9[9] GeForce GTX 1060 3GB
[ 0d 0h 0m32s|12:39:01 25/08/2019] S: 3/0 21(21.5)Sol/s 139(139.0)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 114ms (100.0%) (0.0%)
1>GTX 1060 3GB `S: 3/0 [61°C/82%]*11.03 I/s 21.5(21.5)Sol/s 110(110.1)W clk=1911MHz mclk=4544MHz Sol/W=0.20
9>GTX 1060 3GB `S: 0/0 [NA°C/NA%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=1544554496MHz mclk=1623655180MHz Sol/W=-nan
11>GTX 1060 3GB `S: 0/0 [54°C/53%] 0.00 I/s 0.0( 0.0)Sol/s 29( 28.9)W clk=1544MHz mclk=4414MHz Sol/W=0.00
miniZ<150,5,3>[0:1:00:2933]: Selecting GPU#7[7] GeForce GTX 1060 3GB
[ 0d 0h 0m42s|12:39:11 25/08/2019] S: 4/0 21(21.3)Sol/s 176(174.7)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 109ms (100.0%) (0.0%)
1>GTX 1060 3GB `S: 4/0 [61°C/82%]*11.08 I/s 21.3(21.3)Sol/s 115(113.7)W clk=1923MHz mclk=4544MHz Sol/W=0.19
7>GTX 1060 3GB `S: 0/0 [NA°C/NA%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=944242688MHz mclk=-1879631077MHz Sol/W=-nan
9>GTX 1060 3GB `S: 0/0 [52°C/66%] 0.00 I/s 0.0( 0.0)Sol/s 32( 32.1)W clk=1506MHz mclk=4314MHz Sol/W=0.00
11>GTX 1060 3GB `S: 0/0 [53°C/53%] 0.00 I/s 0.0( 0.0)Sol/s 29( 28.8)W clk=1544MHz mclk=4414MHz Sol/W=0.00
[ 0d 0h 0m52s|12:39:21 25/08/2019] S: 4/0 22(21.6)Sol/s 213(211.2)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 109ms (100.0%) (0.0%)
1>GTX 1060 3GB `S: 4/0 [61°C/82%] 11.12 I/s 21.6(21.6)Sol/s 118(116.1)W clk=1974MHz mclk=4544MHz Sol/W=0.19
7>GTX 1060 3GB `S: 0/0 [52°C/79%] 0.00 I/s 0.0( 0.0)Sol/s 34( 34.2)W clk=1506MHz mclk=4212MHz Sol/W=0.00
9>GTX 1060 3GB `S: 0/0 [51°C/66%] 0.00 I/s 0.0( 0.0)Sol/s 32( 32.1)W clk=1506MHz mclk=4314MHz Sol/W=0.00
11>GTX 1060 3GB `S: 0/0 [52°C/53%] 0.00 I/s 0.0( 0.0)Sol/s 29( 28.8)W clk=1544MHz mclk=4414MHz Sol/W=0.00
[ 0d 0h 1m02s|12:39:31 25/08/2019] S: 4/0 22(21.7)Sol/s 204(206.7)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 109ms (100.0%) (0.0%)
1>GTX 1060 3GB `S: 4/0 [61°C/82%] 11.14 I/s 21.7(21.7)Sol/s 109(111.7)W clk=1898MHz mclk=4544MHz Sol/W=0.19
7>GTX 1060 3GB `S: 0/0 [51°C/79%] 0.00 I/s 0.0( 0.0)Sol/s 34( 34.2)W clk=1506MHz mclk=4212MHz Sol/W=0.00
9>GTX 1060 3GB `S: 0/0 [50°C/66%] 0.00 I/s 0.0( 0.0)Sol/s 32( 32.1)W clk=1506MHz mclk=4314MHz Sol/W=0.00
11>GTX 1060 3GB `S: 0/0 [51°C/53%] 0.00 I/s 0.0( 0.0)Sol/s 29( 28.7)W clk=1544MHz mclk=4414MHz Sol/W=0.00
miniZ<150,5,3>[0:1:00:2933]: Selecting GPU#0[0] GeForce GTX 1060 3GB
[ 0d 0h 1m12s|12:39:41 25/08/2019] S: 5/0 23(22.9)Sol/s 203(205.6)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 105ms (100.0%) (0.0%)
0>GTX 1060 3GB `S: 0/0 [0°C/ 0%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=-nan
1>GTX 1060 3GB `S: 4/0 [62°C/82%] 11.16 I/s 22.0(22.0)Sol/s 108(110.7)W clk=1911MHz mclk=4544MHz Sol/W=0.20
7>GTX 1060 3GB `S: 0/0 [50°C/79%] 0.00 I/s 0.0( 0.0)Sol/s 34( 34.1)W clk=1506MHz mclk=4212MHz Sol/W=0.00
9>GTX 1060 3GB `S: 1/0 [48°C/66%]* 0.03 I/s 0.0( 0.0)Sol/s 32( 32.1)W clk=1506MHz mclk=4314MHz Sol/W=0.00
11>GTX 1060 3GB `S: 0/0 [50°C/53%] 0.00 I/s 0.0( 0.0)Sol/s 29( 28.7)W clk=1544MHz mclk=4414MHz Sol/W=0.00
[ 0d 0h 1m22s|12:39:51 25/08/2019] S: 8/0 27(27.5)Sol/s 268(250.0)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 99ms (100.0%) (0.0%)
0>GTX 1060 3GB `S: 0/0 [47°C/74%] 0.00 I/s 0.0( 0.0)Sol/s 29( 29.3)W clk=1506MHz mclk=4353MHz Sol/W=0.00
1>GTX 1060 3GB `S: 4/0 [62°C/79%] 11.17 I/s 22.2(22.2)Sol/s 109(110.6)W clk=1911MHz mclk=4544MHz Sol/W=0.20
7>GTX 1060 3GB `S: 0/0 [49°C/76%] 0.00 I/s 0.0( 0.0)Sol/s 34( 34.0)W clk=1506MHz mclk=4212MHz Sol/W=0.00
9>GTX 1060 3GB `S: 4/0 [54°C/62%]*10.94 I/s 21.3(21.3)Sol/s 67( 47.5)W clk=1898MHz mclk=4314MHz Sol/W=0.45
11>GTX 1060 3GB `S: 0/0 [49°C/49%] 0.00 I/s 0.0( 0.0)Sol/s 28( 28.6)W clk=1544MHz mclk=4414MHz Sol/W=0.00
miniZ<150,5,3>[0:1:00:2933]: Selecting GPU#10[10] GeForce GTX 1060 3GB
[ 0d 0h 1m32s|12:40:01 25/08/2019] S: 11/0 31(31.1)Sol/s 281(258.5)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 126ms (100.0%) (0.0%)
0>GTX 1060 3GB `S: 0/0 [47°C/71%] 0.00 I/s 0.0( 0.0)Sol/s 29( 29.3)W clk=1506MHz mclk=4353MHz Sol/W=0.00
1>GTX 1060 3GB `S: 7/0 [62°C/77%]*11.18 I/s 22.4(22.4)Sol/s 105(108.7)W clk=1911MHz mclk=4544MHz Sol/W=0.21
7>GTX 1060 3GB `S: 0/0 [48°C/73%] 0.00 I/s 0.0( 0.0)Sol/s 34( 33.9)W clk=1506MHz mclk=4212MHz Sol/W=0.00
9>GTX 1060 3GB `S: 4/0 [56°C/59%] 10.96 I/s 22.8(22.8)Sol/s 84( 58.2)W clk=1898MHz mclk=4314MHz Sol/W=0.39
10>GTX 1060 3GB `S: 0/0 [NA°C/NA%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=1556090752MHz mclk=16188950MHz Sol/W=-nan
11>GTX 1060 3GB `S: 0/0 [48°C/46%] 0.00 I/s 0.0( 0.0)Sol/s 28( 28.5)W clk=1544MHz mclk=4414MHz Sol/W=0.00

2:33 from start and still not all GPUs started:

Code:

[ 0d 0h 2m33s|12:41:01 25/08/2019] S: 30/0 59(59.0)Sol/s 513(423.3)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 99ms (100.0%) (0.0%)
0>GTX 1060 3GB `S: 0/0 [46°C/35%] 0.00 I/s 0.0( 0.0)Sol/s 28( 28.4)W clk=1506MHz mclk=4353MHz Sol/W=0.00
1>GTX 1060 3GB `S: 14/0 [61°C/75%]*11.19 I/s 22.1(22.1)Sol/s 109(109.1)W clk=1911MHz mclk=4544MHz Sol/W=0.20
4>GTX 1060 3GB `S: 0/0 [41°C/35%] 0.00 I/s 0.0( 0.0)Sol/s 29( 28.7)W clk=1506MHz mclk=4556MHz Sol/W=0.00
5>GTX 1060 3GB `S: 0/0 [42°C/35%] 0.00 I/s 0.0( 0.0)Sol/s 27( 27.1)W clk=1506MHz mclk=4117MHz Sol/W=0.00
7>GTX 1060 3GB `S: 3/0 [54°C/41%]*10.48 I/s 20.0(20.0)Sol/s 78( 47.2)W clk=1873MHz mclk=4212MHz Sol/W=0.42
9>GTX 1060 3GB `S: 9/0 [61°C/55%] 10.93 I/s 21.3(21.3)Sol/s 93( 82.7)W clk=1911MHz mclk=4314MHz Sol/W=0.26
10>GTX 1060 3GB `S: 2/0 [52°C/36%]*10.10 I/s 21.0(21.0)Sol/s 67( 42.0)W clk=1759MHz mclk=4233MHz Sol/W=0.50
11>GTX 1060 3GB `S: 2/0 [58°C/43%] 10.47 I/s 21.4(21.4)Sol/s 82( 58.3)W clk=1771MHz mclk=4414MHz Sol/W=0.37

invizion

newbie

Activity: 44

Merit: 0

Quote from: miniZ on August 24, 2019, 04:22:58 PM

Quote from: invizion on August 24, 2019, 03:06:37 AM

Mining AION with v1.5q_cuda10_linux-x64 - perhaps an issue with the fee pool in this release? when I get to 98% share submits I start getting:

Code:

[ERROR ] Cannot connect to any mining pool!!!

Hi invizion,
this can happen if connection to all your pools is lost. Generally the message disappears when the pool is online again.
The miner also stops mining after a while if the pools stay down (and it cannot connect to any of your mining pool).

If you specified failover pools the miner should connect to the second (or third) pool.
Unfortunately there is a bug in the latest version and failover pools are not working...
We got this error now and it will be fixed in the next update.
Cheers

v1.5q2 fixed the issue thanks!

Question, does OC1/OC2 work for all algos? What determines "power saving" to use OC1 vs OC2?

miniZ

member

Activity: 690

Merit: 17

Quote from: darkneorus on August 24, 2019, 06:41:47 PM

Quote from: miniZ on August 24, 2019, 06:05:49 PM

Quote from: darkneorus on August 24, 2019, 05:23:23 PM

something is broken with 150,5,3 on P104-100 GPUs. the hashrate is low, 20-30 Sol/s max, expected 40+.

Hi darkneorus,
if you try adding --oc1 to your command line do you get the same hashrate?
Thanks.
Cheers

yup. way lower than it should be

Hi darkneorus,
thanks for the information.

We don't have your card so, for the moment we cannot test it.
Maybe you can help us understand this GPU

You could try test other mode values by adding --mode=x, with x=[1,2,4,6,8,9] to your command line, and see if you can get a better hashrate.

Let us know which performs better.
Cheers

darkneorus

jr. member

Activity: 238

Merit: 3

Quote from: miniZ on August 24, 2019, 06:05:49 PM

Quote from: darkneorus on August 24, 2019, 05:23:23 PM

something is broken with 150,5,3 on P104-100 GPUs. the hashrate is low, 20-30 Sol/s max, expected 40+.

Hi darkneorus,
if you try adding --oc1 to your command line do you get the same hashrate?
Thanks.
Cheers

yup. way lower than it should be

Code:

0>P104-100 ` 100% [41°C/68%]* 9.17 I/s 18.1(18.1)Sol/s 106(112.3)W clk=1911MHz mclk=5005MHz Sol/W=0.16
1>P104-100 ` 100% [48°C/62%]* 7.74 I/s 15.0(15.0)Sol/s 124(114.0)W clk=1885MHz mclk=5005MHz Sol/W=0.13
2>P104-100 ` 100% [38°C/62%] 9.19 I/s 18.8(18.8)Sol/s 136(136.6)W clk=1898MHz mclk=5005MHz Sol/W=0.14
3>P104-100 ` 100% [50°C/90%] 14.02 I/s 29.2(29.2)Sol/s 148(152.3)W clk=1797MHz mclk=5005MHz Sol/W=0.19
4>P106-100 ` 100% [48°C/84%] 8.49 I/s 16.7(16.7)Sol/s 98(103.0)W clk=1885MHz mclk=4006MHz Sol/W=0.16
5>P104-100 ` 100% [55°C/100%]*13.86 I/s 27.6(27.6)Sol/s 149(151.3)W clk=1784MHz mclk=5005MHz Sol/W=0.18
6>P106-100 ` 100% [44°C/77%]* 8.53 I/s 16.8(16.8)Sol/s 89( 93.3)W clk=1911MHz mclk=4006MHz Sol/W=0.18
7>P104-100 ` 100% [44°C/77%]*14.00 I/s 27.5(27.5)Sol/s 146(154.2)W clk=1822MHz mclk=5005MHz Sol/W=0.18
8>P104-100 ` 100% [51°C/92%] 14.03 I/s 28.1(28.1)Sol/s 139(143.4)W clk=1797MHz mclk=5005MHz Sol/W=0.20

miniZ

member

Activity: 690

Merit: 17

Hi everyone,
Thank you for your precious feedback!

You can find miniZ v1.5q2 here.

In brief:

* Fixed support ZEL mining on 3GB GPU, on Windows 10.
* (Hopefully!) Fixed slow start for some GPUs/rigs.
* Fixed failover pools.
* Fixed --pers=auto for 150,5,3.
* Improved performance for 192,7 (GTX 1660 GPUs).
* Other minor bug fixes.

For additional information check our Usage or FAQ pages.

Happy mining!

miniZ

member

Activity: 690

Merit: 17

Quote from: darkneorus on August 24, 2019, 05:23:23 PM

something is broken with 150,5,3 on P104-100 GPUs. the hashrate is low, 20-30 Sol/s max, expected 40+.

Hi darkneorus,
if you try adding --oc1 to your command line do you get the same hashrate?
Thanks.
Cheers

darkneorus

jr. member

Activity: 238

Merit: 3

something is broken with 150,5,3 on P104-100 GPUs. the hashrate is low, 20-30 Sol/s max, expected 40+.

miniZ

member

Activity: 690

Merit: 17

Quote from: MineOrDie on August 24, 2019, 12:57:44 PM

Really waiting for it! You can send me a beta in PM to test it before public release if you want.

Hi MineOrDie,
thanks!
Cheers

miniZ

member

Activity: 690

Merit: 17

Quote from: 12miners on August 24, 2019, 04:12:28 AM

Hello devs
i found a bug with failover pools in config.
https://i.ibb.co/sJ2CMqS/img-2019-08-24-12-05-52.png

when I have pools on the command line, but they are offline, the program cannot switch to pools that are in the configuration. Although before hard fork BEAM it worked.

Quote

:loop
.\miniZ.exe --url=ssl://[email protected]:5000 --read-config beam.json --log --extra
timeout /t 5
goto loop

Now the program is idle if the pool is offline.
I hope that you will return as it was before. That the command line and configuration files would complement each other, and not conflict, as in version above 1.5p
all my mining rigs now on miniz! Cool

Hi 12miners,
You are right the pool gets stuck in the first pool, until the pool is online again.
It is not trying the second pool, failover pools are not working.
This is independent of command line or config file usage.

We got the error now and it will be fixed in the next update. (soon!)

Thanks a lot for letting us know! And for your preference

Cheers

miniZ

member

Activity: 690

Merit: 17

Quote from: invizion on August 24, 2019, 03:06:37 AM

Mining AION with v1.5q_cuda10_linux-x64 - perhaps an issue with the fee pool in this release? when I get to 98% share submits I start getting:

Code:

[ERROR ] Cannot connect to any mining pool!!!

Hi invizion,
this can happen if connection to all your pools is lost. Generally the message disappears when the pool is online again.
The miner also stops mining after a while if the pools stay down (and it cannot connect to any of your mining pool).

If you specified failover pools the miner should connect to the second (or third) pool.
Unfortunately there is a bug in the latest version and failover pools are not working...
We got this error now and it will be fixed in the next update.
Cheers

miniZ

member

Activity: 690

Merit: 17

Quote from: 2h4u on August 23, 2019, 10:09:35 PM

Looks like miniZ creates some strange trash files at segfault:

Quote from: 2h4u on August 23, 2019, 10:23:08 PM

Quote

* Fixed slow start for some GPUs/rigs.

No, it didn't:

Quote from: 2h4u on August 23, 2019, 10:43:50 PM

1.5q has a LOT of segmentation faults. 5 segfaults per 1 good start. Reverted back to 1.5p.

Hi 2h4u,
we are looking into this.
It seems that these issues are all related.
We hope that this time it will be fixed.
We are double checking and will release an update soon.
Cheers

MineOrDie

jr. member

Activity: 75

Merit: 1

Quote from: miniZ on August 24, 2019, 08:17:24 AM

Quote from: MineOrDie on August 24, 2019, 02:40:48 AM

Code:

miniZ<125,4>[3:1:00:2480]: Selecting GPU#0[0] GeForce GTX 1060 3GB

Hi MineOrDie,
Thanks a lot for the information.
As you can see it was still loading mode 3, and not 10.
We got the error! This bug will be fixed in the next update.
Cheers

Really waiting for it! You can send me a beta in PM to test it before public release if you want.

miniZ

member

Activity: 690

Merit: 17

Quote from: MineOrDie on August 24, 2019, 02:40:48 AM

Code:

miniZ<125,4>[3:1:00:2480]: Selecting GPU#0[0] GeForce GTX 1060 3GB

Hi MineOrDie,
Thanks a lot for the information.
As you can see it was still loading mode 3, and not 10.
We got the error! This bug will be fixed in the next update.
Cheers

miniZ

member

Activity: 690

Merit: 17

Quote from: 2h4u on August 23, 2019, 09:40:58 PM

Quote from: miniZ on August 23, 2019, 07:14:07 PM

You can find new miniZ v1.5q here.

Something wrong with the new release, Linux version. All shares are invalid, no good shares at all. Looks like --pers=auto doesn't work.

Command line: --par=150,5,3 [email protected]:3378 --templimit=75 --latency --shares-detail --extra --pers=auto --show-pers --localtime=11 --oc2=0,1,2,3,4,5,6,7 --oc1=8,9

Hi 2h4u,
thanks for spotting this.
Indeed Nicehash does not support 'auto' for Beam. We had a check in v1.5p that we accidentally removed, it will be back again in the next update.

Generally, for pools that do not support auto it is better to specify the real pers (--pers=Beam-PoW in this case) or no --pers at all.

Regarding the fee, it should be OK. Note that to show fee shares you had to use --all-shares in command line.

We're looking into the other issues.
Cheers

12miners

newbie

Activity: 14

Merit: 0

Quote from: MineOrDie on August 24, 2019, 06:05:35 AM

Quote from: 12miners on August 24, 2019, 04:12:28 AM

Hello devs
i found a bug with failover pools in config.
https://i.ibb.co/sJ2CMqS/img-2019-08-24-12-05-52.png

You misspelled aionmine.org. That's the reason.

no, this is specifically as an example, to show that the backup pools will not work

MineOrDie

jr. member

Activity: 75

Merit: 1

Quote from: 12miners on August 24, 2019, 04:12:28 AM

Hello devs
i found a bug with failover pools in config.

You misspelled aionmine.org. That's the reason.

12miners

newbie

Activity: 14

Merit: 0

Quote from: miniZ on July 29, 2019, 07:07:45 PM

Quote from: 12miners on July 23, 2019, 12:28:53 PM

Dear dev,
I really look forward to the function of the failover pool in pools.txt file!

Hi 12miners,
you can add more pools to your command line.
Example for YEC:

Code:

./miniZ --par=192,7 [email protected]:5001 [email protected]:50152 --pers=ZcashPoW

You can also add failover pools to your config file. You can create a config file by adding --write-config filename to the end of your command line. Then run miniZ with this file by typing just miniZ.exe --read-config filename. Feel free to edit this file with your favorite text editor.

Let us know if this helped.
Cheers

Hello devs
i found a bug with failover pools in config.
https://i.ibb.co/sJ2CMqS/img-2019-08-24-12-05-52.png

when I have pools on the command line, but they are offline, the program cannot switch to pools that are in the configuration. Although before hard fork BEAM it worked.

Quote

:loop
.\miniZ.exe --url=ssl://[email protected]:5000 --read-config beam.json --log --extra
timeout /t 5
goto loop

Now the program is idle if the pool is offline.
I hope that you will return as it was before. That the command line and configuration files would complement each other, and not conflict, as in version above 1.5p
all my mining rigs now on miniz! Cool

invizion

newbie

Activity: 44

Merit: 0

Mining AION with v1.5q_cuda10_linux-x64 - perhaps an issue with the fee pool in this release? when I get to 98% share submits I start getting:

Code:

[ERROR ] Cannot connect to any mining pool!!!

MineOrDie

jr. member

Activity: 75

Merit: 1

Code:

miniZ.exe --url [email protected]:2001 --par=125,4 --extra --latency --shares-detail --gpu-line --telemetry=0 --f11=1 --oc1 --mode=10

Code:

miniZ<125,4>[3:1:00:2480]: Selecting GPU#0[0] GeForce GTX 1060 3GB
miniZ<125,4>[3:1:00:2480]: Selecting GPU#1[1] GeForce GTX 1060 3GB
miniZ<125,4>[3:1:00:2480]: Selecting GPU#2[2] GeForce GTX 1060 3GB
miniZ<125,4>[3:1:00:2480]: Selecting GPU#3[3] GeForce GTX 1060 3GB
miniZ<125,4>[3:1:00:2480]: Selecting GPU#4[4] GeForce GTX 1060 3GB
[FATAL ] CUDA: failed to alloc 2524 MB for main data
miniZ<125,4>[3:1:00:2480]: Selecting GPU#5[5] GeForce GTX 1060 3GB
Algo: EQ[125,4]
Pool#0: user[wallet.RIG2]
server[stratum.zel.cash] port[2001] ssl[no] pers[ZelProof]
Optimisation: oc1[0 1 2 3 4 5] f11[0 1 2 3 4 5]
Temp. limit: [90°C]
[INFO ] Disconnecting from stratum.zel.cash
[FATAL ] CUDA: failed to alloc 2524 MB for main data
[FATAL ] CUDA: failed to alloc 2524 MB for main data
[INFO ]stratum.zel.cash[FATAL ] CUDA: failed to alloc 2524 MB for main data
[FATAL ] CUDA: failed to alloc 2524 MB for main data
Stopping miner
[FATAL ] CUDA: failed to alloc 2524 MB for main data

2h4u

newbie

Activity: 55

Merit: 0

1.5q has a LOT of segmentation faults. 5 segfaults per 1 good start. Reverted back to 1.5p.

Code:

************ miniZ v1.5q ************
Number of CUDA[10.0] devices found: 13
/hive/miners/miniz/h-run.sh: line 20: 28592 Segmentation fault ./miniZ $(< ${MINER_NAME}.conf) --logfile $MINER_LOG_BASENAME.log --telemetry 127.0.0.1:${MINER_API_PORT} --gpu-line

miniz exited, waiting to cooldown a bit

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