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

Because on Crazypool I'm getting about 10% more in profits, compared to the pools you mentioned.

Why don't you mine on 2miners.com, miningpoolhub.com, nanopool.org or other recommended pools. Mine on high intensity and get a poolside profit of +5% or more.

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

After several tests, comparing TBMiner with GMiner/T-rex/lolminer I found out that the total shares number submitted to the pool was more or less the same, despite the hashrates difference.

RED TBM Share !

Green Gminer Share


https://0bin.net/paste/VlP1g9SC#PSL3QHWAXHtIwAO+hqgkR7ib9av3k5sXrVCxlcPBBAY


-----------

the question is how one can have with such a low OC memory still 61MHS?

I had fun putting at 61 Mhs as for Gminer in order to have 2.133Ghs and the surprise
consumption only drops by 50W on all rigs? and the heated cards in the same way as at 2400Mhz !!

in reality that I drop from 2400Mhz to 1900Mhz the consumption is identical but as my cards run at 61Mhs I am at 650 / 720shares instead of 800/900

So I tested all the possible settings, I conclude either you are lying on hashrate in order to deceive the newbie because it judges only by the power instead of looking at the number of shares / hour.

I read all the pages, you play with stales and recommended pools that don't pay!

you say that 2% of stale is not serious because the pool pays! except that 2% solo is too much! then say to go on 2min because it is more profitable it is completely wrong ... especially with the stories of M.E.V and E.D.E.N network

You have just taken the sources of Ethemine with the ideas of lolminer (besides he released 192 in workload, you also recommended after 192 ??) .. Gminer and so on.

the miner is too complicated to set, we have no course of action you even do not know which setting to put

I'm sorry but when I take Gminer, lolminer or trex whether on 2miner or crazypool I don't need to spend 2 days finding the right setting for $ 0.20 more but which will actually end up in the business because your miner takes 100w more

So for me it will not be recommended at all to my community.

simplified the miner and really displayed what we mine and rule

Looking better, great hashrate, but still tiny bit too unstable. With "normal" usage of this desktop.

- for these 3 GPU I received the message of start generating dag, but no other message (dag generated, verified, kernel selected and xintensity set)

- there's a recurring error/warning "Cannot open shared object file"

Additional step for AMD devices
TBM uses AMD ADL library to read GPU information from AMD cards.

We have added two AMD libraries to make this step a little easier.

This step is not neccesary if you already have the libraries.

The miner can work without them but then without statistics for AMD GPU cards.

Copy the shared objects (.so) to the systems library path:

sudo cp libatiadlxx.so /usr/lib/
sudo cp libatiuki.so.1 /usr/lib/

Try --kernel 0

--xintensity 60 works good on the 580

