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

[fluffier]

Can gpu's be chosen with this miner or not?

--cuda-devices [0,1,2,3] or short option -U
--cl-devices [0,1,2,3] or short option -Y

hiveos use the short option.

to see the correct index, run tbminer --list-devices

Ok, thanks!

[1713296300]

1713296300

[1713296300]

1713296300

[th3dark1nSid3me]

Good day.

I was looking for a miner that has the "maintenance fee" feature or something similar and stumbled upon TBM. I found out about the "maintenance fee" option through the changelog of Simple Mining.  
Unfortunately I couldn't find any documentation in TBM site's or on your github page on the exact commands for setting this up.
With a bit looking around I thought I found how the command should be written but it doesn't work.

Running teamblackminer-v1.31-cuda11.4 in SMOS,

-a ethash -o stratum+tcp://eu1.ethermine.org:4444 -u "ETH_WALLET" -w $rigName -p x --maintainance-wallet "ETH_WALLET" --maintainance-percent 5 --worker-name $rigName --miningtime 100 --script-crash reboot.sh

I get /root/miner/teamblackminer-v1.31-cuda11.4/TBMiner: unrecognized option '--maintainance-wallet'

Any help?

[sxemini]

Good day.

I was looking for a miner that has the "maintenance fee" feature or something similar and stumbled upon TBM. I found out about the "maintenance fee" option through the changelog of Simple Mining.  
Unfortunately I couldn't find any documentation in TBM site's or on your github page on the exact commands for setting this up.
With a bit looking around I thought I found how the command should be written but it doesn't work.

Running teamblackminer-v1.31-cuda11.4 in SMOS,

-a ethash -o stratum+tcp://eu1.ethermine.org:4444 -u "ETH_WALLET" -w $rigName -p x --maintainance-wallet "ETH_WALLET" --maintainance-percent 5 --worker-name $rigName --miningtime 100 --script-crash reboot.sh

I get /root/miner/teamblackminer-v1.31-cuda11.4/TBMiner: unrecognized option '--maintainance-wallet'

Any help?

maintenance and not maintanance

[sp_]

I get /root/miner/teamblackminer-v1.31-cuda11.4/TBMiner: unrecognized option '--maintainance-wallet'

spelling error. The option has been renamed to:

--maintenance-wallet
--maintenance-percent (1-50)%

So you can split your income between two adresses. The maintenance-wallet is mined to continuously, so you won't get jumping hashrate on the main worker.

And you don't need to specify the workername twice. remove -w $rigname. Miningtime is not needed anymore either (v1.31+)

[th3dark1nSid3me]

Good day.

I was looking for a miner that has the "maintenance fee" feature or something similar and stumbled upon TBM. I found out about the "maintenance fee" option through the changelog of Simple Mining.  
Unfortunately I couldn't find any documentation in TBM site's or on your github page on the exact commands for setting this up.
With a bit looking around I thought I found how the command should be written but it doesn't work.

Running teamblackminer-v1.31-cuda11.4 in SMOS,

-a ethash -o stratum+tcp://eu1.ethermine.org:4444 -u "ETH_WALLET" -w $rigName -p x --maintainance-wallet "ETH_WALLET" --maintainance-percent 5 --worker-name $rigName --miningtime 100 --script-crash reboot.sh

I get /root/miner/teamblackminer-v1.31-cuda11.4/TBMiner: unrecognized option '--maintainance-wallet'

Any help?

maintenance and not maintanance

Thank you for that.

[th3dark1nSid3me]

I get /root/miner/teamblackminer-v1.31-cuda11.4/TBMiner: unrecognized option '--maintainance-wallet'

spelling error. The option has been renamed to:

--maintenance-wallet
--maintenance-percent (1-50)%

So you can split your income between two adresses. The maintenance-wallet is mined to continuously, so you wont get jumping hashrate on the main worker.

And you don't need to specify the workername twice. remove -w $rigname. Miningtime is not needed anymore either (v1.31+)

It seems that all my config was wrong.
I now run this config:

-b -a ethash -H stratum+tcp://eu1.ethermine.org -p 4444 -r 40 -y 20 -t 120 -W "ETH_WALLET" -w $rigName -P x --maintenance-wallet "ETH_WALLET" --maintenance-percent 10

It starts ok but I get

