Akyboy
Jr. Member
Offline
Activity: 90
Merit: 1
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 26, 2022, 07:58:56 PM |
|
use msi afterburner. We don't support sdtting the clocks on Amd cards
Ah ok ok! Thanks!
|
|
|
|
KillrBee
Jr. Member
Offline
Activity: 139
Merit: 3
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 26, 2022, 10:27:30 PM |
|
use msi afterburner. We don't support sdtting the clocks on Amd cards
Better yet, use OverdriveNTool for AMD cards, much easier to set the OC script to run from the TBMiner script and to check that the values are holding.
|
|
|
|
sp_ (OP)
Legendary
Offline
Activity: 2926
Merit: 1087
Team Black developer
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 27, 2022, 09:31:16 AM |
|
Mr.sp__ , when can we expect update with DAG generate/verification on HDD? Thanks!
Windows version perhaps tomorrow. This feature need alot of testing.
|
|
|
|
Akyboy
Jr. Member
Offline
Activity: 90
Merit: 1
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 27, 2022, 11:31:23 PM Last edit: January 28, 2022, 02:07:26 AM by Akyboy |
|
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_ (OP)
Legendary
Offline
Activity: 2926
Merit: 1087
Team Black developer
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 28, 2022, 12:40:04 PM Last edit: January 28, 2022, 01:14:39 PM by sp_ |
|
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. ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.ibb.co%2FmNpNvWx%2Fdag-validation-fix.png&t=665&c=ziueQrEdOEMj8w)
|
|
|
|
KillrBee
Jr. Member
Offline
Activity: 139
Merit: 3
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 28, 2022, 02:11:02 PM |
|
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_ (OP)
Legendary
Offline
Activity: 2926
Merit: 1087
Team Black developer
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 28, 2022, 02:21:32 PM |
|
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
Offline
Activity: 139
Merit: 3
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 28, 2022, 02:44:47 PM |
|
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 <==
|
|
|
|
KillrBee
Jr. Member
Offline
Activity: 139
Merit: 3
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 28, 2022, 03:09:13 PM |
|
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 devicesfor version 1.46
|
|
|
|
sp_ (OP)
Legendary
Offline
Activity: 2926
Merit: 1087
Team Black developer
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 28, 2022, 04:36:20 PM Last edit: January 29, 2022, 01:21:15 PM by sp_ |
|
|
|
|
|
Akyboy
Jr. Member
Offline
Activity: 90
Merit: 1
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 28, 2022, 05:36:34 PM |
|
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_ (OP)
Legendary
Offline
Activity: 2926
Merit: 1087
Team Black developer
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 28, 2022, 05:52:10 PM |
|
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? v1.42
1. Fixed gpu timeouts on AMD rigs.
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
Offline
Activity: 90
Merit: 1
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 28, 2022, 05:56:44 PM |
|
.
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](https://bitcointalk.org/Smileys/default/sad.gif)
|
|
|
|
sp_ (OP)
Legendary
Offline
Activity: 2926
Merit: 1087
Team Black developer
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 29, 2022, 12:04:54 AM Last edit: January 29, 2022, 07:19:19 AM by sp_ |
|
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.
|
|
|
|
KillrBee
Jr. Member
Offline
Activity: 139
Merit: 3
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 29, 2022, 03:16:45 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? v1.42
1. Fixed gpu timeouts on AMD rigs.
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.
|
|
|
|
KillrBee
Jr. Member
Offline
Activity: 139
Merit: 3
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 29, 2022, 03:24:04 AM |
|
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
|
|
|
|
|
cafemax
Newbie
Offline
Activity: 28
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 29, 2022, 01:25:40 PM |
|
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](https://bitcointalk.org/Smileys/default/huh.gif)
|
|
|
|
sp_ (OP)
Legendary
Offline
Activity: 2926
Merit: 1087
Team Black developer
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 29, 2022, 01:37:37 PM Last edit: January 30, 2022, 01:24:52 PM by sp_ |
|
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)
|
|
|
|
atoue
Newbie
Offline
Activity: 9
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 29, 2022, 02:11:37 PM |
|
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?
|
|
|
|
|