⛏Team Black Miner (ETHB3 ETHW ETC VTC KAWPOW FIROPOW ZIL +dual +tripple mining )

[sp_]

My last question is I get high mhs on first run. After a few minutes the mhs goes down and stays constant, any solution?

I see that the coreclock of your gpus are all different. It's probobly because they trottle. Not enough power or too much heat. You can increase the templimit, but not sure if this is the problem.

[1713864497]

1713864497

[1713864497]

1713864497

[1713864497]

1713864497

[1713864497]

1713864497

[yuzuak]

My last question is I get high mhs on first run. After a few minutes the mhs goes down and stays constant, any solution?

I see that the coreclock of your gpus are all different. It's probobly because they trottle. Not enough power or too much heat. You can increase the templimit, but not sure if this is the problem.

The old series 1070 can be bought this much mhs. I was able to reach 26.5 mhs (old miner 24.5). If I increase the power, maybe it will be 28 mhs, but I am in a country with high electricity prices. Thank you very much for your help. Compared to other miners, there was a total increase of about 200 mhs in my system with the same power operation.

[ZerodayTrader]

Would say keep it as is, 25mh/s average on <110 Watt is a very decent result for that old card.

[yuzuak]

Would say keep it as is, 25mh/s average on <110 Watt is a very decent result for that old card.

We were getting 32 mhs with the good old 110 W. Dag epoch increased, mhs started to drop on nvdia cards, no solution was found.

[ZerodayTrader]

Would say keep it as is, 25mh/s average on <110 Watt is a very decent result for that old card.

We were getting 32 mhs with the good old 110 W. Dag epoch increased, mhs started to drop on nvdia cards, no solution was found.

Yea i know, did >34mh/s on ETC, but not worth for me to mine, as it had still less Payout over ETH.

And also my suffer has a found an end.

https://i.imgur.com/uMKuHf6.png

Finally showing up as it has to be with 1.22. 25mh/s with <110 Watts is perfect. Good job guys!

Lets see how the 3080 will do with the switch from 1.15 to 1.22.

[duddabudda]

I try mining with unMineable and encountered this problem -
If I use the Terminal to check the ping to the server ethash-eu.unminable.com avg ping 54
https://i.ibb.co/1KyshKP/2021-11-04-10-30-11.png
and in the miner the ping is very high 399
https://i.ibb.co/Bzd4Jmx/2021-11-04-10-27-36.png

It's the same with nanopool

What might be the problem?

[sp_]

I try mining with unMineable and encountered this problem -
If I use the Terminal to check the ping to the server ethash-eu.unminable.com avg ping 54

and in the miner the ping is very high 399

It's the same with nanopool
What might be the problem?

Not sure we can check it. Can you open a ticket on our github?

https://github.com/sp-hash/TeamBlackMiner/issues

Make sure that you are connecting to the eu server in the launch config.

ethash.unmineable.com --port 3333
ethash-us.unmineable.com --port 3333
ethash-ca.unmineable.com --port 3333
ethash-eu.unmineable.com --port 3333
ethash-asia.unmineable.com --port 3333

[symplink]

How can we find the best --xintensity and --dagintensity?
I have some 6800xt, 3070, 3080. Which should be the best choices? Based on what?

[yuzuak]

My last question is I get high mhs on first run. After a few minutes the mhs goes down and stays constant, any solution?

I see that the coreclock of your gpus are all different. It's probobly because they trottle. Not enough power or too much heat. You can increase the templimit, but not sure if this is the problem.

I brought all my rigs to your miner. However, a rig gave an error. The only difference now is that it's connected to wifi.

[sp_]

Make sure that your wifi router doesn't have a local proxy server. You need to correct directly to the pool.
Also don't use ssl connection to the pool because the miner has issues with it. Use normal the ports.

[yuzuak]

Make sure that your wifi router doesn't have a local proxy server. You need to correct directly to the pool.
Also don't use ssl connection to the pool because the miner has issues with it. Use normal the ports.

I am using Xioami Wifi repeater, I will try to reset it. I am not using ssl.

[sp_]

How can we find the best --xintensity and --dagintensity?
I have some 6800xt, 3070, 3080. Which should be the best choices? Based on what?

