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

dle378

copper member

Activity: 77

Merit: 0

Quote from: dle378 on October 25, 2021, 11:25:18 AM

Crashes after one minute of running with --kernel 0, 1, 4, 6, 8.

I am using default clocks during the initial start of TBM.

try with --no-stats. And then without --lock-cclock. The dag verification code will be improved in v1.20. With options to create the dag slower.

Adding the parameter "--no-stats" fixed the issue!

Any chance as to why this parameter prevents the crashing of the miner in this version versus the previous ones?

Ramsete2

jr. member

Activity: 87

Merit: 5

Testing latest TBMiner version vs GMiner.
Here below results after about 10 hours:

TBMiner (ver 1.19)

GMiner (ver 2.70)

Honestly I don't know what to say, despite TBMiner shows more hashrate, GMiner is always providing more shares to the pool...
Even shares per minute calculation seems wrong, since both miners startd at the same time.

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: sxemini on October 25, 2021, 04:30:09 AM

Ehm no? I am mining on it with 14 RIG´s - but only TBM will not connect.

https://zil.rustpool.xyz/

Oh. sorry about that, it will be added again in v1.20

Quote from: dle378 on October 25, 2021, 11:25:18 AM

Crashes after one minute of running with --kernel 0, 1, 4, 6, 8.

I am using default clocks during the initial start of TBM.

try with --no-stats. And then without --lock-cclock. The dag verification code will be improved in v1.20. With options to create the dag slower.

[moderator's note: consecutive posts merged]

dle378

copper member

Activity: 77

Merit: 0

Quote from: sp_ on October 24, 2021, 11:08:57 PM

Quote from: dle378 on October 24, 2021, 08:56:36 PM

Still crashes even when running on either --kernel 6 or --kernel 4.

Does it crash with --kernel 0 ? Try to lower the clock.

Crashes after one minute of running with --kernel 0, 1, 4, 6, 8.

I am using default clocks during the initial start of TBM.

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

yes. we will try to improve this in the next versions.

hashatharias

newbie

Activity: 12

Merit: 0

These are dead low frequencies: Angry

memory [MHz]
9751 MHz
9501 MHz
5001 MHz
810 MHz
405 MHz
7001 MHz
6801 MHz
5001 MHz
810 MHz
405 MHz

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: hashatharias on October 25, 2021, 09:54:40 AM

Also, it seems that there's a problem when trying to set memory clock

Read a couple of posts back, we only support the memclock values from nvidia-smi. Use another program to set the memclock for now. msi afterburner is good.

hashatharias

newbie

Activity: 12

Merit: 0

Also, it seems that there's a problem when trying to set memory clock

TBMiner --algo ethash --lock-cclock [[1140,1140][1140,1140]] --lock-mclock [[10775,10775][8075,8075]] --hostname daggerhashimoto.usa-east.nicehash.com --port 3353 --xintensity 224 --wallet %WALLET% --worker-name %computername%

Code:

0m [2021-10-25 10:49:06.014]
   0m [2021-10-25 10:49:06.073] OpenCL driver version: 496.13
   0m [2021-10-25 10:49:06.093] Cuda driver version: 11.5
   0m [2021-10-25 10:49:06.093] Cuda runtime API version: 11.5
   0m [2021-10-25 10:49:06.093]
   0m [2021-10-25 10:49:06.093]
   0m [2021-10-25 10:49:06.093]
   0m [2021-10-25 10:49:06.093] Welcome to Team Black Miner 1.19
   0m [2021-10-25 10:49:06.093]
   0m [2021-10-25 10:49:06.093]
   0m [2021-10-25 10:49:06.200] GPU0 NVIDIA GeForce RTX 3090 25GB added to miner as Cuda device
   0m [2021-10-25 10:49:06.261] GPU1 NVIDIA GeForce RTX 3070 8GB added to miner as Cuda device
   0m [2021-10-25 10:49:06.291] Trying daggerhashimoto.usa-east.nicehash.com:3353 (ethash)
   0m [2021-10-25 10:49:06.334] Extranonce is set to 7028830390697590784
   0m [2021-10-25 10:49:06.334] Pool responded successfully to subscribe
   0m [2021-10-25 10:49:06.379] Pool responded successfully to extranonce subscribe
   0m [2021-10-25 10:49:06.395] Pool responded successfully to authorize
   0m [2021-10-25 10:49:06.411] Difficulty is set to 0.237865
   0m [2021-10-25 10:49:06.494] GPU0 Started Cuda work thread
   0m [2021-10-25 10:49:06.589] GPU1 Started Cuda work thread
   0m [2021-10-25 10:49:06.719] GPU0 All done.
   0m [2021-10-25 10:49:06.813] GPU1 All done.
Le processus ne peut pas accéder au fichier car ce fichier est utilisé par un autre processus. <- process is currently being used and cannot be used kinda means
   0m [2021-10-25 10:49:06.881] Cannot open nvidia-smi for gpu utilization information
   0m [2021-10-25 10:49:06.911] GPU0 All done.
Le processus ne peut pas accéder au fichier car ce fichier est utilisé par un autre processus. <- process is currently being used and cannot be used kinda means
   0m [2021-10-25 10:49:06.966] Cannot open nvidia-smi for gpu utilization information
   0m [2021-10-25 10:49:06.988] GPU0 All done.
   0m [2021-10-25 10:49:07.084] GPU1 All done.
   0m [2021-10-25 10:49:09.042] GPU1 Starting generating ethash dag (Epoch: 449)
   0m [2021-10-25 10:49:09.234] GPU0 Starting generating ethash dag (Epoch: 449)
   0m [2021-10-25 10:49:09.234] GPU1 DAG generated in 2.27 seconds (4726783kb)
   0m [2021-10-25 10:49:09.234] GPU1 Autoselect kernel activated
   0m [2021-10-25 10:49:09.234] GPU1 XIntensity set to 224
   0m [2021-10-25 10:49:09.405] GPU0 DAG generated in 2.32 seconds (4726783kb)
   0m [2021-10-25 10:49:09.405] GPU0 Autoselect kernel activated
   0m [2021-10-25 10:49:09.405] GPU0 XIntensity set to 224
   0m [2021-10-25 10:49:13.314] Job 00000000a2b5a244
   0m [2021-10-25 10:49:13.713] GPU0 Dag buffer verified ok!
   0m [2021-10-25 10:49:13.812] GPU0 GPU clocks set to "(gpuClkMin 1140, gpuClkMax 1140)" for GPU 00000000:04:00.0
   0m [2021-10-25 10:49:13.906] GPU1 GPU clocks set to "(gpuClkMin 1140, gpuClkMax 1140)" for GPU 00000000:07:00.0
   0m [2021-10-25 10:49:14.008] GPU0 Memory clocks set to "(memClkMin 10775, memClkMax 10775)" for GPU 00000000:04:00.0
   0m [2021-10-25 10:49:14.150] GPU1 Memory clocks set to "(memClkMin 8075, memClkMax 8075)" for GPU 00000000:07:00.0
   0m [2021-10-25 10:49:14.150] Job 00000000a2b5a245
   0m [2021-10-25 10:49:14.688] Job 00000000a2b5a246
   0m [2021-10-25 10:49:15.752] Job 00000000a2b5a247
   0m [2021-10-25 10:49:15.800] GPU1 Dag buffer verified ok!
   0m [2021-10-25 10:49:15.895] GPU0 GPU clocks set to "(gpuClkMin 1140, gpuClkMax 1140)" for GPU 00000000:04:00.0
   0m [2021-10-25 10:49:15.930] GPU0 speed 0:98.18 1:99.74 2:99.95 3:100.00 4:99.94 5:99.93 6:99.99 7:99.90 8:99.97
   0m [2021-10-25 10:49:15.930] GPU0 using gpu kernel 3
   0m [2021-10-25 10:49:16.197] GPU1 GPU clocks set to "(gpuClkMin 1140, gpuClkMax 1140)" for GPU 00000000:07:00.0
   0m [2021-10-25 10:49:16.308] GPU0 Memory clocks set to "(memClkMin 10775, memClkMax 10775)" for GPU 00000000:04:00.0
   0m [2021-10-25 10:49:16.402] GPU1 Memory clocks set to "(memClkMin 8075, memClkMax 8075)" for GPU 00000000:07:00.0
   0m [2021-10-25 10:49:16.816] Job 00000000a2b5a248
   0m [2021-10-25 10:49:17.702] Job 00000000a2b5a249
   0m [2021-10-25 10:49:18.595] GPU1 speed 0:98.30 1:99.13 2:100.00 3:92.92 4:91.19 5:99.20 6:93.88 7:86.45 8:89.72
   (...)
   1m [2021-10-25 10:50:07.221]
   1m [2021-10-25 10:50:07.221] usa-east.nicehash.com (ethash) PING: 66ms DIFFICULTY: 0.238 EPOCH: 449
   1m [2021-10-25 10:50:07.221]
   1m [2021-10-25 10:50:07.221]
   1m [2021-10-25 10:50:07.221] ID BOARD TYPE KERN XINT TEMP FAN CORE MEM WATT
   1m [2021-10-25 10:50:07.221] GPU0 3090 Cuda 3 224 55/0 30 1139 9492 253
   1m [2021-10-25 10:50:07.221] GPU1 3070 Cuda 2 224 60/0 46 1139 6794 103
   1m [2021-10-25 10:50:07.221] 356
   1m [2021-10-25 10:50:07.221]
   1m [2021-10-25 10:50:07.221] ID BOARD HASHRATE/W HASHRATE AVERAGE SHARES
   1m [2021-10-25 10:50:07.221] GPU0 3090 445.69 kH/W 112.76 MH/s 112.68 MH/s 4/0/1 (100.00)
   1m [2021-10-25 10:50:07.221] GPU1 3070 510.86 kH/W 52.62 MH/s 52.22 MH/s 2/0/0 (100.00)
   1m [2021-10-25 10:50:07.221] 478.27 kH/W 165.38 MH/s 164.90 MH/s 6/0/1 (100.00)
   1m [2021-10-25 10:50:07.221]
   1m [2021-10-25 10:50:07.221] SHARES PER MINUTE: 6.00 POOL HASHRATE: 102.16 MH/s
   1m [2021-10-25 10:50:07.221]
   1m [2021-10-25 10:50:07.804] GPU0 Solution found in 0.94s (Submit every 8.83 seconds)
   1m [2021-10-25 10:50:07.892] Job 00000000a2b5a288
   1m [2021-10-25 10:50:07.917] Accepted (7/7/1) Reply: 112ms
   1m [2021-10-25 10:50:08.956] Job 00000000a2b5a289
   1m [2021-10-25 10:50:10.020] Job 00000000a2b5a28b
   1m [2021-10-25 10:50:10.906] Job 00000000a2b5a28c
   1m [2021-10-25 10:50:11.083] Job 00000000a2b5a28d
   1m [2021-10-25 10:50:11.615] Job 00000000a2b5a28e
   1m [2021-10-25 10:50:12.504] GPU0 Solution found in 0.04s (Submit every 8.31 seconds)
   1m [2021-10-25 10:50:12.504] Job 00000000a2b5a28f

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: hashatharias on October 25, 2021, 09:34:59 AM

NiceHash, it was working on 1.16 and 1.18

Working, but the value is not accurate. We need each share to have the samme difficulty in order to calculate the poolside hashrate. With vardiff it's a different calculation. since some shares are worth more, and some are worth less. Over time it might be correct though.. Perhaps we should enable it with a (VARDIFF) in brackets.

hashatharias

newbie

Activity: 12

Merit: 0

Quote from: ?? on ??

Quote from: hashatharias on October 24, 2021, 07:42:51 PM

Weird thing with 1.19

Code:

21m [2021-10-24 21:02:47.279] POOL HASHRATE: VARDIFF

While the value was at like 2000 when I started the miner, then it switched to VARDIFF

We don't support calculating the Pool hashrate if the pool is changing difficulty while you mine. This can be implemented later, but require some more work. Which pool is this?

NiceHash, it was working on 1.16 and 1.18

mikeonepu

newbie

Activity: 5

Merit: 0

@sp_ I tried but still the same result no AMD mining

KillrBee

jr. member

Activity: 139

Merit: 3

Quote from: poisons77 on October 25, 2021, 08:30:06 AM

I'm still not able to make TBlackMiner work. I've installed the 1.19 from HiveOs, and this is the screenshot of the Miner console.
As you can see is printing multiple time per second the hashrate of each GPU, and still 3 GPU are not recognized. Then they go in timeout and exit, the system freezes, I've to phisically reboot.

All are RX 580. I've no problem with other miners.

Are you manually setting your Xintensity? Because 0 (zero) should never be a number you see there.

The only thing I can think of is that your AMD drivers are out of date and the driver isn't registering properly with the miner. I'm not running Rx580s so there isn't much direct help I can provide, I just run a bunch of RDNA2 RX6[8/9]00 with HiveOS AMD drivers - A20.40 (5.11.0701)...

maybe try manually setting {--xintensity -1 --kernel 1} in the extra config arguments section of the miner setup to see if those numbers in the console change..?

sxemini

member

Activity: 1558

Merit: 69

@sp_

Please take a look why zil.rustpool.xyz not working. It is online and i am mining with 14 Rigs over this zil pool, all other miner work, only TBM will not connect.

poisons77

newbie

Activity: 14

Merit: 0

I'm still not able to make TBlackMiner work. I've installed the 1.19 from HiveOs, and this is the screenshot of the Miner console.
As you can see is printing multiple time per second the hashrate of each GPU, and still 3 GPU are not recognized. Then they go in timeout and exit, the system freezes, I've to phisically reboot.

All are RX 580. I've no problem with other miners.

https://ibb.co/9VqVY65

KillrBee

jr. member

Activity: 139

Merit: 3

Quote from: ?? on ??

Quote from: KillrBee on October 24, 2021, 09:53:33 PM

I can never get my 3090 to lock the MemClock -- nvidia-smi will say it's changed the clock, but it doesn't change anything (same with setting the fan speed through the nvidia-smi). Core clock will change, but that's it. I just add the nvidiaInspector overclocking shortcut I have into the batch file and it will run the proper memory clock from there.

We support setting the memclock too whatever the nvidia-smi tool support. This might not be as high as msi afterburner. Type this to see the supported clocks

$ nvidia-smi --query-supported-clocks=memory --format=csv
memory [MHz]
7001 MHz
6801 MHz
5001 MHz
810 MHz
405 MHz

Yeah, which are the default power state levels, so you can't overclock the memory at all with nvidia-smi (3090 - P0 = 9751MHz; which about 15-1600MHz below where my O.C. is). Calling the NvidiaInspector from batch works fine (as long as you're administrator, and I use Powershell, so specifically you need to call powershell c:\...\nvidiaInspector.exe --flags, or the .lnk before running TBMiner.

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: exotik997 on October 25, 2021, 07:06:27 AM

Hello, ty for ur work.
Now testing this miner on hiveos on my 2 rigs with 2060s and found some kind of bug which u can see on my screenshot.

Thanks for testing. we will add a ticket on github and fix this.

Quote from: exotik997 on October 25, 2021, 07:06:27 AM

TBM can't recognize my 580 and 590 and mining start only on 5700xt. Last release of hiveos with TBM 1.19.

The 580 is working fine on windows, perhaps this is a driver issue? not sure

Quote from: exotik997 on October 25, 2021, 07:06:27 AM

What about calculating pool hashrate? Is it accurate with hiveon pool? As far as I know its a vardiff pool and u said earlier TBM wouldn't calculate pool hashrate on vardiff pools, but I see the calculation.

It is calculated as long as the difficulty hasn't changed. When/if the difficulty change the pool hashrate will be switched to VARDIFF.

Quote from: exotik997 on October 25, 2021, 07:06:27 AM

If someone is interested here is my configuration. Xint 512. Looking for some advices to improve my results.
https://ibb.co/GFcr26s

Increasing beyond 512 can produce more stale shares on the pool. Hiveon pay 85% for stale shares, so it shouldn't matter. 768 has been reported giving good results. You can try that.

exotik997

newbie

Activity: 2

Merit: 0

Quote from: ?? on ??

hiveos has added Team Black Miner v1.19. check it out

Hello, ty for ur work.
Now testing this miner on hiveos on my 2 rigs with 2060s and found some kind of bug which u can see on my screenshot.
https://ibb.co/fFRddz7
Both of my rigs have this issue. Also I can't start mining on one of my rigs with 5700xt and rx580 together. TBM can't recognize my 580 and 590 and mining start only on 5700xt. Last release of hiveos with TBM 1.19.

What about calculating pool hashrate? Is it accurate with hiveon pool? As far as I know its a vardiff pool and u said earlier TBM wouldn't calculate pool hashrate on vardiff pools, but I see the calculation.

If someone is interested here is my configuration. Xint 512. Looking for some advices to improve my results.
https://ibb.co/GFcr26s

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

make sure that --auto-detect in not specified. Add --cl-devices first in the list, and then --cuda-devices

Or use 2 instances of the miner.

Hiveos has added Team Black Miner v1.19. check it out.

https://hiveos.farm/changelog/?type=All&page=1

[moderator's note: consecutive posts merged]

mikeonepu

newbie

Activity: 5

Merit: 0

I am trying to disable TBM on my LHR card because the result are not as good as with other miner.
However when I disable GPU 0,4 it give me this error.
Tried to use --cuda-devices [1,2,3,5] --cl-devices [6,7] it works for disabling the GPU's 0 and 4 but will not mine with AMD GPU like it does not even take the "--cl-devices" argument.

I don't know how I can solve this can you maybe help on this one ?

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

are you using --opencl-devices [0,1]

linux 1.19 build has been re-uploaded with some more fixes for amd cards

[moderator's note: consecutive posts merged]

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