00:00:00 [2021-12-10 16:13:41.336] No GPU devices available on platform 0 (Advanced Micro Devices, Inc.)
00:00:00 [2021-12-10 16:13:41.336] No devices are set

This rig has 8 * RTX3070
...

Any idea?

[sp_]

It starts ok but I get

00:00:00 [2021-12-10 16:13:41.336] No GPU devices available on platform 0 (Advanced Micro Devices, Inc.)
00:00:00 [2021-12-10 16:13:41.336] No devices are set

This rig has 8 * RTX3070
...

Any idea?

You need to upgrade the nvidia driver to the latest. That can run cuda 11.4 or 11.5 code

[Zels]

Think i'm at the max I can get out of this 1660 super

~ 31.5 - 32Mh @ 75watt 24/24 with low reject, staying in the range of 99 - 99.5% instead of the 28mh @ 105 watt before the overclock 

Still using the v.29 (.30 & 31 nicehash is fixed, but not prohashing ) with the same speed. No Lhr card on this rig ^^

Nice work SP 

[sp_]

v1.32
1. Fixed cpu validation error on ethproxy pools that caused rejects/skipping valid work.
2. Added LHR detector and reset the device if detected. Removed reset every hour in LHR more.
3. Removed some LHR code for non LHR cards.
4. Cuda devices that are busy/unavailable will be skipped instead of program exit.
5. Added support for more pools, and fixed prohashing.
6. Reduced the use of stack, also reduced the overall memory needed.
7. Removed memleak in --list-devices and --version



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

TeamBlackMiner_1_32_cuda_11_2.7z
https://www.virustotal.com/gui/file/46376a42f8c288a19e5ad0f44660d661fe610158af1a6b7611310918f4e1dbf3?nocache=1

TeamBlackMiner_1_32_cuda_11_4.7z
https://www.virustotal.com/gui/file/bd81117a38011a86f7e5c7a14df09a068285c679d53b93b9a5554f4c2e01f827?nocache=1

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

TeamBlackMiner_1_32_Ubuntu_18_04_Cuda_11_5.tar.gz
https://www.virustotal.com/gui/file/889860e31c09a4fc4849416b747a32343f63c47ff878a56407958fd84a3f5aeb?nocache=1

TeamBlackMiner_1_32_Ubuntu_18_04_Cuda_11_5.tar.gz
https://www.virustotal.com/gui/file/d478d01b665092f98998e6337eb40638b3bccdc36c14ac7d3f5a741c0a72ee80?nocache=1

Still using the v.29 (.30 & 31 nicehash is fixed, but not prohashing ) with the same speed. No Lhr card on this rig Nice work SP 

We fixed prohashing in 1.32 removed some LHR code as well, so it should be a little bit faster than 1.29