- High --xintensity, higher amout of stale shares, higher speed. Some pools doesn't pay for stales so the setting is pool dependent. (AMD intensity settings  are 1/4 of NVIDIA)
- --dagintensity , 1-8(9) is for high memclocks. When dag buffer crash. 1 is low (slow dag) 8 amd is the fastest, 9 on nvidia. or 0 (default)
- --kernel , Different kernels can give a speedup on different models. Your power setting can also count. Autotune will try to find the fastest kernel for you.

[yuzuak]

Wifi

Mining rigs will produce more if they are connected to cables. Lower ping, more accepted pool hash.

Yes, you are right. One of them has to be wifi in a remote place for cable. I tried reset, unfortunately it didn't work

[sp_]

Yes, you are right. One of them has to be wifi in a remote place for cable. I tried reset, unfortunately it didn't work

ssh into the rig and run:

$ sudo apt install libcurl4-openssl-dev

[yuzuak]

Yes, you are right. One of them has to be wifi in a remote place for cable. I tried reset, unfortunately it didn't work

ssh into the rig and run:

$ sudo apt install libcurl4-openssl-dev

I tried but unfortunately it gave the same error.

[sp_]

I tried but unfortunately it gave the same error.

https://askubuntu.com/questions/1211782/curl-openssl-4-not-found-required-by-curl

Did you upgrade to the latest hiveos image? Perhaps it will help

[yuzuak]

I tried but unfortunately it gave the same error.

https://askubuntu.com/questions/1211782/curl-openssl-4-not-found-required-by-curl

Did you upgrade to the latest hiveos image? Perhaps it will help

yes, latest version hiveos is installed.

[wasarianta]

sp_, i found probs yesterday..
--lock-cclock [[1300,1300],[1390,1390],[1390,1390],[0,0]]

Device Number: 0
    Device name: NVIDIA GeForce RTX 2080 SUPER
    PCIe bus id: 5
    Memory: 8GB
    Memory clock rate (KHz): 7751000
    Memory bus width (bits): 256
    Peak memory bandwidth (GB/s): 496.064000

Device Number: 1
    Device name: NVIDIA GeForce GTX 1660
    PCIe bus id: 2
    Memory: 8GB
    Memory clock rate (KHz): 4001000
    Memory bus width (bits): 192
    Peak memory bandwidth (GB/s): 192.048000

Device Number: 2
    Device name: NVIDIA GeForce GTX 1660
    PCIe bus id: 6
    Memory: 8GB
    Memory clock rate (KHz): 4001000
    Memory bus width (bits): 192
    Peak memory bandwidth (GB/s): 192.048000

Device Number: 3
    Device name: NVIDIA GeForce GTX 1080
    PCIe bus id: 4
    Memory: 8GB
    Memory clock rate (KHz): 5005000
    Memory bus width (bits): 256
    Peak memory bandwidth (GB/s): 320.320000

     0m [2021-11-02 01:16:06.673] OpenCL driver version: 30.0
     0m [2021-11-02 01:16:06.704] Cuda driver version: 11.5
     0m [2021-11-02 01:16:06.704] Cuda runtime API version: 11.5
     0m [2021-11-02 01:16:06.704]
     0m [2021-11-02 01:16:06.704]                                 
     0m [2021-11-02 01:16:06.704]
     0m [2021-11-02 01:16:06.704] Welcome to Team Black Miner 1.22
     0m [2021-11-02 01:16:06.704]                                 
     0m [2021-11-02 01:16:06.704]
     0m [2021-11-02 01:16:06.814] GPU0 NVIDIA GeForce RTX 2080 SUPER 8GB added to miner as Cuda device
     0m [2021-11-02 01:16:06.970] GPU1 NVIDIA GeForce GTX 1660 6GB added to miner as Cuda device
     0m [2021-11-02 01:16:07.064] GPU2 NVIDIA GeForce GTX 1660 6GB added to miner as Cuda device
     0m [2021-11-02 01:16:07.157] GPU3 NVIDIA GeForce GTX 1080 8GB added to miner as Cuda device
     0m [2021-11-02 01:16:07.204] Trying asia-eth.2miners.com:2020 (ethash)
     0m [2021-11-02 01:16:07.220] Extranonce is set to 6171057389404422144
     0m [2021-11-02 01:16:07.220] Pool responded successfully to subscribe
     0m [2021-11-02 01:16:07.251] Pool responded successfully to extranonce subscribe
     0m [2021-11-02 01:16:07.267] Extranonce is set to 6171057389404422144
     0m [2021-11-02 01:16:07.282] Pool responded successfully to authorize
     0m [2021-11-02 01:16:07.298] Difficulty is set to 2.031715
     0m [2021-11-02 01:16:07.407] GPU0 Started Cuda work thread
     0m [2021-11-02 01:16:07.595] GPU1 Started Cuda work thread
     0m [2021-11-02 01:16:07.720] GPU2 Started Cuda work thread
     0m [2021-11-02 01:16:07.845] Api server started at 127.0.0.1:4068
     0m [2021-11-02 01:16:07.845] GPU3 Started Cuda work thread
     0m [2021-11-02 01:16:12.023] GPU0 Starting generating ethash dag (Epoch: 451)
     0m [2021-11-02 01:16:12.054] GPU1 Starting generating ethash dag (Epoch: 451)
     0m [2021-11-02 01:16:12.085] GPU3 Starting generating ethash dag (Epoch: 451)
     0m [2021-11-02 01:16:12.226] GPU2 Starting generating ethash dag (Epoch: 451)
     0m [2021-11-02 01:16:12.335] GPU0 DAG generated in 3.15 seconds (4743167kb)
     0m [2021-11-02 01:16:12.335] GPU0 kernel 8 selected
     0m [2021-11-02 01:16:12.335] GPU0 XIntensity set to 2048
     0m [2021-11-02 01:16:12.835] GPU1 DAG generated in 3.65 seconds (4743167kb)
     0m [2021-11-02 01:16:12.835] GPU1 kernel 5 selected
     0m [2021-11-02 01:16:12.835] GPU1 XIntensity set to 1152
     0m [2021-11-02 01:16:12.851] GPU3 DAG generated in 3.65 seconds (4743167kb)
     0m [2021-11-02 01:16:12.851] GPU3 kernel 0 selected
     0m [2021-11-02 01:16:12.851] GPU3 XIntensity set to 2048
     0m [2021-11-02 01:16:12.851] GPU2 DAG generated in 3.65 seconds (4743167kb)
     0m [2021-11-02 01:16:12.851] GPU2 kernel 5 selected
     0m [2021-11-02 01:16:12.851] GPU2 XIntensity set to 1152
     0m [2021-11-02 01:16:23.834] Job 88e3
     0m [2021-11-02 01:16:28.771] GPU0 Dag buffer verified ok!
     0m [2021-11-02 01:16:28.833] GPU0 GPU clocks set to "(gpuClkMin 1300, gpuClkMax 1300)" for GPU 00000000:02:00.0
     0m [2021-11-02 01:16:28.927] GPU1 Setting locked GPU clocks is not supported for GPU 00000000:04:00.0.
     0m [2021-11-02 01:16:28.989] GPU2 GPU clocks set to "(gpuClkMin 1390, gpuClkMax 1390)" for GPU 00000000:05:00.0
     0m [2021-11-02 01:16:28.989] Job 88e4
     0m [2021-11-02 01:16:30.460] GPU3 Dag buffer verified ok!
     0m [2021-11-02 01:16:30.522] GPU0 GPU clocks set to "(gpuClkMin 1300, gpuClkMax 1300)" for GPU 00000000:02:00.0
     0m [2021-11-02 01:16:30.585] GPU1 Setting locked GPU clocks is not supported for GPU 00000000:04:00.0.
     0m [2021-11-02 01:16:30.647] GPU2 GPU clocks set to "(gpuClkMin 1390, gpuClkMax 1390)" for GPU 00000000:05:00.0
     0m [2021-11-02 01:16:31.397] Job 88e5
     0m [2021-11-02 01:16:35.521] GPU1 Dag buffer verified ok!
     0m [2021-11-02 01:16:35.584] GPU0 GPU clocks set to "(gpuClkMin 1300, gpuClkMax 1300)" for GPU 00000000:02:00.0
     0m [2021-11-02 01:16:35.646] GPU1 Setting locked GPU clocks is not supported for GPU 00000000:04:00.0.
     0m [2021-11-02 01:16:35.709] GPU2 GPU clocks set to "(gpuClkMin 1390, gpuClkMax 1390)" for GPU 00000000:05:00.0
     0m [2021-11-02 01:16:35.787] GPU2 Dag buffer verified ok!
     0m [2021-11-02 01:16:35.849] GPU0 GPU clocks set to "(gpuClkMin 1300, gpuClkMax 1300)" for GPU 00000000:02:00.0
     0m [2021-11-02 01:16:35.943] GPU1 Setting locked GPU clocks is not supported for GPU 00000000:04:00.0.
     0m [2021-11-02 01:16:36.005] GPU2 GPU clocks set to "(gpuClkMin 1390, gpuClkMax 1390)" for GPU 00000000:05:00.0
     0m [2021-11-02 01:16:36.131] Job 88e6
     0m [2021-11-02 01:16:38.489] Job 88ea
     0m [2021-11-02 01:16:45.589] Job 88eb
     0m [2021-11-02 01:16:50.323] Job 88ed
     0m [2021-11-02 01:16:52.681] Job 88f1
     0m [2021-11-02 01:16:59.789] Job 88f3
     0m [2021-11-02 01:17:06.881] Job 88f4
     1m [2021-11-02 01:17:07.303]
     1m [2021-11-02 01:17:07.303]
     1m [2021-11-02 01:17:07.303] asia-eth.2miners.com (ethash)    PING: 0ms    DIFFICULTY: 2.03     EPOCH: 451
     1m [2021-11-02 01:17:07.303]                                                                                 
     1m [2021-11-02 01:17:07.303]
     1m [2021-11-02 01:17:07.303] ID   BOARD   TYPE   KERN   XINT   TEMP   FAN   CORE   MEM   WATT
     1m [2021-11-02 01:17:07.303] GPU0   2080S   Cuda   8   2048   44/0   72   1394   8692   91 <== lockclock at 1390 (this clock for 1660)
     1m [2021-11-02 01:17:07.303] GPU1   1660   Cuda   5   1152   47/0   75   1315   4891   51 <== lockclock  but miner say not supported at 1300 (for 2080S)
     1m [2021-11-02 01:17:07.303] GPU2   1660   Cuda   5   1152   54/0   75   1884   4891   88 <== miner say lock clock at 1390 but using stock clock [0,0]
     1m [2021-11-02 01:17:07.303] GPU3   1080   Cuda   0   2048   50/0   75   2119   4911   140 <== runing fine
     1m [2021-11-02 01:17:07.303]                            370
     1m [2021-11-02 01:17:07.303]
     1m [2021-11-02 01:17:07.303] ID   BOARD   HASHRATE/W   HASHRATE   AVERAGE      SHARES
     1m [2021-11-02 01:17:07.303] GPU0   2080S   623.35 kH/W   56.72 MH/s   45.83 MH/s   0/0/0 (100.00)
     1m [2021-11-02 01:17:07.303] GPU1   1660   574.11 kH/W   29.28 MH/s   25.79 MH/s   0/0/0 (100.00)
     1m [2021-11-02 01:17:07.303] GPU2   1660   332.56 kH/W   29.27 MH/s   25.76 MH/s   0/0/0 (100.00)
     1m [2021-11-02 01:17:07.303] GPU3   1080   220.76 kH/W   30.91 MH/s   26.16 MH/s   0/0/0 (100.00)
     1m [2021-11-02 01:17:07.303]       437.69 kH/W   146.18 MH/s   123.54 MH/s   0/0/0 (100.00)
     1m [2021-11-02 01:17:07.303]                                                                                 
     1m [2021-11-02 01:17:07.303] COST: 0.37 KWH (555.00IDR)            POOL HASHRATE: 0.00 H/s

have change bat..

nvidia-smi -i 0 -lgc 1490
nvidia-smi -i 2 -lgc 1490
nvidia-smi -i 3 -lgc 1390

START "TBMiner.exe" "C:\Users\len4_\Downloads\MINING\MINE\TeamBlackMiner_1_22_cuda_11_5\TBMiner.exe" --algo ethash --dagintensity [0,0,0,0] --kernel [8,5,5,7] --cuda-devices [0,1,2,3] --xintensity [768,768,768,768] --hostname asia-eth.2miners.com --port 2020

https://ibb.co/gMKKLvB

[sp_]

sp_, i found probs yesterday..
--lock-cclock [[1300,1300],[1390,1390],[1390,1390],[0,0]]

Fixed in v1.23

[Shlimann]

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