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

Salva52

newbie

Activity: 4

Merit: 0

What do you recommand for a 3080FE and 3090Fe on miningpoolhub ? (xintensity/tweak/kernel) Thanks

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

1.45 has a gpu timeout bug on AMD cards on high intensity. Upgrade to 1.47

atoue

newbie

Activity: 9

Merit: 0

Hi, I am trying to use this miner in 2miners, however i always got 5-10% lower average hashrate compared to the reported hashrate? I am using v1.45, is there anything wrong I did?

I am using 6700xt rig with xintensity 595 and also mixed 30xx using xintensity 3108

any suggestions?

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

Quote from: cafemax on January 29, 2022, 08:25:40 AM

I can't understand: if dag verification fail, it's mean a hardware error here,
Is there have any meaning? The card could make a lot invalid shares, the hash rate of pool will be bad.

No. Because the dag creation is a heavy process for the gpu that fails on the highest clocks.

To calculate the hash is an easier task. TBM can copy a working dag from another gpu, so you can increase the mem clock and still get 100% accepted shares.

I have tested it on the 3070 and 2060 and it works. +200-300 mz stable

the RTX 2060 went from 33MHASH to 35MHASH. (high xintensity on miningpoolhub)

cafemax

newbie

Activity: 28

Merit: 0

Quote from: ?? on ??

v1.46

1. If dag verification fails, copy a verified dag from another gpu. (NVIDIA)

I can't understand: if dag verification fail, it's mean a hardware error here,

Is there have any meaning? The card could make a lot invalid shares, the hash rate of pool will be bad.

Huh

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

v1.47

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

1. Fix dag verification copy on mixed cards rig AMD/NVIDIA.
2. Fix AMD timeouts in linux on high intensity.
3. Removed No GPU devices available on platform error message on startup.

TeamBlackMiner_1_47_cuda_11_5.7z
https://www.virustotal.com/gui/file/7809fcf40ad8bfeccee69bca1c73f8aeeb5d602c64128a1f150cbd0c8a957fcf?nocache=1

TeamBlackMiner_1_47_cuda_11_4.7z
https://www.virustotal.com/gui/file/acff4d45e4e765174e8b67560de9e6a6dfc7af988a56bd282a92dfcbb0dafd2a?nocache=1

TeamBlackMiner_1_47_Ubuntu_18_04_Cuda_11_5.tar.xz
https://www.virustotal.com/gui/file/c27750518e2ecba1dea05ed2515bfbbf12735f0b58ee4e36b9b2c5677846b0e3?nocache=1

TeamBlackMiner_1_47_Ubuntu_18_04_Cuda_11_4.tar.xz
https://www.virustotal.com/gui/file/b03bc7f374cd9fa6a89ee4efc84b999750578a9d1e6404aaf106ec7e127907ae?nocache=1

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

With v1.47 and the new copy dag function I managed to reach 35MHASH on the RTX 2060 6gb!! by increasing the memclock

Quote from: KillrBee on January 28, 2022, 10:24:04 PM

The DAG copy doesn’t work with mixed AMD and NVidia. I can get the DAG to copy from my 3090 to my 2060S when they’re run alone in their own miner and the AMD cards running in another instance, but when I combine them into one instance I get:

fixed in v1.47

KillrBee

jr. member

Activity: 139

Merit: 3

The DAG copy doesn’t work with mixed AMD and NVidia. I can get the DAG to copy from my 3090 to my 2060S when they’re run alone in their own miner and the AMD cards running in another instance, but when I combine them into one instance I get:

terminate called after throwing an instance of' cuda_runtime error!
what(): CUDA error in func run_black_search_13 at line 1565 invalid device ordinal

KillrBee

jr. member

Activity: 139

Merit: 3

Quote from: sp_ on January 28, 2022, 12:52:10 PM

Quote from: KillrBee on January 28, 2022, 09:44:47 AM

I have noticed that My AMD cards under Linux are crashing a lot, sometimes it's a GPU timing out, which might be due to the undervolting settings which I'm still adjusting on a per-card basis, but I also get the occasional straight crash where the miner is running fine and then just restarts without any information as per:

I believe this was fixed in v1.42. Did you run the v1.41 version?

Quote from: Akyboy on January 28, 2022, 12:36:34 PM

So there is no way you can do something `fancy` for 1GPU cases in terms of DAG verification?

I tried the hdd->gpu aproach but it took 15 seconds on the pci1 riser. and used too much memory.

I am running 1.46 and it’s been happening again since 1.44 I think? This is only in Linux as my windows 6900xt has been running for more than 18 hours, while the Linux ones timeout after 2-4 hours.

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

Quote from: Akyboy on January 28, 2022, 12:56:44 PM

I so want to use your miner "full time", but due to those little probs with 3070 i cannot, yet.

With 6 3070/3060ti cards in the rig. lower the clock on one of the cards, or replace one card with an older card. +300-400mz on the memclock will give you a few percent profit increase.

Akyboy

jr. member

Activity: 90

Merit: 1

Quote from: ?? on ??

.

I believe in you Mister! - I know you will come up with something soon, we need it!

I so want to use your miner "full time", but due to those little probs with 3070 i cannot, yet.
Really need set and forget settings as I'm running with other miner Sad

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

Quote from: KillrBee on January 28, 2022, 09:44:47 AM

I have noticed that My AMD cards under Linux are crashing a lot, sometimes it's a GPU timing out, which might be due to the undervolting settings which I'm still adjusting on a per-card basis, but I also get the occasional straight crash where the miner is running fine and then just restarts without any information as per:

I believe this was fixed in v1.42. Did you run the v1.41 version?

Quote from: Akyboy on January 28, 2022, 12:36:34 PM

So there is no way you can do something `fancy` for 1GPU cases in terms of DAG verification?

I tried the hdd->gpu aproach but it took 15 seconds on the pci1 riser. and used too much memory.

Akyboy

jr. member

Activity: 90

Merit: 1

Quote from: sp_ on January 28, 2022, 11:36:20 AM

v1.46 re-upload

1. If dag verification fails, copy a verified dag from another gpu. (NVIDIA)
2. RTX 3070/3060ti stable on +300mz memclock, when the dag is created on another gpu.
3. Exit faster on linux

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

TeamBlackMiner_1_46_cuda_11_5.7z
https://www.virustotal.com/gui/file/5c4de8414cc0acf0353ab1bb69c4fad5997f211abeaca54f0b63305798160246?nocache=1

TeamBlackMiner_1_46_cuda_11_4.7z
https://www.virustotal.com/gui/file/b68c56f30fdb51ad13ae39efa36def7c1c2238b1f0f51736331974b5aa7c38d6?nocache=1

TeamBlackMiner_1_46_Ubuntu_18_04_Cuda_11_5.tar.xz
https://www.virustotal.com/gui/file/ad45e90dd5990fa3fa50c0922a59e6120d8e2ce2a27834e4ad518daa40d5edc1?nocache=1

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

Thanks Mister!

So there is no way you can do something `fancy` for 1GPU cases in terms of DAG verification?
p.s. Yes i have several rigs with multiple cards but i also have couple of gaming machines (3 kids) with 3070 in them.

Thanks!

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

v1.46 re-upload

1. If dag verification fails, copy a verified dag from another gpu. (NVIDIA)
2. RTX 3070/3060ti/2060/2070/2060S/2070S stable on +300mz memclock, when the dag is created on another gpu.
3. Exit faster on linux

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

TeamBlackMiner_1_46_cuda_11_5.7z
https://www.virustotal.com/gui/file/5c4de8414cc0acf0353ab1bb69c4fad5997f211abeaca54f0b63305798160246?nocache=1

TeamBlackMiner_1_46_cuda_11_4.7z
https://www.virustotal.com/gui/file/b68c56f30fdb51ad13ae39efa36def7c1c2238b1f0f51736331974b5aa7c38d6?nocache=1

TeamBlackMiner_1_46_Ubuntu_18_04_Cuda_11_5.tar.xz
https://www.virustotal.com/gui/file/ad45e90dd5990fa3fa50c0922a59e6120d8e2ce2a27834e4ad518daa40d5edc1?nocache=1

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

KillrBee

jr. member

Activity: 139

Merit: 3

Quote from: ?? on ??

v1.46

1. If dag verification fails, copy a verified dag from another gpu. (NVIDIA)
2. RTX 3070/3060ti stable on +300mz memclock, when the dag is created on another gpu.
3. Exit faster on linux

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

TeamBlackMiner_1_46_cuda_11_4.7z
https://www.virustotal.com/gui/file/2eb855d1888f23d9a5e41196dc02241a7a598353643c7e53e79353f24bdb1e99?nocache=1