00:00:35 [2021-10-31 08:52:08.028] Cannot open shared object file
00:00:35 [2021-10-31 08:52:08.028]
00:00:35 [2021-10-31 08:52:08.028]
00:00:35 [2021-10-31 08:52:08.028] asia-eth.2miners.com (ethash)    PING: 50ms    DIFFICULTY: 2.03     EPOCH: 450
00:00:35 [2021-10-31 08:52:08.028]                                                                                 
00:00:35 [2021-10-31 08:52:08.028]
00:00:35 [2021-10-31 08:52:08.028] ID     BOARD   TYPE    KERN    XINT    TEMP    FAN     CORE    MEM     WATT
00:00:35 [2021-10-31 08:52:08.028] GPU0  Ellesme OpenCL  0       60      0/0     0       0       0       0
00:00:35 [2021-10-31 08:52:08.028] GPU1  Ellesme OpenCL  0       60      0/0     0       0       0       0
00:00:35 [2021-10-31 08:52:08.028] GPU2  Ellesme OpenCL  0       60      0/0     0       0       0       0
00:00:35 [2021-10-31 08:52:08.028] GPU3  Ellesme OpenCL  0       60      0/0     0       0       0       0
00:00:35 [2021-10-31 08:52:08.028] GPU4  Ellesme OpenCL  0       60      0/0     0       0       0       0
00:00:35 [2021-10-31 08:52:08.028] GPU5  Ellesme OpenCL  0       60      0/0     0       0       0       0
00:00:35 [2021-10-31 08:52:08.028] GPU6  Ellesme OpenCL  0       60      0/0     0       0       0       0
00:00:35 [2021-10-31 08:52:08.028] GPU7  Ellesme OpenCL  0       60      0/0     0       0       0       0
00:00:35 [2021-10-31 08:52:08.028] GPU8  Ellesme OpenCL  0       60      0/0     0       0       0       0
00:00:35 [2021-10-31 08:52:08.028]                                                                     0
00:00:35 [2021-10-31 08:52:08.028]
00:00:35 [2021-10-31 08:52:08.028] ID     BOARD   HASHRATE/W      HASHRATE        AVERAGE         SHARES
00:00:35 [2021-10-31 08:52:08.028] GPU0  Ellesme 0.00 H/W        33.59 MH/s      33.25 MH/s      1/0/0 (100.00%)
00:00:35 [2021-10-31 08:52:08.029] GPU1  Ellesme 0.00 H/W        33.73 MH/s      32.73 MH/s      2/0/0 (100.00%)
00:00:35 [2021-10-31 08:52:08.029] GPU2  Ellesme 0.00 H/W        30.22 MH/s      29.90 MH/s      2/0/0 (100.00%)
00:00:35 [2021-10-31 08:52:08.029] GPU3  Ellesme 0.00 H/W        0.00 H/s        0.00 H/s        0/0/0 (100.00%)
00:00:35 [2021-10-31 08:52:08.029] GPU4  Ellesme 0.00 H/W        0.00 H/s        0.00 H/s        0/0/0 (100.00%)
00:00:35 [2021-10-31 08:52:08.029] GPU5  Ellesme 0.00 H/W        41.97 MH/s      32.51 MH/s      0/0/0 (100.00%)
00:00:35 [2021-10-31 08:52:08.029] GPU6  Ellesme 0.00 H/W        0.00 H/s        0.00 H/s        0/0/0 (100.00%)
00:00:35 [2021-10-31 08:52:08.029] GPU7  Ellesme 0.00 H/W        32.27 MH/s      32.33 MH/s      0/0/0 (100.00%)
00:00:35 [2021-10-31 08:52:08.029] GPU8  Ellesme 0.00 H/W        29.81 MH/s      29.54 MH/s      0/0/0 (100.00%)
00:00:35 [2021-10-31 08:52:08.029]             0.00 H/W        201.58 MH/s     190.26 MH/s     5/0/0 (100.00%)
00:00:35 [2021-10-31 08:52:08.029]                                                                                 
00:00:35 [2021-10-31 08:52:08.029] SHARES PER MINUTE: 1.00                                POOL HASHRATE: 145.44 MH/s

Aaaaaand its me again. Newest version is sadly not as "stable
1.15 was running for days, with heavy heavy usage from my side. Like; tradingview + youtube/netflix, compiling very huge C++ project, and so on.

In the batfile tbminer_unmineable_eth, it has the correct launch parameter to connect to this pool.


TBMiner --algo ethash --hostname ethash.unmineable.com --port 3333 --wallet ETH:%ETH_WALLET% --worker-name %computername%

In v1.22 there will be  a new setting for amd card to set the intensity of dag creation. With this setting you can overclock your memory even more than before, and get better hashrates.

It's a bug in v1.21 in the --cl-device selection. I have reproduced and fix it in v1.22. So you need to wait for the new version.

I have the same problem, asked SP_ 3-4 times and didn’t respond...
Choose Nvidia card ok no problem, choose only AMD card no problem, but choose couple of nvidia and all amd card impossible...

It doesn't work. I had to write --cuda-devices [2], cu is not recognized by TBM
TBM doesn't mine with my AMD cards with those settings

https://ibb.co/KrZsvTc
https://ibb.co/pbV9R4q
https://ibb.co/PG4mhTp

You pick the devices you want to mine with the command line options


to see the correct id use:

tbminer --list-devices

And btw. Stale shares; maybe its a Pool "problem"?! I was mining with my 2 Cards for 2 Weeks+ now on unminable.com, and had 1(!) Staleshare over the time. Binance Pool gave me with same Overclock about 2-3%.

Thanks a lot for the advice, sp_!  I understand that you are well versed, please tell me another moment - is it worth trying to change the overclocking of 6700 for results of 50+ or ​​49.5 is this the maximum that is possible?
can you recommend something? 

Noticed that. But same error.

The  default setting can give more stale shares than other miners, so wotls best on miningpools that accept stale shares

--worker_name has been renamed to --worker-name