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

Hello, Im new here.
Reading&scrolling through almost 60 pages to find people who conquered 1660super+hynix memory with this miner to work over 36Mgh/s.
Me myself tried to play with intensity while mining on ethermine and finished with around 700-1000 intensity with same speed 35-37Mgh including 5%-15% stales.
So I wonder if I change pool nothing will change for me if pool pays for stales.
It could be great if community creates a spreadsheet with intencity and overclock settings for GPUs.
Personaly I still believe that TBM can be great for 1660s but I tired to do experiments.

Toncoin will go POS in a month, so not worth it. We still have basic issues that need to be fixed, but getting closer and closer.

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

Team Black Miner v1.51

1. Fix LHR-unlock device on linux.
2. Fix missing AMD cards Hiveos. (multiple amd opencl platforms)

linux only release

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

TeamBlackMiner_1_51_Ubuntu_18_04_Cuda_11_5.tar.xz
https://www.virustotal.com/gui/file/5351a7ff802bcc0faadfa44a280e7e5c3c9ebd07942494c49f3492f6219692c5?nocache=1

TeamBlackMiner_1_51_Ubuntu_18_04_Cuda_11_4.tar.xz
https://www.virustotal.com/gui/file/5ffd7847e6faceefd80b44bfbeea75638333325079ee4c179ead6b26d6b1d3bc?nocache=1


The unlock function was broken on Linux, but fixed now.
v1.51

can you add dual mining toncoin + eth, same as lolminer?

Use brackets around the gpu selector -Y [3]

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



One of the cards in the rig needs to be clocked lower than the others so that the dag buffer is created without errors and loaded onto all of the other gpus without errors. My 3070 LHR can run with up to 8300 Memclock if the dag is created on the 3080ti. (T-rex is crashing at 8100)
But if your rig is only 3070 cards, let one of them run at 7800 to create the dag buffer.
Stale shares can be removed by lowering the --xintensity or switching the pool.

This image was created in p2 mode. But after set my cards in P0 mode, I could clock it even higher



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

new fixed build with working lhr-unlock for linux uploaded

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

TeamBlackMiner_1_50_Ubuntu_18_04_Cuda_11_4_fixed.tar.xz
https://www.virustotal.com/gui/file/3af45ac62fc80c2b214152424ffdfc690c7e3117689ada1bf4dc96713277c4e0?nocache=1

the lhr unlock is broken on linux, so I have to update the binaries

Hi SP,
hi guys!

I wasn't here for couple of days and I see there were couple good updates to miner.

Can somebody please share setup multiple 3070 (I have 8x3070 (original ones) and Afterburner clocks, as Im still getting lots of dag errors and stales.

Just as a followup to my comment yesterday:

The following (minus the obvious) command: ./TBMiner --algo ethash ... -Y 3 --xintensity 1000 --log, resulted in:


00:00:00 [2022-02-03 16:31:25.818]                                                                                
00:00:00 [2022-02-03 16:31:26.495] OpenCL driver version: 495.46
00:00:00 [2022-02-03 16:31:26.500] Cuda driver version: 11.5
00:00:00 [2022-02-03 16:31:26.500] Cuda runtime API version: 11.4
00:00:00 [2022-02-03 16:31:26.500]
00:00:00 [2022-02-03 16:31:26.500]                                
00:00:00 [2022-02-03 16:31:26.500]
00:00:00 [2022-02-03 16:31:26.500] Welcome to Team Black Miner 1.49
00:00:00 [2022-02-03 16:31:26.500]                                
00:00:00 [2022-02-03 16:31:26.500]
00:00:00 [2022-02-03 16:31:26.500] GPU0 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU1 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU2 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU3 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU4 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU5 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU6 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU7 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU8 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU9 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU10 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU11 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU12 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU13 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU14 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU15 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU16 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU17 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU18 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU19 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU20 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU21 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU22 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU23 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU24 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU25 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU26 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU27 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU28 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-02-03 16:31:26.500] GPU29 gfx1030 17GB added to miner as OpenCL device


Up until GPU63, then it did it again (0-63), then it created 63 work threads, connected to the pool, and attempted to generate DAGs for the 63 GPUs and crashed the system.

00:00:00 [2022-02-03 16:31:27.172] GPU43 Starting generating ethash dag (Epoch: 471)
00:00:00 [2022-02-03 16:31:27.172] GPU16 Starting generating ethash dag (Epoch: 471)
00:00:00 [2022-02-03 16:31:27.172] GPU12 Starting generating ethash dag (Epoch: 471)
00:00:00 [2022-02-03 16:31:27.172] GPU8 Starting generating ethash dag (Epoch: 471)
00:00:00 [2022-02-03 16:31:27.172] GPU15 Starting generating ethash dag (Epoch: 471)
00:00:00 [2022-02-03 16:31:27.172] GPU56 Starting generating ethash dag (Epoch: 471)
00:00:00 [2022-02-03 16:31:27.172] GPU11 Starting generating ethash dag (Epoch: 471)
00:00:00 [2022-02-03 16:31:27.172] GPU44 Starting generating ethash dag (Epoch: 471)
00:00:00 [2022-02-03 16:31:27.172] GPU62 Starting generating ethash dag (Epoch: 471)
00:00:00 [2022-02-03 16:31:27.172] GPU6 Starting generating ethash dag (Epoch: 471)

Actually, it just zombied the process and left behind hundreds of Xorg instances.  'ps -ef' will give you the parentID of the defunct process, which needs to be killed in order for the zombie process to be released and it should save having to perform a reboot.

v1.50

1. Fix rejected shares on the 9th device bug cuda.
2. Ethproxy fixes opencl.
3. Added more pools

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

TeamBlackMiner_1_50_cuda_11_4.7z
https://www.virustotal.com/gui/file/6bbfbd0fdc3ec1a0b927d2e008eb960c89032cb568d09d4da035e930261c052b?nocache=1

TeamBlackMiner_1_50_cuda_11_5.7z
https://www.virustotal.com/gui/file/50672724b93b8752299159d3cfacda3ca092f214598271b6287a438a7583750f?nocache=1

TeamBlackMiner_1_50_cuda_11_6.7z
https://www.virustotal.com/gui/file/0db7b4ae85dff5ecd9a24e76864db1a404bffee92b48c85ffa9f01b55092c735?nocache=1

TeamBlackMiner_1_50_Ubuntu_18_04_Cuda_11_5_fixed.tar.xz
https://www.virustotal.com/gui/file/b8e0e135c76b15e8b4b1f6ffe07fdf678029b71927bc8d740153f97067e90dc9?nocache=1

TeamBlackMiner_1_50_Ubuntu_18_04_Cuda_11_4_fixed.tar.xz
https://www.virustotal.com/gui/file/3af45ac62fc80c2b214152424ffdfc690c7e3117689ada1bf4dc96713277c4e0?nocache=1

While waiting for the autotune, we have added  Lost hashrate and Reset count to the LHR unlocker (v1.49)


Here is the RTX 3070 LHR on default lhr unlock settings.

in 11.5 hours, lhr has been detected 47 times. Loosing around 0.75MHASH in average on the period.

42.51 - 0.75 = 41.75MHASH effective.

To increase the hashrate you can add values to the --lhr-unlock parameter, but you risk to increase the reset count and lose hash.

Thats good news. I will start a test in a few hours with my 12x BC-160 rig.

Big improvement to the rejected share count in v1.49 on the hiveon pool and other pools that use the ethproxy protocol..

Don't use --cl-devices together with --amd-only you end up having duplicated threads on the same device.
I had a crash at startup on one of my rigs with high intensity on rx 570 cards.  (ethereum classic) The program found alot of solutions that where rejected, and got trown off the pool. Investegating..



yes

So I attempted to run the miner version 1.49 with just one of my AMD cards using the --cl-devices

• and the miner started generating something like 64 GPUs worth of DAG buffers, killed the machine and I'm trying to get it to reboot but HiveOS is taking forever to come back -- well it finally just came back online.  Also, if I use the --amd-only flag, it will use all the cards and ignore any limits in the --cl-devices [ , ] flag; is that expected behaviour?

I'm going to hold off on attempting to generate 1 miner instance per card until this can be reproduced and fixed, or when I have more time to investigate myself.

Refresh the download page. I rebuilt with 1.49

FYI, the Banner is still showing 1.48

v1.49 should have no issues with mixed card rigs now. Got 500 accepted shares and no rejects in the testrig on the hivos.com pool. So the Ethproxy protocol pools seems to be fixed.


If you run 2 instances of the miner, perhaps it helps to mine on the same workername? If a worker is unable to find a share in a round, might lower the pplns payouts?

I think I screwed myself over on 2miners.  

I was the one who identified to them that their PPLNS shares per round was too low (considering the significant increase in their pool hashrate), and so they increased the shares per round from 300,000 to 1,000,000.  Since TBM is what I'll call a 'peak' mining miner, it generates significant peaks of shares at the expense of some lower share rate periods.  Since the peaks were all generally within a 2-4 minute period, I was gaining an advantage by increasing my % round share which wasn't offset by the times when it was lower (so the peaks were paying out more than just a steady state would).  So, now my peaks are getting washed out by the longer round time and the extra advantage seems to be disappearing (as witnessed by my much lower round % average).  

I'm going to play around with different intensities and play around with multiple miner instances vs. a single instance to see if there's a way to push those share bursts into a single round while not screwing the next round and due to the separate miner instances, possibly find solutions for the same job on multiple GPUs...

 

yes. Many changes.

It might trigger LHR in the beginning, but then stay stable. The autotune is not done yet, so hashrate on default settings are nerfed.
The program calculate the reset count and hashrate lost because of the resets. On the 3070 I use 55% powerlimit, and on the 3080ti 70%

Any major LHR improvements since TBM v1.43?

I made attempts to get my 2x 3080 LHR's to a stable hash rate but have been unsuccessful since then.

yes, been like this for a long time. Working on a fix for stats on 5xxx and 6xxx cards. Perhaps in the next release.

00:00:01 [2022-02-02 16:41:49.843] Job c2a3
00:00:01 [2022-02-02 16:41:56.826] Job c2a4
00:00:01 [2022-02-02 16:42:03.805] Job c2a5
00:00:01 [2022-02-02 16:42:04.840] Job c2a6
00:00:01 [2022-02-02 16:42:05.098] Job c2a7
00:00:01 [2022-02-02 16:42:12.070] Job c2a8
00:00:01 [2022-02-02 16:42:19.067] Job c2a9
00:00:02 [2022-02-02 16:42:21.029]
00:00:02 [2022-02-02 16:42:21.029]
00:00:02 [2022-02-02 16:42:21.029] eth.2miners.com (ethash)    PING: 20ms    VARDIFF: 2.03     EPOCH: 470
00:00:02 [2022-02-02 16:42:21.029]
00:00:02 [2022-02-02 16:42:21.029]
00:00:02 [2022-02-02 16:42:21.029] ID      BOARD    TYPE    KERN    XINT    TEMP    FAN     CORE    MEM     WATT
00:00:02 [2022-02-02 16:42:21.029] GPU0    5500XT   OpenCL  0       71      0/0     0       0       0       0
00:00:02 [2022-02-02 16:42:21.029]                                                                          0
00:00:02 [2022-02-02 16:42:21.029]
00:00:02 [2022-02-02 16:42:21.029] ID      BOARD    HASHRATE/W    HASHRATE      AVERAGE       SHARES       RATE
00:00:02 [2022-02-02 16:42:21.029] GPU0    5500XT   0.00 H/W      25.74 MH/s    25.85 MH/s    1/0/0        100.00%
00:00:02 [2022-02-02 16:42:21.029]                  0.00 H/W      25.74 MH/s    25.85 MH/s    1/0/0        100.00%
00:00:02 [2022-02-02 16:42:21.029]
00:00:02 [2022-02-02 16:42:21.029] SHARES PER MINUTE: 0.50                              POOL HASHRATE: 72.72 MH/s
00:00:02 [2022-02-02 16:42:21.029]
00:00:02 [2022-02-02 16:42:21.908] Job c2aa
00:00:02 [2022-02-02 16:42:28.896] Job c2ab
00:00:02 [2022-02-02 16:42:29.151] Job c2ac
00:00:02 [2022-02-02 16:42:30.704] Job c2ad
00:00:02 [2022-02-02 16:42:30.962] Job c2ae
00:00:02 [2022-02-02 16:42:37.942] Job c2af
00:00:02 [2022-02-02 16:42:42.333] Job c2b0

Hi,

always no temp, fan, core, mem, watt for RX5500XT windows.

Thank you!