Pages:
Author

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

newbie
Activity: 28
Merit: 0
v1.40

1. Fix build issue on AMD rigs.
2. Tiny improvement in the cuda kernel.


It's work,  Wink
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
terminate called after throwing an instance of 'cl::BuildError'                                                                                                         
  what():  clBuildProgram                                                                                                                                                                                                                 

I have fixed it. Will release 1.40 later today.

v1.40

1. Fix build issue on AMD rigs.
2. Tiny improvement in the cuda kernel.

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

TeamBlackMiner_1_40_cuda_11_5.7z
https://www.virustotal.com/gui/file/643125624bfadf450b2dcfcb1691f7b88095b91371bc48ce90a6bb6ee40c5170?nocache=1

TeamBlackMiner_1_40_cuda_11_3.7z
https://www.virustotal.com/gui/file/9146ff9d966b3af27d1a92848be5091d1d36d1ed0e5c397545d6b064e5098577?nocache=1

TeamBlackMiner_1_40_Ubuntu_18_04_Cuda_11_5.tar.xz
https://www.virustotal.com/gui/file/d4fb8c7c50c332fd86ee96d54c9b11b0c684b2cec4f51ef1d8283079cba2b13a?nocache=1
newbie
Activity: 30
Merit: 0
Has anyone been able to get AMD 6-series cards running under HiveOS with the latest 1.38 version?  

I will build a ubuntu 18.04 cuda 11.5 binary of 1.39. Should work fine on HiveOS.

edit:

TeamBlackMiner_1_39_Ubuntu_18_04_Cuda_11_5.tar.xz
https://www.virustotal.com/gui/file/30eba90d3a51a18891e0b67cf089179ad643e93b62e38851e860bcc220c89c13


I'm still unable to get my AMD cards to run with the build:



Same here, it seems a build problem:

terminate called after throwing an instance of 'cl::BuildError'                                                                                                         
  what():  clBuildProgram                                                                                                                                                                                                                                                                                                                       
teamblackminer exited (exitcode=0), waiting to cooldown a bit
newbie
Activity: 28
Merit: 0
xintensity to 1 / ETC algo, all the same.

Don't set --xintensity 1 , use --dagintensity 1



OK, I tested the --dagintensity 1, It's still.
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
xintensity to 1 / ETC algo, all the same.

Don't set --xintensity 1 , use --dagintensity 1

newbie
Activity: 28
Merit: 0
I am back.
This time I have tried the 1.39, and got this:

00:00:00 [2022-01-15 18:26:54.937]
00:00:00 [2022-01-15 18:26:55.195] OpenCL driver version: 335.0
00:00:00 [2022-01-15 18:26:55.195] Cuda driver version: 0.0
00:00:00 [2022-01-15 18:26:55.195] Cuda runtime API version: 11.6
00:00:00 [2022-01-15 18:26:55.195]
00:00:00 [2022-01-15 18:26:55.195]
00:00:00 [2022-01-15 18:26:55.195]
00:00:00 [2022-01-15 18:26:55.195] Welcome to Team Black Miner 1.39
00:00:00 [2022-01-15 18:26:55.195]
00:00:00 [2022-01-15 18:26:55.195]
00:00:00 [2022-01-15 18:26:55.195] GPU0 gfx1032 8GB added to miner as OpenCL device
00:00:00 [2022-01-15 18:26:55.195] GPU1 gfx1032 8GB added to miner as OpenCL device
00:00:00 [2022-01-15 18:26:55.195] GPU2 gfx1032 8GB added to miner as OpenCL device
00:00:00 [2022-01-15 18:26:55.195] Trying eth-hk.flexpool.io:4444 (ethash)
00:00:00 [2022-01-15 18:26:55.218] GPU0 Started CL work thread
00:00:00 [2022-01-15 18:26:55.233] GPU1 Started CL work thread
00:00:00 [2022-01-15 18:26:55.249] GPU2 Started CL work thread
00:00:00 [2022-01-15 18:26:55.272] Pool responded successfully to subscribe
00:00:00 [2022-01-15 18:26:55.296] Pool responded successfully to extranonce subscribe
00:00:00 [2022-01-15 18:26:55.311] Pool responded successfully to authorize
00:00:00 [2022-01-15 18:26:55.311] Difficulty is set to 0.931308
00:00:00 [2022-01-15 18:26:55.326] GPU0 Starting generating ethash dag (Epoch: 466)
00:00:00 [2022-01-15 18:26:55.326] GPU1 Starting generating ethash dag (Epoch: 466)
00:00:00 [2022-01-15 18:26:55.326] GPU2 Starting generating ethash dag (Epoch: 466)