TeamBlackMiner_1_46_cuda_11_5.7z
https://www.virustotal.com/gui/file/d4885e7c0fdfe3243dfc62b7736ca1fc33f8b18ae1481f20a125dda02017fceb?nocache=1

TeamBlackMiner_1_46_Ubuntu_18_04_Cuda_11_4.tar.xz
https://www.virustotal.com/gui/file/2503fa9d890e106a7d1ee0db7bc66071d34b46de1e8f62cc14205357406deb3a?nocache=1

TeamBlackMiner_1_46_Ubuntu_18_04_Cuda_11_5.tar.xz
https://www.virustotal.com/gui/file/c511099e2a8312a2104568f24052aed2863b9b80fe3c4c648a1c7c0a11735e43?nocache=1

Just FYI: The INIT screen is showing:

00:00:00 [2022-01-28 10:07:20.320]
00:00:00 [2022-01-28 10:07:20.344] Cuda driver version: 11.5
00:00:00 [2022-01-28 10:07:20.344] Cuda runtime API version: 11.4
00:00:00 [2022-01-28 10:07:20.344]
00:00:00 [2022-01-28 10:07:20.344]
00:00:00 [2022-01-28 10:07:20.344]
00:00:00 [2022-01-28 10:07:20.344] Welcome to Team Black Miner 1.45
00:00:00 [2022-01-28 10:07:20.344]
00:00:00 [2022-01-28 10:07:20.344]
00:00:00 [2022-01-28 10:07:20.344] Using all Nvidia devices

for version 1.46

KillrBee

jr. member

Activity: 139

Merit: 3

I have noticed that My AMD cards under Linux are crashing a lot, sometimes it's a GPU timing out, which might be due to the undervolting settings which I'm still adjusting on a per-card basis, but I also get the occasional straight crash where the miner is running fine and then just restarts without any information as per:

00:02:33 [2022-01-27 17:40:10.784] Job 11fba0
00:02:33 [2022-01-27 17:40:20.220] GPU0 Solution found in 11.29s (Submit every 23.09 seconds)
00:02:33 [2022-01-27 17:40:20.220] Job 11fba1
00:02:33 [2022-01-27 17:40:20.259] Accepted (427/428/186) Reply: 39ms
00:02:33 [2022-01-27 17:40:24.937] Job 11fba3
00:02:34 [2022-01-27 17:40:29.655]
00:02:34 [2022-01-27 17:40:29.655]
00:02:34 [2022-01-27 17:40:29.655] us-eth.2miners.com (ethash) PING: 44ms VARDIFF: 2.03 EPOCH: 469
00:02:34 [2022-01-27 17:40:29.655]
00:02:34 [2022-01-27 17:40:29.655]
00:02:34 [2022-01-27 17:40:29.655] ID BOARD TYPE KERN XINT TEMP FAN CORE MEM WATT
00:02:34 [2022-01-27 17:40:29.655] Job 11fba6
00:02:34 [2022-01-27 17:40:29.655] GPU0 gfx1030 OpenCL 0 1000 34/0 73 1350 1071 132
00:02:34 [2022-01-27 17:40:29.655] GPU1 gfx1030 OpenCL 0 1000 27/0 73 1325 1071 116
00:02:34 [2022-01-27 17:40:29.655] GPU2 gfx1030 OpenCL 0 1000 26/0 73 1365 1071 135
00:02:34 [2022-01-27 17:40:29.655] GPU3 gfx1030 OpenCL 0 1000 27/0 73 1350 1071 113
00:02:34 [2022-01-27 17:40:29.655] GPU4 3090 CUDA 8 4000 35/0 0 0 0 338
00:02:34 [2022-01-27 17:40:29.655] GPU5 2060S CUDA 13 4000 34/0 85 1650 7950 115
00:02:34 [2022-01-27 17:40:29.655] 949
00:02:34 [2022-01-27 17:40:29.655]
00:02:34 [2022-01-27 17:40:29.655] ID BOARD HASHRATE/W HASHRATE AVERAGE SHARES RATE
00:02:34 [2022-01-27 17:40:29.655] GPU0 gfx1030 499.41 kH/W 66.42 MH/s 66.36 MH/s 71/1/39 98.61%
00:02:34 [2022-01-27 17:40:29.655] GPU1 gfx1030 553.17 kH/W 66.38 MH/s 66.32 MH/s 54/0/34 100.00%
00:02:34 [2022-01-27 17:40:29.655] GPU2 gfx1030 523.82 kH/W 66.00 MH/s 66.00 MH/s 65/0/37 100.00%
00:02:34 [2022-01-27 17:40:29.655] GPU3 gfx1030 593.03 kH/W 66.42 MH/s 66.36 MH/s 67/0/39 100.00%
00:02:34 [2022-01-27 17:40:29.655] GPU4 3090 397.44 kH/W 134.33 MH/s 134.33 MH/s 124/0/25 100.00%
00:02:34 [2022-01-27 17:40:29.655] GPU5 2060S 384.86 kH/W 44.26 MH/s 44.26 MH/s 46/0/12 100.00%
00:02:34 [2022-01-27 17:40:29.655] 491.95 kH/W 443.81 MH/s 443.61 MH/s 427/1/186 99.77%
00:02:34 [2022-01-27 17:40:29.655]
00:02:34 [2022-01-27 17:40:29.655] SHARES PER MINUTE: 2.79 POOL HASHRATE: 405.89 MH/s
00:02:34 [2022-01-27 17:40:29.655]
00:02:34 [2022-01-27 17:40:32.457] GPU4 Solution found in 3.03s (Submit every 23.07 seconds)
00:02:34 [2022-01-27 17:40:32.489] Accepted (428/429/186) Reply: 32ms

==> teamblackminer.8.log <==

Where the .8.log is the next log in my 'tail -n 75 *.log' command.

Is there any way to get more information on this? I can't seem to find any crash or coredump logs for these events either.

A normal timeout looks like this:

00:02:53 [2022-01-27 20:38:19.560] GPU2 Solution found in 9.08s (Submit every 33.29 seconds)
00:02:53 [2022-01-27 20:38:19.601] Accepted (316/317/199) Reply: 40ms
00:02:53 [2022-01-27 20:38:20.447] Job 1207d3
00:02:53 [2022-01-27 20:38:29.710]
00:02:53 [2022-01-27 20:38:29.710]
00:02:53 [2022-01-27 20:38:29.710] us-eth.2miners.com (ethash) PING: 35ms VARDIFF: 2.03 EPOCH: 469
00:02:53 [2022-01-27 20:38:29.710]
00:02:53 [2022-01-27 20:38:29.710]
00:02:53 [2022-01-27 20:38:29.710] ID BOARD TYPE KERN XINT TEMP FAN CORE MEM WATT
00:02:53 [2022-01-27 20:38:29.710] GPU0 gfx1030 OpenCL 0 1000 32/0 73 1350 1071 131
00:02:53 [2022-01-27 20:38:29.710] GPU1 gfx1030 OpenCL 0 1000 18/0 73 1325 1071 116
00:02:53 [2022-01-27 20:38:29.710] GPU2 gfx1030 OpenCL 0 1000 26/0 73 1365 1071 125
00:02:53 [2022-01-27 20:38:29.710] GPU3 gfx1030 OpenCL 0 1000 27/0 73 1350 1071 109
00:02:53 [2022-01-27 20:38:29.710] 481
00:02:53 [2022-01-27 20:38:29.710]
00:02:53 [2022-01-27 20:38:29.710] ID BOARD HASHRATE/W HASHRATE AVERAGE SHARES RATE
00:02:53 [2022-01-27 20:38:29.710] GPU0 gfx1030 499.42 kH/W 66.42 MH/s 66.31 MH/s 73/0/46 100.00%
00:02:53 [2022-01-27 20:38:29.710] GPU1 gfx1030 1952.41 kH/W 66.38 MH/s 66.32 MH/s 81/0/53 100.00%
00:02:53 [2022-01-27 20:38:29.711] GPU2 gfx1030 519.71 kH/W 66.00 MH/s 65.91 MH/s 84/0/42 100.00%
00:02:53 [2022-01-27 20:38:29.711] GPU3 gfx1030 598.40 kH/W 66.42 MH/s 66.31 MH/s 78/1/58 98.73%
00:02:53 [2022-01-27 20:38:29.711] 892.49 kH/W 265.23 MH/s 264.85 MH/s 316/1/199 99.68%
00:02:53 [2022-01-27 20:38:29.711]
00:02:53 [2022-01-27 20:38:29.711] SHARES PER MINUTE: 1.83 POOL HASHRATE: 265.65 MH/s
00:02:53 [2022-01-27 20:38:29.711]
00:02:53 [2022-01-27 20:38:29.882] Job 1207d4
00:02:53 [2022-01-27 20:38:34.598] GPU3 Solution found in 8.65s (Submit every 33.23 seconds)
00:02:53 [2022-01-27 20:38:34.599] Job 1207d5
00:02:53 [2022-01-27 20:38:34.630] Accepted (317/318/200) Reply: 31ms
00:02:54 [2022-01-27 20:38:44.033] Job 1207d7
00:02:54 [2022-01-27 20:38:48.751] Job 1207d8
00:02:54 [2022-01-27 20:38:58.185] Job 1207d9
00:02:54 [2022-01-27 20:39:02.903] Job 1207da
00:02:54 [2022-01-27 20:39:07.035] GPU2 Solution found in 4.43s (Submit every 33.23 seconds)
00:02:54 [2022-01-27 20:39:07.066] Accepted (318/319/200) Reply: 30ms
00:02:54 [2022-01-27 20:39:12.338] Job 1207dd
00:02:54 [2022-01-27 20:39:17.055] GPU3 Solution found in 5.18s (Submit every 33.16 seconds)
00:02:54 [2022-01-27 20:39:17.087] Accepted (319/320/200) Reply: 31ms
00:02:54 [2022-01-27 20:39:21.772] Job 1207de
00:02:54 [2022-01-27 20:39:26.490] Job 1207df
00:02:54 [2022-01-27 20:39:29.093] GPU1: has timed out
00:02:54 [2022-01-27 20:39:29.093] Shutting down threads
00:02:54 [2022-01-27 20:39:29.093] Stratum thread exited
00:02:54 [2022-01-27 20:39:30.775] GPU2 thread exited
00:02:54 [2022-01-27 20:39:31.207] GPU3 thread exited
00:02:54 [2022-01-27 20:39:31.207] GPU0 thread exited
00:02:54 [2022-01-27 20:39:36.157] Api thread exited
00:02:55 [2022-01-27 20:39:46.093] Exiting

==> teamblackminer.6.log <==

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

Quote from: KillrBee on January 28, 2022, 09:11:02 AM

BTW, what's the current unlocked hashrate for a 3080Ti on TBM? I have an opportunity to pick one up at slightly below retail and was wondering if the unlock would put it on par with the 3090.

V1.46 is Peaking at 112 MHASH but average speed is 80-90 at maximum. The LHR autotune is not done yet, so perhaps it will beat my manual tuning. But the maximum limit is probobly below 100MHASH somewhere. The LHR limit seems to be in hardware, so a crack is not possible.

The numbers are with the LHR partial unlock mode enabled. Without LHR 120MHASH should be possible I think. but then the gpu will switch to LHR mode in a few seconds and the hashrate fall to 60 ish.

KillrBee

jr. member

Activity: 139

Merit: 3

Is there any way that we can get a toggle to switch the mining time from DD:HH:MM to just number of minutes? I know there was a big request to switch it to the more human readable form, but when I'm doing my own calculations it's tedious to have to convert 18 hours 26 minutes into 18*60+26 minutes, it doesn't need to be a single dash toggle, it could just be something like --showTime {1 = human readable, 2 = minutes, 3 = hours (in case for some reason hours is useful to someone)}.

Thanks

BTW, what's the current unlocked hashrate for a 3080Ti on TBM? I have an opportunity to pick one up at slightly below retail and was wondering if the unlock would put it on par with the 3090.

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

The new code seems to work. The 3070LHR is now stable at 8100 Memory (+1500) . v1.45 could only do (+1200)

When the dag verification fails, the program will copy the dag from the fastest card in the rig (here a 3080ti). (gpu->gpu copy. No hardrive or memory buffers needed) Works smooth and fast on linux and windows 4GB rigs. For rigs with only 3070 or 3060ti cards, one of the cards need to be down clocked to be able to verify the dag, then the rest of the cards will copy this validated dag into their memory.

Akyboy

jr. member

Activity: 90

Merit: 1

Quote from: sp_ on January 27, 2022, 04:31:16 AM

Quote from: Akyboy on January 26, 2022, 12:52:37 PM

Mr.sp__ , when can we expect update with DAG generate/verification on HDD?
Thanks!

Windows version perhaps tomorrow. This feature need alot of testing.

Tomorrow it is!

drop down that fee and i test it all day long for you! hahahah!!!!

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

Quote from: Akyboy on January 26, 2022, 12:52:37 PM

Mr.sp__ , when can we expect update with DAG generate/verification on HDD?
Thanks!

Windows version perhaps tomorrow. This feature need alot of testing.

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