Pages:
Author

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

sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
--computername
computername is not needed use:

--worker_name swogerino
legendary
Activity: 3318
Merit: 1247
Bitcoin Casino Est. 2013
I did all above.Now it gives me different errors with the prevalent being --computername command not found but I didn't move anything from the bat file,I just installed latest Nvidia driver 496.xx for GTX 1080 ti from the official site of Nvidia.It didn't gave this error before as you see in the picture.For the moment I switched back to Phoenixminer 5.9 which was just released today and trying it.

However you can help,you can send me a bat file created by you so I know I am not doing anything wrong.I am writing you a personal message as I really want to try your miner.I am giving you my wallets addresses for ETH+ZIL so you can make one for me for the Ezil pool and I will try it.I am also giving you my email so you can send the file to me.Thanks again.
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
Run the ansicolor.reg script in the 7zip archive to activate colors in Windows program console.

Your driver is only cuda 11.1 compatible so you need to install the latest driver. Download from nvidia

https://github.com/sp-hash/TeamBlackMiner/blob/main/INSTALL_WINDOWS.md

legendary
Activity: 3318
Merit: 1247
Bitcoin Casino Est. 2013
I got this error here in the picture below.

sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
Set ETH_WALLET=(ethereum wallet)
Set ZIL_WALLET=(zil wallet)

:loop
   TBMiner --algo ethash --hostname eu.ezil.me --port 5555 --wallet %ETH_WALLET%.%ZIL_WALLET% --worker-name %computername% --dagintensity 1 --kernel 0
   timeout 10
goto :loop

Use the pill in the backround for the 1080ti.
legendary
Activity: 3318
Merit: 1247
Bitcoin Casino Est. 2013
v1.28 will have improved performance for amd cards on ETH+ZIL (dagger cache). We have also added the possibility to mine to ip adresses directly instead of hostnames.


I just tried 1.27 and it directly crashed out,to make a long story short I need the ETH+ZIL bat file,or you can write it down here so I can give it another try,all other miners are crashing after a certain amount of time so at least I will win some more Mhsh with your miner and I am ready to make the switch.Maybe you have put it somewhere here in the thread as I asked already a long time ago but now I am ready to make the switch and see what happens.My cards are 2 RX 6800 XT and 1 GTX 1080 ti in this rig.Thank you.

I mean for Ezil.me pool I didn't see a bat for that.
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
v1.28 will have improved performance for amd cards on ETH+ZIL (dagger cache). We have also added the possibility to mine to ip adresses directly instead of hostnames.
copper member
Activity: 77
Merit: 0
I have tried testing on other miner software such as GMiner and T-Rex. After three + hours or so, I either get 1-2% rejected shares or the miner software ends up crashing.

Well, if you had problems on those rock solid miners there is something wrong with your setup/OC.

I won't disagree with you on that.

I'll probably need to spend more time troubleshooting/modifying my OC settings that would adhere stability to each individual miner software.
jr. member
Activity: 87
Merit: 5
I have tried testing on other miner software such as GMiner and T-Rex. After three + hours or so, I either get 1-2% rejected shares or the miner software ends up crashing.

Well, if you had problems on those rock solid miners there is something wrong with your setup/OC.
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
I am setting the dagintensity value to "9", is that considered too high of a number?

Thanks.

0 or 9 is the default setting for nvidia.
copper member
Activity: 77
Merit: 0
Is there any benefit in adding the dagintensity value if mining on miningpoolhub?

The point of the --dagintensity 1 is to avoid crash on dag creation on high clockrates. You can oc the memory +100-200 or more with this setting on, but the dag generation will be slower. So not good in eth-zil mining. In v1.28 we will do an adjustemnt to the dag creation  with --dagintensity and make it slower.

Thanks for the explanation.

I am setting the dagintensity value to "9", is that considered too high of a number?

Also, I don't understand why I see so many negative posts about your miner software. I have tried testing on other miner software such as GMiner and T-Rex. After three + hours or so, I either get 1-2% rejected shares or the miner software ends up crashing.

Plus your level of support within the thread is top notch so you can't beat that!

Please keep up the great work.  Grin
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
Is there any benefit in adding the dagintensity value if mining on miningpoolhub?

The point of the --dagintensity 1 is to avoid crash on dag creation on high clockrates. You can oc the memory +100-200 or more with this setting on, but the dag generation will be slower. So not good in eth-zil mining. In v1.28 we will do an adjustemnt to the dag creation  with --dagintensity and make it slower.
newbie
Activity: 1
Merit: 0
pls change text color when dag fail verify.
copper member
Activity: 77
Merit: 0
Is there any benefit in adding the dagintensity value if mining on miningpoolhub?
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
Yes it said all... You said Pool 53 Mhs and is 50Mhs... where are this 3Mhs?

The pool is the average of 6 hours, but he has only mined for 5:48 and the last accepted shares has not been added to the pool yet... The pool only refresh every 10minutes. So I expect the 50.50MHASH poolside hashrate comes from 5:30 minutes of mining
newbie
Activity: 26
Merit: 2
Yes it said all... You said Pool 53 Mhs and is 50Mhs... where are this 3Mhs?
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
Quote
--kernel [5] --xintensity [4096] (no add --tweak and no add --dagintensity)







Pictures say more than words.
newbie
Activity: 40
Merit: 0
Quote
--kernel [5] --xintensity [4096] (no add --tweak and no add --dagintensity)

https://ibb.co/bXbbSvf

https://ibb.co/c2MGyhF
jr. member
Activity: 139
Merit: 3
It's all AMD and I explicitly use --amd-only to exclude the 1 Nvidia card I have in that machine from TBM

Perhaps the --amd-only switch isn't working. Try to select --cl-devices manually

--cl-devices [0,1,2,3,4,5]

Use tbminer --list-devices to get the correct indexes.

That's not it... I suspect that it probably has something to do with the stratum re-write and how HiveOS handles the pool connection.  It selects the pool and then injects it into the miner as %URL%, but if you're now expecting a different format, like 'stratum+tcp://%URL%' or whatever, and HiveOS isn't providing the correct values, there might be an issue. 
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
It's all AMD and I explicitly use --amd-only to exclude the 1 Nvidia card I have in that machine from TBM

Perhaps the --amd-only switch isn't working. Try to select --cl-devices manually

--cl-devices [0,1,2,3,4,5]

Use tbminer --list-devices to get the correct indexes.
Pages:
Jump to: