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

[sp_]

terminate called after throwing an instance of 'cl::BuildError'                                                                                                         
  what():  clBuildProgram                                                                                                                                                                                                                 

I have fixed it. Will release 1.40 later today.

v1.40

1. Fix build issue on AMD rigs.
2. Tiny improvement in the cuda kernel.

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

TeamBlackMiner_1_40_cuda_11_5.7z
https://www.virustotal.com/gui/file/643125624bfadf450b2dcfcb1691f7b88095b91371bc48ce90a6bb6ee40c5170?nocache=1

TeamBlackMiner_1_40_cuda_11_3.7z
https://www.virustotal.com/gui/file/9146ff9d966b3af27d1a92848be5091d1d36d1ed0e5c397545d6b064e5098577?nocache=1

TeamBlackMiner_1_40_Ubuntu_18_04_Cuda_11_5.tar.xz
https://www.virustotal.com/gui/file/d4fb8c7c50c332fd86ee96d54c9b11b0c684b2cec4f51ef1d8283079cba2b13a?nocache=1

[cafemax]

v1.40

1. Fix build issue on AMD rigs.
2. Tiny improvement in the cuda kernel.

It's work, 

[sp_]

v1.40
1. Fix build issue on AMD rigs.
2. Tiny improvement in the cuda kernel.

It's work,  

working good on all testrigs

[yanyan20]

                                                                                                                                                                                                           
00:00:00 [2022-01-16 21:23:22.209]                                                                                 
00:00:00 [2022-01-16 21:23:22.320] OpenCL driver version: 318.0
00:00:00 [2022-01-16 21:23:22.335] Cuda driver version: 11.4
00:00:00 [2022-01-16 21:23:22.335] Cuda runtime API version: 11.4
00:00:00 [2022-01-16 21:23:22.335]
00:00:00 [2022-01-16 21:23:22.335]                                 
00:00:00 [2022-01-16 21:23:22.335]
00:00:00 [2022-01-16 21:23:22.335] Welcome to Team Black Miner 1.39
00:00:00 [2022-01-16 21:23:22.335]                                 
00:00:00 [2022-01-16 21:23:22.335]
00:00:00 [2022-01-16 21:23:22.335] GPU0 gfx1031 12GB added to miner as OpenCL device
00:00:00 [2022-01-16 21:23:22.335] GPU1 gfx1031 12GB added to miner as OpenCL device
00:00:00 [2022-01-16 21:23:22.335] GPU2 gfx1031 12GB added to miner as OpenCL device
00:00:00 [2022-01-16 21:23:22.335] GPU3 gfx1031 12GB added to miner as OpenCL device
00:00:00 [2022-01-16 21:23:22.335] GPU4 gfx1010 8GB added to miner as OpenCL device
00:00:00 [2022-01-16 21:23:22.335] GPU5 gfx1010 8GB added to miner as OpenCL device
00:00:00 [2022-01-16 21:23:22.335] GPU6 gfx1010 8GB added to miner as OpenCL device
00:00:00 [2022-01-16 21:23:22.335] GPU7 gfx1010 8GB added to miner as OpenCL device
00:00:00 [2022-01-16 21:23:22.335] GPU8 gfx1010 8GB added to miner as OpenCL device
00:00:00 [2022-01-16 21:23:22.336] Trying eth.ss.poolin.me:1883 (ethash)
00:00:00 [2022-01-16 21:23:22.338] GPU0 Started CL work thread
00:00:00 [2022-01-16 21:23:22.339] GPU1 Started CL work thread
00:00:00 [2022-01-16 21:23:22.340] GPU2 Started CL work thread
00:00:00 [2022-01-16 21:23:22.341] GPU3 Started CL work thread
00:00:00 [2022-01-16 21:23:22.342] GPU4 Started CL work thread
00:00:00 [2022-01-16 21:23:22.343] GPU5 Started CL work thread
00:00:00 [2022-01-16 21:23:22.344] GPU6 Started CL work thread
00:00:00 [2022-01-16 21:23:22.345] GPU7 Started CL work thread
00:00:00 [2022-01-16 21:23:22.347] GPU8 Started CL work thread
00:00:00 [2022-01-16 21:23:22.347] Api server started at 127.0.0.1:64068
00:00:00 [2022-01-16 21:23:22.403] Pool responded successfully to subscribe
00:00:00 [2022-01-16 21:23:22.403] Extranonce is set to 0
00:00:00 [2022-01-16 21:23:22.435] mining.extranonce.subscribe: Pool reponded with error
00:00:00 [2022-01-16 21:23:22.435] Error(26): Illegal method
00:00:00 [2022-01-16 21:23:22.466] Pool responded successfully to authorize
00:00:00 [2022-01-16 21:23:22.466] Difficulty is set to 2.000000
00:00:00 [2022-01-16 21:23:22.466] GPU1 Starting generating ethash dag (Epoch: 467)
00:00:00 [2022-01-16 21:23:22.470] GPU6 Starting generating ethash dag (Epoch: 467)
00:00:00 [2022-01-16 21:23:22.470] GPU0 Starting generating ethash dag (Epoch: 467)
00:00:00 [2022-01-16 21:23:22.470] GPU4 Starting generating ethash dag (Epoch: 467)
00:00:00 [2022-01-16 21:23:22.470] GPU8 Starting generating ethash dag (Epoch: 467)
00:00:00 [2022-01-16 21:23:22.470] GPU2 Starting generating ethash dag (Epoch: 467)

[sp_]

00:00:00 [2022-01-16 21:23:22.403] Extranonce is set to 0
00:00:00 [2022-01-16 21:23:22.435] mining.extranonce.subscribe: Pool reponded with error
00:00:00 [2022-01-16 21:23:22.435] Error(26): Illegal method

This pool doesn't support extranonce, but should work.

[sp_]

ubuntu cuda 11.4 build added


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

TeamBlackMiner_1_40_Ubuntu_18_04_Cuda_11_4.tar.xz
https://www.virustotal.com/gui/file/a4acc5a2ffb1aed559765ccf7e83785ee468356d1ba43613ce4bce04d067908c?nocache=1

[abanamat]

ubuntu cuda 11.4 build added


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

TeamBlackMiner_1_40_Ubuntu_18_04_Cuda_11_4.tar.xz
https://www.virustotal.com/gui/file/a4acc5a2ffb1aed559765ccf7e83785ee468356d1ba43613ce4bce04d067908c?nocache=1

Can you add Windows cuda 11.4 please?

[sp_]

Can you add Windows cuda 11.4 please?

You can use the 11.3 build.  (will work on the 470.05 driver 3060 LHR1)

But the best speed with the cuda_11_5 build. A driver upgrade might be worth it.

[Dojo76]

v1.40

1. Fix build issue on AMD rigs.
2. Tiny improvement in the cuda kernel.

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

TeamBlackMiner_1_40_cuda_11_5.7z
https://www.virustotal.com/gui/file/643125624bfadf450b2dcfcb1691f7b88095b91371bc48ce90a6bb6ee40c5170?nocache=1

TeamBlackMiner_1_40_cuda_11_3.7z
https://www.virustotal.com/gui/file/9146ff9d966b3af27d1a92848be5091d1d36d1ed0e5c397545d6b064e5098577?nocache=1

TeamBlackMiner_1_40_Ubuntu_18_04_Cuda_11_5.tar.xz
https://www.virustotal.com/gui/file/d4fb8c7c50c332fd86ee96d54c9b11b0c684b2cec4f51ef1d8283079cba2b13a?nocache=1

In the HiveOn pool still not working:


Miner:   teamblackminer
Version: 1.40


/hive/miners/teamblackminer/1.40/miner.conf


00:00:00 [2022-01-17 14:21:26.358]
00:00:00 [2022-01-17 14:21:26.358] Sorry the provided pool is not supported
00:00:00 [2022-01-17 14:21:26.358] If you think this pool should be, then ask us to configure it
00:00:00 [2022-01-17 14:21:26.358] Shutting down threads
00:00:00 [2022-01-17 14:21:43.358] Exiting

[sp_]

00:00:00 [2022-01-17 14:21:26.358] Sorry the provided pool is not supported
00:00:00 [2022-01-17 14:21:26.358] If you think this pool should be, then ask us to configure it
00:00:00 [2022-01-17 14:21:26.358] Shutting down threads
00:00:00 [2022-01-17 14:21:43.358] Exiting

which pool are you using? url?

[Dojo76]

00:00:00 [2022-01-17 14:21:26.358] Sorry the provided pool is not supported
00:00:00 [2022-01-17 14:21:26.358] If you think this pool should be, then ask us to configure it
00:00:00 [2022-01-17 14:21:26.358] Shutting down threads
00:00:00 [2022-01-17 14:21:43.358] Exiting

which pool are you using? url?

eth.hiveon.com:4444
eth.hiveon.com:14444

TLS = Off

Recentry HiveOn moved to a single address mode, not sure it's the new address not recognized

[UniJo]

v1.40

1. Fix build issue on AMD rigs.
2. Tiny improvement in the cuda kernel.

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

TeamBlackMiner_1_40_cuda_11_5.7z
https://www.virustotal.com/gui/file/643125624bfadf450b2dcfcb1691f7b88095b91371bc48ce90a6bb6ee40c5170?nocache=1

TeamBlackMiner_1_40_cuda_11_3.7z
https://www.virustotal.com/gui/file/9146ff9d966b3af27d1a92848be5091d1d36d1ed0e5c397545d6b064e5098577?nocache=1

TeamBlackMiner_1_40_Ubuntu_18_04_Cuda_11_5.tar.xz
https://www.virustotal.com/gui/file/d4fb8c7c50c332fd86ee96d54c9b11b0c684b2cec4f51ef1d8283079cba2b13a?nocache=1

In the HiveOn pool still not working:


Miner:   teamblackminer
Version: 1.40


/hive/miners/teamblackminer/1.40/miner.conf


00:00:00 [2022-01-17 14:21:26.358]
00:00:00 [2022-01-17 14:21:26.358] Sorry the provided pool is not supported
00:00:00 [2022-01-17 14:21:26.358] If you think this pool should be, then ask us to configure it
00:00:00 [2022-01-17 14:21:26.358] Shutting down threads
00:00:00 [2022-01-17 14:21:43.358] Exiting

I have the exact same problem with HiveOn.

[sp_]

I have the exact same problem with HiveOn.

eth.hiveon.com:4444
eth.hiveon.com:14444
TLS = Off
Recentry HiveOn moved to a single address mode, not sure it's the new address not recognized

The old adresses are working. See examples in the launch config scripts

eu-eth.hiveon.net 4444

[Dojo76]

I have the exact same problem with HiveOn.

eth.hiveon.com:4444
eth.hiveon.com:14444
TLS = Off
Recentry HiveOn moved to a single address mode, not sure it's the new address not recognized

The old adresses are working. See examples in the launch config scripts

eu-eth.hiveon.net 4444

So why is not used? Hive OS configures the miner script with a wizard, first time it happens that is not correct. You can try yourself, impossible to start the miner in the hiveos pool with 1.40

[sp_]

So why is not used? Hive OS configures the miner script with a wizard, first time it happens that is not correct. You can try yourself, impossible to start the miner in the hiveos pool with 1.40

We need to add support in v1.41

[Dojo76]

So why is not used? Hive OS configures the miner script with a wizard, first time it happens that is not correct. You can try yourself, impossible to start the miner in the hiveos pool with 1.40

We need to add support in v1.41

Ok thanks. Not a big problem but otherwise you have to manually nano the config file I suppose, actually is not possible to mine with HiveOS and 1.40

[sp_]

v1.41
1. Fix disconnect problem at nanopool.org
2. Fix crash in --list-devices on opencl
3. Flipped the gpu order for AMD gpu's
4. Fixed an issue with BTC and Nano payouts on 2miners pool
5. Added more pools

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

TeamBlackMiner_1_41_cuda_11_5.7z
https://www.virustotal.com/gui/file/12bea98e07e8a58d9dbe428c299958f38a72a37e576d7f7b41142166341e4790?nocache=1

TeamBlackMiner_1_41_cuda_11_3.7z
https://www.virustotal.com/gui/file/20cd2d2954565e61b806fb2620c597365b88e12d0ed196027809470d6b69a8ce?nocache=1

TeamBlackMiner_1_41_Ubuntu_18_04_Cuda_11_4.tar.xz
https://www.virustotal.com/gui/file/720127bd278f3bdc2665406ea957f80f864fe33614231aec2e77bf6fb6a28a13?nocache=1

TeamBlackMiner_1_41_Ubuntu_18_04_Cuda_11_5.tar.xz
https://www.virustotal.com/gui/file/763bb68d2822a9d8df9940ca2bf7d0a1c7736fe8e834961113a225c95a3e4193?nocache=1

[KillrBee]

I'm getting a lot of timeouts across all my AMD cards (randomly different AMD cards will timeout) on version 1.40 on HiveOS.

Sometimes the miner will just stop getting jobs and continue hashing for a while, other times it just happens, but it always seems to be identified before it happens by a huge spike in the Hashrate/Watt field (as the miner continues to think it's hashing while the card itself has gone idle).  I have set the cards to various under voltage values and OC's on the memory, but it still seems to happen randomly across any of the cards every 2-3 hours (sometimes less, but not more than 4 hours).  

I will try to reduce the OC on the memory to see if that helps, but typically it's not an issue with AMD 6-series cards since the memory is well protected from OC by the bios -- and the machine is currently running in a location where the weather can keep the cards memory under 40 degrees, and under 65 on my 3090, so temperatures aren't an issue.


Here's a sample from a log:

00:00:28 [2022-01-17 21:22:24.542]
00:00:28 [2022-01-17 21:22:24.542] us-eth.2miners.com (ethash)    PING: 39ms    VARDIFF: 2.03     EPOCH: 467
00:00:28 [2022-01-17 21:22:24.542]                                                                                
00:00:28 [2022-01-17 21:22:24.542]
00:00:28 [2022-01-17 21:22:24.542] ID      BOARD    TYPE    KERN    XINT    TEMP    FAN     CORE    MEM     WATT  
00:00:28 [2022-01-17 21:22:24.542] GPU0    gfx1030  OpenCL  0       595     28/0    214     1350    1074    137    
00:00:28 [2022-01-17 21:22:24.542] GPU1    gfx1030  OpenCL  0       595     26/0    214     1450    1069    146    
00:00:28 [2022-01-17 21:22:24.542] GPU2    gfx1030  OpenCL  0       595     0/0     0       0       0       0      
00:00:28 [2022-01-17 21:22:24.542] GPU3    gfx1030  OpenCL  0       595     17/0    214     1350    1074    104    
00:00:28 [2022-01-17 21:22:24.542] GPU4    3090     CUDA    5       3801    32/0    0       0       0       334    
00:00:28 [2022-01-17 21:22:24.542] GPU5    2060S    CUDA    8       2000    29/0    80      1545    7975    106    
00:00:28 [2022-01-17 21:22:24.542]                                                                          827    
00:00:28 [2022-01-17 21:22:24.542]
00:00:28 [2022-01-17 21:22:24.542] ID      BOARD    HASHRATE/W    HASHRATE      AVERAGE       SHARES       RATE    
00:00:28 [2022-01-17 21:22:24.542] GPU0    gfx1030  494.23 kH/W   66.72 MH/s    65.57 MH/s    11/0/8       100.00%
00:00:28 [2022-01-17 21:22:24.542] GPU1    gfx1030  460.98 kH/W   65.92 MH/s    64.88 MH/s    11/0/1       100.00%
00:00:28 [2022-01-17 21:22:24.542] GPU2    gfx1030  0.00 H/W      66.58 MH/s    65.44 MH/s    16/0/6       100.00%
00:00:28 [2022-01-17 21:22:24.542] GPU3    gfx1030  1826.54 kH/W  65.76 MH/s    64.94 MH/s    10/0/6       100.00%
00:00:28 [2022-01-17 21:22:24.542] GPU4    3090     401.23 kH/W   134.01 MH/s   134.13 MH/s   29/0/0       100.00%
00:00:28 [2022-01-17 21:22:24.542] GPU5    2060S    410.89 kH/W   44.38 MH/s    44.44 MH/s    10/0/0       100.00%
00:00:28 [2022-01-17 21:22:24.542]                  598.98 kH/W   443.37 MH/s   439.38 MH/s   87/0/21      100.00%
00:00:28 [2022-01-17 21:22:24.542]                                                                                
00:00:28 [2022-01-17 21:22:24.542] SHARES PER MINUTE: 3.22            POOL HASHRATE: 468.63 MH/s
00:00:28 [2022-01-17 21:22:24.542]
00:00:28 [2022-01-17 21:22:28.644] Job ddf79
00:00:28 [2022-01-17 21:22:31.438] Job ddf7e
00:00:28 [2022-01-17 21:22:39.821] Job ddf80
00:00:28 [2022-01-17 21:22:45.410] Job ddf82
00:00:28 [2022-01-17 21:22:53.793] Job ddf83
00:00:28 [2022-01-17 21:22:59.380] Job ddf84
00:00:28 [2022-01-17 21:23:00.410] GPU4 Solution found in 2.15s (Submit every 21.22 seconds)
00:00:28 [2022-01-17 21:23:00.444] Accepted (88/88/21) Reply: 34ms
00:00:28 [2022-01-17 21:23:02.890] GPU4 Solution found in 4.63s (Submit every 21.06 seconds)
00:00:28 [2022-01-17 21:23:02.924] Accepted (89/89/21) Reply: 34ms
00:00:28 [2022-01-17 21:23:05.373] GPU4 Solution found in 0.15s (Submit every 20.85 seconds)
00:00:28 [2022-01-17 21:23:05.407] Accepted (90/90/21) Reply: 34ms
00:00:28 [2022-01-17 21:23:07.764] Job ddf85
00:00:28 [2022-01-17 21:23:13.353] Job ddf86
00:00:29 [2022-01-17 21:23:21.736] Job ddf87
00:00:29 [2022-01-17 21:23:27.324] Job ddf88
00:00:29 [2022-01-17 21:23:30.558] GPU3: has timed out
00:00:29 [2022-01-17 21:23:30.558] Shutting down threads
00:00:29 [2022-01-17 21:23:30.558] Stratum thread exited
00:00:29 [2022-01-17 21:23:30.652] GPU5 thread exited
00:00:29 [2022-01-17 21:23:30.736] GPU2 thread exited
00:00:29 [2022-01-17 21:23:31.420] GPU4 thread exited
00:00:29 [2022-01-17 21:23:31.889] GPU1 thread exited
00:00:29 [2022-01-17 21:23:32.913] GPU0 thread exited
00:00:29 [2022-01-17 21:23:38.474] Api thread exited
00:00:29 [2022-01-17 21:23:47.558] Exiting

[sp_]

I have set the cards to various under voltage values and OC's on the memory, but it still seems to happen randomly across any of the cards every 2-3 hours (sometimes less, but not more than 4 hours).  

Did you try 1.41? we fixed a couple of bugs there. GPU timeouts are normally caused by GPU failures, but perhaps the timer in our test is too small for the high intensity you are using. 1.42 will have some adjustments that might help.

[abanamat]

Can you add Windows cuda 11.4 please?

You can use the 11.3 build.  (will work on the 470.05 driver 3060 LHR1)

But the best speed with the cuda_11_5 build. A driver upgrade might be worth it.

Nope. My 472.84 desktop driver is most stable. Tried another and got more rejects and stales. So I'll stay with it. Good luck