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

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]

Out of curiosity on your screenshots, it shows using CL drivers 471.41, however, when I start the miner mine is showing it is using 330.0 is that normal for an AMD card?

I've also tried the --xintensity parameter from 12 upto 240  and -1 (12, 24, 36, 48, 64, 120, 240) and while it does seem to 'bog' my system down more at the higher intensities, my hashrash stays between 57-59.  Pool: 2miners, us server, Card: AMD 6800XT on adrenalin 21.30.15.01

Also note in your screenshot you show the 'Xintensity' line, I am not seeing that on mine (I did check to make sure I was using the correct version)

Ethermine, win 10, core +65, mem +150, driver 460

How do you set the miner to only 1 GPU if you have two GPU's under Windows 10. I have a 2080 TI that I use to mine on and a 980 GTX that I use for everything else in my computer. If I use the -D option it just lists all the GPUs and loops. I can't seem to get it to only see the 2080 TI which is listed as GPU0. This is what my current config shows. TBMiner --algo ethash --hostname eth-us-east.flexpool.io --port 4444 --wallet %ETH_WALLET% --worker_name %WORKNAME% -D GPU0  Thanks for the help.

Edit: got it working changed it to TBMiner --algo ethash --hostname eth-us-east.flexpool.io --port 4444 --wallet %ETH_WALLET% --worker_name %WORKNAME% -U [GPU0] and it works now. I am now getting error "'nvidia-smi.exe' is not recognized as an internal or external command" When it tries to display stats. Over all so far it is faster based on what it is displaying. I went from 61.9 mh/s to 64.25 mh/s with no changes in OC on my 2080 TI.

Edit2: I tried to get this working on my 3060 v1 card with 470.05 driver using the 1.01 Cuda 11.2 build. It starts mining fine. I am even have a increase of about 2mh/s with no changes in OC, but all shares are coming up with error " mining.submit: Pool reponded with error." Then showing invalid POW. I am using Flexpool East. I am not having any issues with shares being submitted with this miner on the 1.02 Cuda 11.4 build on my 2080TI.

Wich pool, platform version and settings?

---

v1.02 beta
1. Added stale share check on the submitted shares and display the count.
2. Added --xintensity parameter.(-E) To feed the pool(s) what they need. (default is --xintensity 32, valid values --xintensity 1 and up to 10000? --xintensity -1 For the program to calculate the best intensity.)
3. Try to fix memory problem on startup
4. Added support for more pools
5. Fixed crash in the opencl mining. Cards stopped working.

windows exe only

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


If you have time, post the best --xintensity. We need the pool and cards.  Nicehash and the other 100ms job pools probobly need a low value to avoid rejected/stale shares. Etheremine, Solominingpools, crazypool, miningpoolhub and a few others works best with --xintensity -1 or perhaps high fixed values.

Low xintensity will give poor hashrate, so try to find the sweetspots.

[moderator's note: consecutive posts merged]

I have tried the latest version with gtx 1070 x 8, got 60 shares rejected (100%) and back to t-rex.

Did you get more stales with 1.01? Stales should have been reduced with 1.01. Use the latest _fix version on git. I had to upload a patch because of the duplicate bug. They share the same version number. Stale shares are also pool depended. Some pools spam you with jobs, some are more quiet. You get payed for stale shares. Some pools pay for them as normal shares.

We will add a stale share checker in the next version and perhaps an intensity setting where you can adjust the workload sent to the gpu manually. Good for pool finetuning.

---

Here is a preview of version v1.02. The third column is the stale share amount.  The gpu is a rtx 2060 Mobile (laptop)

Accepted/Rejected/Stale

---

Added a --xintensity option. This option is similar to the one in ccminer or sgminer. It controls the amount of work the gpu does in one warp. A big workload give good hashrate, but can also give rejects and stale shares. We have also added a --xintensity=-1 option to let the program calculate the workload dynamicly based on hashrate.  Without the option the miner will run with --xintensity=32




[moderator's note: consecutive posts merged]

Try 1.01, stats fix. But got a lot stales shares.

https://i.ibb.co/DbV8RgS/vs.png

[/url]

Did you try v1.01?

The cuda 11_2 build is working on 470.05. will build v1.01 soon

---

Thanks for testing. Note that the optimal clock and power settings for gminer might not be the optimal for the Team Black miner. More power will give you more hashrate. Your requests have been put in the todo log . check for updates in the coming days. We are also working on a LHR full unlock feature...

---

- Fixed duplicate share bug on some pools
- Fixed crash in stats when using -Y or -U to manually specifying gpu list
- Added more pools

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

TeamBlackMiner_1_01_cuda_11_2_fix.7z
SHA-256   3b65b2fa7a7c1a66bc0d38778df9429066993ab2df76c3050842f715bfb045d0

TeamBlackMiner_1_01_cuda_11_4_fix.7z
SHA-256   7997f29017dbacb8c731ad7cbcd2369e23b4f209364956ca15585d936ac0683d

TeamBlackMiner_1_01_Ubuntu_18_04_Cuda_11_4.zip
SHA-256   88ad521b6171e84b91f36adc8162d4dc1830a83e9f59ad8198d0b17005f7f570

---

Try the cuda 11.2 build for windows

[moderator's note: consecutive posts merged]

little feedback, I don't know how you manage to get my rtx3070 to 63Mh? while gminer I have 61.40Mh with this same settings, after fault of pool "crazypool" not compatible I can not see if the shares are there

So I'm on hiveOs, not easy the instllation, even with the links in the read-me, I think if you had an automation screen while waiting that could help a lot of people.

I also had to put a dependency in addition I put you here


and for cuda 11.04:
https://medium.com/@anarmammadli/how-to-install-cuda-11-4-on-ubuntu-18-04-or-20-04-63f3dee2099

I did not succeed in integret in hiveos via flight-sheets

I used nvidia-smi for my OCs because in the minor one cannot put the core and memory on nvidia

on the page https://github.com/sp-hash/TeamBlackMiner

it would be nice to put more details on the command line example:
-p or --port
=> mining pool port (for example: '8888', '3333')

A function is missing to generate the dag clean and then check it if there is no error. like at gminer, phoenixminer or trex which generates in slow mode and then checks no error

now we have to fix the crash errors, so more stability and diff on pool is 8.590G

Let's see more ... when it will be more stable and easier to deploy it, I will do a test on one of my farms + 2Ghs to see the sharing rate / hour

Good continuations, with each update I will test and you will return

---

rollback driver and try it !! last version driver for mining is useless

you have to add your own tooooo





[moderator's note: consecutive posts merged]

Not working with 470.05? Are you serious??? Totally useless...

Need to debug that one. isnull indicate a zero nounce. Whats the difficulty was the pool running at?

---

Not yet. added to the todo list.. You can use the -N option (--no-cpu) to reduce cpu usage to almost 0.

---

$$$

[moderator's note: consecutive posts merged]

Is there a way of adjusting intensity? Id like to dial it down just a notch.