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

[sp_]

Did you try --xintensity 24?

You should upgrade to 1.25 so we can see the clocks and power settings.

[nosidefcp]

so i have all my cards apart from 2 rx 580 working on TBM.

apart from the rx 5700, i have awesome results on 6700, 6800, 3080 and 2080 ti.

any xintensity and kernel value to use on the 5700 xt? the 580 i didnt try yet, but i cant get past 55/56 on TBM, when the card is making steady 57.5 on TRM

[sp_]

--xintensity 60 is good on the rx 580. ppl got it working in hiveos after upgrading to the latest image.

And the winner is --xintensity 284

I did a 3hour * 4 test last night on 2miners.com on the same card. rtx 2060 mobile

--xintensity 1024 32.54 mhash (pool less than 30)
--xintensity 2048 32.56 mhash (pool 34++)
--xintensity 3078 32.58 mhash (pool less than 30)
--xintensity 4096 32.60 mhash (pool 38++)

3 hours on each intensity is not a long enough test, but 4096 was still the winner on this pool for NVIDIA... If you compare the local speed to the default (--xintensity 284) you get a +1% speedup. The test had no stales or rejected shares poolside.

[ep690d01]

--xintensity 60 is good on the rx 580. ppl got it working in hiveos after upgrading to the latest image.

And the winner is --xintensity 284

I did a 3hour * 4 test last night on 2miners.com on the same card. rtx 2060 mobile

--xintensity 1024 32.54 mhash (pool less than 30)
--xintensity 2048 32.56 mhash (pool 34++)
--xintensity 3078 32.58 mhash (pool less than 30)
--xintensity 4096 32.60 mhash (pool 38++)

3 hours on each intensity is not a long enough test, but 4096 was still the winner on this pool for NVIDIA... If you compare the local speed to the default (--xintensity 284) you get a +1% speedup. The test had no stales or rejected shares poolside.

It does not take 3 hours to get reliable information about pool hashrate, at least 24 hours

[sp_]

It does not take 3 hours to get reliable information about pool hashrate, at least 24 hours

yes. If anyone wants to test they can do it now easy with the new --miningtime parameter. 576 minutes in 24 hours

So set up the launch config with different --xintensities and use --miningtime 576 for a 24hour test (24*60)

make sure to add --log as well. then you can check in the logfile for the results.

[ep690d01]

It does not take 3 hours to get reliable information about pool hashrate, at least 24 hours

yes. If anyone wants to test they can do it now easy with the new --miningtime parameter. 576 minutes in 24 hours

So set up the launch config with different --xintensities and use --miningtime 576 for a 24hour test (24*60)

make sure to add --log as well. then you can check in the logfile for the results.

https://i.ibb.co/Fkr0516/tune-script.png

Thanks for this very good option.

[wasarianta]

not close... but it's beyond the EST. REWARD by minerstat and whattomine 

using this 46.21 hashrate
https://ibb.co/gdVLdBZ

whattomine
https://ibb.co/Z6d3kD2

minerstat
https://ibb.co/NFv3m0Q

payouts
https://ibb.co/f0Fc5D6

[sp_]

not close... but it's beyond the EST. REWARD by minerstat and whattomine  

Yeah. This software is pretty good, but only if you configure it correctly...

[plavirudar]

The front page post mentions that it supports socks5 proxy, but I could not find such an option on the readme flags list on github, or in the --help option list when starting the miner.

Interestingly enough, the --proxy option does allow the miner to start normally (other options cause the miner to exit with invalid option error), but the socks proxy connection is not used when that option is applied. If using a program like proxifier to redirect the connection into a socks proxy, the miner refuses to connect. This is unlike other miners that do not natively support proxies like teamredminer. I assume this is due to some anti devfee cheating mechanism.

It would be nice if the proxy can be enabled, or if not, at least remove it from the main post.

[sp_]

This is unlike other miners that do not natively support proxies like teamredminer. main post.

The other miners seem to use the same codebase because they behave the same. More hits on the antivirus software as well.. The Team Black miner is written from scratch by opensource developers... Proxy is supported in zil+etc and zil+eth miningmode. Mine at rustpool or shardpool.

[plavirudar]

Proxy is supported in zil+etc and zil+eth miningmode. Mine at rustpool or shardpool.

I see, thanks for the reply. Would be good if you could clarify the OP that the socks5 proxy is not for the pool connection but only for dual mining.


Another question, the AMD device information (clocks, mem, temps etc) seems to be absent on a mixed nv/amd rig, even though I am using 1.25.

I am running AMD driver 21.8.2 (showing as driver 539303.288 on startup) and it detects the 6800 as "GPU0 gfx1030 17GB added to miner as OpenCL device"

Should I be using a different config for this?

[Kolmodor]

Good Rtx 2060
https://ibb.co/xC8LDXt

[sp_]

Good Rtx 2060

yes. v1.25 is really fast. Spread the word..

[Ramsete2]

Still no stats on AMD cards... (ver 1.25)
Sorry but do somebody test releases before submitting them?

eu.crazypool.org (ethash)    PING: 26ms    DIFFICULTY: 2.00     EPOCH: 454                                                                                   
                                                                               
ID      BOARD    TYPE    KERN    XINT    TEMP    FAN     CORE    MEM     WATT 
GPU0    gfx1030  OpenCL  0       24      0/0     0       0       0       0     
GPU1    gfx1030  OpenCL  0       24      0/0     0       0       0       0     
GPU2    gfx1030  OpenCL  0       24      0/0     0       0       0       0     
GPU3    gfx1030  OpenCL  0       24      0/0     0       0       0       0     
GPU4    gfx1030  OpenCL  0       24      0/0     0       0       0       0     
GPU5    gfx1030  OpenCL  0       24      0/0     0       0       0       0     
GPU6    gfx1030  OpenCL  0       24      0/0     0       0       0       0     
                                                                         0     
                                                                               
ID      BOARD    HASHRATE/W    HASHRATE      AVERAGE       SHARES       RATE   
GPU0    gfx1030  0.00 H/W      64.91 MH/s    63.93 MH/s    5/0/0        100.00%
GPU1    gfx1030  0.00 H/W      45.57 MH/s    42.87 MH/s    1/0/0        100.00%
GPU2    gfx1030  0.00 H/W      65.12 MH/s    63.97 MH/s    2/0/0        100.00%
GPU3    gfx1030  0.00 H/W      65.14 MH/s    64.59 MH/s    0/0/0        100.00%
GPU4    gfx1030  0.00 H/W      65.13 MH/s    64.52 MH/s    1/0/0        100.00%
GPU5    gfx1030  0.00 H/W      65.14 MH/s    64.02 MH/s    1/0/0        100.00%
GPU6    gfx1030  0.00 H/W      64.85 MH/s    63.90 MH/s    0/0/0        100.00%
                 0.00 H/W      435.86 MH/s   427.81 MH/s   10/0/0       100.00%
                                                                               
SHARES PER MINUTE: 3.33                                POOL HASHRATE: 477.21 MH/s

[sp_]

Still no stats on AMD cards... (ver 1.25)

yes. Tested on the latest hiveos. We are using a library called rocm-smi. This is buildt into hiveos, but on other linux platforms might need to install it separately.

[Ramsete2]

Still no stats on AMD cards... (ver 1.25)

yes. Tested on the latest hiveos. We are using a library called rocm-smi. This is buildt into hiveos, but on other linux platforms might need to install it separately.

Using mmpOS, which command should I use?

[sp_]

Not sure. Why don't you ask in the MMPos thread. Did you use the latest version of mmpos? rocm-smi is normally included with the driver.

[KillrBee]

It's amazing!

My 6x00 series cards are all clocking over 66 MH/s at the pool on version 1.25 with HiveOS which is in real world terms an improvement of 3-4 MH/s per card over teamRedMiner.  I haven't even experimented that much with the intensity values since these cards are incredibly sensitive to slight differences in voltages, core and memory clocks; they will either just start hashing at a low value or go offline without any details in the logs.  I've found that --xintensity of 1042 and --kernel 5 have been able to produce a fairly stable hash rate without the cards yeeting themselves.

I've been experimenting with my 3090 and have been able to achieve a rock-solid at the pool hashrate of 134 with the following settings @ 2miners.com:  --xintensity 15000, core 1560, memory +1450 (11202), 85%.  This is equalling an average of 1 share per minute, which equates to about 135 MH/s at the pool right now.

Overall, my combined rig hashrate has moved from about 468 MH/s average to 502 MH/s; which is amazing and shows all the hard work that has gone into this software has really paid off for the mining community (and I hope for the Devs too!). I've seen and been involved with the progress that has been made since version 1.01 and we should all give a big shout out to binaryf and sp__ for keeping up an incredible release tempo and continuous improvement!  I can't wait to see what's next!   

[sp_]

A working semi LHR unlock has now been implemented. rtx 3060 32MHASH@50watt. Abit slower than the other teams but use very little power.

This new feature needs more tuning and testing, but v1.26 will be released soon.

[sp_]

Overall, my combined rig hashrate has moved from about 468 MH/s average to 502 MH/s; which is amazing and shows all the hard work that has gone into this software has really paid off for the mining community (and I hope for the Devs too!).

Thanks for your support and testing. The fee is picking up, but we have a long way to go. Hopefully the new semi LHR unlock feature will move more ppl over to the fastest miner.