[moderator's note: consecutive posts merged]

[Alexstabilini]

Hi!
Maybe a error in ZET etc and eth config file.
pool address is eth.zetpool.org:8005 not eth.pool.zet-tech.eu:8005.
thanks
Alex

[Zels]

Still using the v.29 (.30 & 31 nicehash is fixed, but not prohashing ) with the same speed. No Lhr card on this rig Nice work SP 

We fixed prohashing in 1.32 removed some LHR code as well, so it should be a little bit faster than 1.29

v32 running, little gain from v29 - v31, prohashing, nicehash working. Thanx for your work

Will test on a 3070 LHR next

[Dojo76]

@SP__

Rejected shares % is higher with Hiveon pool with latest 1.32 so I moved to 2miners for testing.

I can't connect to 2miners pool with TLS enabled, miner is not even starting, while no problem with stratum port. Zero rejected shares and a very high hashrate, I still have to check if share ratio per minute is ok but looks good for now.

Is default Xint = 0  the best setting for AMD cards in 2miners pool?

[sp_]

On 2miners.com ppl have reported good returns on the 6800xt rigs with --xintensity 800 or --xintensity 1024.

The defeult 0 is dynamic which is also good. The intensity will adjust itself. Note that high intensity can use a little more power, and can create stale shares on some mining pools. Thats why we use --xintensty 24 as default on pools that doesn't pay for or reject stale shares.

[Dojo76]

On 2miners.com ppl have reported good returns on the 6800xt rigs with --xintensity 800 or --xintensity 1024.

The defeult 0 is dynamic which is also good. The intensity will adjust itself. Note that high intensity can use a little more power, and can create stale shares on some mining pools. Thats why we use --xintensty 24 as default on pools that doesn't pay for or reject stale shares.

Thanks for the explanation, I'll stick to XINT = 0 for now to calculate profitability, stales and rejected. 

Can you investigate into the TLS problem with 2miners? I tried with 3 different rigs and it's not working, I had to use stratum port with TBM and works just fine 

[Alexstabilini]

On 2miners.com ppl have reported good returns on the 6800xt rigs with --xintensity 800 or --xintensity 1024.

The defeult 0 is dynamic which is also good. The intensity will adjust itself. Note that high intensity can use a little more power, and can create stale shares on some mining pools. Thats why we use --xintensty 24 as default on pools that doesn't pay for or reject stale shares.

Hi sp_
Any solution for the eth ZET pool?
thanks
alex

[sp_]

Can you investigate into the TLS problem with 2miners? I tried with 3 different rigs and it's not working, I had to use stratum port with TBM and works just fine 

TLS and SSL mining is not working at the moment, but we are working on a fix.

[Movalis]

First of all thanks for the nice miner.

I'm getting a little bug arround when i mine just for some selected GPU.

have in rig:

GPU 0 - 3090
GPU 1 - 3060ti LHR
GPU 2 - 3070 non LHR
GPU 3 - 3070 non LHR
GPU 4 - 3070 non LHR

When select just to use the GPU: 0,2,3,4 using the command --cuda-devices [0,2,3,4] the report in the miner come with a bug.

The last GPU in report always stay with value 0 shares , but during the time, miner get a share and represent it in the values of total shares, but never in report board.

https://cdn.discordapp.com/attachments/444585576792981520/919605989597130772/TBM_report_bug.PNG

As can be seen in the picture above, it getting pushing values for a GPU 1 that i effectively turn it off.

I assume that GPU0 it's ok , GPU1 it's for the GPU2 report, GPU2 for the GPU3 and GPU3 for the GPU4.

It's just a report number bug in the miner because not even equal the shares done and shares reported in the board.

With all the cuda devices running, this bug don't appear, just when selecting specific GPU to work.

Running HiveOS
TBM 1.32

Extra config arguments
--cuda-devices [0,2,3,4]
--algo ethash
--log

Cheers

[killer0000001]

2021-12-12 15:28:53][info][miner/0]: Starting with: TBMiner --algo ethash --hostname 47.2x2.2x4.77 --port 11111 --wallet 0xCbF97d5b693263d83387307142Dxxxxxxxxxxxxx --worker-name xxx --x
x[2021-12-12 15:28:55][info][miner/0]: 00:00:00 [2021-12-12 15:28:54.282]                                                                                                                         x
x[2021-12-12 15:28:55][info][miner/0]: 00:00:00 [2021-12-12 15:28:54.282] Sorry the provided pool is not supported                                                                                x
x[2021-12-12 15:28:55][info][miner/0]: 00:00:00 [2021-12-12 15:28:54.282] If you think this pool should be, then ask us to configure it                                                           x
x[2021-12-12 15:28:55][info][miner/0]: 00:00:00 [2021-12-12 15:28:54.282] Shutting down threads                                                                                                   x
x[2021-12-12 15:29:00][info][miner/0]: 00:00:00 [2021-12-12 15:28:58.282] Exiting                                                                                                                 x
x[2021-12-12 15:29:00][info][miner/0]: Miner exited code:-1                                                                                                                                       x
x[2021-12-12 15:29:01][info][miner/0]: Restarting miner in 5 seconds...


can't use ip connect pool?
i set my vps rediect ethermine,other miner soft work fine

[sp_]

First of all thanks for the nice miner.

Thanks. The issue was added to our github

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

can't use ip connect pool?
i set my vps rediect ethermine,other miner soft work fine

We will whitelist all the pool ip's in our supported pools. But local ips or proxys are not supported.

[moderator's note: consecutive posts merged]

[killer0000001]

can't use ip connect pool?
i set my vps rediect ethermine,other miner soft work fine

We will whitelist all the pool ip's in our supported pools. But local ips or proxys are not supported.

China  DNS cache pollution
if local ips or proxys are not supported,will lost many china miner