Team Black Miner (ETHW ETC Vertcoin Ravencoin Zilliqa +dual +tripple mining ) - page 58.

duddabudda

newbie

Activity: 21

Merit: 0

Quote from: sp_ on November 11, 2021, 07:39:22 AM

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

TeamBlackMiner v1.24

Always happy to get new updates! Thanks to the developers of TBM!

I would like to add that I wish more changes were made for AMD cards because no other development team did what you did for 6x00 series)
Thanks again!

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

Quote from: xalinaventure on November 11, 2021, 07:51:02 AM

How long to wait for it on HiveOS Sad

?

They normally add it pretty quickly. 1 day perhaps?

xalinaventure

newbie

Activity: 6

Merit: 0

Quote from: sp_ on November 11, 2021, 07:39:22 AM

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

TeamBlackMiner_1_24_cuda_11_2.7z
https://www.virustotal.com/gui/file/f8741e6b6c957d7361002056e427751efb03a63ef81570f609f9a72cc31d100c?nocache=1

TeamBlackMiner_1_24_cuda_11_4.7z
https://www.virustotal.com/gui/file/093d7c211afe26bfce07557f8044341d27a23b9f92c807744cdc38e946ba896c?nocache=1

TeamBlackMiner_1_24_cuda_11_5.7z
https://www.virustotal.com/gui/file/6529ccea7447eb235add72050835ad0c00aebf45ea9da2c14ef780009c0b4d01?nocache=1

TeamBlackMiner_1_24_Ubuntu_18_04_Cuda_11_4.tar.gz
https://www.virustotal.com/gui/file/8199961b122172a8239ce1675f3ecf095bba210c6c6599cc9882407dbe35cd0d?nocache=1

v1.24
1. Fixed issue with multiple set core, mem, power.
2. Fixed issue with dag cache when switching back from ZIL pow.
3. Always verify dag on regeneration. Not only on the first run.
4. Log date time format is now DD:HH:MM.
5. API bumped to v1.3: Added port, versioning in url and summary.

How long to wait for it on HiveOS Sad

?

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

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

TeamBlackMiner_1_24_cuda_11_2.7z
https://www.virustotal.com/gui/file/f8741e6b6c957d7361002056e427751efb03a63ef81570f609f9a72cc31d100c?nocache=1

TeamBlackMiner_1_24_cuda_11_4.7z
https://www.virustotal.com/gui/file/093d7c211afe26bfce07557f8044341d27a23b9f92c807744cdc38e946ba896c?nocache=1

TeamBlackMiner_1_24_cuda_11_5.7z
https://www.virustotal.com/gui/file/6529ccea7447eb235add72050835ad0c00aebf45ea9da2c14ef780009c0b4d01?nocache=1

TeamBlackMiner_1_24_Ubuntu_18_04_Cuda_11_4.tar.gz
https://www.virustotal.com/gui/file/8199961b122172a8239ce1675f3ecf095bba210c6c6599cc9882407dbe35cd0d?nocache=1

TeamBlackMiner_1_24_Ubuntu_18_04_Cuda_11_5.tar.gz
https://www.virustotal.com/gui/file/6948a7ed9d3a1676d865d093eb8995e20d46bb6075237d6215959ac661dfde96?nocache=1

v1.24
1. Fixed issue with multiple set core, mem, power.
2. Fixed issue with dag cache when switching back from ZIL pow.
3. Always verify dag on regeneration. Not only on the first run.
4. Log date time format is now DD:HH:MM.
5. API bumped to v1.3: Added port, versioning in url and summary.

abanamat

jr. member

Activity: 274

Merit: 1

Quote from: sp_ on November 11, 2021, 06:10:13 AM

Quote from: abanamat on November 11, 2021, 05:58:51 AM

120 OC - is it too much for 1070?

Try to increase the memclock +50 and reduce to +100 on the core

core: 2050
mem: 4350

