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

Untar the file in a new directory and see which files are in the original directory to compare. If something is missing you know straight away.
Being an old IT person I have always compared files first before overwriting just in case having missed something. Use ls -la so you also see hidden files.

I have Latest Drivers installed :

N 470.74
Drivers

The only thing done, is that I manually replaced 1.19 to 1.20 by using commands in bash. may be something went wrong or I miss to do something while replacing 1.19 ?

---

this is the latest available on HiveOS, used : nvidia-driver-update --list and it was latest one in the list

[moderator's note: consecutive posts merged]

Upgrade the driver to the latest

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

Stil might be the same bug and HiveOS not having the latest Nvidia and/or AMD drivers updated yet?

I am not mining to ethermine, I am mining @ 2miners pool. please check screenshot attached

https://i.imgur.com/CbHQS6V.png

GPU0  0GB added to miner as Cuda device

Something is wrong with your cuda driver because your card has 0GB memory. Download the latest driver (800mb) and install it. Make sure you inclide all the files and not only a few dll's.

---

There is a bug in 1.20 that if you use a worker on ethermine with high case letters, it wont show as reported hashrate. this has been fixed in v1.21. So the workaround is to rename all your workers to lowercase.

---

No, same problem on NVIDIA cards, our miner only works on the latest drivers and toolkit. The other miners work on older drivers, our optimized miner don't.

[moderator's note: consecutive posts merged]

I have manually updated HiveOS miner to 1.20, replaced miner in ver 1.19 Folder with the new one.

The issue I cant see now stats in HiveOS portal page, only see it in Shell (ssh), seems like HiveOS not getting data from miner (1.20)

any resolution for this issue ?

I'm not so sure. All other miners are working fine and detects RX580 and RX5700. If it was related to HiveOS, all others miners should also have the issue.

C:\Users\Administrator\Desktop\sandro\TeamBlackMiner_1_20_cuda_11_4>Set ETH_WALLET=0x8a1E0bE188865f239bC9866d08ae62d6Fa2b181D

C:\Users\Administrator\Desktop\sandro\TeamBlackMiner_1_20_cuda_11_4>TBMiner --algo ethash -U

• --no-ansi --xintensity 1 --wallet 0x8a1E0bE188865f239bC9866d08ae62d6Fa2b181D --hostname eth.pool.zet-tech.eu --port 8005

    0m [2021-10-27 21:57:52.053]
     0m [2021-10-27 21:57:52.259] OpenCL driver version: 23.20
     0m [2021-10-27 21:57:52.514] Cuda driver version: 11.4
     0m [2021-10-27 21:57:52.514] Cuda runtime API version: 11.4
     0m [2021-10-27 21:57:52.514]
     0m [2021-10-27 21:57:52.514]
     0m [2021-10-27 21:57:52.514]
     0m [2021-10-27 21:57:52.514] Welcome to Team Black Miner 1.20
     0m [2021-10-27 21:57:52.514]
     0m [2021-10-27 21:57:52.514]
     0m [2021-10-27 21:57:52.649] GPU0  0GB added to miner as Cuda device
     0m [2021-10-27 21:57:52.696] Trying eth.pool.zet-tech.eu:8005 (ethash)
     0m [2021-10-27 21:57:52.743] Pool responded successfully to subscribe
     0m [2021-10-27 21:57:52.837] GPU0 Started Cuda work thread

     0m [2021-10-27 21:57:58.492] GPU0 Starting generating ethash dag (Epoch: 450)
     0m [2021-10-27 21:57:58.492] GPU0 DAG generated in 3.52 seconds (4734972kb)
     0m [2021-10-27 21:57:58.492] GPU0 Autoselect kernel activated
     0m [2021-10-27 21:57:58.492] GPU0 XIntensity set to 1
     0m [2021-10-27 21:57:58.492] Shutting down threads
     0m [2021-10-27 21:57:58.507] Control thread exited
     0m [2021-10-27 21:57:58.507] Stratum thread exited
     0m [2021-10-27 21:58:02.514] Exiting

C:\Users\Administrator\Desktop\sandro\TeamBlackMiner_1_20_cuda_11_4>timeout 10

with TBM 1.20 finally i can make work at least one 1060..other one shutting down (i attach the log) and so my 9 nvidia p104..
:-(

Probobly you don't need to set the memclock with tbminer when you use a low --dagintensity. So only lock the coreclock.

You can test it.

---

yes. We are going to change the library we use for AMD stats.

[moderator's note: consecutive posts merged]

yep, tbm failed to put my settings back:

   172m [2021-10-27 17:42:42.081] ID   BOARD   TYPE   KERN   XINT   TEMP   FAN   CORE   MEM   WATT
   172m [2021-10-27 17:42:42.081] GPU0   3060   Cuda   8   336   51/0   63   1484   8402   104

   172m [2021-10-27 17:42:58.982] GPU0 All done.
   172m [2021-10-27 17:42:59.063] GPU0 All done.
   172m [2021-10-27 17:43:04.480] GPU0 Starting generating ethash dag (Epoch: 450)
   172m [2021-10-27 17:43:04.598] GPU0 DAG generated in 5.53 seconds (4734972kb)
   172m [2021-10-27 17:43:04.598] GPU0 kernel 8 selected

   173m [2021-10-27 17:43:43.099] ID   BOARD   TYPE   KERN   XINT   TEMP   FAN   CORE   MEM   WATT
   173m [2021-10-27 17:43:43.099] GPU0   3060   Cuda   8   336   62/0   63   1954   8402   160

Gotcha, thanks

---

FYI, it seems that there is still some bugs just on AMD command line logs (missing stats, wrong gpu names, etc.).



I guess you're aware of it.

[moderator's note: consecutive posts merged]

Is it possible to disable oc reset with --dagintensity?
Here tbm reseted oc settings, i think with epoch change, but did not put my settings back. Found it out just few minutes ago and i dont like it.

This is what i found in log:

start:
     0m [2021-10-24 21:46:08.306] GPU0 GPU clocks set to "(gpuClkMin 1485, gpuClkMax 1485)" for GPU 00000000:01:00.0
     0m [2021-10-24 21:46:08.388] GPU0 Memory clocks set to "(memClkMin 910, memClkMax 910)" for GPU 00000000:01:00.0

and this, but nothing about clocks change:
   172m [2021-10-27 17:42:58.912] Job 2d2a
   172m [2021-10-27 17:42:58.982] GPU0 All done.
   172m [2021-10-27 17:42:59.063] GPU0 All done.
   172m [2021-10-27 17:43:04.480] GPU0 Starting generating ethash dag (Epoch: 450)
   172m [2021-10-27 17:43:04.598] GPU0 DAG generated in 5.53 seconds (4734972kb)
   172m [2021-10-27 17:43:04.598] GPU0 kernel 8 selected
   172m [2021-10-27 17:43:16.657] Job 2d32

but no any information like at miner start, something like "GPU0 GPU clocks set to...", just GPU0 all done. Is it normal or not?

Since the verification code doesn't fail, you don't need to use this. But you could use to increase the memory clock and put --dagintensity 0. This option is for rtx 3060ti,3070,3080 with extreme clocks. But you seem to be happy with 102MHASH. Higher clocks higher power needed.

Thanks, I'll test these values.
What about --dagintensity ?

Default 224 for crazypool on nvidia. is 60 too much stales for the rx6000? 60 works good on the 580. 78 for the 6800

updated to ver 1.20
which xintensity do you suggest for Crazypool now?

At the moment I'm at 160 for RTX3000 cards and 32 for AMD RX6000 (if I put -1 I get too many stales)

No. We had a bug where we added hashrate while the program was verifying the dag file. Validating is much faster than searching, so perhaps this is the bug. I asked him to reproduce in v1.20, since he is running an older build. Could also be photoshop?

64 mhs on 1070Ti?! It's real?!

I believe this is a hiveos problem. In windows it hash at 33-34 MHASH at max clock hynix..102 watt..

---

The 11.5 build is more stable when applying memtweak (the pill) for gtx 1080ti, 1080.


[moderator's note: consecutive posts merged]