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

[PsKminer]

i'm currently using TREX for my 3080TI and 3080 TBMiner and here are the results, driver 497.09 :

[sp_]

I guess my core clock and power settings where too high for the t-rex miner, been running it for a while and it recovered up to ~70 ish. But tbm without LHR code is doing 69MHASH. Perhaps I need --lock-cclock to make it work? Please share your settings..

I am running

core +0 (default setting) trottles abit
mem 10700 (+1350)
tdp 75%
p0 state

[PsKminer]

[sp_]

Your card is abit better than mine, but powerlmit 65 instead of 75 seems to help. But 75 is needed to do 100+ stable.

[long2905]

I guess my core clock and power settings where too high for the t-rex miner, been running it for a while and it recovered up to ~70 ish. But tbm without LHR code is doing 69MHASH. Perhaps I need --lock-cclock to make it work? Please share your settings..

I am running

core +0 (default setting) trottles abit
mem 10700 (+1350)
tdp 75%
p0 state

here on latest 797.09
https://i.imgur.com/HSNA37X.png

my configs --mt 2,0,0,0,0,6 --fan 85 --lock-cclock 0,1200,1200,1200,1200,0 --cclock 150,0,0,0,0,200 --mclock 400,1250,1400,1750,1900,500 --pl 90,105,0,116,112,90
3080ti is 1900

[dedizonesv2]

I guess my core clock and power settings where too high for the t-rex miner, been running it for a while and it recovered up to ~70 ish. But tbm without LHR code is doing 69MHASH. Perhaps I need --lock-cclock to make it work? Please share your settings..

I am running

core +0 (default setting) trottles abit
mem 10700 (+1350)
tdp 75%
p0 state

here on latest 797.09


my configs --mt 2,0,0,0,0,6 --fan 85 --lock-cclock 0,1200,1200,1200,1200,0 --cclock 150,0,0,0,0,200 --mclock 400,1250,1400,1750,1900,500 --pl 90,105,0,116,112,90
3080ti is 1900

Trex last update / driver 495.44 no problem on my rig dev !



If you specify a lock core no PL need


If you don't know how the LHR MR Sp__ works don't denigrate minors in favor of your rigged software, I'll end up asking for your post to be deleted and your account banned.

It is one thing to come and advertise your minor to the community, but to come and put false settings and say that you are the best when you don't even know what you are doing is another.

will have to explain to me why you copy LOLMINER? you have the same changelog :|

Already called Team Black Miner when there is team red miner for a long time .... TBM vs TRM? this is not clever and I think that this is intended to cause confusion and moreover you copy paste the dev of the others, the last time lolminer reduced to 192 weird want an update or you also put now to 192? !





I post so that people get a real opinion on it and stop downloading anything again!

Because any good miner I recall it knows very well that 2 Mhs more does not change the profitability are the sharing rate and to date you are the last one

[pibhai]

I tried TBM 1.29 on my 2060 Super and I was getting 43.44MHs @102W compared to 43.1MHs @105W on t-rex. I was using following config -

--lock-cclock 1020 --lock-mclock 860 --fan 70 -kernel 8

Then I tried few other miners (GMiner, NBMiner, t-rex) and https://bitcointalk.org/index.php?topic=5368267.0 for a few minutes and then decided to go with TBM but it is not working properly since then.

I am getting two errors -

1) it is not recognizing '--fan' and sets fan speed to 40% by default. I tried using -T 52 but that didn't work either. Though I think maybe '--fan' is not one of the commands supported by TBM, why did it recognize '--fan' in the first attempt but not thereafter?

2) it is not recognizing --lock-mclock or --mclock and gives 'memory lock settings not available for this gpu' and keeps it at 6801mhz (default). I tried using --lock-mlcock 7660, --lock-mclock [[7660,7660]], --mclock 860 but nothing seems to work after the 1st attempt.

Kindly point out what am I doing wrong and how to sort it out. Also, is there any discord server for TBM?

[sp_]

If you specify a lock core no PL need

My code unlocks without the need to lock the clock.

If you don't know how the LHR MR Sp__ works

LHR was created by NVIDIA to reduce the hashrate, so creating a miner that breaks LHR is not an easy task. There are different ways to do it. T-rex way is working good, but failing to unlock on higher power. That meens that around ~90 will be the limit. TBM is not happy with 90, and we try to do 100MHASH++. But we miss is LHR detection and Auto-tune, so more work is needed.

will have to explain to me why you copy LOLMINER? you have the same changelog :|

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

We have 153 solved issues, and fix the issues as they come in. Miners want the features of the other miners, so we fix it for them. Our changelog is long, and we have releases every 5-7 days. We are new in the market and don't have all the features of the other miners yet, but it's coming. Our miner is getting better and better for each release.

