⛏Team Black Miner (ETHB3 ETHW ETC VTC KAWPOW FIROPOW ZIL +dual +tripple mining )

[long2905]

v1.33
1. Fixed index problem in stats when running with a selection of the gpu's.
2. Added more pools.
3. Improve the EXIT code for LHR gpu's
4. Improved the stability and speed of the --lhr-unlock
5. Improved --dagintensity more stable on higher clocks.
6. Try to remove more rejected shares on the hiveon pool (again)
7. Fixed bug in the LHR detector
8. Fixed Hang if selecting a non existing cuda device

Errors during regresstion testing. fixed build tomorrow

linux tomorrow


Note that the default unlock setting is a bit agressive and might not work. Lhr unlock support negative numbers so you can try to adjust it.

--lhr-unlock [-50,-50,-50]

any LHR number we can expect for 3080 or 3080ti for example?

[1715087193]

1715087193

[1715087193]

1715087193

[1715087193]

1715087193

[sp_]

any LHR number we can expect for 3080 or 3080ti for example?

v1.32 could do 85MHASH, v1.33 can do 95 MHASH. (3080ti)

11000 memory, 75% tdp 0 core.

Might need tuning. defaults are nerfed. v1.33 has semi Autotune, but you need to start correct. LHR unlock is still in BETA, so we do small adjustments/improvements for each release.
---------

linux binaries of v1.33 released.

[Reinseik]

v1.33
1. Fixed index problem in stats when running with a selection of the gpu's.
2. Added more pools.
3. Improve the EXIT code for LHR gpu's
4. Improved the stability and speed of the --lhr-unlock
5. Improved --dagintensity more stable on higher clocks.
6. Try to remove more rejected shares on the hiveon pool (again)
7. Fixed bug in the LHR detector
8. Fixed Hang if selecting a non existing cuda device

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

TeamBlackMiner_1_33_cuda_11_5_fix.7z
https://www.virustotal.com/gui/file/faa0f2694d6a2beeeecac615e21975d49eeae3745ce10853be196348a33549c0?nocache=1

TeamBlackMiner_1_33_cuda_11_4_fix.7z
https://www.virustotal.com/gui/file/6600f56f9be19c8e6d670bc103c34798355c92dcc7140ad1f8f166a699cf4c11?nocache=1

TeamBlackMiner_1_33_cuda_11_2_fix.7z
https://www.virustotal.com/gui/file/2c1bbf51b0ee3f90be60bb70e9c7e9cbc47727cf6898de94b005457a46f78e9c?nocache=1

TeamBlackMiner_1_33_Ubuntu_18_04_Cuda_11_5.tar.gz
https://www.virustotal.com/gui/file/ec72ec4cdfadb2bf6a929810c63ea14d447f93c5886b8054231108286ab3720f?nocache=1

TeamBlackMiner_1_33_Ubuntu_18_04_Cuda_11_4.tar.gz
https://www.virustotal.com/gui/file/ec0056312d8c0f3e0b320209aaea44419e7cee3c8c9943868099a796e5a4c48a?nocache=1

Why are the temperatures or consumption or anything not shown?
so it cannot establish temperature limits because the miner simply ignores the limits that I set by not showing them, the gpus are from the 5000 and 6000 series and the version of the drivers is 21,11,03

[sp_]

Why are the temperatures or consumption or anything not shown?
so it cannot establish temperature limits because the miner simply ignores the limits that I set by not showing them, the gpus are from the 5000 and 6000 series and the version of the drivers is 21,11,03

How do you set the limits? The correct way is:

--lock-cclock [[x,x],[x,x],[x,x],[x,x],[x,x],[x,x],[x,x]]

[Reinseik]

Why are the temperatures or consumption or anything not shown?
so it cannot establish temperature limits because the miner simply ignores the limits that I set by not showing them, the gpus are from the 5000 and 6000 series and the version of the drivers is 21,11,03

How do you set the limits? The correct way is:

--lock-cclock [[x,x],[x,x],[x,x],[x,x],[x,x],[x,x],[x,x]]

with --templimit as it puts in the command list, what happens is that the miner does not show anything other than the hashrate, it does not show or core speed, temperatures or consumption, it only puts a 0 in all that

[sp_]

Can you run nvidia-smi please whats the output.




Then you can try to query the device for stats with:

nvidia-smi --query-gpu=gpu_bus_id,temperature.gpu,power.draw,fan.speed,clocks.sm,clocks.mem,temperature.memory -i 0000:01:00.0 --format=csv,noheader,nounits

