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

[sp_]

I really appraise TBM efforts and hope you'll become the next big thing.
Since all the mentioned options vastly change the behavior of a RIG, could you mention recommended settings for all the mainstream cards or recommended low and high values  for different cards along with how a setting changes the behavior of the card?

You need to be more spesific. Which card, which pool? The TBM team have access to many types of cards but not all of them. With abit of trial and error you can gain a few percent by adjusting the program correctly. This is a time consuming process, but some of you have already done it and got rewarded.

[wasarianta]

Only lhr-unlock and tweak works in the lhr mode. It is made for cuda 11.5 and the latest driver, but should work on cuda 11.4 as well. Expected speed on the 3060ti is 42mhash with 60% power and 7900 memory. This is with --lhr-unlock [1]

Hiveos is using the short options, so you have to find the correct letters from the short options.

more info here:

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

if mix : device 1 LHR and device 2 non LHR
 
-æ or --lhr-unlock [1,0]
-K or --dagintensity [0,9]
-E or --xintensity [-2,192]
-J or --kernel [-1,-1]
-u or --tweak [1,0]

correct me...

[sp_]

if mix : device 1 LHR and device 2 non LHR

-æ or --lhr-unlock [1,0]
-K or --dagintensity [0,9]
-E or --xintensity [-2,192]
-J or --kernel [-1,-1]
-u or --tweak [1,0]

The lhr card should have a limit on 60% tdp

Start with -æ [1,0]

if it doesn't work try -æ [-1,0]

if it doesn't work run as admin and try -æ [1,0] -j [[1130,1130],0]


if it doesn't work try  different values from -10 to 10 for -æ [-10,0] ... [10,0].

[nik-qz]

hi
I can not set the value of the parameter --cuda-devices [0,2,3,4,5]
video card number 1 still starts, although it is not on the list

[sp_]

Did you run tbminer --list-devices to check the device order? The device order could be different from other programs.

[steve8lily]

Hi, how to select certain GPUs mining like Gminer --devices as 1 of the GPU is integrated diaply in motherboard

