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

[KillrBee]

My latest and most stable TBM 1.22 run -- photos and a short video to show that I'm not photoshopping or showing very unstable results as being useful.

https://imgur.com/a/BIjeDaU

https://imgur.com/a/w4nAwqo

https://imgur.com/a/stWmdM3

[1714652031]

1714652031

[1714652031]

1714652031

[1714652031]

1714652031

[sp_]

My latest and most stable TBM 1.22 run -- photos and a short video to show that I'm not photoshopping or showing very unstable results as being useful.




https://imgur.com/a/stWmdM3

Nice screenshots, thanks for testing.

You should post the video on youtube.

[duddabudda]

My latest and most stable TBM 1.22 run -- photos and a short video to show that I'm not photoshopping or showing very unstable results as being useful.

https://imgur.com/a/BIjeDaU

https://imgur.com/a/w4nAwqo

https://imgur.com/a/stWmdM3

Hi KillrBee!
Uptime worker 18h?

[KillrBee]

My latest and most stable TBM 1.22 run -- photos and a short video to show that I'm not photoshopping or showing very unstable results as being useful.

https://imgur.com/a/BIjeDaU

https://imgur.com/a/w4nAwqo

https://imgur.com/a/stWmdM3

Hi KillrBee!
Uptime worker 18h?

Yes, it had been running for almost 18 hours, it's now at 23 hours.

[sp_]

1.23 will have a tiny speedup in the cuda 11.5 build for nvidia.
For AMD less stale shares on etheremine, flexpool, crazypool and nicehash. We use --xintensity 24 as default on these pools instead of -1.

v1.23 will be released tomorrow

[dle378]

1.23 will have a tiny speedup in the cuda 11.5 build for nvidia.
For AMD less stale shares on etheremine, flexpool, crazypool and nicehash. We use --xintensity 24 as default on these pools instead of -1.

v1.23 will be released tomorrow

What will the default xintensity value be for Nvidia cards?

On another note. I am currently running xintensity 1025/dagintensity 9 for 3060 TI’s FE for more than 12+ hours with 0 reject shares.

[sp_]

What will the default xintensity value be for Nvidia cards?
On another note. I am currently running xintensity 1025/dagintensity 9 for 3060 TI’s FE for more than 12+ hours with 0 reject shares.

Same intensity but different, you will see tomorrow.
The xintensity is pool dependent. Flexpool and crazpool will not work with xintensity 1025. (4% stale shares)

[dle378]

What will the default xintensity value be for Nvidia cards?
On another note. I am currently running xintensity 1025/dagintensity 9 for 3060 TI’s FE for more than 12+ hours with 0 reject shares.

Same intensity but different, you will see tomorrow.
The xintensity is pool dependent. Flexpool and crazpool will not work with xintensity 1025. (4% stale shares)

I am only using that value when mining on 2miners or miningpoolhub.

Other pools it would be either 224 or 256.

[br2459]

1.23 will have a tiny speedup in the cuda 11.5 build for nvidia.
For AMD less stale shares on etheremine, flexpool, crazypool and nicehash. We use --xintensity 24 as default on these pools instead of -1.

v1.23 will be released tomorrow

Hi sp_. Will 1.23 have the new LHR unlock or is that still work in progress?

[sp_]

We still haven't bought a LHR2 card. The LHR1 seem to unlock, but not always.
Buying amd cards seems to be the best option right now... Enable Smart Access Memory ...

[duddabudda]

1.23 will have a tiny speedup in the cuda 11.5 build for nvidia.
For AMD less stale shares on etheremine, flexpool, crazypool and nicehash. We use --xintensity 24 as default on these pools instead of -1.

v1.23 will be released tomorrow

Yeah! Good news!!

Thx sp_ for support amd cards, anyone miner-dev not develop something  new for 6x00 all busy unlocking stupid lhr cards)

May you write tutorial how update miner after release without update hiveOS? so as not to wait for the hive to release an OS update with a new version of the miner.

[varadero]

I have this error message again under hiveos while under t-rex I have been stable for more than 15 days

https://i.ibb.co/BcbDkkW/1.jpg

https://i.ibb.co/THtgTSY/2.jpg

[sp_]

I have this error message again under hiveos while under t-rex I have been stable for more than 15 days

Try to add --dagintensity 1


v1.23
1. Tiny speedup on Nvidia cards. Faster on lower intensity than before.
2. More accurate kernel autotune. Now running twice as long as before.
3. Reduced stales on ethermine.org, flexpool.org, crazypool and nicehash on amd (default --xintensity 24)
4. Console stats are rewritten to work with all terminals.
5. Fixed zil mining at rustpool.
6. Fix index problem in set memclock / coreclock / powerlimit (nvidia)
7. Added --tweak parameter for nvidia 0-7
8. Added more pools.

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

TeamBlackMiner_1_23_cuda_11_5.7z
https://www.virustotal.com/gui/file/ed205b60b676f6d25f8fb703b083c1090e2992355fa198cf241333e60707ecad?nocache=1

TeamBlackMiner_1_23_cuda_11_4.7z
https://www.virustotal.com/gui/file/4e9353c90f7b4b7358a204bafd88d8f9b207fd76584754d2750b270499f2e87c?nocache=1

TeamBlackMiner_1_23_cuda_11_2.7z
https://www.virustotal.com/gui/file/6f9fef1bc06ad7b12f6f89fd2aa0a3a1a4439625bf87dd648a1ee2b3ff7e0e06?nocache=1

TeamBlackMiner_1_23_Ubuntu_18_04_Cuda_11_4.tar.gz
https://www.virustotal.com/gui/file/0a6cfcac33ae044475564d0fd00cea87dda8fc5e0c612c4a2da85de8e75bf539?nocache=1

TeamBlackMiner_1_23_Ubuntu_18_04_Cuda_11_5.tar.gz
https://www.virustotal.com/gui/file/5de9d43c5c847e746a8f4008d07af7db50d754a16e68952eaead120a51042fcc?nocache=1

May you write tutorial how update miner after release without update hiveOS? so as not to wait for the hive to release an OS update with a new version of the miner.

here is a toturial how to upgrade: (v1.16 to v1.19) , but replace 1.16 with 1.22, and 1_19 with 1_23

To install v1.19 on HiveOS, after 1.16, follow these steps

Code:

cd /hive/miners/teamblackminer/1.16/
mv TBMiner TBMiner.1.18.bak
wget https://github.com/sp-hash/TeamBlackMiner/releases/download/v1.19/TeamBlackMiner_1_19_Ubuntu_18_04_Cuda_11_4.tar.gz
tar -xf TeamBlackMiner_1_19_Ubuntu_18_04_Cuda_11_4.tar.gz
cp /hive/miners/teamblackminer/1.16/TeamBlackMiner_1_19_Ubuntu_18_04_Cuda_11_4/TBMiner /hive/miners/teamblackminer/1.16/

>It seems that TBMiner is arlready executable (type ls then hit return, TBMiner should be green)
>if not, run this command
chmod +x TBMiner

Then type miner restart and hit return

[moderator's note: consecutive posts merged]

[bliko911]

Hey sp_,

Thanks for your work, - just sharing some feedback: 5 x RX 6600 XT rig went from 160 Mhs to 171 Mhs. Is that a solid 6.8% increase or what?

https://ibb.co/nLfr1Hf

Further, another rig of 8 x  RX 5600 XT's went from 336 Mhs to 350 Mjs, however, - after swapping to TBM (from TeamRedMiner), GPU 3 started "dropping". It stops mining and nothing happens, - other cards remain online. I dropped the memory clock by 15, then GPU 0 started doing the same - a "gap in hashrate" can be visitble in the below snippet. So, I ended up decreasing the memory clock by 15 as well. However, an increase of 4.1% is very, very pleasant to see.

https://ibb.co/Hhr6qcZ

Thanks again, all the best,
Ric.

[sp_]

Hey sp_,

Thanks for your work, - just sharing some feedback: 5 x RX 6600 XT rig went from 160 Mhs to 171 Mhs. Is that a solid 6.8% increase or what?



Further, another rig of 8 x  RX 5600 XT's went from 336 Mhs to 350 Mjs, however, - after swapping to TBM (from TeamRedMiner), GPU 3 started "dropping". It stops mining and nothing happens, - other cards remain online. I dropped the memory clock by 15, then GPU 0 started doing the same - a "gap in hashrate" can be visitble in the below snippet. So, I ended up decreasing the memory clock by 15 as well. However, an increase of 4.1% is very, very pleasant to see.



Thanks again, all the best,
Ric.

Nice results. If you want to remove stale shares on ethermine use --xintensity 24 or perhaps --xintensity 8 can work as well. Lower number, less stale shares, but can hurt performance on some rigs.

[varadero]

always the same same with --dagintensity 1

https://zupimages.net/up/21/44/ogi2.jpg

[sp_]

always the same same with --dagintensity 1

Upgrade to v1.23. If it doesn't work Lower the memclock -100, -200 until it's stable.

[cryptoinvestor_x]

I seem to consistently get a lower avg hashrate when running it on HiveON as opposed to TeamRedMiner even though the miner reports higher hashrates. Stales seem to be under control. This has been running for 7 days so it should have averaged out any hashrate fluctations, on TBM 1.22 kernel 8 default xintensity.

https://imgur.com/a/8sRz7K7

[sp_]

This has been running for 7 days so it should have averaged out any hashrate fluctations, on TBM 1.22 kernel 8 default xintensity.

You get best results if you change the pool, but you can try 1.23 with --xintensity 144. It's not only about stale shares, it's the way the protocol on the pool works and how much work the miner needs to throw away. Jobs are too frequent. v1.23 has an increased performance on lower --xintensity so should work better on the hiveon pool.

[mo35]

Im experiencing weird issue , starting from 1.22 (prolly 1.21 , skipped that one) , at some point shares stops validating on cpu , experiencing that on 2 separate boxes, one with 3080 & 5900x on shardpool eth/zil , second with 2060 cards and 3700x on ethermine. rolling back to 1.20 issue goes away, no overclocks , default intensity , using --no cpu. CPUs mining ghostrider , but on each cpu couple cores left free. ideas ?

edit: caught one on 1.20 also , see below