00:00:00 [2022-01-15 18:26:58.657] Shutting down threads
00:00:00 [2022-01-15 18:26:58.665] Control thread exited
00:00:00 [2022-01-15 18:26:58.665] Stratum thread exited


xintensity to 1 / ETC algo, all the same.


BTW,

1. The rig has a little different from last one, it's 3 card RX 6600 with another MB, AMD Driver: 21.12.1

2. log file was created, but empty (0 size)

3. sometimes can start up correctly, it's randomly in rare.






jr. member
Activity: 139
Merit: 3
Has anyone been able to get AMD 6-series cards running under HiveOS with the latest 1.38 version?  

I will build a ubuntu 18.04 cuda 11.5 binary of 1.39. Should work fine on HiveOS.

edit:

TeamBlackMiner_1_39_Ubuntu_18_04_Cuda_11_5.tar.xz
https://www.virustotal.com/gui/file/30eba90d3a51a18891e0b67cf089179ad643e93b62e38851e860bcc220c89c13


I'm still unable to get my AMD cards to run with the build:

00:00:00 [2022-01-14 14:21:24.811]                                                                                
00:00:00 [2022-01-14 14:21:32.117] OpenCL driver version: 495.46
00:00:00 [2022-01-14 14:21:37.830] Cuda driver version: 11.5
00:00:00 [2022-01-14 14:21:37.830] Cuda runtime API version: 11.5
00:00:00 [2022-01-14 14:21:37.830]
00:00:00 [2022-01-14 14:21:37.830]                                
00:00:00 [2022-01-14 14:21:37.830]
00:00:00 [2022-01-14 14:21:37.830] Welcome to Team Black Miner 1.39
00:00:00 [2022-01-14 14:21:37.830]                                
00:00:00 [2022-01-14 14:21:37.830]
00:00:00 [2022-01-14 14:21:37.830] GPU0 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-01-14 14:21:37.830] GPU1 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-01-14 14:21:37.830] GPU2 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-01-14 14:21:37.830] GPU3 gfx1030 17GB added to miner as OpenCL device
00:00:00 [2022-01-14 14:21:39.372] GPU4 NVIDIA GeForce RTX 2060 SUPER 8GB added to miner as Cuda device
00:00:00 [2022-01-14 14:21:39.372] Trying us-eth.2miners.com:2020 (ethash)
00:00:00 [2022-01-14 14:21:39.374] GPU0 Started CL work thread
00:00:00 [2022-01-14 14:21:39.375] GPU1 Started CL work thread
00:00:00 [2022-01-14 14:21:39.376] GPU2 Started CL work thread
00:00:00 [2022-01-14 14:21:39.377] GPU3 Started CL work thread
00:00:00 [2022-01-14 14:21:39.420] GPU4 Started Cuda work thread
00:00:00 [2022-01-14 14:21:39.505] Pool responded successfully to subscribe
00:00:00 [2022-01-14 14:21:39.546] Pool responded successfully to extranonce subscribe
00:00:00 [2022-01-14 14:21:39.546] Extranonce is set to 18376093854555176960
00:00:00 [2022-01-14 14:21:39.588] Pool responded successfully to authorize
00:00:00 [2022-01-14 14:21:39.590] Difficulty is set to 2.031715
00:00:00 [2022-01-14 14:21:39.591] GPU3 Starting generating ethash dag (Epoch: 466)
00:00:00 [2022-01-14 14:21:39.591] GPU0 Starting generating ethash dag (Epoch: 466)
00:00:00 [2022-01-14 14:21:39.591] GPU2 Starting generating ethash dag (Epoch: 466)
00:00:00 [2022-01-14 14:21:39.591] GPU1 Starting generating ethash dag (Epoch: 466)
00:00:00 [2022-01-14 14:21:40.895] GPU4 Starting generating ethash dag (Epoch: 466)
00:00:00 [2022-01-14 14:21:40.898] GPU4 DAG generated in 1.31 seconds (4866046kb)
00:00:00 [2022-01-14 14:21:40.898] GPU4 Autoselect kernel activated
00:00:00 [2022-01-14 14:21:40.898] GPU4 XIntensity set to 952
terminate called after throwing an instance of 'cl::BuildError'
  what():  clBuildProgram
Aborted


with just the Nvidia cards (-G):

