For this release, do we still need to specify the xintensity value since by default it is configured to 1200?
No need if you mine on miningpoolhub, 2miners, nanopool and many others. But Flexpool, ethermine, nicehash probobly need a lower --xintensity |
|
|
|
All my gpus in all rigs are in P0 state for many years, it is something else.
Here in p0 clocks are stable except when temp is to hot, or the card doesn't have enough power. Anyway v1.14 has been released. check it out. v1.14 has few detected stales on miningpoolhub on --xintensity 1200 (default) and the poolside profit is amazing. |
|
|
|
It's from mmpOS shell
So it's a bug in mmpOs. The cuda toolkit has a switch to sort gpu's. We use the sortorder of the best gpu first in the list. (default) v1.14 beta has been released. Windows only for now.
Team Black Miner V1.14 beta v1.14 1. Added gpu watchdog, Automatic restart gpu threads on crash. 2. Fixed amd-only option if nvidia drivers where installed but no nvidia gpus enabled. 3. Faster NVIDIA. Increased the default xintensity. Decrease the --xintensity on pools that doesn't pay for stale shares. 4. Force the average hashrate to display at startup even if it has few samples. https://github.com/sp-hash/TeamBlackMiner/releases/TeamBlackMiner_1_14_cuda_11_4_beta.7z https://www.virustotal.com/gui/file/58103e66bf9957dfa32b0b5ff01f6c14ea499d936a00d1bf949a28beb5539682?nocache=1 [moderator's note: consecutive posts merged] |
|
|
|
|
Your sortorder is strange seems to be an index mismatch. Cuda normally sort the best cards first in the rig, so I would expect the 3080 cards be be listed first
this is not the original output of the miner:
[2021-10-12 13:42:05][info][miner/0]:
so where did you get it from?
|
|
|
|
--amd-only
ok. thanks. Found it. Fixed in 1.14 |
|
|
|
Your miner does not support core-locking and i dont like to lock cores by hand for every gpu in that rig (3060 rev 1, 3060 ti, 3070).
If it can be done with the nvidia-smi it's easy to include. We write it down as a feature request. Locking the clocks can also be done by forcing the gpu into p0 state with the nvidia profile inspector. Reboot the rig, and then set the clocks in Msi afterburner afterwards. The clocks will stay the same after reboot if you click on the box to remember your settings. So you only need to tune once, until you reinstall the driver.
It seems it's looking for NVidia cards, not present on this rig...
What does your launch config look like? (bat file) [moderator's note: consecutive posts merged] |
|
|
|
Another problem I found with my rig with just AMD RX6800 cards:
│[2021-10-12 11:43:48][info][miner/0]: 0m [2021-10-12 11:43:45.318] GPU0 XIntensity set to 352
Solutions?
352 is too high xintensity for AMD cards [2021-10-12 11:43:48][info][miner/0]: 0m [2021-10-12 11:43:47.215] source/sp_workers/cuda_gpu.cpp:cuda_get_num_devices():73: A cuda runtime error occured: no CUDA-capable device is detected
But this could be a bug. was this in v1.13? |
|
|
|
Reducing mem clock on 3070 did the trick.
I found this annoying bug: starting the miner, on some cards, it takes some time before showing the average hashrate.
Seeing some cards at 0MHs could trigger watchdog and reboot rig.
It won't trigger the watchdog. When you increase the intensity gpu samples take longer time to complete and the average is only calculated if you have enough samples. We could let the average be calcuted of the existing samples but then the speed will trottle in the beginning. |
|
|
|
|
reduce the clocks and or increase power on gpu4. --xintensity 1024 is fine with miningpoolhub. Stales are rewarded 100%, so stale count doesn't matter
|
|
|
|
Testing Flexpool with xintensity 896:
│[2021-10-12 07:39:34][info][miner/0]: 19m [2021-10-12 07:39:33.269] flexpool.io (ethash) PING: 26ms DIFFICULTY: 0.931 EPOCH: 446
You are using port 4444 on flexpool which is 4GH if you use high intensity switch to port 14444 which is 100GH. If not, you will get too many stale shares..
When I start the miner I always got these warnings, is it normal?
Do you have 2 instances of the miner running on the same computer? Find the option to switch off the api, or change the api port
1-2 times 1.13 got lagging, so no new entry to see, gpu temp also show no mining because its cold. Press enter helped.
This is an issue in windows 10 if you mark text in the commandline window, the app will stop mining. f.ex by rightclicking in it. Has nothing to do with the version number.
I suggest that you report issues on our github https://github.com/sp-hash/TeamBlackMiner/issues4 open, 53 closed. The watchdog has been completed in v1.14. If a gpu crash because of high oc and don't report hashrate in 3 minutes, the watchdog will restart the thread. This will improve the performance on rigs with "has timed out" messages. Every time the EPOC changes, TBMiner have to recalculate the DAG buffer. If the rig is tuned too high clocks, v1.00 - v1.13 could crash with "has timed out" messages. [moderator's note: consecutive posts merged] |
|
|
|
Only with core-lock 1.10 and newer will be as fast as 1.09. What i dont like in 1.09 - high cpu usage.
Core lock? Increase the Temp limit so the cards don't trottle. The cpu usage in 1.09 is increasing the hashrate with 1-2% on low intensity but using too much power to be justified. We can add a flag --cpu-mining in the next version. If you use 1.09 with --xintensity you have to multiply by 4 to compare the two versions.
Been running TBM 1.13 with xintensity 352 for 8 hours and my results are below:
485m [2021-10-11 20:07:37.418] ID BOARD HASHRATE/W HASHRATE AVERAGE SHARES
485m [2021-10-11 20:07:37.418] GPU0 3060Ti 436.17 kH/W 64.99 MH/s 64.99 MH/s 133/0/0 485m
[2021-10-11 20:07:37.418] 2470.18 kH/W 389.84 MH/s 389.85 MH/s 845/1/0 (99.88)
Looks good with no calculated stale shares. The most important is how is the payout / poolside reward? Try with --xintensity 1408
Which xintensity should I set on Flexpool for the following cards to get the best performances? - NVIDIA RTX 3080 and 3070 (not LHR)
- AMD RX 6800 and 6800 XT
On flexpool you should mine on the high difficulty port. Why don't you try out 10 intensities and check yourself? What hashrate are you getting with rtx 3080 --xintensity 1200 ? Amd cards works best with lower --xintensities than NVIDIA teamred miner: 58.8
s-eth.2miners.com:2020 (ethash) DIFFICULTY: 2.03 EPOCH: 440
(At least 2 shares/10 mins at each intensity)
'Stock' settings - 6800xt (2400 clock / 1990 mem)
Xintensity = -1: 62.32
Xintensity = 1: 58.51 - 213W
Xintensity = 12: 61.10
Xintensity = 24: 61.94
Xintensity = 36: 62.03
Xintensity = 48: 62.11
Xintensity = 78: 62.15
Xintensity = 128: 62.33
Xintensity = 240: 62.60
Xintensity = 360: 62.64
Xintensity = 512: 62.70 - 230W
No shares reject
[moderator's note: consecutive posts merged] |
|
|
|
|
In the later versions on Nvidia you need to multiply the xintensity by 4 (cuda 11.4 build)
1.09: rtx 3080 --xintensity 300... 109MHASH
1.13: rtx 3080 --xintensity 1200... 109MHASH
We nerfed it because of too many stale shares and poor results on some pools.
|
|
|
|
Is there a thread link to this suggestion?
Also, would that increase more stale shares submitted since we are increasing the xintensity?
Scroll a few pages back and look at the pictures. Miningpoolhub pay 100% for stale shares so it doesn't matter. 2miners, nanopool, wollypooly 100% as well. ezil.me 70% , hiveon.com 80%. Flexpool, ethermine, nicehash, binance pay 0%. So the configuration of the mining software needs to be changed accordingly Note that the ethereum blockchain rewards stale work/blocks. They are called uncle blocks. The uncle blocks are protecting the security of the blockchain. For bitcoin based blockchains stale work is not rewarded and not needed. |
|
|
|
On miningpoolhub try --xintensity 352 (suggested by one of the other users)
We are making a watchdog to be able to detect gpu's that are hanging / timed out. Hopefully done in v1.14  [moderator's note: consecutive posts merged] |
|
|
|
384m [2021-10-11 15:42:39.022] ID BOARD HASHRATE/W HASHRATE AVERAGE SHARES
384m [2021-10-11 15:42:39.022] GPU0 5500XT 0.00 H/W 27.75 MH/s 27.85 MH/s 149/0/2 (100.00)
On the 5500XT try --xintensity 24, no stales poolside, lower power |
|
|
|
|
This is how you can configure ETC+ZIL on miningpoolhub.com / shardpool.io with tbminer. Inside the miningpoolhub page you can configure to autosell the ETC to get ethereum.
Set ETC_WALLET=(miningpoolhub username)
Set ZIL_WALLET=(zil_wallet)
:loop
TBMiner --algo ethash --hostname eu1-zil.shardpool.io --port 3333 --wallet %ETC_WALLET% --server_passwd %ZIL_WALLET%@europe.etchash-hub.miningpoolhub.com:20615 --worker_name %computername% --xintensity 256
timeout 10
goto :loop
on zergpool you can mine ethereum classic and get payed in ethereum:
set WALLET=(ethereum adress)
set PAYOUT_CURRENCY=ETH
:loop
TBMiner --algo etchash --hostname etchash.eu.mine.zergpool.com --port 9997 --wallet %WALLET% --server-passwd c=%PAYOUT_CURRENCY%,ID=%computername% --xintensity 128
timeout 10
goto :loop
Play with the --xintensity to get higher hashrate.
|
|
|
|
Can you verify how ethermine is on your 3090? I can crank the intensity upto 350 without issue but I see 224 being suggested a lot. Thoughts?
--xintensity 350 produce more stale shares than 224 and ethermine seems to have a reduced payout for stales, but you can try. Increased intensity usually give more hashrate, but more stale shares and powerusage. miningpoolhub.com pay for stale shares and 350 can be used with good results.
10 mhs slower with 6 gpu rig, just try it a couple minute ago
What cards in the rig, which pool, which launch configuration?
Can't exclude cards when AMD and Nvidia cards are selected.
This is is supported run tbminer --list-devices Manually specify which devices you want, start with cl, then cuda. Make sure that you don't select the same device for cuda and cl because cl is supported for NVIDIA devices as well --cl-devices [1,2] --cuda-devices [0,2] [moderator's note: consecutive posts merged] |
|
|
|
|
Anybody else get the Ansi graphics problem? I have submitted another possible fix in v1.14
|
|
|
|
|
You can mine ethereum classic with ethereum payout on zergpool.com with The Team Black miner
|
|
|
|
|
Show Posts
