Pages:
Author

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

member
Activity: 690
Merit: 17
The new version v1.9z2 doesn't find any shares for 144,5 + LTZ on ZergPool (Windows 10, 6x GTX1070).

Quote
miniZ.exe -cd 0 1 2 3 4 5 [email protected]:2146 -p ID=wrk1,c=BTC,mc=LTZ --worker=wrk1 --pers=ZcashPoW --gpu-line --extra --latency --par=144,5

It all looks good, and the miner mines away, but shares, accepted and rejected, stay at 0 always and the miner is not detected at the pool. Also the hashrate is much much too high at the beginning at 830 for one GTX1070 and decreases down to 60 only slowly, over time.

For reference: all other miners (Gminer, MiniZ v1.8z3, ..) in fact do find shares with the equivalent parameter configuration.

Hi rainbowminer,

We tested your command line and it is working well.
Have you tried the new v1.9z3 version already?

Regarding 96,5, there is an issue affecting the windows version. The next miniZ release will have a fix for the issue.

Cheers
jr. member
Activity: 312
Merit: 2
Thank you... i try it tomorrow and i post a feedback...

Have a nice day Miners Wink

Uh, there is a mistake in setting card mode in my config, it should be --mode=03, not --mode 3. Since wrong settings are ignored you will probably run mode 8 for flux any way, which is the best(same as setting --oc2 I think)
newbie
Activity: 2
Merit: 0
Hi Divinity666,

Do you already mining FLUX with miniZ v1.9zxx ?
I have 10 1080ti and when i launche miniZ that reboot my linux Rig.
I have no OC activated, only fan speed 100%.
However all my GPU work fine with T-Rex for exemple.
If you can past your miniZ command line that would be great.

Thank You.

:loop
.\miniZ.exe [email protected]:2033  -p xxx --par=125,4 --pers=auto --mode=3 --mt=auto --telemetry=0.0.0.0:3333 --show-shares --stat-int=30 --log --log-period=30 --server-share --localtime=13 --avg0=600 --avg1=999999

timeout /t 1
goto loop

What is the OC for the 3070 cards ?

Well, OC is basically shown in the log except gpu voltage which is individual for each card. I run them on minimum possible voltage I can get them to work with Afterburner. So u find maximum stable clock for given minimum voltage... And downclocking memory drops powerdraw a bit as well, while not going to low almost doesn't drop h\r at all.

Thank you... i try it tomorrow and i post a feedback...

Have a nice day Miners Wink
jr. member
Activity: 312
Merit: 2
Hi Divinity666,

Do you already mining FLUX with miniZ v1.9zxx ?
I have 10 1080ti and when i launche miniZ that reboot my linux Rig.
I have no OC activated, only fan speed 100%.
However all my GPU work fine with T-Rex for exemple.
If you can past your miniZ command line that would be great.

Thank You.

:loop
.\miniZ.exe [email protected]:2033  -p xxx --par=125,4 --pers=auto --mode=3 --mt=auto --telemetry=0.0.0.0:3333 --show-shares --stat-int=30 --log --log-period=30 --server-share --localtime=13 --avg0=600 --avg1=999999

timeout /t 1
goto loop

What is the OC for the 3070 cards ?

Well, OC is basically shown in the log except gpu voltage which is individual for each card. I run them on minimum possible voltage I can get them to work with Afterburner. So u find maximum stable clock for given minimum voltage... And downclocking memory drops powerdraw a bit as well, while not going to low almost doesn't drop h\r at all.
newbie
Activity: 15
Merit: 0
newbie
Activity: 2
Merit: 0
BUG in 1.9z2.
In 1.8z3 all OK!

I have rig of 4x1080ti+2x1070 - no such thing with latest version of the miner...

Hi Divinity666,

Do you already mining FLUX with miniZ v1.9zxx ?
I have 10 1080ti and when i launche miniZ that reboot my linux Rig.
I have no OC activated, only fan speed 100%.
However all my GPU work fine with T-Rex for exemple.
If you can past your miniZ command line that would be great.

Thank You.
jr. member
Activity: 312
Merit: 2
BUG in 1.9z2.
In 1.8z3 all OK!

I have rig of 4x1080ti+2x1070 - no such thing with latest version of the miner...
full member
Activity: 1199
Merit: 209
BUG in 1.9z2.
In 1.8z3 all OK!

Code:
************ miniZ v1.9z2 ************
Number of miniZ CUDA>=[8.0] using driver CUDA[11.60] devices found: 4
miniZ: Excluding GPU#0 NVIDIA GeForce RTX 3060 v2
miniZ: Excluding GPU#3 NVIDIA GeForce RTX 2070 SUPER
Driver:         512.15
Algo:           EQ[144,5] [smart-pers]
Pool#0:         user[*****************************]
                server[zhash.auto.nicehash.com] port[9200] ssl[no] pers[auto]
Telemetry:      [http://localhost:4003]
Temp. limit:    [90 C]
[INFO   ] Mining fee set to 2.00%
miniZ<144,5>[10:0:00.0: 6798]: Selecting GPU#2[1] Gigabyte GeForce GTX 1070
miniZ<144,5>[10:0:00.0: 6798]: Selecting GPU#1[0] Nvidia GeForce GTX 1070
[ 0d 0h 0m02s] 1690(1690.2)Sol/s  70( 70.3)W
 1>GTX 1070      ` 100% [40 C/33%] 430.11 I/s 858.06(858.06)Sol/s  33( 33.2)W clk=1653MHz mclk=4006MHz Sol/W=25.818
 2>GTX 1070      ` 100% [39 C/33%] 417.12 I/s 832.14(832.14)Sol/s  37( 37.1)W clk=1427MHz mclk=4006MHz Sol/W=22.427
[ 0d 0h 0m10s] 1721(1720.7)Sol/s 146(146.4)W
 1>GTX 1070      ` 100% [47 C/35%] 433.30 I/s 864.42(864.42)Sol/s  74( 73.7)W clk=1944MHz mclk=3802MHz Sol/W=11.733
 2>GTX 1070      ` 100% [44 C/34%] 429.72 I/s 856.32(856.32)Sol/s  73( 72.8)W clk=1926MHz mclk=3802MHz Sol/W=11.770
[ 0d 0h 0m20s] 1654(1654.3)Sol/s 143(143.4)W
 1>GTX 1070      ` 100% [49 C/38%] 400.37 I/s 830.70(830.70)Sol/s  72( 72.2)W clk=1944MHz mclk=3802MHz Sol/W=11.499
 2>GTX 1070      ` 100% [45 C/36%] 396.67 I/s 823.55(823.55)Sol/s  71( 71.2)W clk=1927MHz mclk=3802MHz Sol/W=11.572
[ 0d 0h 0m30s] 1654(1654.3)Sol/s 147(147.4)W
 1>GTX 1070      ` 100% [51 C/39%] 406.70 I/s 830.70(830.70)Sol/s  74( 74.3)W clk=1943MHz mclk=3802MHz Sol/W=11.174
 2>GTX 1070      ` 100% [46 C/37%] 403.83 I/s 823.55(823.55)Sol/s  73( 73.0)W clk=1926MHz mclk=3802MHz Sol/W=11.275
newbie
Activity: 1
Merit: 0
Hi I am getting an error while trying the latest MiniZ on Hive OS using AMD rx 5700xt and rx 5600xt.

the error is [FATAL] OpenCL Kernel2: CL_INVALID_WORK_GROUP_SIZE

newbie
Activity: 1
Merit: 0
Anyone knows how to capture status of the running miniZ.  I know you can do it via browser http://minerIP:20000, but I'd like to send email every once in a while with status, and miner is not on public IP.
Using wget or curl in bash doesn't really work with javascript.  so you only capture first empty page withouth refresh.
I know that NBMiner has specific address like minerIP:22333/api/v1/status which will give you Json file with the current info about mining.
Does MiniZ has a similar thing?
Thanks
member
Activity: 325
Merit: 42
I getting abnormal hashrate with my 1070  card other 1060 6gb working good tho any fix?

Which algo, pool?
newbie
Activity: 77
Merit: 0
I getting abnormal hashrate with my 1070  card other 1060 6gb working good tho any fix?
jr. member
Activity: 312
Merit: 2
Seems like miner didn't switch from devfee and was mining it for 10 minutes, wtf? Had to stop it and restart

Quote
[ 4d 5h20m00s|23:22:36] 271(270.1)Sol/s 602(602.2)W (98.1%) (1.9%)
 0>RTX 3080      S:8582/0 [58 C/55%]*44.50 I/s 89.12(88.81)Sol/s 228(229.5)W clk=1649MHz mclk=8243MHz Sol/W=0.387
 1>RTX 3070      S:5723/0 [55 C/54%] 30.15 I/s 60.15(60.25)Sol/s 118(118.6)W clk=1631MHz mclk=6889MHz Sol/W=0.508
 2>RTX 3070      S:5910/0 [55 C/31%]*30.75 I/s 61.75(61.48)Sol/s 133(132.7)W clk=1664MHz mclk=6889MHz Sol/W=0.463
 3>RTX 3070      S:5646/0 [56 C/32%]*29.77 I/s 59.34(59.53)Sol/s 123(123.0)W clk=1604MHz mclk=6889MHz Sol/W=0.484
[ 4d 5h21m00s|23:23:36] 269(270.1)Sol/s 603(602.2)W (98.1%) (1.9%)
 0>RTX 3080      S:8582/0 [58 C/55%] 44.50 I/s 88.59(88.81)Sol/s 228(229.5)W clk=1649MHz mclk=8243MHz Sol/W=0.387
 1>RTX 3070      S:5725/0 [55 C/54%]*30.15 I/s 60.01(60.25)Sol/s 118(118.6)W clk=1632MHz mclk=6889MHz Sol/W=0.508
 2>RTX 3070      S:5910/0 [55 C/31%] 30.75 I/s 61.60(61.48)Sol/s 133(132.7)W clk=1664MHz mclk=6889MHz Sol/W=0.463
 3>RTX 3070      S:5646/0 [56 C/32%] 29.77 I/s 59.69(59.54)Sol/s 124(123.0)W clk=1604MHz mclk=6889MHz Sol/W=0.484
[ 4d 5h22m00s|23:24:36] 271(270.1)Sol/s 602(602.2)W (98.1%) (1.9%)
 0>RTX 3080      S:8582/0 [58 C/55%] 44.50 I/s 88.48(88.81)Sol/s 228(229.5)W clk=1649MHz mclk=8243MHz Sol/W=0.387
 1>RTX 3070      S:5726/0 [55 C/54%]*30.15 I/s 60.41(60.26)Sol/s 118(118.6)W clk=1631MHz mclk=6889MHz Sol/W=0.508
 2>RTX 3070      S:5910/0 [55 C/30%] 30.75 I/s 61.56(61.48)Sol/s 132(132.7)W clk=1664MHz mclk=6889MHz Sol/W=0.463
 3>RTX 3070      S:5648/0 [56 C/32%]*29.77 I/s 59.73(59.54)Sol/s 123(123.0)W clk=1604MHz mclk=6889MHz Sol/W=0.484
[ 4d 5h23m00s|23:25:36] 271(270.1)Sol/s 602(602.2)W (98.1%) (1.9%)
 0>RTX 3080      S:8582/0 [58 C/55%] 44.50 I/s 88.87(88.81)Sol/s 228(229.5)W clk=1649MHz mclk=8243MHz Sol/W=0.387
 1>RTX 3070      S:5726/0 [55 C/54%] 30.15 I/s 60.31(60.26)Sol/s 118(118.6)W clk=1630MHz mclk=6889MHz Sol/W=0.508
 2>RTX 3070      S:5910/0 [55 C/31%] 30.75 I/s 61.64(61.48)Sol/s 132(132.7)W clk=1664MHz mclk=6889MHz Sol/W=0.463
 3>RTX 3070      S:5648/0 [56 C/32%] 29.77 I/s 59.79(59.54)Sol/s 123(123.0)W clk=1604MHz mclk=6889MHz Sol/W=0.484
[ 4d 5h24m00s|23:26:36] 272(270.1)Sol/s 602(602.2)W (98.1%) (1.9%)
 0>RTX 3080      S:8582/0 [58 C/55%] 44.50 I/s 88.95(88.81)Sol/s 228(229.5)W clk=1649MHz mclk=8243MHz Sol/W=0.387
 1>RTX 3070      S:5726/0 [55 C/54%] 30.15 I/s 60.65(60.26)Sol/s 118(118.6)W clk=1631MHz mclk=6889MHz Sol/W=0.508
 2>RTX 3070      S:5910/0 [55 C/31%] 30.75 I/s 61.69(61.48)Sol/s 132(132.7)W clk=1664MHz mclk=6889MHz Sol/W=0.463
 3>RTX 3070      S:5648/0 [56 C/32%] 29.77 I/s 59.76(59.54)Sol/s 124(123.0)W clk=1604MHz mclk=6889MHz Sol/W=0.484
[ 4d 5h25m00s|23:27:36] 271(270.1)Sol/s 602(602.3)W (98.1%) (1.9%)
 0>RTX 3080      S:8582/0 [58 C/55%] 44.50 I/s 88.87(88.81)Sol/s 228(229.5)W clk=1649MHz mclk=8243MHz Sol/W=0.387
 1>RTX 3070      S:5726/0 [55 C/54%] 30.15 I/s 60.89(60.26)Sol/s 118(118.6)W clk=1631MHz mclk=6889MHz Sol/W=0.508
 2>RTX 3070      S:5910/0 [55 C/30%] 30.75 I/s 61.68(61.48)Sol/s 133(132.7)W clk=1664MHz mclk=6889MHz Sol/W=0.463
 3>RTX 3070      S:5648/0 [56 C/32%] 29.77 I/s 59.73(59.54)Sol/s 123(123.0)W clk=1604MHz mclk=6889MHz Sol/W=0.484
[ 4d 5h26m00s|23:28:36] 272(270.1)Sol/s 602(602.3)W (98.0%) (2.0%)
 0>RTX 3080      S:8582/0 [58 C/55%] 44.50 I/s 88.81(88.81)Sol/s 228(229.5)W clk=1649MHz mclk=8243MHz Sol/W=0.387
 1>RTX 3070      S:5726/0 [55 C/54%] 30.15 I/s 60.53(60.26)Sol/s 118(118.6)W clk=1631MHz mclk=6889MHz Sol/W=0.508
 2>RTX 3070      S:5910/0 [55 C/31%] 30.75 I/s 61.75(61.48)Sol/s 133(132.7)W clk=1664MHz mclk=6889MHz Sol/W=0.463
 3>RTX 3070      S:5648/0 [56 C/32%] 29.77 I/s 59.96(59.54)Sol/s 123(123.0)W clk=1604MHz mclk=6889MHz Sol/W=0.484
[ 4d 5h27m00s|23:29:36] 272(270.1)Sol/s 603(602.3)W (98.0%) (2.0%)
 0>RTX 3080      S:8582/0 [58 C/55%] 44.50 I/s 88.72(88.81)Sol/s 228(229.5)W clk=1649MHz mclk=8243MHz Sol/W=0.387
 1>RTX 3070      S:5726/0 [55 C/54%] 30.15 I/s 60.65(60.26)Sol/s 119(118.6)W clk=1631MHz mclk=6889MHz Sol/W=0.508
 2>RTX 3070      S:5910/0 [55 C/31%] 30.75 I/s 62.07(61.48)Sol/s 133(132.7)W clk=1664MHz mclk=6889MHz Sol/W=0.463
 3>RTX 3070      S:5648/0 [56 C/32%] 29.77 I/s 59.73(59.54)Sol/s 123(123.0)W clk=1604MHz mclk=6889MHz Sol/W=0.484
[ 4d 5h28m00s|23:30:36] 271(270.1)Sol/s 602(602.3)W (98.0%) (2.0%)
 0>RTX 3080      S:8582/0 [58 C/55%] 44.50 I/s 88.96(88.81)Sol/s 228(229.5)W clk=1649MHz mclk=8243MHz Sol/W=0.387
 1>RTX 3070      S:5726/0 [55 C/54%] 30.15 I/s 60.53(60.26)Sol/s 118(118.6)W clk=1631MHz mclk=6889MHz Sol/W=0.508
 2>RTX 3070      S:5910/0 [55 C/31%] 30.75 I/s 61.97(61.48)Sol/s 133(132.7)W clk=1664MHz mclk=6889MHz Sol/W=0.463
 3>RTX 3070      S:5648/0 [56 C/32%] 29.77 I/s 59.64(59.54)Sol/s 123(123.0)W clk=1604MHz mclk=6889MHz Sol/W=0.484
[ 4d 5h29m00s|23:31:36] 271(270.1)Sol/s 602(602.3)W (98.0%) (2.0%)
 0>RTX 3080      S:8582/0 [58 C/55%] 44.50 I/s 88.81(88.81)Sol/s 228(229.5)W clk=1649MHz mclk=8243MHz Sol/W=0.387
 1>RTX 3070      S:5726/0 [55 C/54%] 30.15 I/s 60.65(60.26)Sol/s 118(118.6)W clk=1631MHz mclk=6889MHz Sol/W=0.508
 2>RTX 3070      S:5910/0 [55 C/31%] 30.75 I/s 62.13(61.48)Sol/s 133(132.7)W clk=1664MHz mclk=6889MHz Sol/W=0.463
 3>RTX 3070      S:5648/0 [56 C/32%] 29.77 I/s 59.71(59.54)Sol/s 123(123.0)W clk=1604MHz mclk=6889MHz Sol/W=0.484
[ 4d 5h30m00s|23:32:36] 271(270.1)Sol/s 602(602.3)W (98.0%) (2.0%)
 0>RTX 3080      S:8582/0 [58 C/55%] 44.50 I/s 88.43(88.81)Sol/s 228(229.5)W clk=1649MHz mclk=8243MHz Sol/W=0.387
 1>RTX 3070      S:5726/0 [55 C/54%] 30.15 I/s 60.96(60.26)Sol/s 118(118.6)W clk=1631MHz mclk=6889MHz Sol/W=0.508
 2>RTX 3070      S:5910/0 [55 C/31%] 30.75 I/s 61.89(61.48)Sol/s 133(132.7)W clk=1664MHz mclk=6889MHz Sol/W=0.463
 3>RTX 3070      S:5648/0 [56 C/32%] 29.77 I/s 59.67(59.54)Sol/s 123(123.0)W clk=1604MHz mclk=6889MHz Sol/W=0.484
[ 4d 5h31m00s|23:33:36] 269(270.1)Sol/s 602(602.3)W (98.0%) (2.0%)
 0>RTX 3080      S:8582/0 [58 C/55%] 44.50 I/s 88.45(88.81)Sol/s 228(229.4)W clk=1649MHz mclk=8243MHz Sol/W=0.387
 1>RTX 3070      S:5726/0 [55 C/54%] 30.15 I/s 60.73(60.26)Sol/s 119(118.6)W clk=1631MHz mclk=6889MHz Sol/W=0.508
 2>RTX 3070      S:5910/0 [55 C/31%] 30.75 I/s 61.72(61.48)Sol/s 133(132.7)W clk=1664MHz mclk=6889MHz Sol/W=0.463
 3>RTX 3070      S:5648/0 [56 C/32%] 29.77 I/s 59.39(59.54)Sol/s 123(123.0)W clk=1604MHz mclk=6889MHz Sol/W=0.484
[ 4d 5h32m00s|23:34:36] 269(270.1)Sol/s 602(602.3)W (97.9%) (2.1%)
 0>RTX 3080      S:8582/0 [58 C/55%] 44.50 I/s 88.66(88.81)Sol/s 228(229.4)W clk=1649MHz mclk=8243MHz Sol/W=0.387
 1>RTX 3070      S:5726/0 [55 C/54%] 30.15 I/s 60.55(60.26)Sol/s 119(118.6)W clk=1632MHz mclk=6889MHz Sol/W=0.508
 2>RTX 3070      S:5910/0 [55 C/30%] 30.75 I/s 61.52(61.48)Sol/s 133(132.7)W clk=1664MHz mclk=6889MHz Sol/W=0.463
 3>RTX 3070      S:5648/0 [56 C/32%] 29.77 I/s 59.66(59.54)Sol/s 123(123.0)W clk=1604MHz mclk=6889MHz Sol/W=0.484
[ 4d 5h33m00s|23:35:36] 270(270.1)Sol/s 603(602.4)W (97.9%) (2.1%)
 0>RTX 3080      S:8582/0 [58 C/55%] 44.50 I/s 88.88(88.81)Sol/s 228(229.4)W clk=1649MHz mclk=8243MHz Sol/W=0.387
 1>RTX 3070      S:5726/0 [55 C/54%] 30.15 I/s 60.49(60.26)Sol/s 119(118.6)W clk=1631MHz mclk=6889MHz Sol/W=0.508
 2>RTX 3070      S:5910/0 [55 C/31%] 30.76 I/s 61.75(61.48)Sol/s 133(132.7)W clk=1664MHz mclk=6889MHz Sol/W=0.463
 3>RTX 3070      S:5648/0 [56 C/32%] 29.77 I/s 59.42(59.54)Sol/s 123(123.0)W clk=1604MHz mclk=6889MHz Sol/W=0.484
[ 4d 5h34m00s|23:36:36] 272(270.1)Sol/s 603(602.4)W (97.9%) (2.1%)
 0>RTX 3080      S:8582/0 [58 C/55%] 44.51 I/s 88.89(88.81)Sol/s 228(229.4)W clk=1649MHz mclk=8243MHz Sol/W=0.387
 1>RTX 3070      S:5726/0 [55 C/54%] 30.16 I/s 60.66(60.26)Sol/s 119(118.6)W clk=1631MHz mclk=6889MHz Sol/W=0.508
 2>RTX 3070      S:5910/0 [55 C/31%] 30.76 I/s 61.78(61.48)Sol/s 133(132.7)W clk=1664MHz mclk=6889MHz Sol/W=0.463
 3>RTX 3070      S:5648/0 [56 C/32%] 29.78 I/s 59.54(59.54)Sol/s 123(123.0)W clk=1604MHz mclk=6889MHz Sol/W=0.484
[ 4d 5h35m00s|23:37:36] 272(270.1)Sol/s 603(602.4)W (97.9%) (2.1%)
 0>RTX 3080      S:8582/0 [58 C/55%] 44.52 I/s 89.01(88.81)Sol/s 228(229.4)W clk=1649MHz mclk=8243MHz Sol/W=0.387
 1>RTX 3070      S:5726/0 [55 C/53%] 30.17 I/s 60.66(60.26)Sol/s 119(118.6)W clk=1632MHz mclk=6889MHz Sol/W=0.508
 2>RTX 3070      S:5910/0 [55 C/31%] 30.77 I/s 61.78(61.48)Sol/s 133(132.7)W clk=1664MHz mclk=6889MHz Sol/W=0.463
 3>RTX 3070      S:5648/0 [56 C/32%] 29.79 I/s 59.79(59.54)Sol/s 123(123.0)W clk=1604MHz mclk=6889MHz Sol/W=0.484
************ miniZ v1.9z2 ************
jr. member
Activity: 95
Merit: 2
The new version v1.9z2 doesn't find any shares for 144,5 + LTZ on ZergPool (Windows 10, 6x GTX1070).

Quote
miniZ.exe -cd 0 1 2 3 4 5 [email protected]:2146 -p ID=wrk1,c=BTC,mc=LTZ --worker=wrk1 --pers=ZcashPoW --gpu-line --extra --latency --par=144,5

It all looks good, and the miner mines away, but shares, accepted and rejected, stay at 0 always and the miner is not detected at the pool. Also the hashrate is much much too high at the beginning at 830 for one GTX1070 and decreases down to 60 only slowly, over time.

For reference: all other miners (Gminer for example) in fact do find shares with the equivalent parameter configuration.



Same problem for 96,5 on Zpool - but this time it shows "bad shares". If I use the former MiniZ version, all is good, shares found and ok.
jr. member
Activity: 95
Merit: 2
The new version v1.9z2 doesn't find any shares for 144,5 + LTZ on ZergPool (Windows 10, 6x GTX1070).

Quote
miniZ.exe -cd 0 1 2 3 4 5 [email protected]:2146 -p ID=wrk1,c=BTC,mc=LTZ --worker=wrk1 --pers=ZcashPoW --gpu-line --extra --latency --par=144,5

It all looks good, and the miner mines away, but shares, accepted and rejected, stay at 0 always and the miner is not detected at the pool. Also the hashrate is much much too high at the beginning at 830 for one GTX1070 and decreases down to 60 only slowly, over time.

For reference: all other miners (Gminer, MiniZ v1.8z3, ..) in fact do find shares with the equivalent parameter configuration.
jr. member
Activity: 312
Merit: 2
Cheers


Yes, thanks, it was wrong algo settings indeed.

ps. on RTX 3080\3070 there is also like .5 sol\s increasement on Zelhash with latest release  Grin
newbie
Activity: 8
Merit: 1
I already tested miniz 1.9z2 now. hashrate gets increased up to 5 sol (from 58/59 sol to 63/64/65). any improvement is welcome. thank you
member
Activity: 690
Merit: 17

Thanks for the replies! I have solved it by now, nothing wrong with your miner, maybe it was a little bit more sensitive. But it got worse and affected other algos like ETH, was a faulty PCIe power cable. When I replaced it, your miner worked fine!
Hi iRonNuke,
Thanks for letting us know.
Cheers
member
Activity: 690
Merit: 17

It fixed card's naming, yes, but telemetry may still stop working after a wile and then all of a sudden it will fix itself and start working again....

Why won't it mine zano?

Quote
Number of miniZ CUDA>=[8.0] using driver CUDA[11.40] devices found: 1
Number of OpenCL[] devices found: 0
[WARNING] GPU[0]: NVIDIA GeForce GTX 1080 Ti does not have oc1 for this algo.
Driver:      471.11
Algo:      EQ[kawpow] [smart-pers]
Pool#0:    user[iZ2CFBHEsbjPYCWHns75LFT5NwNLc2i9hPTG1SwJjonyBnBUGCtdCdpKwBbo6KdZgH1Azg9vNcyLoBXBLEaz3HADLho9Qm6UAo11UmDDANCg.test]
      server[zano.luckypool.io] port[8877] ssl[no] pers[rAVENCOINKAWPOW]
Telemetry:   [http://localhost:3333]
Logging::    file[miniZ.log] period[30] delay[0]
Optimisation:   oc1[0]
Temp. limit:   [90 C]
[INFO   ] Mining fee set to 1.00%
miniZ[00:0:00.0: 9326]: Selecting GPU#0[0] MSI GeForce GTX 1080 Ti
[ERROR  ] invalid method (rAVENCOINKAWPOW)
[ERROR  ] Pool:zano.luckypool.io - worker not authorized: iZ2CFBHEsbjPYCWHns75LFT5NwNLc2i9hPTG1SwJjonyBnBUGCtdCdpKwBbo6KdZgH1Azg9vNcyLoBX BLEaz3HADLho9Qm6UAo11UmDDANCg.test
[ERROR  ] invalid method (rAVENCOINKAWPOW)
[ERROR  ] Pool:zano.luckypool.io - worker not authorized: iZ2CFBHEsbjPYCWHns75LFT5NwNLc2i9hPTG1SwJjonyBnBUGCtdCdpKwBbo6KdZgH1Azg9vNcyLoBX BLEaz3HADLho9Qm6UAo11UmDDANCg.test

And can this miner mine firo? I tried mining on 2miners and it connects ok and card is actually mining, but it gets 100% bad shares

Hi Divinity666,
We'll continue to have a look at telemetry. We didn't manage to replicate this behavior.
Regarding zano mining, it seems that miniZ started mining the wrong algo. Normally, you do not need to write --par=ProgPowZ or --pers=zano.
You do not need to specify the algo for this pool. Check the command line it looks that there is the wrong par or pers was specified.
For firo, maybe the same happened. We find no issue with mining firo to 2miners. To mine Firo on 2miners, you do not need to specify --par=ProgPow or --pers=firo. Please check also the wallet. Make sure you set a Firo wallet.
Let us know how it goes.
Cheers
newbie
Activity: 8
Merit: 1
hello thanks for adding amd to hiveos Smiley now I can run it. but 1.9z2 not yet out on hiveos. and how is the sol/s on 6800xt now on 1.9z2? previously around 58-59 sol
and please add beamhash3 to amd gpus, thank you Smiley
Pages:
Jump to: