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

[dle378]

Which cards? 3060ti LHR3 unlocks with -85

--lhr-unlock [-85]

10GB 3080 LHR

[sp_]

10GB 3080 LHR

Try on 2miners.com with --lhr-unlock[1] --log. 70% tdp on the card below 1500 coreclock . mem 10200 or more (linux 2550). Reboot the rig and let it start clean without any programs in the backround. In a mixed card environment add --xintensity 3000 for the other nvidia cards.

[KillrBee]

10GB 3080 LHR

Try on 2miners.com with --lhr-unlock[1] --log. 70% tdp on the card below 1500 coreclock . mem 10200 or more (linux 2550). Reboot the rig and let it start clean without any programs in the backround. In a mixed card environment add --xintensity 3000 for the other nvidia cards.

Assuming it's Windows -- use the Task Scheduler to create a task that is triggered on the computer startup - before user logon, with full admin permissions.  This will ensure that there are no user-specific apps that are running.  The caveat here is that if you're dependent on any overclocking software like MSI afterburner or Precision X1, you need to either set up scripts that execute these apps before you start the miner, or have the apps execute from within the batch file before running the miner.  I have to execute X1 to get my 3rd fan spinning on my EVGA cards, but I have the script execute and then kill the application after a few minutes so it's not always running in the background taking up resources (X1 is a resource hog).

[Vladegg]

You're right, ETC works. But on ETH Gminer works on that rig without problems. What can I do to make TBM work?

On linux you need to add swap. 4GB * 12 = 48gb should be enough

https://minerstat.com/help/how-to-increase-virtual-memory-on-linux

In RaveOS command swap-on helped. Thanks!

[mxx]

I increased memclock of GPUs to use feature of copying dag from non corrupted

Try with ---dagintensity 1

No, this is not because of bad dag. My cards crashes because I min/maxing my overclocks and with other miners I see in log which card is crashed and restarted miner, so I know where to reduce overclock. But with your TBM miner feedback doesnt mention which card is crashed so it is unknown and makes tweaking hard.
We need miner to report more clear what GPU is failing before restart.

[sp_]

We need miner to report more clear what GPU is failing before restart.

Did you try 1.61? a bug was fixed. The failing GPU number should be written to the commandline. You only need to downclock one card in the rig, the other cards will copy the working dag to their gpu.



Remember to add enough virtual memory / SWAP

--------------------------------------------------------

v1.61 seems to be pretty good.
From the devfee I can see that some of you are still mining on the older versions, but the latest have bugs fixed, fewer rejected shares and higher poolside speeds.
An upgrade is recommended.

[mxx]

We need miner to report more clear what GPU is failing before restart.

Did you try 1.61? a bug was fixed. The failing GPU number should be written to the commandline. You only need to downclock one card in the rig, the other cards will copy the working dag to their gpu.

https://i.ibb.co/mNpNvWx/dag-validation-fix.png

Remember to add enough virtual memory / SWAP

--------------------------------------------------------

v1.61 seems to be pretty good.
From the devfee I can see that some of you are still mining on the older versions, but the latest have bugs fixed, fewer rejected shares and higher poolside speeds.
An upgrade is recommended.

I said before that problem not with dag: https://bitcointalk.org/index.php?topic=5358334.msg59524405#msg59524405
It occurs while mining so to solve it I need to reduce overclock, but how I know which GPU is failing, miner not reporting card index.

[Movalis]

Found a little bug

using v1.61

Have 2 AMD cards one 6600XT and other 6800XT

On miner side:

https://imgur.com/a/KPtP8lJ

On HiveOS side:

https://imgur.com/a/YaUzq5m

GPU id swaped infos in HiveOS


Cheers

[sp_]

GPU id swapped infos in HiveOS

This used to be a problem in the older versions. Make sure that you download the v1.61 from my github

If it still fails, you can try the option

--all-platform 1

to see if it helps

[Movalis]

GPU id swapped infos in HiveOS

This used to be a problem in the older versions. Make sure that you download the v1.61 from my github

If it still fails, you can try the option

--all-platform 1

to see if it helps

Didn't download v1.61 as i assume it's the same i have on HiveOS. I did used --all-platform 1 but got same result.

- Using HiveOS version 0.6-213@220325
- Miner set to the latest release so currently using the v1.61

My cards

https://imgur.com/a/1ddmqIV

Miner extra config arguments

--all-platforms 1
--cl-devices [0,1]
--cuda-devices [0,1,2,3]
--algo ethash
--log

Note: Cuda devices working well

.[1;36m00:00:00.[0m .[1m[2022-03-30 16:42:55..[0m.[0m314.[0m.[1m].[0m .[32mGPU0 gfx1032 8GB added to miner as OpenCL device.[0m                                                                                   
.[1;36m00:00:00.[0m .[1m[2022-03-30 16:42:55..[0m.[0m314.[0m.[1m].[0m .[32mGPU1 gfx1030 17GB added to miner as OpenCL device.[0m                                                                                   
.[1;36m00:00:00.[0m .[1m[2022-03-30 16:42:55..[0m.[0m496.[0m.[1m].[0m .[32mGPU2 NVIDIA GeForce RTX 3070 8GB added to miner as Cuda device.[0m                                                                     
.[1;36m00:00:00.[0m .[1m[2022-03-30 16:42:55..[0m.[0m654.[0m.[1m].[0m .[32mGPU3 NVIDIA GeForce RTX 3070 8GB added to miner as Cuda device.[0m                                                                     
.[1;36m00:00:00.[0m .[1m[2022-03-30 16:42:55..[0m.[0m877.[0m.[1m].[0m .[32mGPU4 NVIDIA GeForce RTX 3070 8GB added to miner as Cuda device.[0m                                                                     
.[1;36m00:00:00.[0m .[1m[2022-03-30 16:42:56..[0m.[0m089.[0m.[1m].[0m .[32mGPU5 NVIDIA GeForce RTX 2060 12GB added to miner as Cuda device.[0m                                                                     
.[1;36m00:00:00.[0m .[1m[2022-03-30 16:42:56..[0m.[0m090.[0m.[1m].[0m .[1;36mTrying eth.2miners.com:2020 (ethash).[0m                                                                                             
.[1;36m00:00:00.[0m .[1m[2022-03-30 16:42:56..[0m.[0m092.[0m.[1m].[0m .[32mGPU0 Started CL work thread.[0m                                                                                                         
.[1;36m00:00:00.[0m .[1m[2022-03-30 16:42:56..[0m.[0m093.[0m.[1m].[0m .[32mGPU1 Started CL work thread.[0m                                                                                                         
.[1;36m00:00:00.[0m .[1m[2022-03-30 16:42:56..[0m.[0m182.[0m.[1m].[0m .[32mPool responded successfully to subscribe.[0m                                                                                           
.[1;36m00:00:00.[0m .[1m[2022-03-30 16:42:56..[0m.[0m225.[0m.[1m].[0m .[32mPool responded successfully to extranonce subscribe.[0m                                                                                 
.[1;36m00:00:00.[0m .[1m[2022-03-30 16:42:56..[0m.[0m225.[0m.[1m].[0m .[36mExtranonce is set to c59d000000000000.[0m                                                                                               
.[1;36m00:00:00.[0m .[1m[2022-03-30 16:42:56..[0m.[0m225.[0m.[1m].[0m .[32mPool responded successfully to authorize.[0m                                                                                           
.[1;36m00:00:00.[0m .[1m[2022-03-30 16:42:56..[0m.[0m225.[0m.[1m].[0m .[36mDifficulty is set to 2.031715.[0m                                                                                                       
.[1;36m00:00:00.[0m .[1m[2022-03-30 16:42:56..[0m.[0m226.[0m.[1m].[0m .[36mGPU1 Starting generating ethash dag (Epoch: 482).[0m                                                                                   
.[1;36m00:00:00.[0m .[1m[2022-03-30 16:42:56..[0m.[0m226.[0m.[1m].[0m .[36mGPU0 Starting generating ethash dag (Epoch: 482).[0m                                                                                   
.[1;36m00:00:00.[0m .[1m[2022-03-30 16:42:56..[0m.[0m280.[0m.[1m].[0m .[32mGPU2 Started Cuda work thread.[0m                                                                                                       
.[1;36m00:00:00.[0m .[1m[2022-03-30 16:42:56..[0m.[0m472.[0m.[1m].[0m .[32mGPU3 Started Cuda work thread.[0m                                                                                                       
.[1;36m00:00:00.[0m .[1m[2022-03-30 16:42:56..[0m.[0m706.[0m.[1m].[0m .[32mGPU4 Started Cuda work thread.[0m                                                                                                       
.[1;36m00:00:00.[0m .[1m[2022-03-30 16:42:56..[0m.[0m907.[0m.[1m].[0m .[32mGPU5 Started Cuda work thread.[0m                                                                                                       


.[1;36m00:00:01.[0m .[1m[2022-03-30 16:42:27..[0m.[0m421.[0m.[1m].[0m .[1meth.2miners.com (ethash)    PING: 43ms    DIFFICULTY: 2.03     EPOCH: 482.[0m                                                           
.[1;36m00:00:01.[0m .[1m[2022-03-30 16:42:27..[0m.[0m421.[0m.[1m].[0m .[4m                                                                                .[0m                                                     
.[1;36m00:00:01.[0m .[1m[2022-03-30 16:42:27..[0m.[0m421.[0m.[1m].[0m .[0m.[0m                                                                                                                                     
.[1;36m00:00:01.[0m .[1m[2022-03-30 16:42:27..[0m.[0m421.[0m.[1m].[0m .[1mID      BOARD    TYPE    KERN    XINT    TEMP    FAN     CORE    MEM     WATT   .[0m                                                     
.[1;36m00:00:01.[0m .[1m[2022-03-30 16:42:27..[0m.[0m421.[0m.[1m].[0m .[36mGPU0    gfx1032  OpenCL  0       71      40/0    68      1260    1074    79     .[0m                                                   
.[1;36m00:00:01.[0m .[1m[2022-03-30 16:42:27..[0m.[0m421.[0m.[1m].[0m .[36mGPU1    gfx1030  OpenCL  0       71      41/0    68      1150    1084    46     .[0m                                                   
.[1;36m00:00:01.[0m .[1m[2022-03-30 16:42:27..[0m.[0m421.[0m.[1m].[0m .[36mGPU2    3070     CUDA    2       284     43/0    70      1095    7800    95     .[0m                                                   
.[1;36m00:00:01.[0m .[1m[2022-03-30 16:42:27..[0m.[0m421.[0m.[1m].[0m .[36mGPU3    3070     CUDA    2       284     51/0    70      1095    7800    98     .[0m                                                   
.[1;36m00:00:01.[0m .[1m[2022-03-30 16:42:27..[0m.[0m421.[0m.[1m].[0m .[36mGPU4    3070     CUDA    2       284     50/0    70      1095    7800    92     .[0m                                                   
.[1;36m00:00:01.[0m .[1m[2022-03-30 16:42:27..[0m.[0m421.[0m.[1m].[0m .[36mGPU5    2060     CUDA    2       284     47/0    70      1065    7800    71     .[0m                                                   
.[1;36m00:00:01.[0m .[1m[2022-03-30 16:42:27..[0m.[0m421.[0m.[1m].[0m .[1;36m                                                                         481    .[0m                                                 
.[1;36m00:00:01.[0m .[1m[2022-03-30 16:42:27..[0m.[0m421.[0m.[1m].[0m .[0m.[0m                                                                                                                                     
.[1;36m00:00:01.[0m .[1m[2022-03-30 16:42:27..[0m.[0m421.[0m.[1m].[0m .[1mID      BOARD    HASHRATE/W    HASHRATE      AVERAGE       SHARES       RATE    .[0m                                                     
.[1;36m00:00:01.[0m .[1m[2022-03-30 16:42:27..[0m.[0m422.[0m.[1m].[0m .[36mGPU0    gfx1032  348.67 kH/W   32.08 MH/s    32.26 MH/s    0/0/0        100.00% .[0m                                                   
.[1;36m00:00:01.[0m .[1m[2022-03-30 16:42:27..[0m.[0m422.[0m.[1m].[0m .[36mGPU1    gfx1030  1232.44 kH/W  65.32 MH/s    65.74 MH/s    1/0/0        100.00% .[0m                                                   
.[1;36m00:00:01.[0m .[1m[2022-03-30 16:42:27..[0m.[0m422.[0m.[1m].[0m .[36mGPU2    3070     547.78 kH/W   62.45 MH/s    61.90 MH/s    0/0/0        100.00% .[0m                                                   
.[1;36m00:00:01.[0m .[1m[2022-03-30 16:42:27..[0m.[0m422.[0m.[1m].[0m .[36mGPU3    3070     529.57 kH/W   62.49 MH/s    61.89 MH/s    0/0/0        100.00% .[0m                                                   
.[1;36m00:00:01.[0m .[1m[2022-03-30 16:42:27..[0m.[0m422.[0m.[1m].[0m .[36mGPU4    3070     555.64 kH/W   62.23 MH/s    61.68 MH/s    1/0/0        100.00% .[0m                                                   
.[1;36m00:00:01.[0m .[1m[2022-03-30 16:42:27..[0m.[0m422.[0m.[1m].[0m .[36mGPU5    2060     419.36 kH/W   35.65 MH/s    35.12 MH/s    1/0/0        100.00% .[0m                                                   
.[1;36m00:00:01.[0m .[1m[2022-03-30 16:42:27..[0m.[0m422.[0m.[1m].[0m .[1;36m                 605.58 kH/W   320.21 MH/s   318.58 MH/s   3/0/0        100.00% .[0m                                                 
.[1;36m00:00:01.[0m .[1m[2022-03-30 16:42:27..[0m.[0m422.[0m.[1m].[0m .[4m                                                                                .[0m                                                     
.[1;36m00:00:01.[0m .[1m[2022-03-30 16:42:27..[0m.[0m422.[0m.[1m].[0m .[1mSHARES PER MINUTE: 0.00               POOL HASHRATE: 0.00 H/s.[0m                                                                       

[sp_]

Miner extra config arguments

--all-platforms 1
--cl-devices [0,1]
--cuda-devices [0,1,2,3]
--algo ethash
--log

why don't you just run with:

--algo ethash
--log
--no-ansi

do you need to exclude some cards?

To reverse the order of the AMD gpu's you can probably do:

--cl-devices [1,0]

[Movalis]

Miner extra config arguments

--all-platforms 1
--cl-devices [0,1]
--cuda-devices [0,1,2,3]
--algo ethash
--log

why don't you just run with:

--algo ethash
--log
--no-ansi

do you need to exclude some cards?

To reverse the order of the AMD gpu's you can probably do:

--cl-devices [1,0]

Yes, need to exclude 2 Cuda devices --cl-devices [1,0] didn't work out

[Movalis]

For reference

I put just GPU0 mining . It's the 6600XT. On HiveOS it appear on 6800XT line

--cl-devices [ 0 ]

on miner side:

00:00:01 [2022-03-31 17:13:18.015] GPU0    gfx1032  OpenCL  0       71      33/0    68      1260    1074    30                                                                                                    
00:00:01 [2022-03-31 17:13:18.015] GPU1    3070     CUDA    13      284     43/0    70      1095    7800    96                                                                                                    
00:00:01 [2022-03-31 17:13:18.015] GPU2    3070     CUDA    13      284     48/0    92      1095    7800    99                                                                                                    
00:00:01 [2022-03-31 17:13:18.015] GPU3    3070     CUDA    2       284     48/0    86      1095    7800    94                                                                                                    
00:00:01 [2022-03-31 17:13:18.015] GPU4    2060     CUDA    13      284     47/0    70      1065    7800    71                                                                                                    
00:00:01 [2022-03-31 17:13:18.015]                                                                          390                                                                                                    
00:00:01 [2022-03-31 17:13:18.015]                                                                                                                                                                                
00:00:01 [2022-03-31 17:13:18.015] ID      BOARD    HASHRATE/W    HASHRATE      AVERAGE       SHARES       RATE                                                                                                    
00:00:01 [2022-03-31 17:13:18.015] GPU0    gfx1032  1034.51 kH/W  32.07 MH/s    32.28 MH/s    0/0/0        100.00%                                                                                                
00:00:01 [2022-03-31 17:13:18.015] GPU1    3070     543.56 kH/W   62.51 MH/s    61.89 MH/s    0/0/0        100.00%                                                                                                
00:00:01 [2022-03-31 17:13:18.015] GPU2    3070     520.55 kH/W   62.47 MH/s    61.89 MH/s    0/0/0        100.00%                                                                                                
00:00:01 [2022-03-31 17:13:18.015] GPU3    3070     541.32 kH/W   62.25 MH/s    61.70 MH/s    0/0/0        100.00%                                                                                                
00:00:01 [2022-03-31 17:13:18.015] GPU4    2060     419.42 kH/W   35.65 MH/s    35.13 MH/s    0/0/0        100.00%                                                                                                
00:00:01 [2022-03-31 17:13:18.015]                  611.87 kH/W   254.95 MH/s   252.89 MH/s   0/0/0        100.00%


https://imgur.com/a/ccZMLAe          

Thanks                                                                                      

[sp_]

I put just GPU0 mining . It's the 6600XT. On HiveOS it appear on 6800XT line
--cl-devices [ 0 ]

The device order has been flipped in the autodetect, but not in the manual selection for opencl. I think I will fix this in the next release. Thanks for reporting

[Movalis]

Thanks in advance

Cheers

[KillrBee]

Just as an update / FYI:

I'm still getting GPU timeouts on my AMD cards when mining on 2Miners.  The mining time is quite random and can be anywhere from 1-24 hours with 1 - 3 cards timing out at the same time in the mixed AMD/NVidia rig (4 AMD cards).  My AMD card running in windows will still crash occasionally, but it takes a while longer for it to happen (although the card quite often drops power to 15 watts in windows so there's a different pattern of disfunction which may hide the mining issue).

I waited on sending an update until I had updated the HiveOS kernel to the latest version, and it's still crashing.  Although, the new AMD drivers / Linux Kernel does seem to improve the performance on the AMD cards, or at least reduces the variability in performance, with the dips in hashrate being higher than before.

The new Linux kernel is letting the miner run CUDA 11.5 at a consistent 130+ MH/s, although with the temperatures climbing, I'm going to have to keep an eye on thermals vs. pure hash power; right now I can push the card to 134 - 137 MH/s average at the pool, but Memory Temps are creeping up into the 80's with ambient being 12-15 Celsius.

[sp_]

Try to upgrade to the latest drivers. On linux you can try to add swap.
We are reducing the number of releases but still working on improvements.
Note that we have upgraded the atiadlxx.dll to a later version, so copying the exe file only into an older folder with an old atiadlxx.dll might have issues.

[KillrBee]

Try to upgrade to the latest drivers. On linux you can try to add swap.
We are reducing the number of releases but still working on improvements.
Note that we have upgraded the atiadlxx.dll to a later version, so copying the exe file only into an older folder with an old atiadlxx.dll might have issues.

I'm running the 5.11.1001 AMD drivers that HiveOS provides -- I've messed around with updating the AMD drivers before and while it's possible -- there's always something that breaks because of it.  I added 48G of swap, but 'free -m' is showing I don't need any swap and there is still roughly 12 GB of free RAM. I am running the TBM code supplied by hive for version 1.61, so all the files are what is found within the distro.

I punched up the voltages and switched mining over to MiningPoolHub to see if there was any difference and I still had an AMD GPU timeout on me... Next step is to drop the intensity values on a couple of cards to see if they remain functional and only the higher intensity cards fail.

I'm also getting a 3090Ti delivered in a couple of days -- I'm curious to see how much I can crank out of that card!

[sp_]

Team Black Miner

v1.62
1. Improved the rejected check before exit.
2. Fix device order when using the --cl-devices to select gpus.
3. Fixed rare crash on linux
4. Remove rejected shares at the hiveon pool.

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

TeamBlackMiner_1_62_cuda_11_4.7z
https://www.virustotal.com/gui/file/3fc83b159e73a838496b267857e2217fbb4a5ac7960d1b8893121288ab24c1b0?nocache=1

TeamBlackMiner_1_62_cuda_11_5.7z
https://www.virustotal.com/gui/file/e708aa42fbc549570bf2e842ad5629260096f7dd66a6392708f89e9117db0c82?nocache=1

TeamBlackMiner_1_62_Ubuntu_18_04_Cuda_11_4.tar.xz
https://www.virustotal.com/gui/file/7e3e465c27d84ee5d4b7c1b884439c962a5f300b980dc78d84d5f7f4f3eb3c9c?nocache=1

TeamBlackMiner_1_62_Ubuntu_18_04_Cuda_11_5.tar.xz
https://www.virustotal.com/gui/file/3ffcab3ae365612e4206952e391bb4a882a57509cd3cd6cd2ea3ef8427f90afe?nocache=1

------------------------------------------

I put just GPU0 mining . It's the 6600XT. On HiveOS it appear on 6800XT line
--cl-devices [ 0]

fixed in 1.62

Next step is to drop the intensity values on a couple of cards to see if they remain functional and only the higher intensity cards fail

In v1.62 we have fixed some bugs that where present in the linux release only. Hopefully your rig will work 100% now. Mixed cards rigs NVIDIA/AMD high intensity.

I'm also getting a 3090Ti delivered in a couple of days -- I'm curious to see how much I can crank out of that card!

Please keep us updated..

[STSMiner]

Team Black Miner

v1.62
1. Improved the rejected check before exit.
2. Fix device order when using the --cl-devices to select gpus.
3. Fixed rare crash on linux
4. Remove rejected shares at the hiveon pool.

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

TeamBlackMiner_1_62_cuda_11_5.7z
https://www.virustotal.com/gui/file/f42ad36828c37855bad3ae492fffbd4ec3d5c537bbc47e65def7d5f43a54b038?nocache=1

TeamBlackMiner_1_62_cuda_11_4.7z
https://www.virustotal.com/gui/file/9248cecfb0c325fe8c606825d9c3a9a0917ee81a286572b927f327db6bd43189?nocache=1

TeamBlackMiner_1_62_Ubuntu_18_04_Cuda_11_4.tar.xz
https://www.virustotal.com/gui/file/7e3e465c27d84ee5d4b7c1b884439c962a5f300b980dc78d84d5f7f4f3eb3c9c?nocache=1

TeamBlackMiner_1_62_Ubuntu_18_04_Cuda_11_5.tar.xz
https://www.virustotal.com/gui/file/3ffcab3ae365612e4206952e391bb4a882a57509cd3cd6cd2ea3ef8427f90afe?nocache=1

------------------------------------------

I put just GPU0 mining . It's the 6600XT. On HiveOS it appear on 6800XT line
--cl-devices [ 0]

fixed in 1.62

Next step is to drop the intensity values on a couple of cards to see if they remain functional and only the higher intensity cards fail

In v1.62 we have fixed some bugs that where present in the linux release only. Hopefully your rig will work 100% now. Mixed cards rigs NVIDIA/AMD high intensity.

I'm also getting a 3090Ti delivered in a couple of days -- I'm curious to see how much I can crank out of that card!

Please keep us updated..

@sp_

Possible bug (see images 1.61 vs 1.62) ?


Same issue with the Cuda 11.5 version as well for Windows where the temp, fan, core etc is not being displayed in the output in version 1.62.

Look forward to a fix.