how do i start this miner. all the examples BAt in the folder do not wrok
am getting "Your system does not support cuda 11.5 api" ihave downlooad and install cuda 11.5 toolkit
Download and install the latest driver from NVIDIA. |
|
|
|
Hello, three questions:
1. Is SSL implemented yet ? When I try it the miner says it is not but maybe I am doing something wrong. This is my bat file: TBMiner --algo ethash --ssl --hostname eth-de.flexpool.io --port 5555
It's implemented, but not working 100% so we disabled it. 2. When using TBM, is it better to use the high difficulty port in flexpool 14444 (I have read in this thread that it works better in high difficulty pools)
Depends on the rig. TBM doesn't work good on low difficulty but above 1.0 should be ok. Flexpool doesn't pay for stale shares, so --xintensity above 512 (nvida) or 128 (amd) will produce alot of stales. 3. I cant use --lock-cclock with amd cards, can I ?
This option is nvidia only.
which is about 12-13% above anything else I've ever seen! (512 intensity; 1642 MHz GPU; 2122 MHz Memory {Actual runtime reported values} @ 145 Watts).
You should make a youtube video. How to increase your ethereum mining profit +12-13% poolside with the latest AMD cards.. 1. Use the new The Team Black miner. 2. Change the Mining pool (?) 3. Run on high --xintensity |
|
|
|
time: 4
Have not received response from pool
When the fee thread is unable to find solutions the pool will force disconnect. This happens sometimes. We forgot to remove the debug output. Nothing to worry about. Also, I think this may be a windows driver issue and maybe someone has a solution for it, but I notice that my 6900XT will momentarily drop power for a second and then ramp back up to full power. I am well aware of the fun little quirky behaviour that AMD cards have for running at full power and then deciding to just go into idle and stay there, but this drop to idle and restore to full power a second later is something I've only seen with my 6900XT.. Anyone have any ideas on what's happening?
Disable the amd watchdog service. Disable fast startup mode in windows use AMD settings to enable fast memory timings use MSI afterburner to set clocks. Other than that, there were times when this wasn't occurring that I was seeing 71 MH/s as the Average (3 hour) hashrate at the 2miners pool -- which is about 12-13% above anything else I've ever seen! (512 intensity; 1642 MHz GPU; 2122 MHz Memory {Actual runtime reported values} @ 145 Watts).
Great work!
Thanks for your support!
what does the form mean on your screen, shares 1/1/1 if these are found shares, disabled shares, obsolete shares, then there are too many obsolete shares and this is nothing good
Accepted/Rejected/ (Estimated stale shares) The estimation code in the miner window is not good, so you should always check the pool. Some pools pay for stale shares. edit: cuda 11.4 and 11.2 builds added. Linux will be added in a few days. |
|
|
|
|
1.27 has a higher default xintensity, that give more stale shares.
Try 1.36 with --xintensity 512 or 384
|
|
|
|
I have problems since version 1.29. Speed are go lower and lower and lower every second. The miner started with very high speed - example RTX2060S with over 50mh - but the speed goes down and down.
With version 1.28 it start with low hashrate and raising to the max. I use 11.2 cuda version and no i don´t want to update my driver - it is not a solution to update the driver with every new miner version.
We have had many bugs in the avg. hashrate. You should run the latest version 1.36. LHR unlock not working for me, only a few seconds and the card is locked again. (tested with newest driver)
You might need manual tuning of clocks and lhr parameters. Run with --log, and --lock-cclock example: RTX 3070 LHR3 60% tdp 7900 memory RX6600XT it show an inflated hashrate by around 10% (TRM = 32,7 | TBM = 34,5)
You should get much less than 10% difference, but it depends on the pool and intensity. Try the 1.36 version. We have fixed a jumping hashrate bug. How do you set multiple intensity if those cards are on the same rig ?
First run tbminer --list-devices to get the indexes. then for 4 cards: --xintensity [60,24,0,256] |
|
|
|
|
All rtx 3060 cards are LHR, but LHR1 cards with 470.05 beta driver on windows, x16 riser port and hdmi dongle can unlock them.
51MHASH is possible with the latest cuda 11.2 build of Team Black Miner.
Without the driver, hdmiplug or x16 pci port you can run in --lhr-unlock mode. around 35MHASH with the Team Black Miner.
The Team Black Miner 1.35 can partially unlock all LHR cards at a reduced rate.
LHR1, LHR2, LHR3
example:
Gigabyte Auros 3070 LHR3 (V2 LHR) ~42MHASH.
|
|
|
|
I have been using miningpoolhub with high intensity, but seems like pool hashrate has been lower with versions since the timeout bug occurred.
Try with -t 80 I have reproduced on one of my amd rigs. 1 card seem to timeout. This causes the miner to restart, and recreate dag / loss of poolside hashrate. I am trying 1.35 with -t 80 now.. The default -t 20 in v1.35 is too short. edit: 3 hours stable with -t 80 , so this is a fix for miningpoolhub and crazypool in v1.35 |
|
|
|
|
The new Team Black Miner is optimized for the RTX4000 with only 0.5% fee. You should check it out. Available in hiveos.
works best on 2miners.com, miningpoolhub, nanopool.org, f2pool and a few others. You can try run with -E 3000 on these pools. (--xintensity)
|
|
|
|
|
Changing pool and increasing the intensity will increase the poolside speed. This miner is a staleshare miner. It's by design.
In 1.36 we have identified and fixed a couple of buffer errors that could cause crashes. The AMD kernel has been rewritten and optimized. Will release soon.
|
|
|
|
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/stWmdM3bugs reported.
The bugs you reported have been added to our github and been fixed https://github.com/sp-hash/TeamBlackMiner/issuesI 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 |
|
|
|
|
run tbminer --list-devices to get the device order
--cl-devices [1,2,3]
Run the .reg script fir colors or add --no-ansi
|
|
|
|
|
Did you run tbminer --list-devices to check the device order? The device order could be different from other programs.
|
|
|
|
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]. |
|
|
|
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. |
|
|
|
|
Enable faat memory timings. Disable amd watchdog. use msi afterburner for oc. Use the Team Black Miner. 69 Mhash
|
|
|
|
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 |
|
|
|
RX6600 (non-XT) 8GB
Please check and tell me what should I do ?
I have XFX and Powercolor two rigs.
The Team Black miner is working good on the AMD RX 6x00 series. Please check it out. |
|
|
|
|
you should get around 72MHASH with The Team Black Miner and --lhr-unlock 1
V1.35 can unlock LHR 4 cards as well.
|
|
|
|
|
Show Posts
