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

Third day. You had a v1.18 vs 2.70 earlier.

1. You are running on a mining pool that doesn't pay for stale shares. Change the pool and increase the intensity
2. You are running on sub optimal clocks. I know this is a power issue, and that pushing it to 106MHASH is not worth the power, but still..

---

v1.20
1. Removed unwanted debug output for AMD/OpenCL. (Linux)
2. Removed cost from console status if watt reading is null.
3. Added mutex lock to average solution time to avoid thread race condition.
4. Avoid gpu timouts at startup on rigs with more than 12 cards
5. Improved staleshare checker less stales reported.
6. increased default nvidia --xintensity to 225 to improve the poolsite hashrate.
7. Added --dagintensity 0-9 for nvidia cards to prevent crash on high oc RTX cards.
8. Fixed reported hashrate on some pools with high case workernames.
9. Added following pools: 666pool.cn, gpumine.org and rustpool.xyz.

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

TeamBlackMiner_1_20_cuda_11_5.7z
https://www.virustotal.com/gui/file/41d5cd1b48cdde280f3d3f1b236d9c1c892f67742772e75bd32420ce7ac9b6bd?nocache=1

TeamBlackMiner_1_20_cuda_11_4.7z
https://www.virustotal.com/gui/file/9a26df7e3f60ceaca3b44d4216d067c9e30295b0490068cfa3cb81cdd1e90919?nocache=1

TeamBlackMiner_1_20_cuda_11_2.7z
https://www.virustotal.com/gui/file/7a99d5404890abbb80e9965b7e76a913abdaf13abf9685604c511a25c61766fd?nocache=1

TeamBlackMiner_1_20_Ubuntu_18_04_Cuda_11_4.tar.gz
https://www.virustotal.com/gui/file/af0374531ff5807315c7b10fc241a26b84c581640fb5c7075173911e9a479e0f?nocache=1

v1.20, 150 shares test on crazypool with default --xintensity 224. no stales. Good poolside hashrate.






[moderator's note: consecutive posts merged]

2nd day of fight: TBMiner vs GMiner

TBMiner (ver 1.19)


GMiner (ver 2.70)


To be honest I expected more distance between the two miners, but they are very close indeed.
Still confused about results.

Yes, they are Hynix memories but the Microns mark 34 Mh / s and only the Samsung mark 32 Mh / s because if I increase the speed a bit they give me memory errors.

Change the intensity -1 and increase the power for the rx 6800 but they only go up to 66.5 Mh / s and I have no idea how to get them to 72 Mh / s, I thought you were working on that

My internet connection is not stable so when I change the network I must wait 3 minutes to reconnect again, I would appreciate knowing how to reduce this time. Help me with this.

Nice speed for the 580 is that hynix memory ?


Use lowercase in the worker name


You should get around 68MHASH with a change in --xintensity to dynamic Bios mod can give you 72-75 but with more power

--xintensity [60,60,-1,-1,-1]

AMD kernel rewrite is ongoing.

---

In v1.20 we have implemented a --dagintensity parameter that can help users remove DAG validation errors with RTX cards on high oc. Will Release tomorrow


[moderator's note: consecutive posts merged]

https://i.ibb.co/N7Bwp8V/gpus.jpg
https://i.ibb.co/bPZx6Z1/ab.jpg

Greetings,
Results for platform (2 RX 580 AND 3 RX 6800) TBM Ver. 1.19

-My internet connection is not stable so when I change the network I must wait 3 minutes to reconnect again, I would appreciate knowing how to reduce this time.

-In Nanopool the Hashrate is not being reported, I would appreciate it being fixed in the next version.

-And finally I would like to know if it is working to increase the speed of the RX6800 gpu; I understand that it was necessary to exceed the limit of memory OC and modifications of times that for now are blocked.

Thanks for the explanation.

Using the xintensity value of "768", TBM was reporting less than 2% of stale shares.

I switched to the default value "160" and this seems to be much more stable since I am not seeing any stale shares reported yet. (Only been 70 minutes)

Will definitely report the status in the next 8 hours.

Go to the "Shares" tab and you'll see the number of accepted / stale / rejected shares.  The 'stale' reported in TBM are type 1, so 2Miners won't call them stale, but if you submit a solution after the round window, you'll get a true stale share.

Read the faq

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

Many miningpools accept stale shares, but can start rejecting them if you send more than 5% stales.
The ethereum blockchain pay 87.5% for stale share blocks (uncle blocks)
The bitcoin blockchain pay 0%
More than 50% of the Ethereum mining pools pay for stale shares.

The Team Black Miner works best on pools that pay for stale shares.

Any reason as to why we are not able to see the invalid shares reporting within 2Miners?

Or are they still counted as "Valid Shares"?

I want more stales...

But I'm not going to argue with this result:

https://imgur.com/a/MNxNqOb

To reduce stales you need to decrease xintensity, not increase…

Actually I'm paying no attention to stale rates as those don't even get reported as stale to 2Miners.  It's mostly just maximum speed vs. stability and average per round percentage.  I suppose I could try dropping the overclocks and increasing the intensity to see if the share rate increases...

That's a nice pool hashrate.  

Too much focus on stale shares, and too little focus on profit... This is not bitcoin mining, this is ethereum.

My Nvidia card is a 3090, and it seems to be one of the best binned, because it runs cool and fast.  Right now it's doing 136 MH/s at 43/88 degrees (I do have some heatsinks and fans on the backplate for the VRAM though), so take the numbers with that in mind.

C-Clock = 1500 (this is a good mid-point for managing the voltage without actually setting the voltage -- I'm running 0.778V at 1500 core)
M-Clock = +1625MHz => 11376MHz  PState =0
PowerLevel = (85-119% depending on your Xintensity level)
Xintensity = 2100

I'm mining on 2Miners and getting 136 - 137MH/s at the client (reporting 158.74 MH/s as Pool Hashrate @ 1.11 Shares per minute)

>Added Screen Cap:

https://i.imgur.com/PNP81zq.jpg

1.20 will be released soon with more fixes

I'm using the version used by mmpOS.

it's already been fixed. Download the latest 1.19 from github.

Hi, when mining with AMD cards, command log is now flooded like this:

│[2021-10-26 14:34:20][info][miner/0]:      0m [2021-10-26 14:34:20.725] GPU1 miner_hashrate 648114775754.373291
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:20.812] GPU3 miner_hashrate 648415229209.702148
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:20.816] GPU2 miner_hashrate 642886118460.344482
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:20.832] GPU0 miner_hashrate 644258230597.936646
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:20.849] GPU6 miner_hashrate 644334613551.354370
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:20.870] GPU5 miner_hashrate 648681862621.815796
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:20.880] GPU4 miner_hashrate 648162693425.092163
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:20.946] GPU2 miner_hashrate 642886118460.344482
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:20.962] GPU0 miner_hashrate 644258230597.936646
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:20.967] GPU3 miner_hashrate 648415229209.702148
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:20.978] GPU6 miner_hashrate 644334613551.354370
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.034] GPU1 miner_hashrate 648409463750.701660
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.035] GPU4 miner_hashrate 648162693425.092163
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.076] GPU2 miner_hashrate 642886118460.344482
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.091] GPU0 miner_hashrate 644258230597.936646
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.108] GPU6 miner_hashrate 644334613551.354370
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.122] GPU3 miner_hashrate 648415229209.702148
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.180] GPU5 miner_hashrate 648527151838.149780
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.189] GPU1 miner_hashrate 648409463750.701660
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.206] GPU2 miner_hashrate 642886118460.344482
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.221] GPU0 miner_hashrate 644258230597.936646
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.238] GPU6 miner_hashrate 644334613551.354370
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.334] GPU5 miner_hashrate 648527151838.149780
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.336] GPU2 miner_hashrate 642886118460.344482
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.344] GPU4 miner_hashrate 648244143535.504028
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.344] GPU1 miner_hashrate 648409463750.701660
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.351] GPU0 miner_hashrate 644258230597.936646
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.368] GPU6 miner_hashrate 644334613551.354370
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.431] GPU3 miner_hashrate 648463715535.033081
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.466] GPU2 miner_hashrate 642886118460.344482
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.481] GPU0 miner_hashrate 644258230597.936646
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.489] GPU5 miner_hashrate 648527151838.149780
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.498] GPU6 miner_hashrate 644334613551.354370
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.498] GPU4 miner_hashrate 648244143535.504028
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.498] GPU1 miner_hashrate 648409463750.701660
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.585] GPU3 miner_hashrate 648463715535.033081
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.596] GPU2 miner_hashrate 642886118460.344482
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.611] GPU0 miner_hashrate 644258230597.936646
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.611] Job 51fc2b9b
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.627] GPU6 miner_hashrate 644334613551.354370
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.643] GPU5 miner_hashrate 648527151838.149780
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.653] GPU4 miner_hashrate 648244143535.504028
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.653] GPU1 miner_hashrate 648409463750.701660
│[2021-10-26 14:34:21][info][miner/0]:      0m [2021-10-26 14:34:21.726] GPU2 miner_hashrate 642886118460.344482

PLEASE FIX!

What are the best settings (C-Clock and Mem-Clock) that works good with this miner for:
RTX 3060Ti (non LHR)
RTX 3070 (non LHR)
RTX 3090
?

Thank you in advance

Changed Binance pool to 2miners and have great results!

---

Can anybody post their 3060 LHR - 3060Ti LHR - 3070 LHR results with TBM? Thanks

[moderator's note: consecutive posts merged]