Will try it now, thanks

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

Quote from: abanamat on November 11, 2021, 05:58:51 AM

120 OC - is it too much for 1070?

Try to increase the memclock +50 and reduce to +100 on the core

core: 2050
mem: 4350

abanamat

jr. member

Activity: 274

Merit: 1

Quote from: sp_ on November 11, 2021, 05:50:43 AM

Quote from: abanamat on November 11, 2021, 05:22:17 AM

Hello. What can it be?

Probobly the core clock that is too high. Too much oc.

120 OC - is it too much for 1070?

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

Quote from: abanamat on November 11, 2021, 05:22:17 AM

Hello. What can it be?

Probobly the core clock that is too high. Too much oc.

abanamat

jr. member

Activity: 274

Merit: 1

Hello. What can it be?

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

Quote from: dle378 on November 10, 2021, 05:55:17 PM

I don't see it reported in 2Miners unless I am missing something...

Exactly. The stale shares reported in the miner window is an estimate. The pool is accepting all your shares so you can increase the intensity more if you want. You are using xintensity 1024, try 4096

dle378

copper member

Activity: 77

Merit: 0

Quote from: sp_ on November 10, 2021, 04:24:57 PM

Quote from: dle378 on November 10, 2021, 09:49:02 AM

Do the stale shares that reflect in TBM show up as “accepted” or “stale” in 2Miners?

stales are accepted, but if you click on the worker in the 2miners www gui you can see the staleshare and invalid count.

I don't see it reported in 2Miners unless I am missing something...

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

Quote from: dle378 on November 10, 2021, 09:49:02 AM

Do the stale shares that reflect in TBM show up as “accepted” or “stale” in 2Miners?

stales are accepted, but if you click on the worker in the 2miners www gui you can see the staleshare and invalid count.

wasarianta

newbie

Activity: 40

Merit: 0

Quote from: sp_ on November 10, 2021, 04:26:00 AM

on 2miners try --xintensity 1024 for amd cards. and --xintensity 4096 for nvidia

2048 also good boss or just lucky me.. sharing this... hope will help

Quote

0m [2021-11-08 14:43:14.758]
0m [2021-11-08 14:43:15.945] OpenCL driver version: 30.0
0m [2021-11-08 14:43:15.945] Cuda driver version: 11.5
0m [2021-11-08 14:43:15.945] Cuda runtime API version: 11.5
0m [2021-11-08 14:43:15.945]
0m [2021-11-08 14:43:15.945]
0m [2021-11-08 14:43:15.945]
0m [2021-11-08 14:43:15.945] Welcome to Team Black Miner 1.23
0m [2021-11-08 14:43:15.945]
0m [2021-11-08 14:43:15.945]
0m [2021-11-08 14:43:15.945] Using all Nvidia devices
0m [2021-11-08 14:43:16.039] GPU0 NVIDIA GeForce RTX 2080 SUPER 8GB added to miner as Cuda device
0m [2021-11-08 14:43:16.195] GPU0 DAG intensity set to 9
0m [2021-11-08 14:43:16.195] GPU0 Started Cuda work thread
0m [2021-11-08 14:43:16.195] Api server started at 127.0.0.1:4068
0m [2021-11-08 14:43:16.273] Trying asia-eth.2miners.com:2020 (ethash)
0m [2021-11-08 14:43:16.289] Extranonce is set to 13305322149112709120
0m [2021-11-08 14:43:16.289] Pool responded successfully to subscribe
0m [2021-11-08 14:43:16.320] Pool responded successfully to extranonce subscribe
0m [2021-11-08 14:43:16.336] Extranonce is set to 13305322149112709120
0m [2021-11-08 14:43:16.352] Pool responded successfully to authorize
0m [2021-11-08 14:43:16.617] Difficulty is set to 2.031715
0m [2021-11-08 14:43:19.766] GPU0 Starting generating ethash dag (Epoch: 452)
0m [2021-11-08 14:43:19.922] GPU0 DAG intensity set to 9
0m [2021-11-08 14:43:19.922] GPU0 DAG generated in 3.30 seconds (4751358kb)
0m [2021-11-08 14:43:19.922] GPU0 kernel 8 selected
0m [2021-11-08 14:43:19.922] GPU0 Tweak set to 7
0m [2021-11-08 14:43:19.922] GPU0 XIntensity set to 2048
0m [2021-11-08 14:43:35.861] Job 33f1c
0m [2021-11-08 14:43:36.424] GPU0 Dag buffer verified ok!
0m [2021-11-08 14:43:36.471] GPU0 GPU clocks set to "(gpuClkMin 1390, gpuClkMax 1390)" for GPU 00000000:03:00.0
.......
60m [2021-11-08 15:43:16.075] asia-eth.2miners.com (ethash) PING: 25ms DIFFICULTY: 2.03 EPOCH: 452
60m [2021-11-08 15:43:16.075]
60m [2021-11-08 15:43:16.075]
60m [2021-11-08 15:43:16.075] ID BOARD TYPE KERN XINT TEMP FAN CORE MEM WATT
60m [2021-11-08 15:43:16.075] GPU0 2080S CUDA 8 2048 44/0 71 1394 8692 90
60m [2021-11-08 15:43:16.075] 90
60m [2021-11-08 15:43:16.075]
60m [2021-11-08 15:43:16.075] ID BOARD HASHRATE/W HASHRATE AVERAGE SHARES RATE
60m [2021-11-08 15:43:16.075] GPU0 2080S 494.02 kH/W 44.46 MH/s 44.46 MH/s 18/0/0 100.00%
60m [2021-11-08 15:43:16.075] 494.02 kH/W 44.46 MH/s 44.46 MH/s 18/0/0 100.00%
60m [2021-11-08 15:43:16.075]
60m [2021-11-08 15:43:16.075] SHARES PER MINUTE: 0.31 POOL HASHRATE: 44.37 MH/s
.......
.......
.......
475m [2021-11-08 22:38:16.067] asia-eth.2miners.com (ethash) PING: 24ms DIFFICULTY: 2.03 EPOCH: 452
475m [2021-11-08 22:38:16.067]
475m [2021-11-08 22:38:16.067]
475m [2021-11-08 22:38:16.067] ID BOARD TYPE KERN XINT TEMP FAN CORE MEM WATT
475m [2021-11-08 22:38:16.067] GPU0 2080S CUDA 8 2048 46/0 71 1394 8692 91
475m [2021-11-08 22:38:16.067] 91
475m [2021-11-08 22:38:16.067]
475m [2021-11-08 22:38:16.067] ID BOARD HASHRATE/W HASHRATE AVERAGE SHARES RATE
475m [2021-11-08 22:38:16.067] GPU0 2080S 488.65 kH/W 44.47 MH/s 44.46 MH/s 136/0/0 100.00%
475m [2021-11-08 22:38:16.067] 488.65 kH/W 44.47 MH/s 44.46 MH/s 136/0/0 100.00%
475m [2021-11-08 22:38:16.067]
475m [2021-11-08 22:38:16.067] SHARES PER MINUTE: 0.29 POOL HASHRATE: 41.73 MH/s
475m [2021-11-08 22:38:16.067]
475m [2021-11-08 22:38:22.682] Job 3622d
475m [2021-11-08 22:38:29.523] Job 3622e
475m [2021-11-08 22:38:29.788] Job 3622f
475m [2021-11-08 22:38:36.880] Job 36230
475m [2021-11-08 22:38:37.146] Job 36232
475m [2021-11-08 22:38:43.987] Job 36233
475m [2021-11-08 22:38:51.099] Job 36234
475m [2021-11-08 22:38:53.458] Job 36235
475m [2021-11-08 22:38:53.990] Job 36236
475m [2021-11-08 22:39:00.575] Job 36237
475m [2021-11-08 22:39:01.610] Shutting down threads
475m [2021-11-08 22:39:01.626] Control thread exited
475m [2021-11-08 22:39:01.626] Stratum thread exited
475m [2021-11-08 22:39:01.626] GPU0 thread exited
475m [2021-11-08 22:39:05.627] Exiting GO TO BED

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

