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

[KillrBee]

Hello there.

By no way i can use LHR unlock.

System:

- hiveOS with latest TBM 1.55 cuda 11.4

- 2 GPU 3060ti LHR with Hynix memory

- OC on both: 1350 CC / 2100 memory / pl 0

- In that rig they are 5 gpus working with TBM all nvidia, this two lhr gou are the 4 and 5

I used the --lhr-unlock [0,0,0,1,1]

Didn't catch any lhr unlock point and went to the 50th try of the miner and stayed reseting it

What am i missing from this tune ?

Thanks for all the help

Cheers

Make sure that the actual card location you're using is the one from TBMiner --list-devices since the order in HiveOS might be different than the order in which the miner assigns them, and I think, depending on the version of your 3060ti, you may need to use the CUDA 1.13 distro that you will need to get from TBM's Git site and copy the TBMiner executable into the /hive/miners/teamblackminer/1.55 directory (since Hive is only supplying the CUDA 1.14 version with 1.55), which will unlock the version 1 LHR (I think -- not an expert here since I don't have any LHR cards).

[1714011779]

1714011779

[1714011779]

1714011779

[sp_]

Is there a chance for a bit Win7 support? [for ETC mining on 1050 Ti]

Windows 7 will not be supported, but you can mine ETC on the 1050ti on windows 10
------------------

since Hive is only supplying the CUDA 1.14 version with 1.55), which will unlock the version 1 LHR (I think -- not an expert here since I don't have any LHR cards).

The correct name is cuda 11.4 and cuda 11.5. The LHR unlock was made for cuda 11.5, but should work on cuda 11.4 builds as well. The lhr autotune code needs to be enabled with --lhr-unlock [1,1,1,1,1]. One entry per card in the rig.

1 = on, 0 = off

You can adjust the starting point of the unlock to avoid the card resetting many times, and loose average hashrate.

here is my rig running v1.55 for 5 hours without triggering the lhr: (passive powersave unlock setting)


If you want to try to increase the hashrate you can increase the --lhr-unlock  value

--lhr-unlock  [10,10,10,10...] or higher, but might trigger lhr. So a higher hashrate in the miner window. (80-90MHASH 3080ti, but also a higher lost hashrate rate because of gpu reset's)

Latest nvidia driver on windows:



------------------

- OC on both: 1350 CC / 2100 memory / pl 0

You need to use the the --lock-cclock option in the miner instead of setting clocks in hiveos. When locking the clock low, the gpu will automaticly undervolt to save power. The LHR mode only works with lower power.

[Riptide_NVN]

Cards are 6000 series AMD mixed but all reference.
Pool is crazypool.

Anyone running in hive? Does this flight sheet look correct? TIA

https://imgur.com/a/q1vneep

[sp_]

SSL Port 5555 is not working.

you need to remove the TLS and use the statum port 3333

[Riptide_NVN]

Hey thanks I'm up and running with 3333.

I am getting a lot of invalid shares. I did set the intensity to 24 which was suggested for 6000 series cards. I am using the same overclocks and settings that worked OK with team red. How do I resolve this issue with the invalid shares?

Thanks

https://imgur.com/a/y76Ro55

[sp_]

How do I resolve this issue with the invalid shares?

You need to upgrade to the latest version. 1.56

v1.56

1.  Fix gpu timeouts AMD.
2.  Fix rejects at crazypool.org

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

TeamBlackMiner_1_56_cuda_11_5.7z
https://www.virustotal.com/gui/file/7d9dcf1c8de6c116557d349a70e2bc51f00bc82c6c1ccb74cb40f8be61bc7dcb?nocache=1

TeamBlackMiner_1_56_cuda_11_4.7z
https://www.virustotal.com/gui/file/d7b5fe82a1efa72a5a573e6e92bf5e0efa87c5c16810d8e510cefe791fc80c17?nocache=1

TeamBlackMiner_1_56_Ubuntu_18_04_Cuda_11_4.tar.xz
https://www.virustotal.com/gui/file/7f1b12a2a228f7d71f8423d5a225d3e3464bbe3f7fa6a523897b1d11de9c4ebd?nocache=1

TeamBlackMiner_1_56_Ubuntu_18_04_Cuda_11_5.tar.xz
https://www.virustotal.com/gui/file/8ed7a8edd0a7ab0d8368608345c09b0af809408b3fa5acfcfa699f9da665b13a?nocache=1
---------------------------------------

[Riptide_NVN]

Once it is available in Hive then I will go ahead and give that a try thank you very much. I kept the flight sheet so should be easy to try once I update.

0.6-213@220220 is showing as a 'miners update' and doesn't note the new version of TBM so it may be a few days before I can try this.

[sp_]

0.6-213@220220 is showing as a 'miners update' and doesn't note the new version of TBM so it may be a few days before I can try this.

0.6-213@220220 🐧

What's new?

MINERS 👷‍♂️
⛏ TeamBlackMiner v1.56
* Fixed timeoutson  AMD GPUs
* Fixed rejects at crazypool

[Riptide_NVN]

I don't doubt it. They are hiding this somewhere on their website though. The changelog doesn't even mention this and when I try the dropdown on the rig dashboard it just says the same thing 'miners update' with no details.

https://hiveon.com/changelog/?type=All&page=1

[KillrBee]

0.6-213@220220 is showing as a 'miners update' and doesn't note the new version of TBM so it may be a few days before I can try this.

0.6-213@220220 🐧

What's new?

MINERS 👷‍♂️
⛏ TeamBlackMiner v1.56
* Fixed timeoutson  AMD GPUs
* Fixed rejects at crazypool

Yeah, it's not showing as an option in HiveOS, I still have to hijack 1.55 with the 1.56 executable.

--scratch that.  It's there but the HiveOS GUI hadn't updated, I had to log out and log back in for it to show up on the miner configuration flight sheet dropdown.

Also, have there been any changes to the CUDA 11.5 compilation for Linux?  It still is underperforming compared to 11.4 on HiveOS with both the CUDA 11.5 and 11.6 Nvidia drivers.

[Riptide_NVN]

I have two AMD 6000 series rigs and have switched over to 1.56 late yesterday on crazypool. I'll let it go a few days and then run a comparison on pool side stats for shares.

With same settings as TRM power consumption is a bit higher. For example, one rig went from 570w to 592w moving over to TBM. Software figures there but power at the wall seems to back it up increasing an additional 30w over TRM. With additional tinkering it MAY be possible to pull that back down however I'm not going to spend time trying until the initial test is over and I can compare the pool side shares over a few days at least.

[sp_]

I have two AMD 6000 series rigs and have switched over to 1.56 late yesterday on crazypool. I'll let it go a few days and then run a comparison on pool side stats for shares.

Crazypool doesn't pay for stale shares and is not a recomended pool for The Team Black miner. You might need to reduce the default xintensities to get fewer rejecs/stales.

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

With same settings as TRM power consumption is a bit higher. For example, one rig went from 570w to 592w moving over to TBM.

More power and higher hashrate. With the right miningpool and the right settings. +5-10%

[Riptide_NVN]

I'm not done testing it as one day isn't conclusive. So far at same settings I ran with team red I am getting about 0.5-0.75% more stales on crazypool with the slightly higher power use. Going to test through tomorrow and check the result.

I could try reducing intensity to knock down the stale shares however reducing intensity, I assume, would also pull back hash rate and possibly overall shares. It may be that while it works better than it used to and has improved quite a lot team red is just going to be a better option right now for crazypool since they do not pay any stales.

If I were to reduce intensity below 24 what do you recommend trying next sp?

[sp_]

For crazypool and other pools that doesn't pay for stale shares:

Users report less stales with --xintensity 24 on AMD cards. <1% . If you reduce it lower than that, f.ex 16 the lost performance will probobly eat up the gain.
But Lower intensity = lower power.

But why mine on crazypool, when you can get +10% more poolside hash on other pools. Are they paying +10% or more per MHASH than 2miner.com f.ex?

Crazypool only have 0.2% of the ethereum network hash

[Riptide_NVN]

Currently I'm specifying intensity 24.

Before employing TBM I was getting stales of around 0.5-0.8%. Now I'm seeing around 1.25-1.5% so this is within the range you specified and not anything unusual.

I mine on crazypool because they tend to be one of the more profitable pools to mine at and I prefer to mine on smaller pools. They also have a lottery system which affords the chance to win 0.1 ETH.

The git page seems to have some odd information here:
https://github.com/sp-hash/TeamBlackMiner/blob/main/FAQ.md
Conflating uncle blocks and stale shares. Even if that were true, crazypool does find and pay out uncles.

I checked a few of the pools on the page (MPH, f2pool, 2miners) for their stales policy. MPH and 2miners don't say anything about it one way or another. F2pool indicates they don't pay stale shares.

The client seems to be running per expectation on my end and I'm going to continue with it for a couple more days to get a conclusive result to compare with.

[sp_]

I checked a few of the pools on the page (MPH, f2pool, 2miners) for their stales policy. MPH and 2miners don't say anything about it one way or another. F2pool indicates they don't pay stale shares.

On 2miners you can also get a rejected shares (stale). The difference is that 2miners always pay 100% for level1 stale shares. The ethereum blockchain reward stale work, so pools have a different definition of what a stale share is. On the 2miners pool you can get 100% accepted shares with --xintensity 512 and 0 stale shares, on crazypool you get ~5% stales. Miningpoolhub, f2pool,nanopool accept more shares.  You can get a 5-10% higher poolspeed, and this will almost always lead to a higher profit.

Conflating uncle blocks and stale shares. Even if that were true, crazypool does find and pay out uncles.

It's the reward system on crazypool that is odd. Every miner that find an uncle block will get his work rejected(stale), and the profit from the work will be divided to the other miners that have more accepted shares. Uncleblocks are securing the ethereum blockchain, and if every miningsoftware and pool try to remove the reward , it could be dangerous.

[KillrBee]

Currently I'm specifying intensity 24.

Before employing TBM I was getting stales of around 0.5-0.8%. Now I'm seeing around 1.25-1.5% so this is within the range you specified and not anything unusual.

I mine on crazypool because they tend to be one of the more profitable pools to mine at and I prefer to mine on smaller pools. They also have a lottery system which affords the chance to win 0.1 ETH.

The git page seems to have some odd information here:
https://github.com/sp-hash/TeamBlackMiner/blob/main/FAQ.md
Conflating uncle blocks and stale shares. Even if that were true, crazypool does find and pay out uncles.

I checked a few of the pools on the page (MPH, f2pool, 2miners) for their stales policy. MPH and 2miners don't say anything about it one way or another. F2pool indicates they don't pay stale shares.

The client seems to be running per expectation on my end and I'm going to continue with it for a couple more days to get a conclusive result to compare with.

So there are different levels of 'stale' that the pools deal with, and TBM reports true stales in the rejected frame - you'll see an error report back from the pool as a stale share in the TBM output, so the numbers that the TBM client is reporting are an estimate of a 'level 1' stale share and is not anything I pay attention to if I'm mining on 2Miners (which I do).

What cards are you running?  An intensity of 24 on an AMD Big-Navi RX68/900 series shouldn't be generating any stale shares -- even in the client window.   I run a rig with 6800/6800XT/6900XT in HiveOS and am averaging about 63 MH/s at the pool (but TBM is a spiky miner, so the rates over 6 hours can change from a 6 hour average of 70+ to 59 MH/s).  With the profits of ETH declining so much in the past couple of months I am loathe to give away mining secrets, but it's most likely the ASICs that are killing my profits, so here's my 6800XT details for HiveOS against 2Miners (you can test them and see if you are getting better stats on crazypool):

Version 1.56; xIntensity = 190



And those share rates on 2miners averages out to 61.5 MH/s. -  Windows will give the same client reported hashrate, but mine +2MH/s at the pool

[Riptide_NVN]

It's the reward system on crazypool that is odd. Every miner that find an uncle block will get his work rejected(stale), and the profit from the work will be divided to the other miners that have more accepted shares. Uncleblocks are securing the ethereum blockchain, and if every miningsoftware and pool try to remove the reward , it could be dangerous.

Crazypool does not remove uncle rewards. They pay the full uncle reward and it is split amongst the pool the same as any other block is. The more valid shares you have submitted then the higher your share of the reward. Uncle blocks and stale shares are not the same thing.

I've never heard of 'level 1' stale shares before this isn't a term commonly employed in the space. The stale shares reported on the pool side are not seen in the miner client output screen. The only non valid shares the miner client reports are the two rejected shares I have currently which are also shown in the hiveos dashboard.

I'm currently running the recommended intensity by the dev of 24 with my 69/68/67/6600 series cards.

[sp_]

Uncle blocks and stale shares are not the same thing.

No but stale shares can find uncle blocks and should be rewarded. In Bitcoin mining stale shares are not rewarded by the blockchain, and should not be rewarded.

[KillrBee]

I managed to pick up a 3070Ti for basically just the shipping costs and I've been trying my best to figure out how I'm supposed to interpret the TBMiner output for tuning.  The following screen shows some very confusing information and I'm wondering if there's something wrong with the setup or if this is what I should expect with LHR cards:


 

00:00:42 [2022-02-24 08:28:17.128] GPU0 LHR: 49.02 Mh (max:80.20 Mh, Lost:0.00 Mh, Reset Count:0)
00:00:42 [2022-02-24 08:28:25.357] Job 1de02
00:00:42 [2022-02-24 08:28:25.357] GPU0 LHR: 48.20 Mh (max:80.15 Mh, Lost:0.00 Mh, Reset Count:0)
00:00:43 [2022-02-24 08:28:30.049]
00:00:43 [2022-02-24 08:28:30.049]
00:00:43 [2022-02-24 08:28:30.049] us-eth.2miners.com (ethash)    PING: 48ms    DIFFICULTY: 2.03     EPOCH: 475
00:00:43 [2022-02-24 08:28:30.049]                                                                                 
00:00:43 [2022-02-24 08:28:30.049]
00:00:43 [2022-02-24 08:28:30.049] ID      BOARD    TYPE    KERN    XINT    TEMP    FAN     CORE    MEM     WATT   
00:00:43 [2022-02-24 08:28:30.049] GPU0    3070Ti   CUDA    15      19      45/0    71      1319    11028   137   
00:00:43 [2022-02-24 08:28:30.049]                                                                          137   
00:00:43 [2022-02-24 08:28:30.049]
00:00:43 [2022-02-24 08:28:30.049] ID      BOARD    HASHRATE/W    HASHRATE      AVERAGE       SHARES       RATE   
00:00:43 [2022-02-24 08:28:30.049] GPU0    3070Ti   537.18 kH/W   74.67 MH/s    48.51 MH/s    18/0/0       100.00%
00:00:43 [2022-02-24 08:28:30.049]                  537.18 kH/W   74.67 MH/s    48.51 MH/s    18/0/0       100.00%
00:00:43 [2022-02-24 08:28:30.049]                                                                                 
00:00:43 [2022-02-24 08:28:30.049] SHARES PER MINUTE: 0.42            POOL HASHRATE: 60.88 MH/s
00:00:43 [2022-02-24 08:28:30.049]
00:00:43 [2022-02-24 08:28:31.968] Job 1de03
00:00:43 [2022-02-24 08:28:31.968] GPU0 LHR: 48.27 Mh (max:80.13 Mh, Lost:0.00 Mh, Reset Count:0)
00:00:43 [2022-02-24 08:28:38.989] Job 1de04
00:00:43 [2022-02-24 08:28:38.989] GPU0 LHR: 48.53 Mh (max:80.26 Mh, Lost:0.00 Mh, Reset Count:0)
00:00:43 [2022-02-24 08:28:40.130] Job 1de05


The 'real-time' reported hashrate is showing as 74.67 while the average is being shown as 48, while the pool is showing 60.88 and the LHR line information is showing 48 MH/s, but also 80 MH/s with 0 lost...  Then, in the next minute, the real-time rate will be something like 31 MH/s...

I have the settings as LHR-unlock @ -20 and Tweak @ -3, if I let the autotune go without the tweak, it keeps resetting until about -31.

My card settings are core @ 1320 (-262), Memory @ 10790 (+1538), PowerLimit @ 72, Voltage locked at 856 mV under windows 10