←[1;36m00:00:00←[0m ←[1m[2021-12-26 23:14:16.←[0m←[0m009←[0m←[1m]←[0m ←[31mGPU0 Not enough GPU memory available←[0m
←[1;36m00:00:00←[0m ←[1m[2021-12-26 23:14:16.←[0m←[0m009←[0m←[1m]←[0m ←[31mRequired memory size is 5026607596←[0m
←[1;36m00:00:00←[0m ←[1m[2021-12-26 23:14:16.←[0m←[0m009←[0m←[1m]←[0m ←[36mShutting down threads←[0m
←[1;36m00:00:00←[0m ←[1m[2021-12-26 23:14:16.←[0m←[0m024←[0m←[1m]←[0m ←[33mControl thread exited←[0m
←[1;36m00:00:00←[0m ←[1m[2021-12-26 23:14:16.←[0m←[0m024←[0m←[1m]←[0m ←[33mStratum thread exited←[0m

[sp_]

run tbminer --list-devices to get the device order

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

Run the .reg script fir colors or add --no-ansi

[th3dark1nSid3me]

I really appraise TBM efforts and hope you'll become the next big thing.
Since all the mentioned options vastly change the behavior of a RIG, could you mention recommended settings for all the mainstream cards or recommended low and high values  for different cards along with how a setting changes the behavior of the card?

You need to be more spesific. Which card, which pool? The TBM team have access to many types of cards but not all of them. With abit of trial and error you can gain a few percent by adjusting the program correctly. This is a time consuming process, but some of you have already done it and got rewarded.

As a pool I use Ethermine.
Rigs in farm.
RTX 3060 Ti FHR
RTX 3060 Ti LHR
RTX 3070 FHR
RTX 3080 FHR
RX5600 XT
RX5700 XT
RX580 8GB
RX6700
RX6800

Any recommendations on specific settings would be appreciated.

[cafemax]

Sorry for these basic question, but I can't find answer:

1. What dose share 0/0/0 mean?  Submitted/Accept/Invalid ?

2. How to specify each AMD card? If I use -Y 0,1 , it blow up more than 50 cards that I don't have....

3. What different with  --

TeamBlackMiner_1_35_cuda_11_2.7z
TeamBlackMiner_1_35_cuda_11_4.7z
TeamBlackMiner_1_35_cuda_11_5.7z

??

Thanks for reply  

[JL97786]

Sorry for these basic question, but I can't find answer:

1. What dose share 0/0/0 mean?  Submitted/Accept/Invalid ?

2. How to specify each AMD card? If I use -Y 0,1 , it blow up more than 50 cards that I don't have....

3. What different with  --

TeamBlackMiner_1_35_cuda_11_2.7z
TeamBlackMiner_1_35_cuda_11_4.7z
TeamBlackMiner_1_35_cuda_11_5.7z

??

Thanks for reply  

1. I think it means total/reject/stale

2. You need to put -Y [0,1]

3. the miner compiled with different versions of CUDA, the latest is generally the best

[br2459]

Does anyone have a LHR 3080? I would like to know what hashrate you are getting with that version. I see the TI version can hit as high as 95MH/s but how well does the 3080 do?

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

I guess they're really playing a good long game, since they keep generating new features and slowly fixing bugs, which based on your comments, I assume they're generating on purpose to be sneaky and underhanded about some GNU violation? 

No, I assume they started off the work of other people, did not credit them, and then made money off of what is partially their work.

Even if they did take open source code and modify it for commercial purposes, the software is better than any others out there and there are a lot worse things in this world to get upset about.  The worst is that they have incorporated an open source project and built out and around it, which is common practice. Even creating a closed-source project based on the modification of the core open source code is not exactly uncommon, and there are far more flagrant violators of the GNU agreement for you to gripe about; how about elastic search, they _IPO'd_ on modified open source software which wasn't shared with the community.

So, because other people have done it, it's okay? As a developer myself, I know just how difficult and time consuming this shit is. While I personally dislike the GPL, If someone gives away their code for free and only wants those using it to follow the GPL - it's their right to decide what gets done with their shit. This is how you get people to stop contributing to open source.

[ekgd39]

run tbminer --list-devices to get the device order

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

Run the .reg script fir colors or add --no-ansi

Kernel 9 and tweak 8 it's more powerful for 3080 no lhr ?

[Alexstabilini]

Hi!
My rig ( 2x1060+9xp104+3060ti+4000) works only with dagintensity 1 in 1.35
any suggestions to solve the problem?
alex

Dag verification failed?

you can try to halve the xintensity and use --dagintensity 2

13 cards need alot of virtual memory in the rig

i have no luck with --dagintensity >1 with mine p104-100 despite low xintensity.
with other cards seems ok.
if i turn off overclock should they work?

thanks
alex

[konanlux]

autotune will help so...... much and will you make autotune kernels be dynamic something like --xintensity [-1] or at least at periodic time or epoch change or whatever haha no idea..

what now --dagintensity in v1.35 are have effect .. well i will find out..

The problem with the current autotune is that it runs for a too short time. Ideally it should run for minutes and not seconds. The problem is that the hashrate is reduced abit when trying out bad configurations. We don't have all the cards and models, so our solution is to create a program that will try to calcuate the best settings automaticly, or let you configure it yourself.

Nothing beats Human testing. V1.35 have 4 tuning options. Different cards have different optimal settings. Different power settings have different optimal settings. Different pools have different optimal settings.

--kernel (0-9) --xintensity (0-10000) / (0-2500 amd) --tweak (0-8) --dagintensity (0-9) / (0-8 amd)

So tune and be rewarded

testing v1.35 now in 2miners(2 days run), get more hash average 760mh, 778reported (rtx3090x6), but get les reward vs flexpool(get more ETH), in flex average 740mh 2% stales, runing same config same oc, only run --xintensity 4096, Any recommendation?

[wasarianta]

testing v1.35 now in 2miners(2 days run), get more hash average 760mh, 778reported (rtx3090x6), but get les reward vs flexpool(get more ETH), in flex average 740mh 2% stales, runing same config same oc, only run --xintensity 4096, Any recommendation?

for to 2miners i just use this..

--cuda-devices [0,1,2,...] --xintensity [192,192,192,...]

let see how job flow and how fast...

...the rest --kernel [,] --dagintensity [,] i let the miner choose what the best for my cards.

[cafemax]

I have a weird bug in 1.35 with flexpool.

When it happend:

01:03:07 [2021-12-29 15:05:57.006] Have not received data from pool for 20 seconds
01:03:07 [2021-12-29 15:05:57.006] Stratum thread exited
01:03:07 [2021-12-29 15:05:57.016] Pool connection disconnected or timed out

In the next period of time, I will get continuously invalid share like this:

01:03:08 [2021-12-29 15:06:41.204] GPU4 Solution found in 10.71s (Submit every 16.72 seconds)
01:03:08 [2021-12-29 15:06:41.234] Rejected (5755/5756) Reply: 23ms
01:03:08 [2021-12-29 15:06:41.234] mining.submit: Pool reponded with error
01:03:08 [2021-12-29 15:06:41.234] Error(-2): Invalid PoW Solution

The period may keep 17 ~ 19 min, make me 50+ invalid shares.

If not in this status, my rig has no any invalid shares.

I am sure not a connect problem, because my other rigs are working correct in the same time, and the gminer is never happend.

Please fix it, 

[KillrBee]

autotune will help so...... much and will you make autotune kernels be dynamic something like --xintensity [-1] or at least at periodic time or epoch change or whatever haha no idea..

what now --dagintensity in v1.35 are have effect .. well i will find out..

The problem with the current autotune is that it runs for a too short time. Ideally it should run for minutes and not seconds. The problem is that the hashrate is reduced abit when trying out bad configurations. We don't have all the cards and models, so our solution is to create a program that will try to calcuate the best settings automaticly, or let you configure it yourself.

Nothing beats Human testing. V1.35 have 4 tuning options. Different cards have different optimal settings. Different power settings have different optimal settings. Different pools have different optimal settings.

--kernel (0-9) --xintensity (0-10000) / (0-2500 amd) --tweak (0-8) --dagintensity (0-9) / (0-8 amd)

So tune and be rewarded

testing v1.35 now in 2miners(2 days run), get more hash average 760mh, 778reported (rtx3090x6), but get les reward vs flexpool(get more ETH), in flex average 740mh 2% stales, runing same config same oc, only run --xintensity 4096, Any recommendation?

Look at the luck of the pool.  2Miners has been over 100% quite a lot recently, so that will reduce the amount of ether rewarded simply because there are fewer reward blocks found; also check the size of the blocks found within the testing timeframe, some blocks can reward quite a lot of ethereum, or if there are a lot of uncles, then the reward can be lower despite the average luck being at or below 100.


Version 1.35 on HiveOS using --amd-only is generating zil DAG's when only "--algo ethash" is used.  This is causing DAG verification failures even when dagintensity is set to 1.

**edit:  Actually this is happening regardless of the amd or nvidia flags. The miner is randomly deciding to generate zil dags on different GPUs, but not all GPUs.


Also, you need to do range and length verification on the input fields because it is currently most likely possible to perform a buffer overrun on the unchecked fields.  For example, I accidentally selected Kernel 9 which was accepted by the miner, but caused corruption in the hashrate reporting (several TH/s and other alphanumeric values in the Hash and average reported rates).

[sp_]

testing v1.35 now in 2miners(2 days run), get more hash average 760mh, 778reported (rtx3090x6), but get les reward vs flexpool(get more ETH), in flex average 740mh 2% stales, runing same config same oc, only run --xintensity 4096, Any recommendation?

I think 4096 is too high on the 2miners pool. Even if all shares are accepted, some can be stale and give a lower payout.

Record poolside hashrate on the 3090x with --xintensity 3108 (137MHASH) (18 hour run)

See the video at:

https://imgur.com/a/stWmdM3

bugs reported.

The bugs you reported have been added to our github and been fixed

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

I have a weird bug in 1.35 with flexpool.
I am sure not a connect problem, because my other rigs are working correct in the same time, and the gminer is never happend.

v1.35 has only 20 second default stratum timeout. This is too short for some pools. You can add -t 80 for a 80 second timout.

As a pool I use Ethermine.
Rigs in farm.
RTX 3060 Ti FHR
RTX 3060 Ti LHR
RTX 3070 FHR
RTX 3080 FHR
RX5600 XT
RX5700 XT
RX580 8GB
RX6700
RX6800
Any recommendations on specific settings would be appreciated.

ok settings on the ethermine pool:

--xintensity 284 works good on nvidia cards on ethermine. If you go higher, you get alot of stale shares.
--xintensity 60 on rx580 8GB
--xintensity 78 on RX6700/rx6800 8GB


note that you can get a few percent poolside increase by changing to the recomended pools and increasing the --xintensity.


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

[JL97786]

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

It seems like pool hashrate is still lower than it should be in 1.35, by about 4%. Have you figured something out?