[sp_]

v1.34

1. Fixed serious pool disconnect bug / GPU timeout bug.
2. Improved the pool reconnection code.
3. Fixed bug in mixed cards rig AMD/NVIDIA

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

TeamBlackMiner_1_34_cuda_11_5_fix.7z
https://www.virustotal.com/gui/file/42d8f1c8f028bc6f1fe7df57ad0eeb0c3b273f46479824eb8c88905c57c2e7b2?nocache=1

TeamBlackMiner_1_34_cuda_11_4_fix.7z
https://www.virustotal.com/gui/file/d8564bdb582cac262c8ee4b18bfe2ec04d5e5689d723116eac00321063307b7b?nocache=1

TeamBlackMiner_1_34_cuda_11_2_fix.7z
https://www.virustotal.com/gui/file/ec39886bb4b7f33b4c3d81f5857055840323007b49b762316da614e302db425e?nocache=1


linux tomorrow.

Regression logs showed problems with 1.32 and 1.33 . GPU timeouts, and stratum timeouts.

Code:

00:00:55 [2021-12-18 19:08:47.011] Have not received data from pool for 185 seconds
00:00:55 [2021-12-18 19:08:47.014] Stratum thread exited
00:00:55 [2021-12-18 19:08:47.029] Pool connection disconnected or timed out
00:00:55 [2021-12-18 19:08:47.029] Starting new stratum thread
00:00:55 [2021-12-18 19:08:47.032] Trying europe.ethash-hub.miningpoolhub.com:20535 (ethash)
00:00:55 [2021-12-18 19:08:47.201] Extranonce is set to 372672869164908544
00:00:55 [2021-12-18 19:08:47.201] Pool responded successfully to subscribe
00:00:55 [2021-12-18 19:08:47.280] Difficulty is set to 3.000000

[th3dark1nSid3me]

Exact same settings on same 7 x 3060 TI FHR with TBM v 1.32 and v 1.33. Running at -450 Core clock, 2400 Memory clock and 130W power limit.
Getting lower hashrate on 1.33, switched back to 1.32. Running SMOS with nv470.74 drivers.

-d -K 1 --dagintensity 1 --xintensity 284 -a ethash -H eu1.ethermine.org -p 4444 -r 40 -y 20 -t 120 -W "MAIN_WALLET" -w $rigName -P x --maintenance-wallet "MAINTENANCE_WALLET" --maintenance-percent 5

RIG is online >24H.

TBM 1.32 reports 437,xx MH/s.
I keep seeing wrong reported values (pool side). Reported hashrate on MAIN_WALLET is full rigs capacity not the 95% of it (as it should) and it fully correlates with what TBM is saying (437,xx MH/s). Reported hashrate on MAINTENANCE_WALLET remains 2,5 MH/s stable.
Average hashrate in MAIN_WALLET is low. It's about 380 - 384 MH/s. Average hashrate on MAINTENANCE_WALLET is between 18-22 MH/s.

So, 2 issues here.
One is the wrong reported values in MAIN and MAINTENANCE wallets respectively.
Two is the lower overall real hashrate than the reported one.

As a side note if you have any recommendations about my config they are most than welcome.
I manage a total of 10 GH/s in mixed AMD and NVIDIA rigs and I would like to switch them all in TBM as long as it is as stable and fast as other miners. My only reason for switching is the implementation of the maintenance fee since this is exactly the feature I want to get easily paid for my maintenance work.

[sp_]

Average hashrate in MAIN_WALLET is low. It's about 380 - 384 MH/s. Average hashrate on MAINTENANCE_WALLET is between 18-22 MH/s.

Se in my previos post.

Regression logs showed problems with 1.32 and 1.33 . GPU timeouts, and stratum timeouts.

On some of my test rigs the rig was sleeping for 3 minutes almost every hour, loosing 5% poolside hash. For single card rigs not a problem, and might work on some pools. But still a pretty serious bug. We are working on a better fix. The 1.34 windows version still have stratum disconnects but only 5 seconds instead of 180++

[th3dark1nSid3me]

Average hashrate in MAIN_WALLET is low. It's about 380 - 384 MH/s. Average hashrate on MAINTENANCE_WALLET is between 18-22 MH/s.

Se in my previos post.

Regression logs showed problems with 1.32 and 1.33 . GPU timeouts, and stratum timeouts.

On some of my test rigs the rig was sleeping for 3 minutes almost every hour, loosing 5% poolside hash. For single card rigs not a problem, and might work on some pools. But still a pretty serious bug. We are working on a better fix. The 1.34 windows version still have stratum disconnects but only 5 seconds instead of 180++

