Show Posts
|
Pages: [1]
|
Retuning can give you a higher hashrate on lower clocks. Perhaps you need to add 2watts of power per card. Some of your cards are working though. Is the 3 same cards crashing or is it random?
I'll test further
|
|
|
I tried the 1.22 both with --xintensity 60 and --dagintensity 1, still GPU are crashing and freezing the system
Perhaps your clocks are too high, or the power is too low to run this kernel on your computer. You might need to retune the rig to find the optimal settings for the Team Black Miner. Yes, my clocks are high, as well as the hashrate, I'll not lower them. All the other miners run smoothly
|
|
|
Additional step for AMD devices TBM uses AMD ADL library to read GPU information from AMD cards.
We have added two AMD libraries to make this step a little easier.
This step is not neccesary if you already have the libraries.
The miner can work without them but then without statistics for AMD GPU cards.
Copy the shared objects (.so) to the systems library path:
sudo cp libatiadlxx.so /usr/lib/ sudo cp libatiuki.so.1 /usr/lib/
After doing this I get this error: modprobe: FATAL: Module fglrx not found in directory /lib/modules/5.4.0-hiveos Error! Fail to load fglrx kernel module! Maybe you can switch to root user to load kernel module directly If I remove the 2 files from /usr/lib it works with no error, but also with no stats
3 of your gpus crashed when creating the dag and didn't start. Try v1.22 with --dagintensity 1
I tried the 1.22 both with --xintensity 60 and --dagintensity 1, still GPU are crashing and freezing the system [moderator's note: consecutive posts merged]
|
|
|
--xintensity 60 works good on the 580
I tried again and it Failed. Key points: - All the stats are 0 - 3 on 9 GPU are all 0, even if they are recognized - for these 3 GPU I received the message of start generating dag, but no other message (dag generated, verified, kernel selected and xintensity set) - there's a recurring error/warning "Cannot open shared object file" - after the threads exited, the system freezes and I've to maually reboot - the average hashrates are lower than teamredminer but probably because of few minutes mining, it's not enough. I use HiveOs last version with TeamBlackMiner 1.21, 2miners pool, --xintensity 60, 9x AMD 580 Nitro Everything works fine with teamredminer, same configs Here the screenshots: 00:00:35 [2021-10-31 08:52:08.028] Cannot open shared object file 00:00:35 [2021-10-31 08:52:08.028] 00:00:35 [2021-10-31 08:52:08.028] 00:00:35 [2021-10-31 08:52:08.028] asia-eth.2miners.com (ethash) PING: 50ms DIFFICULTY: 2.03 EPOCH: 450 00:00:35 [2021-10-31 08:52:08.028] 00:00:35 [2021-10-31 08:52:08.028] 00:00:35 [2021-10-31 08:52:08.028] ID BOARD TYPE KERN XINT TEMP FAN CORE MEM WATT 00:00:35 [2021-10-31 08:52:08.028] GPU0 Ellesme OpenCL 0 60 0/0 0 0 0 0 00:00:35 [2021-10-31 08:52:08.028] GPU1 Ellesme OpenCL 0 60 0/0 0 0 0 0 00:00:35 [2021-10-31 08:52:08.028] GPU2 Ellesme OpenCL 0 60 0/0 0 0 0 0 00:00:35 [2021-10-31 08:52:08.028] GPU3 Ellesme OpenCL 0 60 0/0 0 0 0 0 00:00:35 [2021-10-31 08:52:08.028] GPU4 Ellesme OpenCL 0 60 0/0 0 0 0 0 00:00:35 [2021-10-31 08:52:08.028] GPU5 Ellesme OpenCL 0 60 0/0 0 0 0 0 00:00:35 [2021-10-31 08:52:08.028] GPU6 Ellesme OpenCL 0 60 0/0 0 0 0 0 00:00:35 [2021-10-31 08:52:08.028] GPU7 Ellesme OpenCL 0 60 0/0 0 0 0 0 00:00:35 [2021-10-31 08:52:08.028] GPU8 Ellesme OpenCL 0 60 0/0 0 0 0 0 00:00:35 [2021-10-31 08:52:08.028] 0 00:00:35 [2021-10-31 08:52:08.028] 00:00:35 [2021-10-31 08:52:08.028] ID BOARD HASHRATE/W HASHRATE AVERAGE SHARES 00:00:35 [2021-10-31 08:52:08.028] GPU0 Ellesme 0.00 H/W 33.59 MH/s 33.25 MH/s 1/0/0 (100.00%) 00:00:35 [2021-10-31 08:52:08.029] GPU1 Ellesme 0.00 H/W 33.73 MH/s 32.73 MH/s 2/0/0 (100.00%) 00:00:35 [2021-10-31 08:52:08.029] GPU2 Ellesme 0.00 H/W 30.22 MH/s 29.90 MH/s 2/0/0 (100.00%) 00:00:35 [2021-10-31 08:52:08.029] GPU3 Ellesme 0.00 H/W 0.00 H/s 0.00 H/s 0/0/0 (100.00%) 00:00:35 [2021-10-31 08:52:08.029] GPU4 Ellesme 0.00 H/W 0.00 H/s 0.00 H/s 0/0/0 (100.00%) 00:00:35 [2021-10-31 08:52:08.029] GPU5 Ellesme 0.00 H/W 41.97 MH/s 32.51 MH/s 0/0/0 (100.00%) 00:00:35 [2021-10-31 08:52:08.029] GPU6 Ellesme 0.00 H/W 0.00 H/s 0.00 H/s 0/0/0 (100.00%) 00:00:35 [2021-10-31 08:52:08.029] GPU7 Ellesme 0.00 H/W 32.27 MH/s 32.33 MH/s 0/0/0 (100.00%) 00:00:35 [2021-10-31 08:52:08.029] GPU8 Ellesme 0.00 H/W 29.81 MH/s 29.54 MH/s 0/0/0 (100.00%) 00:00:35 [2021-10-31 08:52:08.029] 0.00 H/W 201.58 MH/s 190.26 MH/s 5/0/0 (100.00%) 00:00:35 [2021-10-31 08:52:08.029] 00:00:35 [2021-10-31 08:52:08.029] SHARES PER MINUTE: 1.00 POOL HASHRATE: 145.44 MH/s
|
|
|
Ok, I want to retry but I'm a bit confused. My configuration is 9x580, on HiveOs, Amd driver 20.40 (5.9.0325)
What is the best configuration for my rig? Till 1.19 it always failed, but before retrying would like to start with the best configuration options
Thanks
|
|
|
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.
|
|
|
try --cl-devices [0,1,2,3,4,5,6,7] instead of --auto-detect . Don't use both options at the same time.
I just use the --cl-devices command in the "extra config arguments" on HiveOs, and it automatically don't use the --auto-detect?
|
|
|
No the 3gb is from the opencl call to determine the size of your card. Could be related to a wrong gpu platform, or a driver installation gone wrong. You should do a driver uninstall with wipe and do a reinstall.
Well, if I stop the miner and run the --list-devices command, all the devices are read again with 8gb, so it is the "free memory" what you see from the tbminer --list-devices command, not the hardware memory
|
|
|
Seems to be a driver problem. Weird, never seen this before..
Maybe because of the DAG generation fails? It makes sense if the memory remain "occupied" by the failed DAG generated. 8gb - DAG size, then rounded is 3gb as I see in the list. This can also explain why I can fix only when I reboot the rig Maybe I can open an issue on github?
|
|
|
try
tbminer --list-devices
what do you get?
Available Cuda devices ----------------------- Available OpenCL devices ------------------------- Device Number: 0 Device name: Ellesmere PCIe bus id: 1 Memory: 3GB Device Number: 1 Device name: Ellesmere PCIe bus id: 2 Memory: 3GB Device Number: 2 Device name: Ellesmere PCIe bus id: 3 Memory: 3GB Device Number: 3 Device name: Ellesmere PCIe bus id: 4 Memory: 3GB Device Number: 4 Device name: Ellesmere PCIe bus id: 8 Memory: 3GB Device Number: 5 Device name: Ellesmere PCIe bus id: 11 Memory: 3GB Device Number: 6 Device name: Ellesmere PCIe bus id: 12 Memory: 3GB Device Number: 7 Device name: Ellesmere PCIe bus id: 13 Memory: 3GB Device Number: 8 Device name: Ellesmere PCIe bus id: 14 Memory: 3GB
|
|
|
Even with 1.19 I've problems. Some cards are recognized only 3gb. I've all 580 8gb here's the screenshot https://ibb.co/jzmTGWQ
|
|
|
v1.16 has a overflow bug if the intensity is too high dynamic -1 for AMD. This bug was fixed in v1.18. The fix is to set --xintensity 78 or similar, or upgrade to v1.18.
v1.19 ready soon. Testing now..
I upgraded to 1.18 as you can see in the screenshot, but still getting the error for the DAG file verification. The difference with the 1.16 in my case is that before the DAG verification was the only error. Now with the 1.18 after getting the DAG verification error, when I restart the miner 2 cards get recognized only 3GB on 8. Restarting the miner didn't work, neither with a different miner, I had to restart the rig to make another miner working again. Can it be because I'm CPU mining with cpuminer-opt?
|
|
|
I still have problems. After exiting the first time because of a Dag file not verified, I restarted the miner and I got another error, it sees only 3GB of memory on 2 GPU. Restarting the miner didn't solve the problem, I could fix only rebooting the rig. I use TBM 1.18 on HiveOs latest version. I also use CPU mining with cpuminer-opt-gr here's the screenshot https://ibb.co/mXyvnXJ
|
|
|
if this doesn't work, do this (right click in Shell-in-a-box, paste from browser, then hit Return key to validate the command) cd /hive/miners/teamblackminer/1.16/ mv TBMiner TBMiner.bak wget https://github.com/sp-hash/TeamBlackMiner/releases/download/v1.18/TeamBlackMiner_1_18_Ubuntu_18_04_Cuda_11_4.zip unzip TeamBlackMiner_1_18_Ubuntu_18_04_Cuda_11_4.zip cp /hive/miners/teamblackminer/1.16/TeamBlackMiner_1_18_Ubuntu_18_04_Cuda_11_4/TBMiner /hive/miners/teamblackminer/1.16/ chmod +x TBMiner Then restart miner in HiveOS Thanks for your time, it worked flawlessy
|
|
|
Use fileZilla upload new version TBMiner and upload news version in dir: /hive/miners/teamblackminer/1.16/ and if you ask to overwrite with a new version you say => yes while waiting for them to update their mirror sometimes they are fast other times not .. Thanks dedizonesv2, I'll give it a try
|
|
|
When for any reason the miner exits, HiveOs stucks on the message: "trying to release TIME_WAIT sockets" Using HiveOs last version and TeamBlackMiner 1.16 (last version available on HiveOs) It happened already twice, once exited because one card was stuck at 0, and once as the screenshot below, one GPU dag verification failed.
|
|
|
There is a problem with the SSL connection. We are working on it. Use the normal ports
If I use the normal port, I get the following error: "SSL connect error" you can see from the screenshot here's the teamblackminer error and here's the configuration tab on HiveOs
|
|
|
I cannoct connect to any pool, I tried 2miners and crazypool, so I assume it is a general problem. I've hiveOs last version and tried with teamblackminer 1.16, latest version available for HiveOs. I get an "incorrect login" if I use the SSL url, and a weird "SSL connect error" if I use the normal url. I set the worker name manually, all lower case and no space I've no problem wth teamredminer and binance pool.
|
|
|
|