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

We finally added support for mining Vertcoin into the Team Black Miner.. The Verhash dag is created with the cpu which is slow, but this process is only needed once.

v1.64
1. Added support for Vertcoin mining (the Verthash algo) . AMD/NVIDIA
2. Fix issues in Zil mining

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

TeamBlackMiner_1_64_cuda_11_5.7z
https://www.virustotal.com/gui/file/7a4f3a6e99f1cac4d4a153d6dac65ec2386aec94b5f1f94daf06b6987ee72630?nocache=1

TeamBlackMiner_1_64_cuda_11_4.7z
https://www.virustotal.com/gui/file/fd16c01eaa1ce33036c8461a226ea54d5c919258e6ab201b3b1d990ae59a4202?nocache=1

TeamBlackMiner_1_64_Ubuntu_18_04_Cuda_11_5.tar.xz
https://www.virustotal.com/gui/file/063fd61e5e38268e7625cbd93964969258feb08c268b2047d34376994f11ba45?nocache=1

TeamBlackMiner_1_64_Ubuntu_18_04_Cuda_11_4.tar.xz
https://www.virustotal.com/gui/file/e63dbea2cef14a27365ed89cd49643c63b1356cbe28e7f0de2fb27792d15ba81?nocache=1

Will there be updates?

I'm wondering if it has something to do with the pool.  I switched from 2Miners to MiningPoolHub and decided to use 1.63 and get some samples of the miner stopping reporting, but it has been running 2 days and is still reporting stats properly.
Also, I decided to try putting the 2060S back into the TBM list (since it was conflicting with the 3090 and generating a lot of rejected shares when they were all running together), and I haven't had any rejected shares for 20 hours.   

Is there some significant difference between MPH and 2Miners that would cause such different behaviour?

Exactly like that.  Just Jobs and Submitted shares being reported.

Similar behaviour as running with
--no-stats
?

Unless you have a dire need for 1.63 just use 1.62 

The terminal stops reporting the card details, so there's just a long list of accepted jobs and submitted jobs but no 60 second block display of power usage or hash rate.  It ~seems~ random, but there may be some other issue that isn't being logged, like the momentary GPU glitch in the Nvidia driver which stops it from reporting the Memory Temp and fan speed.  Whatever it is, it works fine in 1.62, just not in 1.63.

This jumping hashrate and power is when the DevFee for the Pill kicks in 

Running from a terminal does TBM still report the stats as that might indicate HiveOS has issues reporting?

It's been pretty dead around here for a while, but I just wanted to raise a slight issue that seems to happen randomly.

On the latest version in HiveOS, the miner will stop reporting GPU stats after a while.  It's still mining and providing solutions to the pool, but I have no idea what the cards are doing in terms of power usage and thermals (which is becoming more of an issue as summer temperatures start making it harder to keep the cards at a reasonable temperature.

for sometimes i managed to run it on hiveos and working well. i noticed at some point find out some jumping hashrate 54-61mhz and power 125-137w. Pill need a bit more improvement on LHR 100% unlock stability.

https://ibb.co/Vgphyt0

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

Ok, nice with no screenshot for a prove, or a timespan. How long did you mine with every miner and compared it?

this has been fixed in the latest release




Ethermine doesn't pay for stale shares. On the default intensities there are around 2% stales, this is higher than in the other mining software, but that doesn't matter on the 2miners pool.
If you increase the intensity you can get as much as +5% poolside hashrate. The +5% accepted hashrate will probably give you more coins in the pocket..

I used to mine on 2miners but profit declined so I moved to Ethermine. Default settings are ok for stales, I'll monitor the average hashrate that seems just a little lower compared to Gminet/T-Rex but shares are absolutly very close, so probably TBM is not inflating a bit

Yes too high for ethermine, but works good on 2miners.com, nanopool.org , miningpoolhub.com and around 50% of the largest pools for ethereum.

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

I tried 4000 but seems too high for Ethermine, too many stale shares. I also tried 3100 that seem too high too, is there a ratio/multiplier to consider for fine tuning? Minimum for Nvidia is actually 224.

I did not get why starts very strong and then goes lower and lower, probably temperatures

You probably want to put the intensity to about 4000 on the A2000 (which has the 192bit memory bus) and 2800 on the A4000 (which has the 256bit memory bus).

SSL is working fine and stability improved a lot, I'm actually testing NVIDIA RTX A2000 and RTX A4000, results are quite good but I can't find a sweet spot for xintensity level. Can you suggest a recommended value?

It seems that no matter if I use ./start.sh "0" or "1", it will always show "All devices selected." and even when I have my 3090Ti idle (not mining) and set as the output device to the monitor, it will eventually corrupt the monitor and crash the server.

Edit:
If I run both cards together it will still say that all the cards are being selected, but there is no apparent impact on the 3090Ti, it will run at its normal 135-137 MH/s as a miner reported speed, but if I leave the 3090Ti idle, it will corrupt (maybe due to the P-state not switching to P0, or some fan monitoring that is performed by HiveOS when a card is engaged in mining vs. idle?) and the computer will reboot; I will have to try and confirm the actual poolside speed on the card to see if it is reflecting the 135+ from the miner.

As for the speed:  the miner is reporting about 85.6 average, but the 'realtime' fluctuates a lot, as compared to the latest t-rex, which gives 83 MH/s from the miner and is very stable with that value after about the first 5 minutes, I think the pill is cycling too often (maybe there are conditions which make it cycle more often or less?) and when it does a cycle, the hashrate drops and reduces the overall reported rate for the next 60-90 seconds, which will reduce the average to 82 or 83 and possibly the overall poolside hashrate (although 2MH/s isn't really significant on a shares found metric as it's less than .25 SD, which means luck has a far greater impact on overall average share rate than 2 MH/s).

My next test will be to run the 3090Ti in another instance outside of Hive, or with another miner (since HiveOS won't allow the same miner to be running twice within its management software) and see if the Pill hurts the 3090Ti in that case, and also to get single card speed and variability metrics for the 3070Ti LHR card.