|
miniZ (OP)
|
 |
August 24, 2019, 12:14:07 AM |
|
Hi everyone, Thanks a lot for your feedback and support!  You can find new miniZ v1.5q here. In brief: * Adjusted oc modes for ZelHash - 125,4. Major improvements for 1080Ti (>7%). * Adjusted oc modes for BeamHashII - 150,5,3 with improvements. * Improvements for ZHash - 144,5, for RTX cards. * Further attempts to support ZEL mining on 3GB GPU, on Windows 10. * Fixed support for 144,5 for 1050 2GB, on Windows 10. * Fixed slow start for some GPUs/rigs. * Added --csv option for log stats in csv format. * Added busID to -ci output. * Fixed issue connection to sparkpool. * Fixed invalid shares on flypool. * Other minor bug fixes. Check performances here. Or performances page for each algorithm. For additional information check our Usage or FAQ pages. Happy mining! |
miniZ is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter |
|
|
|
|
|
|
|
"Bitcoin: the cutting edge of begging technology." -- Giraffe.BTC
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
MineOrDie
Jr. Member
 Offline
Activity: 75
Merit: 1
|
|
August 24, 2019, 12:22:04 AM
Last edit: August 24, 2019, 12:33:18 AM by MineOrDie |
|
Still the same thing on Windows 10 and 125,4 algo.
Your solver still wants to allocate 2524MB, and my cards only got 2480 memory free.
Nothing changed from the last version.
|
|
|
|
|
|
miniZ (OP)
|
|
August 24, 2019, 12:36:22 AM |
|
Still the same thing on Windows 10 and 125,4 algo.
Your solver still wants to allocate 2524MB, and my cards only got 2480 memory free.
Nothing changed from the last version.
Hi MineOrDie, thanks for the feedback. Could you check what happens if you try to force mode 10 with --mode=10? Cheers |
miniZ is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter |
|
|
MineOrDie
Jr. Member
Offline
Activity: 75
Merit: 1
|
|
August 24, 2019, 12:39:49 AM |
|
Still the same thing on Windows 10 and 125,4 algo.
Your solver still wants to allocate 2524MB, and my cards only got 2480 memory free.
Nothing changed from the last version.
Hi MineOrDie, thanks for the feedback. Could you check what happens if you try to force mode 10 with --mode=10? Cheers I tried with that command already. Using it from the start. It's the same as with not mode 10. You need to shrink your solver just a tiny bit more. Even if that means loss of performance. |
|
|
|
|
|
miniZ (OP)
|
|
August 24, 2019, 12:48:55 AM |
|
Still the same thing on Windows 10 and 125,4 algo.
Your solver still wants to allocate 2524MB, and my cards only got 2480 memory free.
Nothing changed from the last version.
Hi MineOrDie, thanks for the feedback. Could you check what happens if you try to force mode 10 with --mode=10? Cheers I tried with that command already. Using it from the start. It's the same as with not mode 10. You need to shrink your solver just a tiny bit more. Even if that means loss of performance. Hi MineOrDie, thanks. It is weird because the 2524MB message should refer to mode=3. On mode=10 we have 2409 MB. Could you paste here the beginning of miniZ output? And command line. Cheers |
miniZ is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter |
|
|
2h4u
Newbie
Offline
Activity: 55
Merit: 0
|
|
August 24, 2019, 02:40:58 AM |
|
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 --url=xxx@beamv2.eu-new.nicehash.com: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 Number of CUDA[10.0] devices found: 10
miniZ<150,5,3>[1:1:00:7993]: Selecting GPU#0[0] GeForce GTX 1070 Ti
miniZ<150,5,3>[4:1:00:5994]: Selecting GPU#1[1] P106-100
miniZ<150,5,3>[4:1:00:5994]: Selecting GPU#2[2] P106-100
miniZ<150,5,3>[4:1:00:5994]: Selecting GPU#3[3] P106-100
miniZ<150,5,3>[4:1:00:5990]: Selecting GPU#4[4] GeForce GTX 1060 6GB
miniZ<150,5,3>[4:1:00:5990]: Selecting GPU#5[5] GeForce GTX 1060 6GB
miniZ<150,5,3>[4:1:00:5990]: Selecting GPU#6[6] GeForce GTX 1060 6GB
miniZ<150,5,3>[4:1:00:5990]: Selecting GPU#7[7] GeForce GTX 1060 6GB
miniZ<150,5,3>[7:1:00:3970]: Selecting GPU#8[8] GeForce GTX 1050 Ti
miniZ<150,5,3>[7:1:00:3970]: Selecting GPU#9[9] GeForce GTX 1050 Ti
Algo: EQ[150,5,3]
Pool#0: user[xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx]
server[beamv2.eu-new.nicehash.com] port[3378] ssl[no] pers[auto]
Telemetry: [http://localhost:20000]
Logging:: file[/var/log/miner/miniz/miniz.log] period[10] delay[0]
Optimisation: oc1[8 9] oc2[0 1 2 3 4 5 6 7]
Temp. limit: [75°C]
[ 0d 0h 0m09s|09:29:20 24/08/2019] S: 0/1 44(43.6)Sol/s 76( 76.1)W [beamv2.eu-new.nicehash.com,auto]- 121ms (100.0%) (0.0%)
0>GTX 1070 Ti `S: 0/1 [59°C/59%]*19.41 I/s 37.9(37.9)Sol/s 42( 41.6)W clk=1860MHz mclk=4536MHz Sol/W=0.91
1>P106-100 `S: 0/0 [58°C/66%] 0.67 I/s 1.2( 1.2)Sol/s 34( 34.4)W clk=1771MHz mclk=4665MHz Sol/W=0.04
2>P106-100 `S: 0/0 [0°C/ 0%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=5MHz mclk=-1MHz Sol/W=-nan
3>P106-100 `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
4>GTX 1060 6GB `S: 0/0 [NA°C/NA%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=-280358912MHz mclk=88544533MHz Sol/W=-nan
5>GTX 1060 6GB `S: 0/0 [NA°C/NA%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=1544585216MHz mclk=1639390746MHz Sol/W=-nan
6>GTX 1060 6GB `S: 0/0 [NA°C/NA%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=2094080MHz mclk=17240592MHz Sol/W=-nan
7>GTX 1060 6GB `S: 0/0 [NA°C/NA%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=2068480MHz mclk=3669763MHz Sol/W=-nan
8>GTX 1050 Ti `S: 0/0 [NA°C/NA%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=2081793MHz mclk=2557701MHz Sol/W=-nan
9>GTX 1050 Ti `S: 0/0 [NA°C/NA%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=2065408MHz mclk=19335178MHz Sol/W=-nan
[ 0d 0h 0m19s|09:29:30 24/08/2019] S: 0/3 88(88.4)Sol/s 395(395.1)W [beamv2.eu-new.nicehash.com,auto]- 107ms (100.0%) (0.0%)
0>GTX 1070 Ti `S: 0/1 [59°C/59%] 20.99 I/s 42.6(42.6)Sol/s 42( 41.6)W clk=1860MHz mclk=4536MHz Sol/W=1.02
1>P106-100 `S: 0/0 [58°C/66%] 12.52 I/s 26.1(26.1)Sol/s 34( 34.4)W clk=1771MHz mclk=4665MHz Sol/W=0.76
2>P106-100 `S: 0/0 [60°C/69%] 0.00 I/s 0.0( 0.0)Sol/s 31( 31.1)W clk=1506MHz mclk=4738MHz Sol/W=0.00
3>P106-100 `S: 0/1 [63°C/69%]* 0.19 I/s 0.1( 0.1)Sol/s 55( 55.1)W clk=1455MHz mclk=4437MHz Sol/W=0.00
4>GTX 1060 6GB `S: 0/0 [54°C/64%] 0.00 I/s 0.0( 0.0)Sol/s 28( 27.8)W clk=1544MHz mclk=4363MHz Sol/W=0.00
5>GTX 1060 6GB `S: 0/1 [59°C/61%]* 0.14 I/s 0.1( 0.1)Sol/s 106(105.7)W clk=1974MHz mclk=4437MHz Sol/W=0.00
6>GTX 1060 6GB `S: 0/0 [60°C/66%] 0.14 I/s 0.1( 0.1)Sol/s 99( 99.3)W clk=1822MHz mclk=4404MHz Sol/W=0.00
7>GTX 1060 6GB `S: 0/0 [NA°C/NA%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=2068480MHz mclk=3669763MHz Sol/W=-nan
8>GTX 1050 Ti `S: 0/0 [NA°C/NA%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=2081793MHz mclk=2557701MHz Sol/W=-nan
9>GTX 1050 Ti `S: 0/0 [NA°C/NA%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=2065408MHz mclk=19335178MHz Sol/W=-nan
[ 0d 0h 0m29s|09:29:40 24/08/2019] S: 0/16 131(130.7)Sol/s 426(426.1)W [beamv2.eu-new.nicehash.com,auto]- 95ms (100.0%) (0.0%)
0>GTX 1070 Ti `S: 0/2 [59°C/59%]*21.33 I/s 43.7(43.7)Sol/s 42( 41.6)W clk=1860MHz mclk=4536MHz Sol/W=1.05
1>P106-100 `S: 0/2 [58°C/66%]*12.50 I/s 26.8(26.8)Sol/s 34( 34.4)W clk=1771MHz mclk=4665MHz Sol/W=0.78
2>P106-100 `S: 0/6 [60°C/69%]* 0.10 I/s 0.0( 0.0)Sol/s 31( 31.1)W clk=1506MHz mclk=4738MHz Sol/W=0.00
3>P106-100 `S: 0/3 [63°C/69%]*10.27 I/s 20.0(20.0)Sol/s 55( 55.1)W clk=1455MHz mclk=4437MHz Sol/W=0.36
4>GTX 1060 6GB `S: 0/0 [54°C/64%] 0.09 I/s 0.0( 0.0)Sol/s 28( 27.8)W clk=1544MHz mclk=4363MHz Sol/W=0.00
5>GTX 1060 6GB `S: 0/1 [59°C/61%] 13.29 I/s 26.6(26.6)Sol/s 106(105.7)W clk=1974MHz mclk=4437MHz Sol/W=0.25
6>GTX 1060 6GB `S: 0/2 [60°C/66%]*12.67 I/s 21.3(21.3)Sol/s 99( 99.3)W clk=1822MHz mclk=4404MHz Sol/W=0.21
7>GTX 1060 6GB `S: 0/0 [57°C/65%] 0.00 I/s 0.0( 0.0)Sol/s 31( 30.9)W clk=1835MHz mclk=4568MHz Sol/W=0.00
8>GTX 1050 Ti `S: 0/0 [NA°C/NA%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=2081793MHz mclk=2557701MHz Sol/W=-nan
9>GTX 1050 Ti `S: 0/0 [NA°C/NA%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=2065408MHz mclk=19335178MHz Sol/W=-nan
fee.server the same, so it isn't Nicehash problem. [ 0d 0h 2m59s|09:32:10 24/08/2019] S: 0/177 231(230.8)Sol/s 908(888.9)W [fee.server]- 94ms (95.5%) (4.5%)
0>GTX 1070 Ti `S: 0/28 [64°C/55%] 21.63 I/s 43.8(43.8)Sol/s 143(139.5)W clk=1784MHz mclk=4536MHz Sol/W=0.31
1>P106-100 `S: 0/21 [65°C/62%] 12.48 I/s 25.5(25.5)Sol/s 104(100.6)W clk=1797MHz mclk=4665MHz Sol/W=0.25
2>P106-100 `S: 0/28 [64°C/67%] 10.50 I/s 20.4(20.4)Sol/s 72( 70.0)W clk=1506MHz mclk=4738MHz Sol/W=0.29
3>P106-100 `S: 0/20 [66°C/68%] 10.24 I/s 20.5(20.5)Sol/s 64( 60.7)W clk=1430MHz mclk=4437MHz Sol/W=0.34
4>GTX 1060 6GB `S: 0/21 [64°C/62%]*12.86 I/s 25.2(25.2)Sol/s 111(103.4)W clk=1873MHz mclk=4363MHz Sol/W=0.24
5>GTX 1060 6GB `S: 0/21 [64°C/62%] 13.21 I/s 26.5(26.5)Sol/s 102(105.2)W clk=1949MHz mclk=4437MHz Sol/W=0.25
6>GTX 1060 6GB `S: 0/12 [64°C/63%] 12.60 I/s 25.8(25.8)Sol/s 102( 98.4)W clk=1822MHz mclk=4404MHz Sol/W=0.26
7>GTX 1060 6GB `S: 0/15 [64°C/66%] 11.06 I/s 21.5(21.5)Sol/s 72( 73.0)W clk=1594MHz mclk=4568MHz Sol/W=0.29
8>GTX 1050 Ti `S: 0/3 [58°C/35%] 6.18 I/s 12.7(12.7)Sol/s 69( 69.0)W clk=1860MHz mclk=4058MHz Sol/W=0.18
9>GTX 1050 Ti `S: 0/8 [57°C/35%] 6.61 I/s 13.1(13.1)Sol/s 69( 69.0)W clk=1822MHz mclk=4380MHz Sol/W=0.19
[ 0d 0h 3m09s|09:32:20 24/08/2019] S: 0/177 231(230.7)Sol/s 891(887.3)W [fee.server]- 94ms (90.4%) (9.6%)
0>GTX 1070 Ti `S: 0/28 [64°C/55%] 21.63 I/s 43.7(43.7)Sol/s 142(139.7)W clk=1759MHz mclk=4536MHz Sol/W=0.31
1>P106-100 `S: 0/21 [65°C/62%] 12.48 I/s 25.4(25.4)Sol/s 97( 99.6)W clk=1784MHz mclk=4665MHz Sol/W=0.25
2>P106-100 `S: 0/28 [64°C/67%] 10.50 I/s 20.5(20.5)Sol/s 73( 70.5)W clk=1506MHz mclk=4738MHz Sol/W=0.29
3>P106-100 `S: 0/20 [66°C/68%] 10.24 I/s 20.4(20.4)Sol/s 66( 61.4)W clk=1480MHz mclk=4437MHz Sol/W=0.33
4>GTX 1060 6GB `S: 0/21 [64°C/62%] 12.86 I/s 25.1(25.1)Sol/s 107(103.4)W clk=1873MHz mclk=4363MHz Sol/W=0.24
5>GTX 1060 6GB `S: 0/21 [65°C/62%] 13.21 I/s 26.3(26.3)Sol/s 101(104.6)W clk=1949MHz mclk=4437MHz Sol/W=0.25
6>GTX 1060 6GB `S: 0/12 [65°C/63%] 12.59 I/s 25.4(25.4)Sol/s 97( 97.8)W clk=1822MHz mclk=4404MHz Sol/W=0.26
7>GTX 1060 6GB `S: 0/15 [64°C/66%] 11.06 I/s 21.7(21.7)Sol/s 70( 72.4)W clk=1594MHz mclk=4568MHz Sol/W=0.30
8>GTX 1050 Ti `S: 0/3 [58°C/35%] 6.19 I/s 12.7(12.7)Sol/s 69( 69.0)W clk=1898MHz mclk=4058MHz Sol/W=0.18
9>GTX 1050 Ti `S: 0/8 [56°C/35%] 6.61 I/s 13.1(13.1)Sol/s 69( 69.0)W clk=1822MHz mclk=4380MHz Sol/W=0.19
Reverted it back to v1.5p and voila: Number of CUDA[10.0] devices found: 10
miniZ<150,5,3>[1:1:00:7993]: Selecting GPU#0[0] GeForce GTX 1070 Ti
miniZ<150,5,3>[4:1:00:5994]: Selecting GPU#3[3] P106-100
miniZ<150,5,3>[4:1:00:5994]: Selecting GPU#1[1] P106-100
miniZ<150,5,3>[4:1:00:5994]: Selecting GPU#2[2] P106-100
miniZ<150,5,3>[4:1:00:5990]: Selecting GPU#4[4] GeForce GTX 1060 6GB
miniZ<150,5,3>[4:1:00:5990]: Selecting GPU#5[5] GeForce GTX 1060 6GB
miniZ<150,5,3>[7:1:00:3970]: Selecting GPU#8[8] GeForce GTX 1050 Ti
miniZ<150,5,3>[7:1:00:3970]: Selecting GPU#9[9] GeForce GTX 1050 Ti
miniZ<150,5,3>[4:1:00:5990]: Selecting GPU#7[7] GeForce GTX 1060 6GB
miniZ<150,5,3>[4:1:00:5990]: Selecting GPU#6[6] GeForce GTX 1060 6GB
Algo: EQ[150,5,3]
Pool#0: user[xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx]
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: oc1[8 9] oc2[0 1 2 3 4 5 6 7]
Temp. limit: [75°C]
[ 0d 0h 0m07s|09:33:32 24/08/2019] S: 3/0 98(97.9)Sol/s 587(586.5)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 108ms (100.0%) (0.0%)
0>GTX 1070 Ti `S: 0/0 [60°C/55%] 15.03 I/s 28.9(28.9)Sol/s 149(149.1)W clk=1822MHz mclk=4536MHz Sol/W=0.19
1>P106-100 `S: 0/0 [59°C/62%] 3.53 I/s 7.1( 7.1)Sol/s 32( 32.0)W clk=1582MHz mclk=4665MHz Sol/W=0.22
2>P106-100 `S: 2/0 [61°C/67%]* 5.76 I/s 12.1(12.1)Sol/s 31( 31.2)W clk=1506MHz mclk=4738MHz Sol/W=0.39
3>P106-100 `S: 1/0 [63°C/67%]* 7.04 I/s 12.2(12.2)Sol/s 66( 66.4)W clk=1506MHz mclk=4437MHz Sol/W=0.18
4>GTX 1060 6GB `S: 0/0 [58°C/62%] 7.05 I/s 15.6(15.6)Sol/s 28( 28.1)W clk=1544MHz mclk=4363MHz Sol/W=0.56
5>GTX 1060 6GB `S: 0/0 [56°C/62%] 3.74 I/s 7.0( 7.0)Sol/s 28( 28.5)W clk=1594MHz mclk=4437MHz Sol/W=0.25
6>GTX 1060 6GB `S: 0/0 [59°C/63%] 1.55 I/s 2.8( 2.8)Sol/s 43( 42.9)W clk=1721MHz mclk=4404MHz Sol/W=0.06
7>GTX 1060 6GB `S: 0/0 [62°C/64%] 3.27 I/s 8.5( 8.5)Sol/s 70( 70.4)W clk=1594MHz mclk=4568MHz Sol/W=0.12
8>GTX 1050 Ti `S: 0/0 [53°C/36%] 0.88 I/s 1.7( 1.7)Sol/s 69( 69.0)W clk=1430MHz mclk=4058MHz Sol/W=0.03
9>GTX 1050 Ti `S: 0/0 [51°C/36%] 0.88 I/s 1.5( 1.5)Sol/s 69( 69.0)W clk=1290MHz mclk=4380MHz Sol/W=0.02
[ 0d 0h 0m17s|09:33:42 24/08/2019] S: 16/0 204(204.3)Sol/s 851(851.2)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 76ms (100.0%) (0.0%)
0>GTX 1070 Ti `S: 1/0 [63°C/55%]*19.98 I/s 39.4(39.4)Sol/s 132(131.5)W clk=1759MHz mclk=4536MHz Sol/W=0.30
1>P106-100 `S: 1/0 [62°C/62%]*11.18 I/s 22.4(22.4)Sol/s 95( 95.4)W clk=1797MHz mclk=4665MHz Sol/W=0.23
2>P106-100 `S: 2/0 [63°C/67%] 9.47 I/s 20.4(20.4)Sol/s 68( 68.1)W clk=1506MHz mclk=4738MHz Sol/W=0.30
3>P106-100 `S: 2/0 [64°C/68%]* 9.44 I/s 19.3(19.3)Sol/s 68( 67.6)W clk=1506MHz mclk=4437MHz Sol/W=0.29
4>GTX 1060 6GB `S: 2/0 [63°C/61%]*11.58 I/s 22.0(22.0)Sol/s 92( 92.4)W clk=1873MHz mclk=4363MHz Sol/W=0.24
5>GTX 1060 6GB `S: 4/0 [62°C/61%]*11.88 I/s 24.6(24.6)Sol/s 96( 96.2)W clk=1949MHz mclk=4437MHz Sol/W=0.26
6>GTX 1060 6GB `S: 1/0 [62°C/63%]*12.04 I/s 24.6(24.6)Sol/s 86( 85.8)W clk=1822MHz mclk=4404MHz Sol/W=0.29
7>GTX 1060 6GB `S: 3/0 [63°C/65%]* 9.95 I/s 20.9(20.9)Sol/s 76( 76.1)W clk=1594MHz mclk=4568MHz Sol/W=0.28
8>GTX 1050 Ti `S: 0/0 [57°C/36%] 5.91 I/s 10.6(10.6)Sol/s 69( 69.0)W clk=1873MHz mclk=4058MHz Sol/W=0.15
9>GTX 1050 Ti `S: 0/0 [55°C/36%] 6.32 I/s 14.6(14.6)Sol/s 69( 69.0)W clk=1847MHz mclk=4380MHz Sol/W=0.21 |
|
|
|
|
2h4u
Newbie
Offline
Activity: 55
Merit: 0
|
|
August 24, 2019, 03:09:35 AM |
|
Looks like miniZ creates some strange trash files at segfault: ************ miniZ v1.5q ************
Number of CUDA[10.0] devices found: 8
miniZ<150,5,3>[4:1:00:5994]: Selecting GPU#0[0] P106-100
miniZ<150,5,3>[4:1:00:5994]: Selecting GPU#1[1] P106-100
miniZ<150,5,3>[4:1:00:5994]: Selecting GPU#2[2] P106-100
miniZ<150,5,3>[4:1:00:5994]: Selecting GPU#3[3] P106-100
/hive/miners/miniz/h-run.sh: line 20: 12793 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 Files: root@c3:/# cd /hive/miners/miniz/1.5p-cuda100
root@c3:/hive/miners/miniz/1.5p-cuda100# ls -al
total 68664
drwxr-xr-x 2 user user 4096 Aug 23 16:03 .
drwxr-xr-x 3 user user 4096 Aug 15 16:13 ..
-rw-r--r-- 1 user user 189 Aug 15 14:21 control
-rw-r--r-- 1 root root 54 Aug 23 16:03 ??f??V
-rw-r--r-- 1 root root 108 Aug 20 19:36 (l?Y-?
-rwxr-xr-x 1 user user 70276968 Aug 15 14:21 miniZ
lrwxrwxrwx 1 user user 33 Aug 15 14:21 miniz.conf -> /run/hive/miners/miniz/miniz.conf
-rw-r--r-- 1 root root 56 Aug 20 19:36 `????U
-rw-r--r-- 1 root root 54 Aug 19 20:39 ??z?4V
root@c3:/hive/miners/miniz/1.5p-cuda100# cat /hive/miners/miniz/1.5p-cuda100/`.���U
[INFO ] Disconnecting from beamv2.eu-new.nicehash.com
root@c3:/hive/miners/miniz/1.5p-cuda100#cat /hive/miners/miniz/1.5p-cuda100/(l�Y-.
[FATAL ] CUDA: failed to alloc 2801 MB for main data
[FATAL ] CUDA: failed to alloc 2801 MB for main data
|
|
|
|
|
2h4u
Newbie
Offline
Activity: 55
Merit: 0
|
|
August 24, 2019, 03:23:08 AM |
|
* Fixed slow start for some GPUs/rigs. No, it didn't: [ 0d 0h 1m38s|10:21:52 24/08/2019] S: 13/0 40(40.2)Sol/s 62( 62.5)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 97ms (100.0%) (0.0%)
0>GTX 1060 3GB `S: 9/0 [56°C/76%] 10.25 I/s 20.3(20.3)Sol/s 31( 31.4)W clk=1657MHz mclk=4353MHz Sol/W=0.65
1>GTX 1060 3GB `S: 4/0 [59°C/63%]*11.19 I/s 22.8(22.8)Sol/s 31( 31.1)W clk=1657MHz mclk=4544MHz Sol/W=0.73
2>GTX 1060 3GB `S: 0/0 [NA°C/NA%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=10470402MHz mclk=3604486MHz Sol/W=-nan
3>GTX 1060 3GB `S: 0/0 [0°C/ 0%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=11MHz mclk=-1MHz Sol/W=-nan
4>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
5>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=23530508MHz Sol/W=-nan
6>GTX 1060 3GB `S: 0/0 [NA°C/NA%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=1885186MHz mclk=558301976MHz Sol/W=-nan
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=2094112MHz mclk=13103122MHz Sol/W=-nan
8>GTX 1060 3GB `S: 0/0 [NA°C/NA%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=4162560MHz mclk=5701635MHz Sol/W=-nan
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=1533281152MHz mclk=60227587MHz Sol/W=-nan
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=69190656MHz mclk=267845642MHz Sol/W=-nan
11>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 |
|
|
|
|
2h4u
Newbie
Offline
Activity: 55
Merit: 0
|
|
August 24, 2019, 03:43:50 AM |
|
1.5q has a LOT of segmentation faults. 5 segfaults per 1 good start. Reverted back to 1.5p. ************ 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 |
|
|
|
|
MineOrDie
Jr. Member
Offline
Activity: 75
Merit: 1
|
|
August 24, 2019, 07:40:48 AM |
|
miniZ.exe --url wallet.RIG2@stratum.zel.cash:2001 --par=125,4 --extra --latency --shares-detail --gpu-line --telemetry=0 --f11=1 --oc1 --mode=10 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 |
|
|
|
|
invizion
Newbie
Offline
Activity: 44
Merit: 0
|
|
August 24, 2019, 08: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: [ERROR ] Cannot connect to any mining pool!!! |
|
|
|
|
12miners
Newbie
Offline
Activity: 14
Merit: 0
|
|
August 24, 2019, 09:12:28 AM |
|
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: ./miniZ --par=192,7 --url=YourWalletAddress.worker@eu.voidr.net:5001 --url=YourWalletAddress.worker@mine-yec-na.equipool.1ds.us: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.pngwhen 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. :loop
.\miniZ.exe --url=ssl://my_wallet.worker@beam.f2pool.com: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!  |
|
|
|
|
MineOrDie
Jr. Member
Offline
Activity: 75
Merit: 1
|
|
August 24, 2019, 11:05:35 AM |
|
Hello devs i found a bug with failover pools in config.  You misspelled aionmine.org. That's the reason. |
|
|
|
|
12miners
Newbie
Offline
Activity: 14
Merit: 0
|
|
August 24, 2019, 12:32:19 PM |
|
You misspelled aionmine.org. That's the reason. no, this is specifically as an example, to show that the backup pools will not work |
|
|
|
|
|
miniZ (OP)
|
|
August 24, 2019, 01:15:47 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 --url=xxx@beamv2.eu-new.nicehash.com: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 |
miniZ is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter |
|
|
|
miniZ (OP)
|
|
August 24, 2019, 01:17:24 PM |
|
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 is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter |
|
|
MineOrDie
Jr. Member
Offline
Activity: 75
Merit: 1
|
|
August 24, 2019, 05:57:44 PM |
|
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 (OP)
|
|
August 24, 2019, 09:20:44 PM |
|
Looks like miniZ creates some strange trash files at segfault:
* Fixed slow start for some GPUs/rigs. No, it didn't: 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 |
miniZ is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter |
|
|
|
miniZ (OP)
|
|
August 24, 2019, 09:22:58 PM |
|
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: [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 is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter |
|
|
|
miniZ (OP)
|
|
August 24, 2019, 09:27:02 PM |
|
Hello devs i found a bug with failover pools in config. https://i.ibb.co/sJ2CMqS/img-2019-08-24-12-05-52.pngwhen 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. :loop
.\miniZ.exe --url=ssl://my_wallet.worker@beam.f2pool.com: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! 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 is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter |
|
|
|
