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

[dedizonesv2]

Xintensity 400 is to high for crazypool, try 192

yes

I just went through all the pages

and in nucleus an idea? if you use RTX ^^

I tried 5 and 6 and without value so automatic I see no difference

[Ramsete2]

Xintensity 400 is to high for crazypool, try 192

yes

I just went through all the pages

and in nucleus an idea? if you use RTX ^^

I tried 5 and 6 and without value so automatic I see no difference

I leave it on auto at the moment.

[sp_]

gtx 1660 with memtweak (bios mod) ~35MHASH !

--kernel 0 / GPUMemoryTransferRateOffsetAllPerformanceLevels=1700

57m [2021-10-18 17:57:42.023] GPU0 1660S 0.00 H/W 34.98 MH/s 35.01 MH/s 18/0/0 (100.00%)
57m [2021-10-18 17:57:42.023] GPU1 1660S 0.00 H/W 35.14 MH/s 35.11 MH/s 29/0/0 (100.00%)
57m [2021-10-18 17:57:42.023] GPU2 1660S 0.00 H/W 35.18 MH/s 35.10 MH/s 22/0/1 (100.00%)
57m [2021-10-18 17:57:42.023] GPU3 1660S 0.00 H/W 35.10 MH/s 35.01 MH/s 22/0/0 (100.00%)
57m [2021-10-18 17:57:42.023] GPU4 1660S 0.00 H/W 33.33 MH/s 33.49 MH/s 24/0/1 (100.00%)
57m [2021-10-18 17:57:42.023] GPU5 1660S 0.00 H/W 33.43 MH/s 33.47 MH/s 21/0/0 (100.00%)
57m [2021-10-18 17:57:42.023] GPU6 1660S 0.00 H/W 35.02 MH/s 34.96 MH/s 26/0/0 (100.00%)
57m [2021-10-18 17:57:42.023] GPU7 1660S 0.00 H/W 34.83 MH/s 34.96 MH/s 32/0/1 (100.00%)
57m [2021-10-18 17:57:42.023] GPU8 1660S 0.00 H/W 35.03 MH/s 35.03 MH/s 20/0/1 (100.00%)
57m [2021-10-18 17:57:42.023] GPU9 1660S 0.00 H/W 35.03 MH/s 35.03 MH/s 24/0/0 (100.00%)
57m [2021-10-18 17:57:42.023] GPU10 1660S 0.00 H/W 35.09 MH/s 35.01 MH/s 32/0/0 (100.00%)
57m [2021-10-18 17:57:42.023] GPU11 1660S 0.00 H/W 34.94 MH/s 35.00 MH/s 29/0/0 (100.00%)
57m [2021-10-18 17:57:42.023] GPU12 1660S 0.00 H/W 32.47 MH/s 32.42 MH/s 25/0/0 (100.00%)
57m [2021-10-18 17:57:42.023] GPU13 1660S 0.00 H/W 35.16 MH/s 35.09 MH/s 30/0/0 (100.00%)
57m [2021-10-18 17:57:42.023] 0.00 H/W 484.71 MH/s 484.68 MH/s 354/0/4 (100.00%)

The gtx 1660S cost nothing, and very profitable with The Team Black miner.. This snapshot is running with --kernel 0

v1.18 works with --kernel 7 @copyspeed

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

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

Download the v1.18 ubuntu  cuda 11_4 build, unzip it

ssh into the rig and replace the tbminer file...



