Author

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

newbie
Activity: 10
Merit: 0
"recommended settings" core clock 1400 - memclock 2150 (running at 2140)
same as before 10min run / at least 2 shares
Team Red 'config A544' - 38.83 / autoconfig(A672) - 53.65
v1.02 still
Xintensity =  -1: 64.61 - 165w
Xintensity =   1: 58.90 - 157w
Xintensity =  12: 62.92 - 162w
Xintensity =  24: 63.11 - 164w
Xintensity =  36: 63.77 - 165w
Xintensity =  48: 65.21 - 167w
Xintensity =  78: 65.51 - 167w
Xintensity = 128: 65.71 - 167w
Xintensity = 240: 65.66 - 167w
Xintensity = 360: 65.80 - 168w
Xintensity = 512: 65.92 - 170w
no invalid shares

Looking to try and update the bios to increase the max memclock, if I can get it to work will post another set of config/test

What is the look back on the average hash? It seems to fluctuate alot more then I would think an average should at the 10 minute mark

Quote
etheremine, nanopool, f2pool, sparkpool etc all good.
2miners also pays uncle blocks (don't really endorse them but fyi)
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
miningpoolhub is better than other pools now?

no, but some pools need low --xintensity. nicehash.com has 10% rejected shares with --xintensity -1. 1.8% rejected with --xintensity 32 .
flexpool.io give a penalty for stale shares so you need to mine with --xintensity 8 or 16.  The ethereum network is paying for stale work (uncle blocks) so when a pool rejects them, they either steal your money or divide the mined money wrong.

Rtx 3090 --xintensity -1 can give up to 135MHASH
Rtx 3090 --xintensity 8 can give up to 115MHASH (?)

20MHASH wasted on a pool that doesn't compensate the work you do.

etheremine, nanopool, f2pool, sparkpool etc all good.
member
Activity: 181
Merit: 10
1.03 cuda 11.2 - still missing from miningpoolhub.

fixed in v1.04. The profit is amazing @ miningpoolhub


miningpoolhub is better than other pools now?
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
of course, 1 or 2 shares every 5 min,

Looks like there is a bug, but your shares are credited. Will be fixed in the next release. This bug could affect other stratum 1.0 pools as well.



v1.04
1. Fixed bug when submitting shares in stratum 1.0 sometimes the workername was lost
2. Fixed stats printout if the poolname is too long
3. Added more pools
4. Cpu rejected opencl shares now added to the stats
5. Faster opencl kernel
6. Fixed ethereum classic opencl mining on miningpoolhub

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

TeamBlackMiner_1_04_cuda_11_2.7z
sha-256 fbe5c3e03c4a6ca31d9864f050594779b89a32fa8dea43ef3d80ca888bce9915

TeamBlackMiner_1_04_cuda_11_4.7z
sha-256 1af8eaa96aa98d92af5d203f70dcfa48f0899d947abcb7faa24c8cfb6a8c40f7



1.03 cuda 11.2 - still missing from miningpoolhub.

fixed in v1.04. The profit is amazing @ miningpoolhub

[moderator's note: consecutive posts merged]
jr. member
Activity: 212
Merit: 6
of course, 1 or 2 shares every 5 min, i know that it will not be shown as active if there is no shares for long time (about 15 min, with trex).

sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
And you get accepted shares in the console? The diff is high on this pool, so it could take some time with 1 card or small rig.
jr. member
Activity: 212
Merit: 6
ok, now i tried it in few different ways. Yes, worker will appear (i was wrong, used worker name that i had on the list), but it is saying worker is not active.

so, both variant are working, but not active = hashrate is always 0.

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

if i use

--wallet user.name --worker_name name

it will appear as user name.name
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
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.

workaround use both:

--wallet user.name -worker_name name
jr. member
Activity: 212
Merit: 6
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.
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
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.

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%
member
Activity: 181
Merit: 10
can any body share flight sheet compatible config for hiveos? thanks
jr. member
Activity: 212
Merit: 6
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.
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
Any chance to make your miner work with Miningrigrentals? TeamBlack miner says it is not supported.

Yes, it's in the todo list
newbie
Activity: 13
Merit: 0
Good day,

Any chance to make your miner work with Miningrigrentals? TeamBlack miner says it is not supported.
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
and therefore less stale.

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.



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)

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]
jr. member
Activity: 152
Merit: 3
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.
newbie
Activity: 10
Merit: 0
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)
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
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]
jr. member
Activity: 212
Merit: 6
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.
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
We have added cpu verification of the dag buffer. If the verification fail, the miner will exit/restart.


Jump to: