Divinity666
Jr. Member
Offline
Activity: 312
Merit: 2
|
|
September 30, 2022, 07:21:41 PM |
|
Thank you... i try it tomorrow and i post a feedback... Have a nice day Miners 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)
|
|
|
|
|
|
The network tries to produce one block per 10 minutes. It does this by automatically adjusting how difficult it is to produce blocks.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
miniZ (OP)
|
|
October 07, 2022, 06:54:18 PM |
|
The new version v1.9z2 doesn't find any shares for 144,5 + LTZ on ZergPool (Windows 10, 6x GTX1070). miniZ.exe -cd 0 1 2 3 4 5 --url=myBTCwalletaddress@equihash144.mine.zergpool.com: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
|
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)
|
|
October 07, 2022, 06:56:04 PM |
|
Seems like miner didn't switch from devfee and was mining it for 10 minutes, wtf? Had to stop it and restart [ 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 ************ Hi Divinity666, Thanks for the message. This can happen once and a while, if the miner was mining for long time for the user. You can see that the %s are ok, possibly it was 1.9% for the fee for long time. In any case we had a look at it, and although found no issue with this we added a limit to time mining for the fee without interruption. It will check more often when it is time to change for the user/fee. 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)
|
|
October 07, 2022, 06:57:36 PM |
|
I getting abnormal hashrate with my 1070 card other 1060 6gb working good tho any fix?
Hi Dragstar, Thanks for the feedback. Could you elaborate on which algo, maybe also which pool and OS? Could you test the new version v1.9z3 and see if the issue persists? 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)
|
|
October 07, 2022, 06:59:25 PM |
|
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 Hi DaMyna, We have some kind of standard json api. You can open the json api in http://localhost:20000/getstatIn linux you can do curl --silent rig2:20000 -X '{"id":"0", "method":"getstat"}'
Or just curl --silent http://localhost:20000/getstat
Let us know if this was useful. 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)
|
|
October 07, 2022, 07:00:47 PM |
|
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
Hi PrimusPilus, Could you test the new version v1.9z3 and see if the issue persists? If you still get the same error, could you try mining with only the 5700XT, does it work? (You can use -cd option to select gpus.) And paste here the output of running: ./miniZ -ci Thanks for the feedback. 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)
|
|
October 07, 2022, 07:02:02 PM |
|
BUG in 1.9z2. In 1.8z3 all OK! ************ 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
Hi angelbbs, Have you tried mining without OCs? Does it work? Could you test the new version v1.9z3 and see if the issue persists? Thanks! 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)
|
|
October 07, 2022, 07:02:57 PM |
|
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. Hi MrAlgo, Could you test the new version v1.9z3 and see if the issue persists? Could you check if your power supply is enough for the system power demands? If you try running miniZ with just a couple of GPUs does it work? Also, it is good to check your OCs too. Let us know how it goes! 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)
|
|
October 07, 2022, 07:07:52 PM |
|
What is the OC for the 3070 cards ?
Hi pit55, For Flux mining, with our 3070Ti on Linux, we use core clock = +240; memory clock = 0; PL = 215 W Maybe this can help as a reference for your 3070s. Make small increases/decreases at a time. 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)
|
|
October 07, 2022, 07:08:49 PM |
|
Thank you... i try it tomorrow and i post a feedback... Have a nice day Miners 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) Hi Divinity666, MrAlgo, We expect --mode=03 and --mode 3 to work the same way Thank you for sharing your settings/ideas here. Let us know how it goes. 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)
|
|
October 07, 2022, 07:16:59 PM |
|
Hi everyone, A new miniZ version v1.9z3 is out with new options for core and memory clocks offset.
Fixed a few issues with KawPow mining. Also, fixed issues with AMDs stats output. Please find miniZ version v1.9z3 @ Download page. Changelog: * Added --gpuoffset and --memoffset for core/memory clocks offset. (Windows only)* Fixed Ethash, on AMD's, on Windows. * Fixed AMD temperatures, on Windows. * Fixed AMD fan display, on Linux.* Added --hideclocks option to hide clocks from output. * Added socks information to console/file mining log. * Improved invalid/stale shares on progpow/ethash/octopus. * Fixed issues with KawPow mining.(Ravencoin, Sato, KawKaw, Neoxa, Arielcoin...)* Improved stability. Check our website here. For additional information check our Usage or FAQ pages. Follow us on TwitterLet us know how it goes! 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
|
|
|
Divinity666
Jr. Member
Offline
Activity: 312
Merit: 2
|
|
October 08, 2022, 10:59:14 AM |
|
Hi everyone,
A new miniZ version v1.9z3 is out
Please add fan control(target temperature), most of popular miners have it already!
|
|
|
|
Cyb93
Newbie
Offline
Activity: 1
Merit: 0
|
|
October 15, 2022, 01:55:42 PM |
|
Hello everyone,
I have a problem with the miniz miner to mine FLUX. I'm having this problem on one particular rig. I mine through hiveos.
************ miniZ v1.8y4rc2 ************ Number of CUDA[8.0] devices found: 13 /hive/miners/miniz/h-run.sh: line 20: 4392 Segmentation fault (core dumped) ./miniZ $(< ${MINER_NAME}.conf) --logfile $MINER_LOG_BASE NAME.log --telemetry 127.0.0.1:${MINER_API_PORT} --gpu-line
How to solve this problem ? I tried with OC and without OC. On my other rigs, no problem with this flight sheet
|
|
|
|
tswift
Newbie
Offline
Activity: 27
Merit: 0
|
|
October 17, 2022, 08:24:47 AM |
|
Hi, mini Z seems to be not working correctly with Aion Equihash 210,9 for CMP 170HX cards. The cards don't use more than 50w or so and only does about 8-10kSol per card. I uploaded a screenshot to your website in the comments. Could you fix this? I mentioned CMP 170HX performance issues on other Equihash before also
|
|
|
|
miniZ (OP)
|
|
October 22, 2022, 02:12:16 AM |
|
Hi everyone,
A new miniZ version v1.9z3 is out
Please add fan control(target temperature), most of popular miners have it already! Hi Divinity666, You can try option --fantemp with the new version v1.9z4. 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)
|
|
October 22, 2022, 02:13:44 AM |
|
Hello everyone,
I have a problem with the miniz miner to mine FLUX. I'm having this problem on one particular rig. I mine through hiveos.
************ miniZ v1.8y4rc2 ************ Number of CUDA[8.0] devices found: 13 /hive/miners/miniz/h-run.sh: line 20: 4392 Segmentation fault (core dumped) ./miniZ $(< ${MINER_NAME}.conf) --logfile $MINER_LOG_BASE NAME.log --telemetry 127.0.0.1:${MINER_API_PORT} --gpu-line
How to solve this problem ? I tried with OC and without OC. On my other rigs, no problem with this flight sheet
Hi Cyb93, Thank for your message. Was this also happening with version v1.9z3? The new version v1.9z4 has various fixes. Could you try it out and see if this is solved? 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)
|
|
October 22, 2022, 02:15:39 AM |
|
Hi, mini Z seems to be not working correctly with Aion Equihash 210,9 for CMP 170HX cards. The cards don't use more than 50w or so and only does about 8-10kSol per card. I uploaded a screenshot to your website in the comments. Could you fix this? I mentioned CMP 170HX performance issues on other Equihash before also
Hi tswift, Thanks for your messages. This should be solved with the new version v1.9z4. Let us know how it goes. 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)
|
|
October 22, 2022, 02:24:34 AM |
|
Hi everyone, A new miniZ v1.9z4 is out with performance improvements for 125,4 – FLUX – mining! Up to 20%! Added ubqhash support, progpow (and variants) support for AMDs, fan control for AMDs, fan/temperature control option…
Please find miniZ v1.9z4 @ Download page. Changelog: * Performance improvements for 125,4 on all gpus. Up to 20%. * Performance improvements for 150,5 on all gpus. * Added ubqhash algorithm for Ubiq (UBQ) mining. * Added AMD support for all progpow algos. * Added fan/target temperature control option --fantemp.1* Changed AMD GPU order to PCI order. * Added AMD fan control. * Added support for NVIDIA RTX 40XX GPUs.* Fixed issue with Telemetry. * Fixed Ampere modes that were not launching well on Aion mining. * Fixed 96,5 support. * Added reset value to power option. --power=1 will reset to stock value. (0 to ignore) * Power option show range when trying to set different value. 1 Requires sudo (Linux)/administator privileges (Windows) Works with: Linux: AMDs; and NVIDAs w/ driver >515 Windows: Polaris AMDs; and NVIDIAs w/ driver >515 On exit --fantemp resets to auto on AMDs, and to 50% fan on NVIDIAs. When using --fanspeed conjointly with --fantemp, the fan % defined with --fanspeed works as minimum fan speed.Check our website here. For additional information check our Usage or FAQ pages. Follow us on TwitterLet us know how it goes! 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
|
|
|
somaton
Jr. Member
Offline
Activity: 204
Merit: 5
|
|
October 22, 2022, 03:48:53 AM Last edit: October 22, 2022, 04:01:25 AM by somaton |
|
Tried ubqhash. Does not work (windows 10, 466.77):
[INFO ] Mining fee set to 0.75% miniZ<ubqhash>[20:2:00.0: 9106]: Selecting GPU#0[0] MSI GeForce RTX 3080 [INFO ] GPU[0]: Generating DAG #97 [1799+28=1828MB] [INFO ] GPU[0]: Generated DAG in 1.188 [FATAL ] CUDA Driver API error = 0001 from line 1100. [INFO ] QUIT miniZ
|
|
|
|
Divinity666
Jr. Member
Offline
Activity: 312
Merit: 2
|
|
October 24, 2022, 05:15:28 PM Last edit: October 25, 2022, 06:18:22 AM by Divinity666 |
|
Wow, major h\r improvements for on 125,4 with my 3080\3070-rig, but its like +1% with my 1080ti rigs Hi Divinity666, You can try option --fantemp with the new version v1.9z4. Cheers
Finally, thank you!
|
|
|
|
|