⛏Team Black Miner (ETHB3 ETHW ETC VTC KAWPOW FIROPOW EVRPROGPOW MEOWPOW +dual)

[poisons77]

Use fileZilla upload new version TBMiner and upload news version in dir: /hive/miners/teamblackminer/1.16/ and if you ask to overwrite with a new version you say => yes
while waiting for them to update their mirror sometimes they are fast other times not ..

Thanks dedizonesv2, I'll give it a try

[nemzzy668]

Finally got 1.18 working in HiveOs, but can confirm stats still blank and showing 0 for temps,fan,core

[Ramsete2]

Finally got 1.18 working in HiveOs, but can confirm stats still blank and showing 0 for temps,fan,core

Same bug on mmpOS

[sp_]

What's the output of

$ nvidia-smi ?

[nemzzy668]

What's the output of

$ nvidia-smi ?

https://prnt.sc/1x6476f

[sp_]

I added the issue at github.

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

[nemzzy668]

I added the issue at github.

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

Thanks bud

[sp_]

It happened already twice, once exited because one card was stuck at 0, and once as the screenshot below, one GPU dag verification failed.

V1.16 has a too high default xintensity for the rx570/580 cards.

You can try --xintensity 78 or upgrade to v1.18. In v1.18 the default will run at same speed, but half of the stale shares.

[ayiphelmy]

stale share 1% and i dont see any error

Is the miner restarting often. I see a dip in reported hashrate, lost internet connection?
Look for gpu timed out messages in the log.

all normal internet using dedicated service, that dip in graph because 2 rig changing software using tbminer, and 1 rig lots try to adjust xintensity but that only for 30 minute after that i let it run for maybe 8 hours, 1 rig 3090 and 1 rig 2080ti

[sp_]

v1.19 will have reset clock on dag generation. So if you set the clock with lock clock, the program will automaticly reset to default on epoc change/dag generation.

[KillrBee]

I'm doing some Max.Performance testing on version 1.18 with my 3090.  Here is a screen cap of the results and setup values for the OC.