Quote from: mo35 on November 07, 2021, 10:50:04 AM

I'm experiencing weird issue , starting from 1.22 (prolly 1.21 , skipped that one) , at some point shares stops validating on cpu , experiencing that on 2 separate boxes.

We have reproduced this issue for NVIDIA cards and fixed it in v1.24. Eth+zil, Etc+zil pools and nicehash users will have problems with 1.20-1.23. We have also added dag validation on every regeneration to ensure that the program exits quickly on dag errors. In the previous versions the dag was only validated once on startup (nvidia).

Koj1888

newbie

Activity: 5

Merit: 0

Quote from: ?? on ??

Quote from: Koj1888 on November 10, 2021, 04:46:56 AM

have this running on a mixed rig how do i specify it for different cards. Nvidias are all 3080 but amd are mix of 5700xt and 5600xt.

amd cards(opencl) are listed first, then nvidia.

so for --cl_devices [0,1,2] --cuda_devices [0,1,2]

--xintensity [8,8,8,64,64,64]

Thanks giving it a try now.

dle378

copper member

Activity: 77

Merit: 0

Quote from: sp_ on November 10, 2021, 04:26:00 AM

on 2miners try --xintensity 1024 for amd cards. and --xintensity 4096 for nvidia

kernel 0 is slow on low intensity

Do the stale shares that reflect in TBM show up as “accepted” or “stale” in 2Miners?

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

AMD stats are working in Windows. on linux/hivos we trying to fix it in v1.24

UniJo

jr. member

Activity: 60

Merit: 2

Quote from: ?? on ??

Quote from: UniJo on November 10, 2021, 05:38:39 AM

Is there anyone that tried this miner with the old Polaris cards? Any improvements next to Phoenix and TRM?

With --xintensity 60 and hynix memory clocked at 2200-2250MHZ you can reach 32-33mhash

The Hynix ones that i got won't clock that high. 2100 and some 2150 wich gives me -/+32 mh/s. I will try these --xintensity with my other cards (mosltly microns and samsungs) ( 34,3 and 31mh/s now).

Edit: I switched one miner with 10 RX580 to TBM now. I get about the same hashrate as with Phoenix. I will check if there is a increase in shares.

PS: there is now info shown like power consumption, temp, fan speeds and clocks. Can i do something to make that working?

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

Quote from: xalinaventure on November 10, 2021, 04:49:41 AM

Also an error on my mixed rig (6800XT and 1080Ti) "Cannot open shared object file" don't know whether it is causing any issue, just curious.

It's a problem with stats for amd cards on linux. We are working on a fix for this in v1.24

Quote from: Koj1888 on November 10, 2021, 04:46:56 AM

have this running on a mixed rig how do i specify it for different cards. Nvidias are all 3080 but amd are mix of 5700xt and 5600xt.

amd cards(opencl) are listed first, then nvidia.

so for --cl_devices [0,1,2] --cuda_devices [0,1,2]

--xintensity [8,8,8,64,64,64]

Quote from: UniJo on November 10, 2021, 05:38:39 AM

Is there anyone that tried this miner with the old Polaris cards? Any improvements next to Phoenix and TRM?

With --xintensity 60 and hynix memory clocked at 2200-2250MHZ you can reach 32-33mhash

[moderator's note: consecutive posts merged]

UniJo

jr. member

Activity: 60

Merit: 2

Is there anyone that tried this miner with the old Polaris cards? Any improvements next to Phoenix and TRM?

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