[moderator's note: consecutive posts merged]

[poisons77]

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
https://ibb.co/XZTXcK6

I've no problem wth teamredminer and binance pool.

[ayiphelmy]

average hashrate is dropped with tbm see this graph below

[sp_]

I get an "incorrect login" if I use the SSL url, and a weird "SSL connect error"

There is a problem with the SSL connection. We are working on it. Use the normal ports

average hashrate is dropped with tbm see this graph below

Check the log file for errors. perhaps you need to tune different. Too many stale shares?

[moderator's note: consecutive posts merged]

[TheMaster627]

Does this support the Pascal mining edition cards such as P-104's and 102's? Tried it out but after saying it's generating dag it exits the thread and fails to actually mine. Using Windows 10 with 472.12 drivers, tried both the cuda 11.4 and 11.2 versions, as well as auto and default xintensity and lower kernels.

[ayiphelmy]

average hashrate is dropped with tbm see this graph below

Check the log file for errors. perhaps you need to tune different. Too many stale shares?

stale share 1% and i dont see any error

[poisons77]

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 https://ibb.co/XZTXcK6
and here's the configuration tab on HiveOs https://ibb.co/DKGXqc9

[Ramsete2]

Starting to test ver 1.18:

• Still have bug of not showing any statistics (TEMP, FAN, CORE, MEM, WATT, HASHRATE/W), using latest NVidia beta driver
• If Kernel is on Auto, miner will choose various numbers, even if cards (Zotac RTX3080) are identical
• Miner will not connect on pools on SSL (please solve this bug a.s.a.p. thanks)
• Please remove "API request (127.0.0.1)" from logs, it's quite annoying

[dedizonesv2]

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.

For crazypool don't use SSL just use TCP port 3333

It's stratum "nicehash 1.0' ssl is not required for this, ssl is required for old pool with old eth-proxy

@sp_

you could see my different requests like how to remove


=> [2021-10-23 09:32:07.269] API request (127.0.0.1)

how to reduct watt ?

Starting to test ver 1.18:

• Still have bug of not showing any statistics (TEMP, FAN, CORE, MEM, WATT, HASHRATE/W), using latest NVidia beta driver
• If Kernel is on Auto, miner will choose various numbers, even if cards (Zotac RTX3080) are identical
• Miner will not connect on pools on SSL (please solve this bug a.s.a.p. thanks)
• Please remove "API request (127.0.0.1)" from logs, it's quite annoying

Same problem yes, just for SSL i don't use because the protocol has evolved and the middle attacks are rare finally I have never had a company for years

sorry we posted at the same time for the same requests except the higher consumption.

[moderator's note: consecutive posts merged]

[sp_]

=> [2021-10-23 09:32:07.269] API request (127.0.0.1)

yes. will be removed in v1.19

how to reduct watt ?

for nvidia:

-M --power-limit [,]       (set powerlimit)

• Still have bug of not showing any statistics (TEMP, FAN, CORE, MEM, WATT, HASHRATE/W), using latest NVidia beta driver

Windows or linux? There was a bug in the linux version that was fixed in v1.18

• If Kernel is on Auto, miner will choose various numbers, even if cards (Zotac RTX3080) are identical

--kernel 6 should work good on the rtx3080. The autotune can be improved, it is running too short time in v1.18.

• Miner will not connect on pools on SSL (please solve this bug a.s.a.p. thanks)

yes. This is first priority right now.

[moderator's note: consecutive posts merged]

[dedizonesv2]

=> [2021-10-23 09:32:07.269] API request (127.0.0.1)

yes. will be removed in v1.19

how to reduct watt ?

for nvidia:

-M --power-limit [,]       (set powerlimit)

I'm waiting for V.1.19: D

in the new version also put the stars all X min
as an example all --stats 30
so every 30min

No, we use absolute core my rtx 3070 are at 1070 so no need to limit the PL

I say that I have the same frequency as gminer 1070/2200 and I am at 4900w instead of approximately 4750.

I tried all the kernels, all the intensities lol always the same.

[sp_]

All my cards are recognized except the RX 580 models (I have 3 of them).

Not sure about hiveos but I am running the 580 and the 570 without any problems on windows. Stats are working as well for these cards.

I say that I have the same frequency as gminer 1070/2200 and I am at 4900w instead of approximately 4750.

I tried all the kernels, all the intensities lol always the same.

The lowest power with --xintensity 1 --kernel 0, but not so good hashrate...

stale share 1% and i dont see any error

Is the miner restarting often. I see a dip in reported hashrate, lost internet connection?
Look for gpu timed out messages in the log.

in the new version also put the stars all X min
as an example all --stats 30
so every 30min

You can  use the --no-stats option to turn it off.

Does this support the Pascal mining edition cards such as P-104's and 102's? Tried it out but after saying it's generating dag it exits the thread and fails to actually mine. Using Windows 10 with 472.12 drivers, tried both the cuda 11.4 and 11.2 versions, as well as auto and default xintensity and lower kernels.

Use the v1.18 cuda 11.5 build

If not run with --kernel 0. The P102, and P104 is running a build in memtweak that caused problems in the earlier versions. You can try to remove any overclock and tune until it crashes.


[moderator's note: consecutive posts merged]

[Ramsete2]

• Still have bug of not showing any statistics (TEMP, FAN, CORE, MEM, WATT, HASHRATE/W), using latest NVidia beta driver

Windows or linux? There was a bug in the linux version that was fixed in v1.18

linux (mmpOS)


Started new comparison with Gminer:





Let's see after some hours...

[moderator's note: consecutive posts merged]

[TheMaster627]

Does this support the Pascal mining edition cards such as P-104's and 102's? Tried it out but after saying it's generating dag it exits the thread and fails to actually mine. Using Windows 10 with 472.12 drivers, tried both the cuda 11.4 and 11.2 versions, as well as auto and default xintensity and lower kernels.

Use the v1.18 cuda 11.5 build

If not run with --kernel 0. The P102, and P104 is running a build in memtweak that caused problems in the earlier versions. You can try to remove any overclock and tune until it crashes.

Sadly that hasn't worked. I tried an update to the latest 496.13 drivers, 1.18 cuda 11.5 build, same issue. This is with an EVGA P-104 modded to 8gb. Kernel at 0, clocks extremely low (half of what I know they are stable for months on). Trying Ethermine, says it successfully authorized, starts the worker thread, then at the same moment it says the dag was generated, it says the thread was exited. No problem with running any other miners out there new or old. Here's an excerpt from one of the cards in the prompt,

"     0m [2021-10-23 04:37:48.246] GPU7 Starting generating ethash dag (Epoch: 449)
     0m [2021-10-23 04:37:48.247] GPU7 DAG generated in 3.68 seconds (4726783kb)
     0m [2021-10-23 04:37:48.247] GPU7 kernel 0 selected
     0m [2021-10-23 04:37:48.247] GPU7 XIntensity set to 192
     0m [2021-10-23 04:37:48.252] GPU7 thread exited"

[poisons77]

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.
https://ibb.co/RCJVrr6

[dedizonesv2]

Started new comparison with Gminer:





Let's see after some hours...

don't use SSL on crazypool in addition you lose shares via SSL

Crazypool uses the NiceHash-1.0.0 protocol. If you set your miner to use that, it'll work fine. The challenge is to figure out what magic incantation the mining software expects before it will actually select this protocol. Things like "stratum" or "stratum1" don't necessarily mean the same everywhere. Some mining software also tries to auto-detect what the pool uses, and some pools do that, too. The problem is then - of course - that you may end up auto-detecting an inferior protocol than the best both sides support.

[Ramsete2]

don't use SSL on crazypool in addition you lose shares via SSL

Crazypool uses the NiceHash-1.0.0 protocol. If you set your miner to use that, it'll work fine. The challenge is to figure out what magic incantation the mining software expects before it will actually select this protocol. Things like "stratum" or "stratum1" don't necessarily mean the same everywhere. Some mining software also tries to auto-detect what the pool uses, and some pools do that, too. The problem is then - of course - that you may end up auto-detecting an inferior protocol than the best both sides support.

OK thanks for the tip, I'll disable SSL

[dedizonesv2]

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.

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 ..