Team Black Miner (ETHW ETC Vertcoin Ravencoin Zilliqa +dual +tripple mining ) - page 81.

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: onimorza on October 23, 2021, 03:54:16 PM

To understand better for myself; my 5 gpu's are all AMD's, and with your command I would set those first 2 as to use the Nvidia Cuda so disabling them AMD's, right?
Unfortunately it does not seem to work.

For amd you need to use --cl-devices [0,1]

Quote from: ayiphelmy on October 23, 2021, 03:18:36 PM

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

1070ti needs memtweak. You can run an old t-rex miner on ultra low intensity in the backround. will boost the hashrate from 32-33 to 34-35. For the gtx 1080 and gtx 1080ti use "the pill"

[moderator's note: consecutive posts merged]

onimorza

newbie

Activity: 5

Merit: 0

Quote from: sp_ on October 23, 2021, 01:42:16 PM

Use brackets around the selection

--cuda-devices [0,1]

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

To understand better for myself; my 5 gpu's are all AMD's, and with your command I would set those first 2 as to use the Nvidia Cuda so disabling them AMD's, right?
Unfortunately it does not seem to work.
I couldn't get the brackets into the hiveos "disable gpu's" field; so added your command to the "Extra config arguments" field. Now it doesn't even load any gpu with TBM. Only the first 2 with TRM.
Maybe it's a hiveos bug.
I've also noticed they are still on 1.16 whilst you are already at 1.18.

ayiphelmy

copper member

Activity: 416

Merit: 105

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

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: onimorza on October 23, 2021, 01:36:49 PM

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

onimorza

newbie

Activity: 5

Merit: 0

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?

opnep

newbie

Activity: 2

Merit: 0

Quote from: sp_ on October 23, 2021, 09:24:20 AM

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

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: adiman73 on October 23, 2021, 12:07:22 PM

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.

adiman73

newbie

Activity: 11

Merit: 0

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

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: momanz on October 23, 2021, 10:57:30 AM

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.

momanz

newbie

Activity: 15

Merit: 1

Quote from: beber75 on October 22, 2021, 05:12:58 PM

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_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: KillrBee on October 23, 2021, 09:53:01 AM

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

KillrBee

jr. member

Activity: 139

Merit: 3

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_

legendary

Activity: 2926

Merit: 1087

Team Black developer

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.

ayiphelmy

copper member

Activity: 416

Merit: 105

Quote from: ?? on ??

Quote from: ayiphelmy on October 23, 2021, 01:43:04 AM

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_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: poisons77 on October 23, 2021, 04:03:09 AM

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.

nemzzy668

newbie

Activity: 5

Merit: 0

Quote from: sp_ on October 23, 2021, 06:32:03 AM

I added the issue at github.

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

Thanks bud

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

I added the issue at github.

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

nemzzy668

newbie

Activity: 5

Merit: 0

Quote from: sp_ on October 23, 2021, 06:12:00 AM

What's the output of

$ nvidia-smi ?

https://prnt.sc/1x6476f

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

What's the output of

$ nvidia-smi ?

Ramsete2

jr. member

Activity: 87

Merit: 5

Quote from: nemzzy668 on October 23, 2021, 05:51:47 AM

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

Same bug on mmpOS

Topic: Team Black Miner (ETHW ETC Vertcoin Ravencoin Zilliqa +dual +tripple mining ) - page 81. (Read 35053 times)