00:00:00 [2022-01-14 14:26:38.133]                                                                                 
00:00:00 [2022-01-14 14:26:38.192] Cuda driver version: 11.5
00:00:00 [2022-01-14 14:26:38.192] Cuda runtime API version: 11.5
00:00:00 [2022-01-14 14:26:38.192]
00:00:00 [2022-01-14 14:26:38.192]                                 
00:00:00 [2022-01-14 14:26:38.192]
00:00:00 [2022-01-14 14:26:38.192] Welcome to Team Black Miner 1.39
00:00:00 [2022-01-14 14:26:38.192]                                 
00:00:00 [2022-01-14 14:26:38.192]
00:00:00 [2022-01-14 14:26:38.192] Using all Nvidia devices
00:00:00 [2022-01-14 14:26:38.354] GPU0 NVIDIA GeForce RTX 3090 25GB added to miner as Cuda device
00:00:00 [2022-01-14 14:26:38.415] GPU1 NVIDIA GeForce RTX 2060 SUPER 8GB added to miner as Cuda device
00:00:00 [2022-01-14 14:26:38.415] Trying us-eth.2miners.com:2020 (ethash)
00:00:00 [2022-01-14 14:26:38.496] Pool responded successfully to subscribe
00:00:00 [2022-01-14 14:26:38.533] Pool responded successfully to extranonce subscribe
00:00:00 [2022-01-14 14:26:38.533] Extranonce is set to 18401708077435846656
00:00:00 [2022-01-14 14:26:38.570] Pool responded successfully to authorize
00:00:00 [2022-01-14 14:26:38.571] Difficulty is set to 2.031715
00:00:00 [2022-01-14 14:26:38.583] GPU0 Started Cuda work thread
00:00:00 [2022-01-14 14:26:38.644] GPU1 Started Cuda work thread
00:00:00 [2022-01-14 14:26:40.818] GPU1 Starting generating ethash dag (Epoch: 466)
00:00:00 [2022-01-14 14:26:40.996] GPU1 DAG generated in 1.59 seconds (4866046kb)
00:00:00 [2022-01-14 14:26:40.996] GPU1 Autoselect kernel activated
00:00:00 [2022-01-14 14:26:40.996] GPU1 XIntensity set to 952
00:00:00 [2022-01-14 14:26:41.001] GPU0 Starting generating ethash dag (Epoch: 466)
00:00:00 [2022-01-14 14:26:41.001] GPU0 DAG generated in 1.60 seconds (4866046kb)
00:00:00 [2022-01-14 14:26:41.001] GPU0 Autoselect kernel activated
00:00:00 [2022-01-14 14:26:41.001] GPU0 XIntensity set to 952
00:00:00 [2022-01-14 14:26:41.001] Job ccb53 (Validating Dag..)
00:00:00 [2022-01-14 14:26:45.265] Job ccb55 (Validating Dag..)
00:00:00 [2022-01-14 14:26:46.042] GPU0 Dag buffer verified ok!
00:00:00 [2022-01-14 14:26:51.774] GPU1 Dag buffer verified ok!
00:00:00 [2022-01-14 14:26:51.906] Job ccb57 (Autotuning..)
00:00:00 [2022-01-14 14:26:54.473] Job ccb58 (Autotuning..)
00:00:00 [2022-01-14 14:26:54.839] Job ccb59 (Autotuning..)
^C
00:00:00 [2022-01-14 14:26:57.711] Shutting down threads
00:00:00 [2022-01-14 14:26:57.711] Stratum thread exited
newbie
Activity: 30
Merit: 0
v1.39
1. Improved Stale checker/estimates AMD
2. Fix reject bug on ethproxy pools.
3. Fix ETH+ZIL on LHR rigs.

Tests show that 1.39 has around +2.5% poolside speed hiveon.net and ezil.me after 5000 accepted shares.


Thank you sp_ for your effort, I always liked TBM but I had rejected shares issues in Hiveon pool despite the past versions improvements so looking forward to test this new kernel. I'm also very curious to test profitability/share rate compared to other popular miners with a full AMD rig, in my tests despite the higher hashrate it wasn't the best performer
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
Has anyone been able to get AMD 6-series cards running under HiveOS with the latest 1.38 version?  

I will build a ubuntu 18.04 cuda 11.5 binary of 1.39. Should work fine on HiveOS.

edit:

TeamBlackMiner_1_39_Ubuntu_18_04_Cuda_11_5.tar.xz
https://www.virustotal.com/gui/file/30eba90d3a51a18891e0b67cf089179ad643e93b62e38851e860bcc220c89c13
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
jr. member
Activity: 139
Merit: 3
Has anyone been able to get AMD 6-series cards running under HiveOS with the latest 1.38 version?  

