⛏Team Black Miner (ETHB3 ETHW ETC VTC KAWPOW FIROPOW ZIL +dual +tripple mining )

[sp_]

Let's hope ver 1.18 will solve the problem "Miner exited code: -1" bug on mmpOS.

v1.17 had a bug at launch on linux. v1.18 should be good. The miner doesn't support local proxy server, so you have to mine directly to the pool.

Why does the timer not sync with the timestamp? It is lagging behind.

Works good here, Linux or windows? Why don't you open a ticket on github?

[moderator's note: consecutive posts merged]

[1714706856]

1714706856

[1714706856]

1714706856

[1714706856]

1714706856

[1714706856]

1714706856

[1714706856]

1714706856

[KillrBee]

couple of issues.

- Poolstats doesn't work with vardiff pools
- linux scripts have windows lineshift in the .sh files
- The windows cuda 11.5 build need the latest driver because of Cuda 11.5

The miner isn't reporting its hashrate to the 2Miners pool, is this intentional now that the client is calculating the expected poolside hashrate?

[sp_]

The miner isn't reporting its hashrate to the 2Miners pool

We fixed etheremine, try to use workers with lowercase in the workername.

[KillrBee]

The miner isn't reporting its hashrate to the 2Miners pool

We fixed etheremine, try to use workers with lowercase in the workername.

Yep, that fixed it.  Will this also effect Linux/HiveOS?  I just tested in HiveOS and it was working fine (but version 1.16), but my Farm Name always seems to show up in the worker name, my farm name has capitals -- am I going to have to change the name of it too make it all lowercase?

[dle378]

Is it recommended to do dynamic (-1) vs the default for xintensity when mining on miningpoolhub/2miners/nanopool?

Forgive me for asking the same question in previous posts as I am trying to see what the best value is for my NVIDIA 3060 TIs.

[sp_]

Yep, that fixed it.  Will this also effect Linux/HiveOS?  I just tested in HiveOS and it was working fine (but version 1.16)

in v1.16 the workername was sent with both highcase and lowcase to the pool, but for some reason it was rejected by etheremine and the result was 0 reported hashrate. On 2miners and all the other pools it worked fine.
In v1.18 we patched the bug and submitted only lowcase workername to the pool.
The fix is working good on ethermine, but fails on 2miners...

[sp_]

Forgive me for asking the same question in previous posts as I am trying to see what the best value is for my NVIDIA 3060 TIs.

Pools change their code too. I think the best option is to find something that works for you and keep it for yourself. We have created a miner that be tuned to produce great profit. Your job is to find out how to use it...

[dle378]

Forgive me for asking the same question in previous posts as I am trying to see what the best value is for my NVIDIA 3060 TIs.

Pools change their code too. I think the best option is to find something that works for you and keep it for yourself. We have created a miner that be tuned to produce great profit. Your job is to find out how to use it...

That makes sense.

Is there a minimum/maximum value for xintensity?

And also please keep up the great work!!

[hashatharias]

Hello, so I'm super exited about the arrival of TBMiner on HiveOS, finally :-) Congrats to the devs!

though, on Nicehash, with -- xintensity 224 I get more than a couple of rejects

https://i.imgur.com/mazZTnh.jpeg

Any suggestion?

Also, the parameter for the worker name doesn't seem to be passed through properly as it appears in Nicehash as a new rig

Parameters

Code:

Algoethash
Host: daggerhashimoto.usa-east.nicehash.com
Port: 3353
Worker: %WORKER-NAME% (doesn't pass the worker's name)
Template: XXXXMYWALLETADDRESSXXXX (as %wal% wouldn't work)
User Config: --xintensity 224

[sp_]

On amd the intensity is 1/4 on nvidia.
 256 on nvidia 64 on amd.

A user reported that 78 worked good on the 6800 , but 24 might be bether on nicehash

[hashatharias]

if I change the xintensity to anything else than 224, TBMiner fails and restarts

[sp_]

are you running v1.18? can you test --xintensity 1024

[ayiphelmy]

are you running v1.18? can you test --xintensity 1024

what the max can i use for xintensity?? i see some gain in 1070ti using 1024

[hashatharias]

are you running v1.18? can you test --xintensity 1024

I'm running HiveOS 1.16 build
If you know how to update to 1.18 on Hive, I'll be happy to try

[sp_]

it will max when your gpu run out of memory. LHR cards run good at max speed in 2 minutes using --xintensity 10000, but profitwise not good. And then you need to reset the device and regenerate the dag.

[KillrBee]

Yep, that fixed it.  Will this also effect Linux/HiveOS?  I just tested in HiveOS and it was working fine (but version 1.16)

in v1.16 the workername was sent with both highcase and lowcase to the pool, but for some reason it was rejected by etheremine and the result was 0 reported hashrate. On 2miners and all the other pools it worked fine.
In v1.18 we patched the bug and submitted only lowcase workername to the pool.
The fix is working good on ethermine, but fails on 2miners...

It's never easy is it?  I just changed everything to lowercase and it's working fine.

[sp_]

it will max when your gpu run out of memory. LHR cards run good at max speed in 2 minutes using --xintensity 10000, but profitwise not good. And then you need to reset the device and regenerate the dag.

The team black has the fastest dag generator in the world. So all you need to do is to reverse engineer our code. MIT students can do it in a few days. but why don't you try to solve it yourselves?

[dedizonesv2]

hello,

i try on my Farm #1 and nice job

but I'll try to give you a little feedback.

So 6 hours that its running in mode

- intensity 400
- kernel 5

1: RTX 3080 | Ccore 1070 | Mcore 2200 => 104.3 MHS
27: RTX 3070 | Ccore 1070 | Mcore 2200 => 63.72 MHS
6: 3060 TI | Ccore 1070 | Mcore 2200 => 63.72 MHS

I have a bit between 810 / 900 Share for 2.203 GHS and only max 20 stales / hours and no badshare

I mine on crazypool with no ssl, hiveos - 5.10.0-hiveos #60 - N470.74

Suggestion is this possible to

Remove in console this => API request

 2m [2021-10-22 22:20:52.002] API request (127.0.0.1)

possible to see just the JOB, share accept and gpu solution?

consumption level we are still 100 to 150 more than TREX or Gminer I tried automatic kernel in without putting an argument and I am the same.

For exemple
Gminer 4700W for 850 / 920share but 2.133GHS

I am 4900w for 2208w with TBM

for the intensity I am in 3070/3060 Ti and 3080 we can not do an automatic operation or if you have a following range the models because I will not do 256 to 10,000 lol

I am in version 1.18 because the 1.16 bug on my rig of 10 cards

Otherwise very good work, I will try tonight to optimize

EDIT PS: I also forget to put the stats every X min I like every 60 min

[beber75]

Hi,

I've just noticed Teamblack was integrated into HiveOS with version 1.16

I have only AMD cards RX 6600xt, RX 580, RX 6700xt and RX 5700

All my cards are recognized except the RX 580 models (I have 3 of them).
Did anyone have the same effect on HiveOs ?

To bypass that for now, I've configured Teamredmine on RX 580 series and Teamblack on all other models.

Regards

[Ramsete2]

Xintensity 400 is to high for crazypool, try 192