Topic: Team Black Miner (ETHW ETC Vertcoin Ravencoin Zilliqa +dual +tripple mining ) - page 12. (Read 35049 times)

Please try  TheBlackPill_1804.tar.xz

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

HiveOS is now on Ubuntu v18.04.6 LTS it is about time they pull their socks up and upgrade at least to 20.04 LTS.

Getting a runtime error on HiveOS:
./TheBlackPill.x: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by ./TheBlackPill.x)
./TheBlackPill.x: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./TheBlackPill.x)

What version of Linux did you compile this on?  HiveOS is still using Ubuntu Version 16.04 LTS and I can't seem to upgrade the system to use any GLIBC_ past 2.29. 

There are probably some third party ppa: repos that would fix it, but I'm not comfortable using unverified external ppa: repos published by some random on the net.

Alternatively I could probably compile/build the GLIBC_## packages and go through the process of relinking things, but it might be at the expense of disabling part of the main kernel, since the libc is so tightly integrated with the kernel, any changes can mess a lot of things up -- and besides, as soon as an upgrade comes along that updates the kernel for the HiveOS distro, I'll have to do it all over again.

**** gcc-9 and using the ppa: for ubuntu-toolchain-r/r-test is where I can get GLIBC_2.29 functioning, installing gcc-10 -> gcc-11 don't make a difference and my entire package repo is up to date and upgraded.
 

Linux release of The Black Pill LHR hashrate unlocker added. Make sure you download from my github and not from other sources..

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

TheBlackPill.tar.xz
https://www.virustotal.com/gui/file/d5fa16087e09d0e85a63999307e9443f23503899762548adb7e31d55f0916d47?nocache


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


You can ask the hiveos devs to integrate "The Black Pill". Perhaps they will..

how to install and run third-party s/w in hiveos ? Is it same like adding custom miner?

Try the pill with your v1.27 and thank me later.

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



https://bitcointalksearch.org/topic/the-black-pill-hashrate-enlarger-tool-v101-for-nvidia-lhr-cards-5398536

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

Our 100% LHR unlock is running at full speed on the latest driver. 511.65 (windows) and works on all memory algos.

So I guess we do it a bit different than the other teams.. Linux version is delayed some more days..

When the core drops to 750 on that one card, if you're using HiveOS or linux, run "nvidia-info" and it will report if the card is being throttled and the reason for it.  If the card isn't reporting any throttle but you can't manually push it above 750 MHz then it most likely is a power problem and that particular card is sensing decreased amperage which will cause it to limit without reporting. I've seen 1000 watt PSUs that can only supply 700 watts consistently and will run into issues when loaded beyond that -- it can run 1000 watts transiently to provide power for a rapid spike load, but just not for more than a few seconds.

If core drops when you raise the mem clock - you run into the powerlimit - increase it.
I have seen similiar things on 1 of my 2060S, all of this cards run at 45mh, on 1 card, if i raise the mem - the coreclocks drops to 750. For me it makes no sense because the card only use around 120w, but the powerlimit in the bios is a little bit lower than all other cards and i can´t increase the pl over 100% it is kept there.

The lhr-unlock is pretty much done on windows. the next test is running with AMD/NVIDIA cards in a mix with high intensities on the ssl Port.

Linux tomorrow.

Try to run all the AMD cards in once instance, and the nvidia cards in one instance of the miner.

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

TBM 100% LHR unlock is coming soon.. My testcard's core clock is dropping to 900 when I boost the memory clock, and this is hurting the performance.

I read that others have the same problem, but perhaps I can tweak the kernel to use lower memory temps.




 
edit:

Stable test. Will let it run over night.



Shitty clocks on my 3080ti card because it trottle, but managed to tune it abit better. Kernel 0 with 9991 intensity.

Update: 
I did get a timeout on the AMD GPU about 5 1/2 hours after a reboot.  Cards crashed (still showed as hashing for about 4 minutes, but the calculated Hashrate/W jumped up):

00:05:26 [2022-05-07 17:36:30.130] GPU5    3090     CUDA    2       6800    43/0    95      1500    11275   333   
00:05:26 [2022-05-07 17:36:30.130]                                                                          919   
00:05:26 [2022-05-07 17:36:30.130]
00:05:26 [2022-05-07 17:36:30.130] ID      BOARD    HASHRATE/W    HASHRATE      AVERAGE       SHARES       RATE   
00:05:26 [2022-05-07 17:36:30.130] GPU0    gfx1030  1947.58 kH/W  66.22 MH/s    66.14 MH/s    133/0/0      100.00%
00:05:26 [2022-05-07 17:36:30.130] GPU1    gfx1030  2285.92 kH/W  66.29 MH/s    66.29 MH/s    128/0/0      100.00%
00:05:26 [2022-05-07 17:36:30.130] GPU2    gfx1030  2269.47 kH/W  65.81 MH/s    65.82 MH/s    144/0/1      100.00%
00:05:26 [2022-05-07 17:36:30.130] GPU3    gfx1030  1882.83 kH/W  65.90 MH/s    65.90 MH/s    135/0/0      100.00%
00:05:26 [2022-05-07 17:36:30.130] GPU4    gfx1030  2456.14 kH/W  66.32 MH/s    66.28 MH/s    137/0/0      100.00%
00:05:26 [2022-05-07 17:36:30.130] GPU5    3090     399.57 kH/W   133.06 MH/s   133.05 MH/s   296/0/0      100.00%
00:05:26 [2022-05-07 17:36:30.130]                  1873.58 kH/W  463.59 MH/s   463.47 MH/s   973/0/1      100.00%
00:05:26 [2022-05-07 17:36:30.130]                                                                                 
00:05:26 [2022-05-07 17:36:30.130] SHARES PER MINUTE: 2.98            POOL HASHRATE: 434.08 MH/s


Then they posted the failure:


00:05:29 [2022-05-07 17:39:30.159] GPU2: has timed out, trying to restart..
00:05:29 [2022-05-07 17:39:30.159] GPU4: has timed out, trying to restart..
00:05:29 [2022-05-07 17:39:30.160]
00:05:29 [2022-05-07 17:39:30.160]
00:05:29 [2022-05-07 17:39:30.160] us-eth.2miners.com (ethash)    PING: 36ms    DIFFICULTY: 2.03     EPOCH: 491
00:05:29 [2022-05-07 17:39:30.160]                                                                                 
00:05:29 [2022-05-07 17:39:30.160]
00:05:29 [2022-05-07 17:39:30.160] ID      BOARD    TYPE    KERN    XINT    TEMP    FAN     CORE    MEM     WATT   
00:05:29 [2022-05-07 17:39:30.160] GPU0    gfx1030  OpenCL  0       693     27/0    89      1500    1069    114   
00:05:29 [2022-05-07 17:39:30.160] GPU1    gfx1030  OpenCL  0       693     25/0    89      1500    1069    104   
00:05:29 [2022-05-07 17:39:30.160] GPU2    gfx1030  OpenCL  0       949     26/0    89      1500    1059    120   
00:05:29 [2022-05-07 17:39:30.160] GPU3    gfx1030  OpenCL  0       660     24/0    89      1650    1069    124   
00:05:29 [2022-05-07 17:39:30.160] GPU4    gfx1030  OpenCL  0       963     25/0    89      1500    1069    109   
00:05:29 [2022-05-07 17:39:30.160] GPU5    3090     CUDA    2       6800    42/0    95      1500    11275   333   
00:05:29 [2022-05-07 17:39:30.160]                                                                          904   
00:05:29 [2022-05-07 17:39:30.160]
00:05:29 [2022-05-07 17:39:30.160] ID      BOARD    HASHRATE/W    HASHRATE      AVERAGE       SHARES       RATE   
00:05:29 [2022-05-07 17:39:30.160] GPU0    gfx1030  1947.58 kH/W  66.22 MH/s    66.14 MH/s    133/0/0      100.00%
00:05:29 [2022-05-07 17:39:30.160] GPU1    gfx1030  2367.56 kH/W  66.29 MH/s    66.29 MH/s    128/0/0      100.00%
00:05:29 [2022-05-07 17:39:30.160] GPU2    gfx1030  0.00 H/W      0.00 H/s      0.00 H/s      144/0/1      100.00%
00:05:29 [2022-05-07 17:39:30.160] GPU3    gfx1030  1830.53 kH/W  65.90 MH/s    65.90 MH/s    135/0/0      100.00%
00:05:29 [2022-05-07 17:39:30.160] GPU4    gfx1030  0.00 H/W      0.00 H/s      0.00 H/s      137/0/0      100.00%
00:05:29 [2022-05-07 17:39:30.160] GPU5    3090     399.57 kH/W   133.06 MH/s   133.05 MH/s   297/0/0      100.00%
00:05:29 [2022-05-07 17:39:30.160]                  1090.87 kH/W  331.46 MH/s   331.37 MH/s   974/0/1      100.00%
00:05:29 [2022-05-07 17:39:30.160]                                                                                 
00:05:29 [2022-05-07 17:39:30.160] SHARES PER MINUTE: 2.96            POOL HASHRATE: 430.56 MH/s
00:05:29 [2022-05-07 17:39:30.160]
00:05:29 [2022-05-07 17:39:33.624] Job d52cb
00:05:29 [2022-05-07 17:39:40.329] GPU5 Solution found in 0.19s (Submit every 21.29 seconds)
00:05:29 [2022-05-07 17:39:40.329] Job d52cc
00:05:29 [2022-05-07 17:39:40.361] Accepted (975/975/1) Reply: 32ms
00:05:29 [2022-05-07 17:39:47.034] Job d52ce
00:05:29 [2022-05-07 17:39:49.273] Job d52d1
00:05:29 [2022-05-07 17:39:51.508] Job d52d2
00:05:29 [2022-05-07 17:39:58.213] Job d52d4
00:05:29 [2022-05-07 17:40:04.919] Job d52d6
00:05:29 [2022-05-07 17:40:11.624] Job d52d9
00:05:30 [2022-05-07 17:40:13.859] Job d52dc
00:05:30 [2022-05-07 17:40:18.329] GPU5 Solution found in 4.60s (Submit every 21.31 seconds)
00:05:30 [2022-05-07 17:40:18.369] Accepted (976/976/1) Reply: 40ms
00:05:30 [2022-05-07 17:40:20.564] Job d52de
00:05:30 [2022-05-07 17:40:29.504] Job d52df
00:05:30 [2022-05-07 17:40:30.163] GPU0: has timed out, trying to restart..
00:05:30 [2022-05-07 17:40:30.163] GPU1: has timed out, trying to restart..
00:05:30 [2022-05-07 17:40:30.163] GPU3: has timed out, trying to restart..
00:05:30 [2022-05-07 17:40:30.163]



