Pages:
Author

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

copper member
Activity: 416
Merit: 105
Flexpool is already working fine in tbminer, but they decided to block Russian ip addresses for mining. Perhaps you are effected.

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


i use 3080 12gb gpu but it seem very slow to start miner 0 hasrate running 10 minute and more than that, already restart the rig but same behavior
edit : ok i found the problem, need to use non ssl port and it run smooth... Thanks
sp_
legendary
Activity: 2898
Merit: 1087
Team Black developer
Gminer is sponsored by The Russian Industrial Military Complex. By using it you are supporting Putin and his war.
V. Buterin  and Ethereum wil go POS in 3months, and this is when we end our support for ethereum.
member
Activity: 1558
Merit: 69
Russia has invaded Ukraine, and you can do a difference.
Stop mining with Russian mining Software (Gminer, Team Red Miner).

Switch to the more profitable and free

Team Black Miner




V. Buterin is a russian and he is talking with Putin in the past, so you will cancel the ETH support also? This is the wrong way and that makes you very unlikable. What have this developer to do with the government or this war? right nothing!
People die and you use it do promote your miner? This is inhuman!!!!
And where is your software free? No fee? I can´t see it.

Are you drunk? Or how the hell can you think this is good post?
sp_
legendary
Activity: 2898
Merit: 1087
Team Black developer
Flexpool is already working fine in tbminer, but they decided to block Russian ip addresses for mining. Perhaps you are effected.

----------------------------------------------
v1.57

1. Fix rejects on binance.com and gpumine.org

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

TeamBlackMiner_1_57_cuda_11_4.7z
https://www.virustotal.com/gui/file/36df5b926a2fb2550763be4574bd1e57f4fd3d528b76a35c95c2a617378b1988?nocache=1

TeamBlackMiner_1_57_cuda_11_5.7z
https://www.virustotal.com/gui/file/00dfa361c9bea413a5d1437afc8ca65c5429879dd6c8f4c4e8fdca2893d704ef?nocache=1

TeamBlackMiner_1_57_Ubuntu_18_04_Cuda_11_4.tar.xz
https://www.virustotal.com/gui/file/0899d5dfbc09b6dbcd6bd20a6cb7b48276fbf440d01deb94ff86aa43c001bf82?nocache=1

TeamBlackMiner_1_57_Ubuntu_18_04_Cuda_11_5.tar.xz
https://www.virustotal.com/gui/file/8db7650986110799a67d1c2ed78c760b00bf99d94a8120050f493d8bdfc931dd?nocache=1
copper member
Activity: 416
Merit: 105
Please add support for flexpool....

Thank you
sp_
legendary
Activity: 2898
Merit: 1087
Team Black developer
to select the desire gpu

amd:
--cl-devices [0,1,2,3,4]
nvidia
--cuda-devices [0,1,2,3,4]

Or all amd devices;
--amd-only

Or all nvidia devices;
--nvidia-only

use TBMiner --list-devices to see the device order.
jr. member
Activity: 90
Merit: 1
newbie
Activity: 51
Merit: 0
i cannot get this fukcing miner to select the desire gpu to work
sp_
legendary
Activity: 2898
Merit: 1087
Team Black developer
This LHR business is weird... I created a startup - no login script to run the miner on my windows machine (so none of the other user-level garbage is loaded on login), and I set the --LHR-unlock to "0" with a --tweak of "5", to test the baseline full LHR speed (what Nvidia intended for the card to do when mining ethereum), and over the past 16 hours the miner share rate has averaged 54 MH/s and 2Miners poolside for the past 6 hours is 61 MH/s ...  
Which is better than the 47 MH/s I wound up getting when logged in and running an LHR-unlock of -25 / tweak 2 (which was required to allow the miner to mine for > 300 seconds without a reset)...

Based on the non-LHR architecture with GDDR6x RAM, I would expect that the full non-LHR hashrate of this card under a standard miner without insane OC's would be between 67-69 MH/s and getting and average of 54 MH/s without unlocking means it's running between 77 - 80% of its maximum potential at baseline... Is this normal? Am I missing something about how the --LHR-unlock 0 functions? Are my current OC values pushing the card beyond the 'normal' LHR and the standard TBMiner advantage is just compensating for the cards natural speed lock?

No 61MHASH is not the normal LHR rate for this card (3070ti). it will go below 38MHASH in Phoenix miner after a few seconds of mining. I get similar results in windows when I disable fast startup and reboot the rig, the card fail to enter the LHR mode and is hashing at almost full capacity for days with the TBM miner. Reproduced on the 511.23 driver.  The --lhr-unlock option will enable a "reduced hashrate mode" to avoid LHR and  try to autotune if the lhr unlock is triggered.
jr. member
Activity: 139
Merit: 3
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:

In my tests, the autotune can reset a few times and still give a good result. With your current settings, 48MHASH should be the expected speed. Abit low but stable. Adding more LHR cards to the rig or normal cards can add stability and speed to the unlock.

A freshly rebooted rig with the miner running in a startup script seems to be performing best. use --log.
The debug output from the LHR code can be removed with a setting --no-verbose , work is still in progress.


This LHR business is weird... I created a startup - no login script to run the miner on my windows machine (so none of the other user-level garbage is loaded on login), and I set the --LHR-unlock to "0" with a --tweak of "5", to test the baseline full LHR speed (what Nvidia intended for the card to do when mining ethereum), and over the past 16 hours the miner share rate has averaged 54 MH/s and 2Miners poolside for the past 6 hours is 61 MH/s ...  
Which is better than the 47 MH/s I wound up getting when logged in and running an LHR-unlock of -25 / tweak 2 (which was required to allow the miner to mine for > 300 seconds without a reset)...

Based on the non-LHR architecture with GDDR6x RAM, I would expect that the full non-LHR hashrate of this card under a standard miner without insane OC's would be between 67-69 MH/s and getting and average of 54 MH/s without unlocking means it's running between 77 - 80% of its maximum potential at baseline... Is this normal? Am I missing something about how the --LHR-unlock 0 functions? Are my current OC values pushing the card beyond the 'normal' LHR and the standard TBMiner advantage is just compensating for the cards natural speed lock?
sp_
legendary
Activity: 2898
Merit: 1087
Team Black developer
So if im right for example

Wallet A (Main wallet)
Pool A (HiveOn)
Wallet B (maintenance wallet) Lets say 10% of 1gh
Pool B (uses HiveOn aswell?)
So when i try to search Wallet B on HiveOn, there should be 100mh/s hasrate.

Yes, it might take an hour or more, but in the long term around 100 on the other adress on hiveon. 10% of the time will be used to mine on this adress, but the average hashrate depends  on the luck in these 10%. But over a long term 10%
jr. member
Activity: 60
Merit: 2
How does the maintenance wallet function work. Is the wallet mining with the pool of the original wallet? Or can a 2nd pool be selected. Because i dont see any hashrate on the original wallet pool.

You can split the mining reward between two adresses. Remember to specify the percentage as well

--maintenance-wallet --maintenance-percent 5

5% of the mining revenue is mined to
94.5% to  the normal wallet.
0.5% fee

So if im right for example

Wallet A (Main wallet)
Pool A (HiveOn)
Wallet B (maintenance wallet) Lets say 10% of 1gh
Pool B (uses HiveOn aswell?)

So when i try to search Wallet B on HiveOn, there should be 100mh/s hasrate.

sp_
legendary
Activity: 2898
Merit: 1087
Team Black developer
How does the maintenance wallet function work. Is the wallet mining with the pool of the original wallet? Or can a 2nd pool be selected. Because i dont see any hashrate on the original wallet pool.

You can split the mining reward between two adresses on the same pool. Remember to specify the percentage as well.

--maintenance-wallet --maintenance-percent 5

5% of the mining revenue is mined to
94.5% to  the normal wallet.
0.5% fee
jr. member
Activity: 60
Merit: 2
How does the maintenance wallet function work. Is the wallet mining with the pool of the original wallet? Or can a 2nd pool be selected. Because i dont see any hashrate on the original wallet pool.
newbie
Activity: 40
Merit: 0
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.

you can find this info in Payouts FAQ https://eth.crazypool.org/#/about
https://i.ibb.co/3yp9HB4/capture1.jpg
sp_
legendary
Activity: 2898
Merit: 1087
Team Black developer
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:

In my tests, the autotune can reset a few times and still give a good result. With your current settings, 48MHASH should be the expected speed. Abit low but stable. Adding more LHR cards to the rig or normal cards can add stability and speed to the unlock.

A freshly rebooted rig with the miner running in a startup script seems to be performing best. use --log.
The debug output from the LHR code can be removed with a setting --no-verbose , work is still in progress.
jr. member
Activity: 139
Merit: 3
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
sp_
legendary
Activity: 2898
Merit: 1087
Team Black developer
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.
member
Activity: 294
Merit: 16
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.
jr. member
Activity: 139
Merit: 3
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
Pages:
Jump to: