v1.02 of The Black Pill 100% LHR unlocker released.

Check out new The Black Pill enlargement tool 100% LHR unlocker for NVIDIA LHR cards.

https://bitcointalk.org/index.php?topic=5398536.0

Unlock  your LHR cards and hash at fullspeed with the Team Black Miner, Phoenixminer, Srbminer, Miniz, ethminer etc..

Hello,

I have 5 RX580 8Gb cards under HiveOS.

GPU 1 is always getting HW errors... but the strange thing is that it's happening with any card listed on GPU 1 !



I first thought it came from the card or the riser but I figured out that this is not hardware related problem.

I thought it's the biosmod but I tried with the stock rom and it it does not change anything

I removed the GPU 1 card from the rig and replaced it twice with 2 different GPUs (different risers, power cable...) on the PCI slot. They all got a lot of HW errors…
When they are recognized as GPU 2/3/4/5 they are working without issues.

I also leaved the PCI slot of GPU 1 empty and only pu the cards on the other PCI slots of the motherboard: GPU 0 / GPU 2 / GPU 3 / GPU 4 / GPU 5



But I suppose the computer does assign the PCI slot of GPU 2 (PCIEX1_2) as GPU slot 1. Indeed there are always HW errors indicated in GPU 1…while physically there is nothing on this slot.

I configured the BIOS as indicated in the manufacturer's instructions. (https://www.gigabyte.com/MicroSite/462/mining.html)

I can't figure out what is causing this issue.. ? A BIOS setup? A hardware problem with the motherboard? It's a GA-H110-D3A (Gigabyte). Bios is up to date.

I am using HiveOs and Teamredminer (But also tried under other miner and SimpleminingOs)

Thank you 🙂

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.

What is your up time ? With tweak ?

a lot of invalid shares.

Are you using the latest Mesa OpenCL libs for AMD cards in your latest build, or are you using the original bionic libs?  

If it's the newest Mesa drivers, then I think we're out of luck on HiveOS since Mesa ceased supporting Ubuntu version 18.04 LTS and is only publishing new libs for version 20.04 -> 21.04 LTS.  


EDIT:

Also, to at least get the correct GLIBCXX do the following:

sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt update
sudo apt install gcc-9
sudo apt install libstdc++6

strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | grep GLIBCXX

root@***:~# strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | grep GLIBCXX                                                                                                                                        
GLIBCXX_3.4
GLIBCXX_3.4.1
GLIBCXX_3.4.2
GLIBCXX_3.4.3
GLIBCXX_3.4.4
GLIBCXX_3.4.5
GLIBCXX_3.4.6
GLIBCXX_3.4.7
GLIBCXX_3.4.8
GLIBCXX_3.4.9
GLIBCXX_3.4.10
GLIBCXX_3.4.11
GLIBCXX_3.4.12
GLIBCXX_3.4.13
GLIBCXX_3.4.14
GLIBCXX_3.4.15
GLIBCXX_3.4.16
GLIBCXX_3.4.17
GLIBCXX_3.4.18
GLIBCXX_3.4.19
GLIBCXX_3.4.20
GLIBCXX_3.4.21
GLIBCXX_3.4.22
GLIBCXX_3.4.23
GLIBCXX_3.4.24
GLIBCXX_3.4.25
GLIBCXX_3.4.26
GLIBCXX_3.4.27
GLIBCXX_3.4.28
GLIBCXX_3.4.29
GLIBCXX_DEBUG_MESSAGE_LENGTH

sudo apt-get install gcc-4.9

strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | grep GLIBCXX

I will build 1.39 today with fixes for Ethproxy pools and 0 rejected shares.



This bug has been there since version v1.00 Poolside rejects on hiveon.net and ezil.me and some other pools that use the ETHPROXY protocol.
In the later versions we have improved the reject rate abit, but I think v1.39 will remove them all together. A stratum problem solved on NVIDIA and AMD rigs.

Selecting the correct pool has been important when using TBM, but perhaps this will change after the bugfixed release is out.

I seem to be getting build errors with the latest HiveOS release.

Initially I was getting errors for the libc++ library and GLIBCXX_3.4.26 wasn't found in the core s0.6:

./TBMiner: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by ./TBMiner)

so I upgraded the GCC compiler libraries to include .26:

apt-get upgrade libstdc++6
apt install gcc-9


but now I'm getting a OpenCL build error:

terminate called after throwing an instance of 'cl::BuildError'
  what():  clBuildProgram

So, now I'm stumped because I've updated the gcc compiler, the libraries and this is an internal build process, so I have no information about where it might be failing.  
Any help would be appreciated.

sudo apt-get install --only-upgrade libstdc++6

Could you tell me flighsheet example for toncoinpool.io in HiveOS ?
it is the only one pool which supports worker name.
I m currently using their miner but i want to use lolminer.

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?

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

Thanks for your support.
This miner might be harder to setup correctly, but if you do, you will be rewarded.

I plan to create a new improved autotune in the next release which will check 72 kernels/launchconfigs instead of 8 today. Playing with the --dagintensity in v1.35 can actually gain a little bit on some cards. The default 9 is not always the fastest.
The modification is not done on amd cards yet, but can be implemented. I might seperate the tweak into a new setting.

Se in my previos post.

Regression logs showed problems with 1.32 and 1.33 . GPU timeouts, and stratum timeouts.

On some of my test rigs the rig was sleeping for 3 minutes almost every hour, loosing 5% poolside hash. For single card rigs not a problem, and might work on some pools. But still a pretty serious bug. We are working on a better fix. The 1.34 windows version still have stratum disconnects but only 5 seconds instead of 180++

v1.33 will have an improved hashrate on the 3080ti (LHR) + 10MHASH stable. The 3080ti and 3060 LHR1 can run for 24 hours without triggering LHR, but I have problems with the 3070 LHR2.

[moderator's note: consecutive posts merged]

Have you tried these settings on MiningPoolHub?