Then eventually the miner just stopped


00:05:32 [2022-05-07 17:42:30.171] us-eth.2miners.com (ethash)    PING: 36ms    DIFFICULTY: 2.03     EPOCH: 491
00:05:32 [2022-05-07 17:42:30.171]                                                                                 
00:05:32 [2022-05-07 17:42:30.171]
00:05:32 [2022-05-07 17:42:30.171] ID      BOARD    TYPE    KERN    XINT    TEMP    FAN     CORE    MEM     WATT   
00:05:32 [2022-05-07 17:42:30.171] GPU0    gfx1030  OpenCL  0       693     26/0    89      1500    1069    111   
00:05:32 [2022-05-07 17:42:30.171] GPU1    gfx1030  OpenCL  0       693     26/0    89      1500    1069    102   
00:05:32 [2022-05-07 17:42:30.171] GPU2    gfx1030  OpenCL  0       949     26/0    89      1500    1059    117   
00:05:32 [2022-05-07 17:42:30.171] GPU3    gfx1030  OpenCL  0       660     24/0    89      1650    1069    121   
00:05:32 [2022-05-07 17:42:30.171] GPU4    gfx1030  OpenCL  0       963     25/0    89      1500    1069    106   
00:05:32 [2022-05-07 17:42:30.171] GPU5    3090     CUDA    2       6800    43/0    95      1500    11275   333   
00:05:32 [2022-05-07 17:42:30.171]                                                                          890   
00:05:32 [2022-05-07 17:42:30.171]
00:05:32 [2022-05-07 17:42:30.171] ID      BOARD    HASHRATE/W    HASHRATE      AVERAGE       SHARES       RATE   
00:05:32 [2022-05-07 17:42:30.171] GPU0    gfx1030  0.00 H/W      0.00 H/s      0.00 H/s      133/0/0      100.00%
00:05:32 [2022-05-07 17:42:30.171] GPU1    gfx1030  0.00 H/W      0.00 H/s      0.00 H/s      128/0/0      100.00%
00:05:32 [2022-05-07 17:42:30.171] GPU2    gfx1030  0.00 H/W      0.00 H/s      0.00 H/s      144/0/1      100.00%
00:05:32 [2022-05-07 17:42:30.171] GPU3    gfx1030  0.00 H/W      0.00 H/s      0.00 H/s      135/0/0      100.00%
00:05:32 [2022-05-07 17:42:30.171] GPU4    gfx1030  0.00 H/W      0.00 H/s      0.00 H/s      137/0/0      100.00%
00:05:32 [2022-05-07 17:42:30.171] GPU5    3090     399.58 kH/W   133.06 MH/s   133.05 MH/s   299/0/0      100.00%
00:05:32 [2022-05-07 17:42:30.171]                  66.60 kH/W    133.06 MH/s   133.05 MH/s   976/0/1      100.00%
00:05:32 [2022-05-07 17:42:30.171]                                                                                 
00:05:32 [2022-05-07 17:42:30.171] SHARES PER MINUTE: 2.94            POOL HASHRATE: 427.55 MH/s
00:05:32 [2022-05-07 17:42:30.171]
root@red-ether:/var/log/miner/teamblackminer# cat teamblackminer.2.log |grep -i -B 15 -A 250 '1873.58' > ~/StillTimimgOut_163.txt

I've been running 1.63 with different cards running different intensities and the rig has been stable, no GPU timeouts.  

Overall average hashrate on the AMD cards is 62 MH/s, reported average is 65 Mh/s, so in general the reported and actuals are close -- how the peaks and valleys align with the 2miners reporting window has a more significant effect on the hashrate than anything -- I wish they had a more controllable window, but the ETH earned per day is aligning with the values coming out of various hashrate profit calculators based on the miner reported values.
 
I do notice that once in a while, one of the cards will drop its hashrate for a minute from 65-66 MH/s to 40-something and go back to its previous rate a minute later, but that's not really an issue, just some funny behaviour.  

I'm super impressed with how the 3090Ti is working with the miner software.  I am running 9992 intensity with zero stale or invalid hashes -- I set it to autotune and notice that it seems to switch between kernel 2 and kernel 13, any idea why it's only those two kernels that are putting up 100's vs. 99's for the others (aside from kernel 0 which is like 70)?  Performance is 136-137 MH/s from the miner and 135-136 at the pool.  Temperatures on the 3090Ti are great!!  probably the coolest card in all my rigs running no hotter than 52/68 Degrees (Core/Memory) @ 337 watts.
 

Our AMD test rigs is running without any issues on v1.63. Please test the latest version.

Can you try v1.63 please? If you still get problems, try the SSL port. We have rewritten the code here. SSL Should work on all the supported pools.

There will be a new release soon with some fixes. SSL mining, and lower memory requirements bugfixes. The team is preparing for the end of Ethereum mining, and moving our support to the more profitable and secure blockchains.
--
Team Black Miner v1.63

v1.63
1. Added support for SSL mining / anonymous mining.
2. Reduced the GPU memory requirements in copy dag mode (To extend the life of low memory cards.)
3. New fix for gpu timeout on AMD cards with high intensity.
4. Some short options changed names.

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

TeamBlackMiner_1_63_Ubuntu_18_04_Cuda_11_5.tar.xz
https://www.virustotal.com/gui/file/0add4e5b52b83faf3e4155127b9e84b2da5092ec65a065d01b24ff7c35e23a5e?nocache=1

TeamBlackMiner_1_63_Ubuntu_18_04_Cuda_11_4.tar.xz
https://www.virustotal.com/gui/file/9535eedaa1e5b4ce2c7da30d09dbb1e5b1e2385ae45985437c67524f20ccea79?nocache=1

TeamBlackMiner_1_63_cuda_11_5.7z
https://www.virustotal.com/gui/file/522828be6dc4990bea1c87dfe214b3e3e78a6b3c73edec5c5ea71c2877eb4644?nocache=1

TeamBlackMiner_1_63_cuda_11_4.7z
https://www.virustotal.com/gui/file/03817cc3ce120b29e604f4ab8c6142fa31d4fff45492a5b9bb6945c3755a60f7?nocache=1

TeamBlackMiner_1_63_cuda_11_3.7z
https://www.virustotal.com/gui/file/3b8dc8c352676375101d38b63b357377aebc7eb22fa92ceb5e46101c642e9441?nocache=1

In 8-card-rig of GTX 1080Ti the first card drops down hash from 43 to 10 and even 3 Mh periodically.

After a lot of head-scratching and tuning with many crashes and poor hash rates, I finally have found a combination of clocks and intensity that allows the 3090Ti to perform well.

In the following screenshots -- WhiteFang is the 3090Ti and it has been running for about 10 hours now without any crashes.

We need to shorten the time between when a card 'times out' and when the miner restarts.  I've never seen a card recover from a timeout and often times 3-4 will all timeout at the same time which drops my average hashrate significantly, which also affects my poolside share of a given round.

I mean ideally the AMD cards wouldn't just randomly time out, but if they do, I'd rather just have the process restart than wait for the inevitable crash while hashing at a low rate.