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

workaround use both:

--wallet user.name -worker_name name

i tried two variant before reporting and this is what i had and it did not work:

--wallet user --worker_name name
--wallet user.name

looks like there is something in the code, i do not use %% anywhere.

I've tried this morning with one of my rigs. (the one in the picture at my post 7:20). Worker and stats are showing fine.



But now I have added another rig, and it doesn't show. So there is an issue here. Will investegate.

edit:

Looks like the example .bat script is wrong. You need to correct to:

--wallet %USERNAME%.%computername% --worker_name %computername%

can any body share flight sheet compatible config for hiveos? thanks

1.03 cuda 11.2 - still missing from miningpoolhub. With trex it is on the list in ~5 min. So, it is still broken. That text is there for few days. I have 9 other rigs (trex) there and all statistics are updating every few minutes.

Yes, it's in the todo list

Good day,

Any chance to make your miner work with Miningrigrentals? TeamBlack miner says it is not supported.

Some pools pay the same for stale shares as normal shares. Ethereum has a 15 second block time, why does a pool spam you with jobs every 200ms. The Team Black miner is running 8% slower on low intensity settings. Selecting the right pool is important here.

---

Thanks for the test. Looking good. in v1.02 the stale share estimate count was not added yet.  We will release v1.03 today with improvements

---

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

TeamBlackMiner_1_03_cuda_11_2.7z
SHA-256   3154d4c34542a197e5e93b5db174b968353dd80f4751c1065341d0a2d31353b4

TeamBlackMiner_1_03_cuda_11_4.7z
SHA-256   4b2ff528171f5fb6fdf2d47376ea26be64434b52cd08ab1d17f1721232a07d35

TeamBlackMiner_1_03_Ubuntu_18_04_Cuda_11_4.zip
SHA-256   2b495b63431724dbc3122cabac8ec615107ae58779bf0f97e23508caf97baf60

v1.03
1. CPU verification of the Dag buffer (opencl/cuda)
2. Improved the stale share counter with a better estimation
3. Stale counter added to the opencl solver
4. Bumped the default xintensity to 64 (cuda)
5. Improved cuda 11.4 kernel tuning. abit faster
6. Improved DAG generation to be nicer to high oc.
7. Improved 11.4 kernel to accept higher oc.
8. Nicer on the dag generator to accept higher oc. (cuda)


[moderator's note: consecutive posts merged]

I remind you that it is surely useless to have 62Mh if the software does not do better than the others in sharing ...

It is the submitted and valid share number that will determine your income and not the hash power.

I asked hiveos to integrate it but as always with them without answer ... because there will be much more return and especially the possibility of adjusting more finely ... and therefore less stale.

teamred miner: 58.8
s-eth.2miners.com:2020 (ethash)   DIFFICULTY: 2.03     EPOCH: 440
(At least 2 shares/10 mins at each intensity)
'Stock' settings - 6800xt (2400 clock / 1990 mem)
Xintensity =  -1: 62.32
Xintensity =   1: 58.51 - 213W
Xintensity =  12: 61.10
Xintensity =  24: 61.94
Xintensity =  36: 62.03
Xintensity =  48: 62.11
Xintensity =  78: 62.15
Xintensity = 128: 62.33
Xintensity = 240: 62.60
Xintensity = 360: 62.64
Xintensity = 512: 62.70 - 230W
No shares reject
will update this post tomorrow with better memory times then stock (just got the card so haven't set it up fully for mining)

There is a temporarily problem with the pool. Read on the top

---

The best stable setting I found with the cuda 11.2 build v1.02  (hashrate/watts)
rtx 3060 (lhr 1) 50.50MHASH

Disable p2 state (nvidia profile inspector)
370.05 beta driver (x16 riser, hdmi plug)
Add --xintensity 64 to the commandline

msi afterburner:
65% powerlimit
90 degrees templimit
-200 core
+1150 mem


[moderator's note: consecutive posts merged]

Tested 1.02 with 3060, eth, miningpoolhub:

1. worker, specified in .bat (--worker_name 3060) never appeared on pool, waited 30 min. Pool does not see any new workers, but miner is mining...
2. is it possible to turn off date stamp? Timestamp is enough and because of long datestamps, 1 line before and 1 after statistics is too long, 1 line is divided to two lines in command prompt - looks messy.
3. pool difficulty looks strange:

teamblack: europe.ethash-hub.miningpoolhub.com:20535 (ethash)    PING: 70ms    DIFFICULTY: 3.00     EPOCH: 440
trex: europe.ethash-hub.miningpoolhub.com:20535, diff: 12.88 G

Waiting for new version.

We have added cpu verification of the dag buffer. If the verification fail, the miner will exit/restart.

Yup, I can confirm that with the new 11.2 v1.02 build, I can use my 3060 now without issues. Thanks.

Thanks for testing. -1 is for pools like crazypool no penalty for stale shares. And other pools which doesn't spam you with jobs every 300ms.
The local stale checker is not 100% accurate, I see accepted shares on the pool that we report as stale. Will look into it.

added  ubuntu 18.4 build (hiveos)

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

eth/zil , 3080 non lhr , mem +700 , on intensity -1 , from 250 shares 70 was stale , on default intensity value 1400 shares ~60 stale

Thanks for testing. We need to add verification code to the dagbuffer, and recreate it with a lower intensity
on errors.This is in the todo list.

It might help to add som more power. The best clocks on the other miners might not be the best for this one.


124MHASH is a good result. We have 0.5% fee vs 1% in t-rex so you can add another +0.59MHASH to the profit

On nicehash you shouldn't use -1 since you will get alot of job not found and stale shares. This is because nicehash need very small buffersizes sent to the gpu.

With no parameter set, the default is --xintensity 32


you can't because it's calculated on every round based on your hashrate. So it's not a fixed value. But we might added to the stats panel later. Updated every 60 seconds.

---

v1.02
1. Added stale share check on the submitted shares and display the count.
2. Added --xintensity parameter. To finetune the buffer size sent to the gpu. (NVIDIA/AMD)
3. Fixed memory problem on startup
4. Added support for more pools
5. Fixed crash in the opencl mining. Cards stopped working.
6. Print pool difficulty changes to console
7. Fixed bug in list opencl devices
8. Added gpu memory temp to stats

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

windows:

TeamBlackMiner_1_02_cuda_11_2.7z (for the 470.05 driver)
SHA-256   bb517a8e37faf1c1f7c3b4941b941a53fdad3bb09eefc16909d09286642b5659

TeamBlackMiner_1_02_cuda_11_4.7z
SHA-256 984587059306b5f9dfcc5f9c918e9f30a6b9d3725fc712ca0bf2faefcbb56ed0

linux:
TeamBlackMiner_1_02_Ubuntu_18_04_Cuda_11_4.zip
SHA-256   b201ab9d96cbf9c11cca38f9941475d6a3b5aca20a1ceb2ba30924ca09e97a93

---

We have added the --xintensity parameter to the opencl solver. Can you try again? What hashrates are you getting and what is the --xintensity ?

---

The cuda_11_2 v1.02 build seems to be working fine.

[moderator's note: consecutive posts merged]

Hi,

I am testing now with RTX 3080 (Nicehash & --xintensity -1).

Where can one see the dynamic xintensity calculated value (so I can report it  )?

It seems that with default values no log file is generated.

not supported on opencl yet.

---

select cuda devices with -U [0,2,3,4]

---

I guess your problem will be fixed when 1.02 is released for cuda 11.2

[moderator's note: consecutive posts merged]