I really don't want to have to switch my main mining rig back to windows in order to get the upgrade (which I'm running in windows on my 6900XT rig and getting a 24 hour average of 65-70 MH/s on, while getting 62-63 MH/s for my 6800 series cards on HiveOS v. 1.27 (which is the only version that is stable enough to run for more than a few hours without pool timeouts)).

I'm currently getting the clBuild error from the AMD cards when running 1.38-115.  I can run 1.38-115 with just my Nvidia cards by installing the 495.xx drivers in HiveOS, but those drivers and the Xorg / nvidia-settings don't seem to play well with the HiveOS kernel and at the very best, I have to manually run one instance of TBM since HiveOS won't allow two simultaneous instances the same miner (despite being different versions), so if the HiveOS instance of the driver resets, the watchdog restarts it, but HiveOS throws continuous launch errors and then I'm down 50% of my hash power until I see that the rig is only producing 50% (which doesn't work well when I'm sleeping and it fails).

So, ideally I would like to see the benefits of the new AMD kernel and use HiveOS to manage my rig, and if that's not an option, then I guess I will have to move back to windows and remote desktop -- which isn't an ideal situation.
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
one stupid question... it is possible to install in win10 the cuda 11.5 without install new driver 49x from nvidia?
my rig doesnt like anything over 472..

Yes it's possible to install cuda 11.5, but you cannot run cuda 11.5 programs without upgrading the driver.
jr. member
Activity: 42
Merit: 2

Hi sp_!
Finally with 1.38 my rig is ok!
one stupid question... it is possible to install in win10 the cuda 11.5 without install new driver 49x from nvidia?
my rig doesnt like anything over 472..

thanks
alex
newbie
Activity: 40
Merit: 0
Are you using the latest Mesa OpenCL libs for AMD cards in your latest build, or are you using the original bionic libs?  

If it's the newest Mesa drivers, then I think we're out of luck on HiveOS since Mesa ceased supporting Ubuntu version 18.04 LTS and is only publishing new libs for version 20.04 -> 21.04 LTS.  


EDIT:

Also, to at least get the correct GLIBCXX do the following:

sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt update
sudo apt install gcc-9
sudo apt install libstdc++6



if gcc-9 fail...


ADDING :

sudo apt install gcc-10 g++-10 -y

thencheck and confirm GLIBCXX

strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | grep GLIBCXX
jr. member
Activity: 139
Merit: 3
For 1.38, the 18.04 build is reporting lower hashrate than the 20.04 build, is this normal?

the ubuntu 18.04 build is cuda 11.4.

The team black miner is optimized for cuda 11.5

Ubuntu 18.04 (2016) is not going to be supported next year, and is selected by the other mining softwares. A 5 year old ubuntu distribution can easily be hacked..

you can update HiveOS to the Nvidia version 495.46 which has CUDA 11.5 by adding in the latest drivers by using:

sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt update
sudo apt upgrade
sudo apt install nvidia-driver-495
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
For 1.38, the 18.04 build is reporting lower hashrate than the 20.04 build, is this normal?

the ubuntu 18.04 build is cuda 11.4.

The team black miner is optimized for cuda 11.5

Ubuntu 18.04 (2016) is not going to be supported next year, and is selected by the other mining softwares.
newbie
Activity: 11
Merit: 0
For 1.38, the 18.04 build is reporting lower hashrate than the 20.04 build, is this normal?
jr. member
Activity: 139
Merit: 3
Are you using the latest Mesa OpenCL libs for AMD cards in your latest build, or are you using the original bionic libs?  

If it's the newest Mesa drivers, then I think we're out of luck on HiveOS since Mesa ceased supporting Ubuntu version 18.04 LTS and is only publishing new libs for version 20.04 -> 21.04 LTS.  


EDIT:

Also, to at least get the correct GLIBCXX do the following:

sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt update
sudo apt install gcc-9
sudo apt install libstdc++6
newbie
Activity: 40
Merit: 0
check/confirm the necessary dependencies are installed
I will build 1.39 today with fixes for Ethproxy pools and 0 rejected shares.

https://i.ibb.co/khDPj1k/bug-problem.png

This bug has been there since version v1.00 Poolside rejects on hiveon.net and ezil.me and some other pools that use the ETHPROXY protocol.
In the later versions we have improved the reject rate abit, but I think v1.39 will remove them all together. A stratum problem solved on NVIDIA and AMD rigs.

Selecting the correct pool has been important when using TBM, but perhaps this will change after the bugfixed release is out.

please include Ubuntu_20_04 Cuda_11_5 and Ubuntu_20_04 Cuda_11_4 for your next release. thank you.
Pages:
Jump to: