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

KillrBee

jr. member

Activity: 139

Merit: 3

I'm just going to leave this here. Shocked

https://imgur.com/a/SUl8U3U

poisons77

newbie

Activity: 14

Merit: 0

I still have problems.
After exiting the first time because of a Dag file not verified, I restarted the miner and I got another error, it sees only 3GB of memory on 2 GPU.
Restarting the miner didn't solve the problem, I could fix only rebooting the rig. I use TBM 1.18 on HiveOs latest version.
I also use CPU mining with cpuminer-opt-gr

here's the screenshot
https://ibb.co/mXyvnXJ

abanamat

jr. member

Activity: 274

Merit: 1

Quote from: BitBlitzer on October 18, 2021, 03:07:31 PM

Yea I have already broken that!

I have a few cards with aluminium shims instead of thermal pads and can max the memory to +2000. Gives around 111.5MH/s (reported speed). Memory temps drop like crazy with aluminium/copper shims.

That would be great if you tell us how to do it! Wink

poisons77

newbie

Activity: 14

Merit: 0

Quote from: hashatharias on October 23, 2021, 09:01:17 PM

if this doesn't work, do this (right click in Shell-in-a-box, paste from browser, then hit Return key to validate the command)

Code:

cd /hive/miners/teamblackminer/1.16/
mv TBMiner TBMiner.bak
wget https://github.com/sp-hash/TeamBlackMiner/releases/download/v1.18/TeamBlackMiner_1_18_Ubuntu_18_04_Cuda_11_4.zip
unzip TeamBlackMiner_1_18_Ubuntu_18_04_Cuda_11_4.zip
cp /hive/miners/teamblackminer/1.16/TeamBlackMiner_1_18_Ubuntu_18_04_Cuda_11_4/TBMiner /hive/miners/teamblackminer/1.16/
chmod +x TBMiner

Then restart miner in HiveOS

Thanks for your time, it worked flawlessy

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: Ramsete2 on October 24, 2021, 05:33:17 AM

I know, but Crazypool is still the most profitable pool for me...

https://www.miningpoolsprofits.com/

Crazypool is looking good, but the pool is small, so the payouts from day to day will fluctate more than on the other pools.

v1.19 preview cuda 11_5 optimized

Kernel 8 seems to be doing around +6.5% compared to kernel 0 at --xintensity 96. Half the stales from 1.18 and still run at good speeds. (rtx 2060 mobile). On higher intensities the difference is smaller.

[moderator's note: consecutive posts merged]

Ramsete2

jr. member

Activity: 87

Merit: 5

Quote from: sp_ on October 24, 2021, 04:43:40 AM

Quote from: Ramsete2 on October 24, 2021, 04:41:27 AM

I guess most of the stales on TBMiner were caused during Epoch switch.
Better to find a way to reduce them.

The epoch switching code is working fine on ETH+ZIL on ezil.me, but there might be an issue here. In v1.19 we will have a reset gpu clock feature when generating the dag file.. Should improve rtx cards with high clocks. v1.19 will also have a kernel #9 cuda 11_5 optimized that can improve speed on some cards.

Crazypool doesn't pay for stale shares. TBM works best on pools that pay for stales..

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

I know, but Crazypool is still the most profitable pool for me...

https://www.miningpoolsprofits.com/

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: Ramsete2 on October 24, 2021, 04:41:27 AM

I guess most of the stales on TBMiner were caused during Epoch switch.
Better to find a way to reduce them.

The epoch switching code is working fine on ETH+ZIL on ezil.me, but there might be an issue here. In v1.19 we will have a reset gpu clock feature when generating the dag file.. Should improve rtx cards with high clocks. v1.19 will also have a kernel #9 cuda 11_5 optimized that can improve speed on some cards.

Crazypool doesn't pay for stale shares. TBM works best on pools that pay for stales..

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

Ramsete2

jr. member

Activity: 87

Merit: 5

I guess most of the stales on TBMiner were caused during Epoch switch.
Better to find a way to reduce them.

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: Ramsete2 on October 24, 2021, 04:08:46 AM

Update after about one day of GMiner vs TBMiner competition Grin

TBMiner (ver 1.18):

GMiner (ver 2.70):

TBminer - Gminer 1-0

Ramsete2

jr. member

Activity: 87

Merit: 5

Update after about one day of GMiner vs TBMiner competition Grin

TBMiner (ver 1.18):

GMiner (ver 2.70):

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: dle378 on October 24, 2021, 01:04:20 AM

Should I revert back to 1.17 until that bug is fixed in the next release?

No need, the bug is only displaying the wrong pool speed, and has nothing to do with performance. In v1.19 poolspeed will be disabled for vardiff pools.

Quote from: dle378 on October 24, 2021, 01:04:20 AM

Is xintensity 512 too low for 2miners?

you can try 800

dle378

copper member

Activity: 77

Merit: 0

Quote from: ?? on ??

Quote from: dle378 on October 23, 2021, 11:40:39 PM

Is there supposed to be a significant variance between the Pool Hashrate and the Hashrate reporting within TBM?

You seem to be abit unlucky here. Normally it will even out over time. Higher difficulty, higher fluctation in the hashrate poolside. v1.18 has a bug in the stats for pool that use vardiff. F.eks Nicehash.

Should I revert back to 1.17 until that bug is fixed in the next release?

Is xintensity 512 too low for 2miners?

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: Doucesti on October 23, 2021, 11:04:48 PM

Am I the only one who doesnt understand how to disable one of my two GPU?? Shocked

Tried
-Y 0
-Y 1

Use brackets around the selection

--Y [0,1]

Quote from: dle378 on October 23, 2021, 11:40:39 PM

Is there supposed to be a significant variance between the Pool Hashrate and the Hashrate reporting within TBM?

You seem to be abit unlucky here. Normally it will even out over time. Higher difficulty, higher fluctation in the hashrate poolside. v1.18 has a bug in the stats for pool that use vardiff. F.eks Nicehash.

Quote from: hashatharias on October 23, 2021, 09:01:17 PM

1345m [2021-10-23 22:13:06.008] 0.00 H/W 693.68 MH/s 694.60 MH/s 9678/41/200 (99.58%)
Should I be concerned about the rejected shares ?

99.58% is a good result on nicehash. I see that you run with --xintensity 224, you can lower the xintensity to remove stales, but then the hashrate will drop as well.

[moderator's note: consecutive posts merged]

dle378

copper member

Activity: 77

Merit: 0

Been running TBM 1.18 (CUDA 11.4) for 7.5+ hours on 2miners.com with the specs configured below:

441m [2021-10-23 23:31:48.382] ID   BOARD   TYPE     KERN XINT   TEMP FAN   CORE MEM   WATT
441m [2021-10-23 23:31:48.382] GPU0   3060Ti   Cuda     6     512   62/0     70   1417    8092   153
441m [2021-10-23 23:31:48.382] GPU1   3060Ti   Cuda     5     512   66/0     70   1671    8092   184
441m [2021-10-23 23:31:48.382] GPU2   3060Ti   Cuda     2     512   69/0     70   1433    8092   153
441m [2021-10-23 23:31:48.382] GPU3   3060Ti   Cuda     5     512   57/0     70   1700    8092   184
441m [2021-10-23 23:31:48.382] GPU4   3060Ti   Cuda     2     512   67/0     70   1494    8092   153
441m [2021-10-23 23:31:48.382] GPU5   3060Ti   Cuda     5     512   62/0     65   1443    8092   153
441m [2021-10-23 23:31:48.382]                              980
441m [2021-10-23 23:31:48.382] ID   BOARD   HASHRATE/W   HASHRATE     AVERAGE      SHARES
441m [2021-10-23 23:31:48.382] GPU0   3060Ti   425.14 kH/W   65.05 MH/s   65.05 MH/s   170/0/2 (100.00)
441m [2021-10-23 23:31:48.382] GPU1   3060Ti. 353.51 kH/W   65.05 MH/s   65.04 MH/s   183/0/1 (100.00)
441m [2021-10-23 23:31:48.382] GPU2   3060Ti   425.05 kH/W   65.03 MH/s   65.03 MH/s   186/0/1 (100.00)
441m [2021-10-23 23:31:48.382] GPU3   3060Ti   353.50 kH/W   65.04 MH/s   65.04 MH/s   175/0/1 (100.00)
441m [2021-10-23 23:31:48.382] GPU4   3060Ti   425.05 kH/W   65.03 MH/s   65.03 MH/s   183/0/1 (100.00)
441m [2021-10-23 23:31:48.382] GPU5   3060Ti   425.17 kH/W   65.05 MH/s   65.05 MH/s   184/0/1 (100.00)
441m [2021-10-23 23:31:48.382]         401.24 kH/W   390.25 MH/s   390.24 MH/s   1081/0/7 (100.00)
441m [2021-10-23 23:31:48.382]
441m [2021-10-23 23:31:48.382] COST: 0.98 KWH (0.08USD)         POOL HASHRATE: 357.31 MH/s

Is there supposed to be a significant variance between the Pool Hashrate and the Hashrate reporting within TBM?

Doucesti

newbie

Activity: 24

Merit: 0

Am I the only one who doesnt understand how to disable one of my two GPU?? Shocked

Tried
-Y 0
-Y 1

This miner seems faster for one of my two gpus, that's the reason I'm asking

hashatharias

newbie

Activity: 12

Merit: 0

Quote from: dedizonesv2 on October 23, 2021, 05:25:01 AM

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

When for any reason the miner exits, HiveOs stucks on the message:
"trying to release TIME_WAIT sockets"

Using HiveOs last version and TeamBlackMiner 1.16 (last version available on HiveOs)

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

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 .. Wink

if this doesn't work, do this (right click in Shell-in-a-box, paste from browser, then hit Return key to validate the command)

Code:

cd /hive/miners/teamblackminer/1.16/
mv TBMiner TBMiner.bak
wget https://github.com/sp-hash/TeamBlackMiner/releases/download/v1.18/TeamBlackMiner_1_18_Ubuntu_18_04_Cuda_11_4.zip
unzip TeamBlackMiner_1_18_Ubuntu_18_04_Cuda_11_4.zip
cp /hive/miners/teamblackminer/1.16/TeamBlackMiner_1_18_Ubuntu_18_04_Cuda_11_4/TBMiner /hive/miners/teamblackminer/1.16/
chmod +x TBMiner

Then restart miner in HiveOS

Regarding my own setup, what do you think of this

Code:

  1345m [2021-10-23 22:13:06.008] usa-east.nicehash.com (ethash)    PING: 25ms    DIFFICULTY: 1.90     EPOCH: 449
  1345m [2021-10-23 22:13:06.008]                                                                                 
  1345m [2021-10-23 22:13:06.008] 
  1345m [2021-10-23 22:13:06.008] ID      BOARD   TYPE    KERN    XINT    TEMP    FAN     CORE    MEM     WATT
  1345m [2021-10-23 22:13:06.008] GPU0   3070    Cuda    4       224     0/0     0       0       0       0
  1345m [2021-10-23 22:13:06.008] GPU1   3080    Cuda    7       224     0/0     0       0       0       0
  1345m [2021-10-23 22:13:06.008] GPU2   3080    Cuda    6       224     0/0     0       0       0       0
  1345m [2021-10-23 22:13:06.008] GPU3   3080    Cuda    7       224     0/0     0       0       0       0
  1345m [2021-10-23 22:13:06.008] GPU4   3080    Cuda    6       224     0/0     0       0       0       0
  1345m [2021-10-23 22:13:06.008] GPU5   3080    Cuda    3       224     0/0     0       0       0       0
  1345m [2021-10-23 22:13:06.008] GPU6   3080    Cuda    6       224     0/0     0       0       0       0
  1345m [2021-10-23 22:13:06.008]                                                                      0
  1345m [2021-10-23 22:13:06.008] 
  1345m [2021-10-23 22:13:06.008] ID      BOARD   HASHRATE/W      HASHRATE        AVERAGE         SHARES
  1345m [2021-10-23 22:13:06.008] GPU0   3070    0.00 H/W        63.58 MH/s      64.47 MH/s      871/3/24 (99.66%)
  1345m [2021-10-23 22:13:06.008] GPU1   3080    0.00 H/W        104.78 MH/s     104.79 MH/s     1494/6/35 (99.60%)
  1345m [2021-10-23 22:13:06.008] GPU2   3080    0.00 H/W        103.74 MH/s     103.76 MH/s     1511/5/29 (99.67%)
  1345m [2021-10-23 22:13:06.008] GPU3   3080    0.00 H/W        105.36 MH/s     105.39 MH/s     1454/8/31 (99.45%)
  1345m [2021-10-23 22:13:06.008] GPU4   3080    0.00 H/W        105.41 MH/s     105.36 MH/s     1452/5/19 (99.66%)
  1345m [2021-10-23 22:13:06.008] GPU5   3080    0.00 H/W        105.38 MH/s     105.41 MH/s     1446/8/27 (99.45%)
  1345m [2021-10-23 22:13:06.008] GPU6   3080    0.00 H/W        105.42 MH/s     105.42 MH/s     1450/6/35 (99.59%)
  1345m [2021-10-23 22:13:06.008]              0.00 H/W        693.68 MH/s     694.60 MH/s     9678/41/200 (99.58%)
  1345m [2021-10-23 22:13:06.008]                                                                                 
  1345m [2021-10-23 22:13:06.008] SHARES PER MINUTE: 7.20                 POOL HASHRATE: 980.88 MH/s

Should I be concerned about the rejected shares ?

joaogti36

full member

Activity: 162

Merit: 100

so..
anyone with nvidia 1660 super with hynix mem tested the miner for the hashrate?

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: onimorza on October 23, 2021, 04:26:16 PM

Only gpu 2, 3 & 4 should be set as to work with TBM.

--cl-devices [2,3,4]

Quote from: ayiphelmy on October 23, 2021, 04:30:11 PM

i use nb miner with mem tweak get 34.xx mhs

TBM should be faster on the gtx 1070. Memtweak for the gtx 1070ti has not been implemented yet, but you can use the t-rex to get the cards to tweak correctly for free.

nbminer ~34MHASH -1% fee
TBminer+trexmemtweak ~35MHASH -0.5% fee

[moderator's note: consecutive posts merged]

ayiphelmy

copper member

Activity: 416

Merit: 105

Quote from: ?? on ??

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"

i use nb miner with mem tweak get 34.xx mhs

onimorza

newbie

Activity: 5

Merit: 0

Quote from: sp_ on October 23, 2021, 04:06:35 PM

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

That is the command to set OpenCL to those AMD's.
I'm trying to disable gpu 0 & 1 from working with TBM as those should work with another miner.
Only gpu 2, 3 & 4 should be set as to work with TBM.

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