1) it is not recognizing '--fan' and sets fan speed to 40% by default. I tried using -T 52 but that didn't work either. Though I think maybe '--fan' is not one of the commands supported by TBM, why did it recognize '--fan' in the first attempt but not thereafter?

2) it is not recognizing --lock-mclock or --mclock and gives 'memory lock settings not available for this gpu' and keeps it at 6801mhz (default). I tried using --lock-mlcock 7660, --lock-mclock [[7660,7660]], --mclock 860 but nothing seems to work after the 1st attempt.

Kindly point out what am I doing wrong and how to sort it out. Also, is there any discord server for TBM?

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

The correct parameter is called

--fan-speed-min  (or -f)

--lock-mclock is only working for the supported clockspeeds and not for overclocking. Use another program for that.

We don't have a discord, but you can reach us on here, on github, and reddit.

[hieu1010]

https://i.ibb.co/FHfHnH8/CD8943-CC-49-BB-4312-9-D1-A-A580442754-C1.jpg

p106 not working ... driver 472.12 & 496.76 , cuda 11.4 & cuda 11.5

[sp_]

normal launch config is working here.

Set ETC_WALLET=(your wallet)

:loop
   TBMiner --algo etchash --hostname etc.2miners.com --port 1010 --wallet %ETC_WALLET% --worker-name %computername%
   timeout 10
goto :loop


v1.30
1. NVIDIA partial LHR unlock for all models. enabled with (--lhr-unlock)
2. Removed vardiff in the display when pool has static diff.
3. Reduced memory usage.
4. Added support for more pools.

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


pre-release. Linux probobly tomorrow.

Unlock device 1 and 2 in the rig

--lhr-unlock [0,1,1,0,0,0]

Higher number give a faster speed (but can trigger LHR mode)

--lhr-unlock [0,2,10,0,0,0]

Another way to do a more agressive unlock (add tweak 1,2,3,4...)

--lhr-unlock [0,1,1,0,0,0] --tweak [0,1,1,0,0,0]

This version doesn't have a LHR detector but will reset the device every 5 hours just in case.

TeamBlackMiner_1_30_cuda_11_5_pre.7z
https://www.virustotal.com/gui/file/75a6af9d5a854e60629877562c0301782fb2e047989871c06548f62fe07a8908?nocache=1