One thing to note is that there is a large variance on intensity and power, setting the intensity too high with a high OC will drop power levels due to throttling (even though the card doesn't report any performance limits other than utilization, which is normal when the card is being used for mining).

In this run I have the intensity set to 2200 - kennel selected as 7

[sp_]

I'm doing some Max.Performance testing on version 1.18 with my 3090.  Here is a screen cap of the results and setup values for the OC.

One thing to note is that there is a large variance on intensity and power, setting the intensity too high with a high OC will drop power levels due to throttling (even though the card doesn't report any performance limits other than utilization, which is normal when the card is being used for mining).

In this run I have the intensity set to 2200 - kennel selected as 7

Really nice speed, but --xintensity 2200  won't work on all mining pools.

For new miners, you should read our faq

https://github.com/sp-hash/TeamBlackMiner/blob/main/FAQ.md


The trottle could be because the memory temperature get too hot. You feed the card too much work and power

[momanz]

Hi,

I've just noticed Teamblack was integrated into HiveOS with version 1.16

I have only AMD cards RX 6600xt, RX 580, RX 6700xt and RX 5700

All my cards are recognized except the RX 580 models (I have 3 of them).
Did anyone have the same effect on HiveOs ?

To bypass that for now, I've configured Teamredmine on RX 580 series and Teamblack on all other models.

Regards

I have the same problem. I have 2x RX580 1x RX570 1x RX5600XT 2x RX5700 1x 6700XT. The NAVI cards are recognized and run well, but the Polaris cards are not recognized. Also I have no stats showing.

Running HiveOS and tried TBM versions 1.16 and 1.18. same behavior on both. I ran the miner directly from the shell. Same behavior. I've noticed that there is a "Cannot open shared object file" message the occurs occasionally. Maybe this is related?

Are there any additional steps I can take to help debug?

Code:

    12m [2021-10-23 08:44:06.004] Cannot open shared object file
    12m [2021-10-23 08:44:06.004]
    12m [2021-10-23 08:44:06.004]
    12m [2021-10-23 08:44:06.004] miningpoolhub.com (ethash)    PING: 95ms    DIFFICULTY: 3.00     EPOCH: 449
    12m [2021-10-23 08:44:06.004]
    12m [2021-10-23 08:44:06.004]
    12m [2021-10-23 08:44:06.004] ID    BOARD   TYPE    KERN    XINT    TEMP    FAN     CORE    MEM     WATT
    12m [2021-10-23 08:44:06.004] GPU0  gfx1010 OpenCL  0       64      0/0     0       0       0       0
    12m [2021-10-23 08:44:06.004] GPU1  gfx1010 OpenCL  0       64      0/0     0       0       0       0
    12m [2021-10-23 08:44:06.004] GPU2  gfx1010 OpenCL  0       64      0/0     0       0       0       0
    12m [2021-10-23 08:44:06.004] GPU3  gfx1031 OpenCL  0       64      0/0     0       0       0       0
    12m [2021-10-23 08:44:06.004]                                                                       0
    12m [2021-10-23 08:44:06.004]
    12m [2021-10-23 08:44:06.004] ID    BOARD   HASHRATE/W      HASHRATE        AVERAGE         SHARES
    12m [2021-10-23 08:44:06.004] GPU0  gfx1010 0.00 H/W        56.02 MH/s      56.05 MH/s      6/0/0 (100.00%)
    12m [2021-10-23 08:44:06.004] GPU1  gfx1010 0.00 H/W        56.18 MH/s      56.21 MH/s      4/0/0 (100.00%)
    12m [2021-10-23 08:44:06.004] GPU2  gfx1010 0.00 H/W        42.01 MH/s      42.01 MH/s      4/0/0 (100.00%)
    12m [2021-10-23 08:44:06.004] GPU3  gfx1031 0.00 H/W        49.41 MH/s      49.37 MH/s      3/0/0 (100.00%)
    12m [2021-10-23 08:44:06.004]               0.00 H/W        203.62 MH/s     203.64 MH/s     17/0/0 (100.00%)
    12m [2021-10-23 08:44:06.004]

[sp_]

the shell. Same behavior. I've noticed that there is a "Cannot open shared object file" message the occurs occasionally. Maybe this is related?

We are currently using the AMD Display (ADL) Library to read AMD stats. This is an outdated library, and we are working to add another way to do the stats. The error message is probably from a failing adl request. Improved support for AMD cards is comming, Higher priority than LHR NVIDIA support at the moment.

[adiman73]

I noticed that the Nvidia 1060 6Gb cards do not work.
Do I need to set anything to work?

[sp_]

I noticed that the Nvidia 1060 6Gb cards do not work.
Do I need to set anything to work?

1060 6gb should work. Whats your driver version and os?. The cuda 11.5 build needs the latest driver.

[opnep]

v1.19 will have reset clock on dag generation. So if you set the clock with lock clock, the program will automaticly reset to default on epoc change/dag generation.

Thanks this is exactly what I was hoping for. Currently mining on v.1.18 and noticed with yesterday's DAG change half of my cards starting pumping out invalids (after DAG was generated with overclock). Hopefully this clears that up

[onimorza]

I have a split miner on HiveOS on which gpu's 0 and 1 work on a different miner (TRM) than gpu's 2, 3 and 4 (GMiner).
I wanted to switch gpu's 2, 3 and 4 to TeamBlackMiner.
In the miner configuration of TBM I can disable gpu's 0 and 1 by adding 0,1 in the appropriate field.
But this is not really disabling those gpu's. TBM is starting them up together with the other miner, resulting in a rig crash.
Any suggestions?

[sp_]

I have a split miner on HiveOS on which gpu's 0 and 1 work on a different miner (TRM) than gpu's 2, 3 and 4 (GMiner).
I wanted to switch gpu's 2, 3 and 4 to TeamBlackMiner.
In the miner configuration of TBM I can disable gpu's 0 and 1 by adding 0,1 in the appropriate field.
But this is not really disabling those gpu's. TBM is starting them up together with the other miner, resulting in a rig crash.
Any suggestions?

Use brackets around the selection

--cuda-devices [0,1]

Make sure you don't use it with  --auto-detect 

[ayiphelmy]

i think a lot of room to improve 1070ti hashrate... maybe u can consider change something