Understood. I'll wait for v 1.34 to be released in SMOS.

[wasarianta]

Se in my previos post.

Regression logs showed problems with 1.32 and 1.33 . GPU timeouts, and stratum timeouts.

On some of my test rigs the rig was sleeping for 3 minutes almost every hour, loosing 5% poolside hash. For single card rigs not a problem, and might work on some pools. But still a pretty serious bug. We are working on a better fix. The 1.34 windows version still have stratum disconnects but only 5 seconds instead of 180++

1.34

https://ibb.co/2S78sWQ

i let it run...

https://ibb.co/pQrZSfJ

[sp_]

i let it run...

The timeout timer is set to only 5 seconds in this build. Fast reconnection seem to improve the poolspeed, but  we need to investigate why it happens.

edit: Found a fix. In testing now..

[JL97786]

Will the latest Linux builds be released soon? Why do they always lag windows releases?

[sp_]

Will the latest Linux builds be released soon? Why do they always lag windows releases?

1.34 fix has been released for windows. We have regression testing in a windows farm environment, it we find something we delay the linux release. Linux 1.34 soon. We also found a bug with a mixed card rig AMD/NVIDIA. For mixed cards, its best to run 2 instances of the miner. One with amd cards, the other with Nvidia.

[sp_]

Team Black Miner 1.35

1. Improved LHR unlock

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

TeamBlackMiner_1_35_cuda_11_5.7z
https://www.virustotal.com/gui/file/55d2678a7439d0f59ed78f94f9ee694e21cf9662e198ee3b0038ec737bfc6634?nocache=1

TeamBlackMiner_1_35_cuda_11_4.7z
https://www.virustotal.com/gui/file/9227f90e0e5f989a668756a1fd0464dfb0bd7f84c3870118cbc1bf47decf975e?nocache=1

TeamBlackMiner_1_35_cuda_11_2.7z
https://www.virustotal.com/gui/file/7d09ec7d76e8c691e4c6096e14bfd6b6fdd27156f76f09a9a5268d1ddbc351f5?nocache=1

TeamBlackMiner_1_35_Ubuntu_18_04_Cuda_11_5.tar.gz
https://www.virustotal.com/gui/file-analysis/ZjY3YWY2MTAzMzlhODRkODU1MDE4NTllZmNiODhhMjk6MTY0MDExNTE1MA==

v1.35 has
Stable unlock on the 3070 v4 LHR latest driver

60%tdp
7900 memory
0 core.

[long2905]

you are killing it with new releases

[sp_]

linux cuda 11.5 build released

TeamBlackMiner_1_35_Ubuntu_18_04_Cuda_11_5.tar.gz
https://www.virustotal.com/gui/file-analysis/ZjY3YWY2MTAzMzlhODRkODU1MDE4NTllZmNiODhhMjk6MTY0MDExNTE1MA==

[JL97786]

linux cuda 11.5 build released

TeamBlackMiner_1_35_Ubuntu_18_04_Cuda_11_5.tar.gz
https://www.virustotal.com/gui/file-analysis/ZjY3YWY2MTAzMzlhODRkODU1MDE4NTllZmNiODhhMjk6MTY0MDExNTE1MA==

Thanks, will you release cuda 11.4 build soon?

[sp_]

linux cuda 11.5 build released

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

TeamBlackMiner_1_35_Ubuntu_18_04_Cuda_11_5.tar.gz
https://www.virustotal.com/gui/file-analysis/ZjY3YWY2MTAzMzlhODRkODU1MDE4NTllZmNiODhhMjk6MTY0MDExNTE1MA==

Thanks, will you release cuda 11.4 build soon?

The 11.5 build is faster, and early x-mas holiday now. So might not be buildt in a few days. The team is Tired. 10 months of hard work completed..

[Wolf9466]

linux cuda 11.5 build released

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

TeamBlackMiner_1_35_Ubuntu_18_04_Cuda_11_5.tar.gz
https://www.virustotal.com/gui/file-analysis/ZjY3YWY2MTAzMzlhODRkODU1MDE4NTllZmNiODhhMjk6MTY0MDExNTE1MA==

Thanks, will you release cuda 11.4 build soon?

The 11.5 build is faster, and early x-mas holiday now. So might not be buildt in a few days. The team is Tired. 10 months of hard work completed..

All that hard work stealing open source code, making some improvements, and then profiting off of it without giving back.
Must be tiring.