[moderator's note: consecutive posts merged]

[84o3S8V]

1.29 and 1.30 hash about 2MH/s slower than 1.28 on my RTX 3080 (Non LHR) 497.09, at least the reported hashrate is lower.

[sp_]

New pre release with some more lhr fixes/adjustments. Reset device will now run each hour.

TeamBlackMiner_1_30_cuda_11_5_pre.7z
https://www.virustotal.com/gui/file/75a6af9d5a854e60629877562c0301782fb2e047989871c06548f62fe07a8908?nocache=1


3080ti;

core: 0 default
mem: (+1000) 10500mhz
pl: 70% power

lhr-unlock [1] = 81 MHASH stable for 1  hour.
lhr-unlock [1]  --tweak [1] = 85 MHASH stable for 8-15 minutes.

3060:

lhr-unlock [1] = 32 MHASH stable for 1  hour.
lhr-unlock [40] = 35 MHASH stable for 1  hour.

1.29 and 1.30 hash about 2MH/s slower than 1.28 on my RTX 3080 (Non LHR) 497.09, at least the reported hashrate is lower.

Increase the --xintensity to 284 (old default) to get back the 2MH/s or more. This miner works best on high diff and high intensity, but some pools works better on low intensity.

Here is v1.29 been running on --xintensity 144 for ~2.5 days
Old testrig with broken cards.



[moderator's note: consecutive posts merged]

[long2905]

baby steps. keep it up. i noticed that for trex, lhr unlock performance is not as good on the latest driver. it stays at 73 stable while it could get up to 76 on previous drivers. the number here is the LHR unlock %

[84o3S8V]

1.29 and 1.30 hash about 2MH/s slower than 1.28 on my RTX 3080 (Non LHR) 497.09, at least the reported hashrate is lower.

Increase the --xintensity to 284 (old default) to get back the 2MH/s or more. This miner works best on high diff and high intensity, but some pools works better on low intensity.

Here is v1.29 been running on --xintensity 144 for ~2.5 days
Old testrig with broken cards.

https://i.ibb.co/x8zq5Yj/1-29-test.jpg

I meant with the intensity locked at 144, 1.28 is faster here.

[dle378]

1.29 and 1.30 hash about 2MH/s slower than 1.28 on my RTX 3080 (Non LHR) 497.09, at least the reported hashrate is lower.

Increase the --xintensity to 284 (old default) to get back the 2MH/s or more. This miner works best on high diff and high intensity, but some pools works better on low intensity.

Here is v1.29 been running on --xintensity 144 for ~2.5 days
Old testrig with broken cards.

Have you tried any other xintensity values for MPH that worked best for your setup?

[plavirudar]

I post so that people get a real opinion on it and stop downloading anything again!

Because any good miner I recall it knows very well that 2 Mhs more does not change the profitability are the sharing rate and to date you are the last one

It's almost certain that the "improved" reported hashrate is not real and it's actually worse in terms of actual valid share submission rate compared to established miners, even after doing all the things the dev claims will make the reported hashrate real. This has been independently verified by various people in the thread and outside of it.

That being said, I'm sure you can make a better argument than complaining that TBM's dev copied lolminer, then highlight two completely different sentences.

[sp_]

That being said, I'm sure you can make a better argument than complaining that TBM's dev copied lolminer, then highlight two completely different sentences.

I have never tried lolminer, but ppl ask us to add features they need in order to switch their farm over to the more profitable Team Black Miner.

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

Have you tried any other xintensity values for MPH that worked best for your setup?

yes. --xintensity 4096 move the rig up to 115 (+5) mhash and poolside 113 ish.

It's almost certain that the "improved" reported hashrate is not real and it's actually worse in terms of actual valid share submission rate compared to established miners

This is a pool thing. The reported hashrate is an estimate. For the best pools look in your faq.

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

baby steps. keep it up. i noticed that for trex, lhr unlock performance is not as good on the latest driver. it stays at 73 stable while it could get up to 76 on previous drivers. the number here is the LHR unlock %

I get 72.5 after a while with the latest t-rex on the latest driver with autotune. This might not be the optimal settings t-rex, but I do use the same settings in TBM and get a hashincrease.

3080ti;

core: 0 default
mem: (+1000) 10500mhz
pl: 70% power

lhr-unlock [1] = 81 MHASH stable for 1  hour.
lhr-unlock [1]  --tweak [1] = 85 MHASH stable for 8-15 minutes.

Been running rock stable all night with  -lhr-unlock [1]. We will do a linux build and release today. In the next version we probobly will add
a LHR detector, and reset the device automaticly. Then we migth be able to do 85 (90 with 11000 mem) stable. on the latest driver.

If you don't know how the LHR MR Sp__ works don't denigrate minors in favor of your rigged software,

The LHR unlocker has cost me a few hundred hours of work already. Alot of Trial and Error. The first LHR unlock version was released too early, but v1.30 and moving forward should give a good boost. Bugs are being fixed, the miner improves and the fee is picking up.

This is how Software development of the Team Black Miner is done:

live@github:



Alot of hard work.. This is a Marathon not a sprint.

[moderator's note: consecutive posts merged]

[wasarianta]

Have you tried any other xintensity values for MPH that worked best for your setup?

yes. --xintensity 4096 move the rig up to 115 (+5) mhash and poolside 113 ish.

on 1.30 and nvidia 497.09 windows 10
let's try --xintensity [5120] --tweak [7] --kernel [6] on 2miners running at P0 = ON and the latest final MSI AB (i find memclock improve from +1200 (MSI beta version) to +1500 (MSI final version)).

https://ibb.co/DkzmZ9R

[sp_]

Have you tried any other xintensity values for MPH that worked best for your setup?

yes. --xintensity 4096 move the rig up to 115 (+5) mhash and poolside 113 ish.

on 1.30 and nvidia 497.09 windows 10
let's try --xintensity [5120] --tweak [7] --kernel [6] on 2miners running at P0 = ON and the latest final MSI AB (i find memclock improve from +1200 (MSI beta version) to +1500 (MSI final version)).

Thanks, you seem to know how to use this program. But @91 watt ?? Sounds too low

[wasarianta]

Have you tried any other xintensity values for MPH that worked best for your setup?

yes. --xintensity 4096 move the rig up to 115 (+5) mhash and poolside 113 ish.

on 1.30 and nvidia 497.09 windows 10
let's try --xintensity [5120] --tweak [7] --kernel [6] on 2miners running at P0 = ON and the latest final MSI AB (i find memclock improve from +1200 (MSI beta version) to +1500 (MSI final version)).
https://i.ibb.co/xGXwN17/1.jpg

Thanks, you seem to know how to use this program. But @91 watt ?? Sounds too low

yes.. i won't push anymore ...its already good enough for me... other miners are too arround 91-92 but less aggresive in terms of jobs intensity and of course dev fee LOL... that's why i use TBM... keep up good work dev.. thank you..

https://ibb.co/qRK0xtP