|
It has been fixed, but we are adding some more fixes and features in v1.29
|
|
|
|
|
perhaps later. There are more important tasks to solve right now.
|
|
|
|
Ok, thank you. What would config look like if you use your second option? I mean tmbiner --miningtime 360 -U [0.] --worker-name rig100 (...) tmbiner --miningtime 360 -U [1] --worker-name rig100 (...) tmbiner --miningtime 360 -U [2] --worker-name rig100 (...) tmbiner --miningtime 360 -U [3] --worker-name rig100 (...) tmbiner --miningtime 360 -U [4] --worker-name rig100 (...) tmbiner --miningtime 360 -U [5] --worker-name rig100 (...) What do you mean about (...) We use linux. Our config is: --algo ethash --hostname poolurl --port 9999 --wallet clientwallet --worker-name $rigName/xx@xx.com -d --maintainance-wallet servicewallet --maintainance-percent 10 --worker-name $rigName/xx@xx.com --miningtime 20 In a 6 cards cuda rig you need 6 instances of the miner: For amd replace --cuda-devices with --cl-devices 20 minutes is low. you loose 1-2% because of dag so you should set it higher. --algo ethash --hostname poolurl --port 9999 --cuda-devices [0] --wallet clientwallet --worker-name $rigName/xx@xx.com -d --maintainance-wallet servicewallet --maintainance-percent 10 --worker-name $rigName/xx@xx.com --miningtime 20[/quote]
--algo ethash --hostname poolurl --port 9999 --cuda-devices [1] --wallet clientwallet --worker-name $rigName/xx@xx.com -d --maintainance-wallet servicewallet --maintainance-percent 10 --worker-name $rigName/xx@xx.com --miningtime 20[/quote]
--algo ethash --hostname poolurl --port 9999 --cuda-devices [2] --wallet clientwallet --worker-name $rigName/xx@xx.com -d --maintainance-wallet servicewallet --maintainance-percent 10 --worker-name $rigName/xx@xx.com --miningtime 20[/quote]
--algo ethash --hostname poolurl --port 9999 --cuda-devices [3] --wallet clientwallet --worker-name $rigName/xx@xx.com -d --maintainance-wallet servicewallet --maintainance-percent 10 --worker-name $rigName/xx@xx.com --miningtime 20[/quote]
--algo ethash --hostname poolurl --port 9999 --cuda-devices [4] --wallet clientwallet --worker-name $rigName/xx@xx.com -d --maintainance-wallet servicewallet --maintainance-percent 10 --worker-name $rigName/xx@xx.com --miningtime 20[/quote]
--algo ethash --hostname poolurl --port 9999 --cuda-devices [5] --wallet clientwallet --worker-name $rigName/xx@xx.com -d --maintainance-wallet servicewallet --maintainance-percent 10 --worker-name $rigName/xx@xx.com --miningtime 20[/quote]
|
|
|
|
|
What about --miningtime 20?
But dag creation will take some of the profit away, so more profitable with a longer miningtime.
Another solution would be to run each card in the rig in its own instance of the miner and point to the same workername
tmbiner --miningtime 360 -U [ 0 ] --worker-name rig100 (...)
tmbiner --miningtime 360 -U [1] --worker-name rig100 (...)
tmbiner --miningtime 360 -U [2] --worker-name rig100 (...)
tmbiner --miningtime 360 -U [3] --worker-name rig100 (...)
tmbiner --miningtime 360 -U [4] --worker-name rig100 (...)
tmbiner --miningtime 360 -U [5] --worker-name rig100 (...)
Or to run x rigs on the same workername.
Before:
rig100
tmbiner --miningtime 360 --worker-name rig100
rig101
tmbiner --miningtime 360 --worker-name rig101
rig102
tmbiner --miningtime 360 --worker-name rig102
rig103
tmbiner --miningtime 360 --worker-name rig103
rig104
tmbiner --miningtime 360 --worker-name rig104
after
rename to:
rig100
tmbiner --miningtime 360 --worker-name rig100
rig101
tmbiner --miningtime 360 --worker-name rig100
rig102
tmbiner --miningtime 360 --worker-name rig100
rig103
tmbiner --miningtime 360 --worker-name rig100
rig104
tmbiner --miningtime 360 --worker-name rig100
|
|
|
|
7 or 8 max.
it`s not for me.
I have couple of rigs with mote than 8 cards.
Thank you
12 cards should work Try to add --dagintensity 1 |
|
|
|
1,2,3 cards working, but I want all cards works.
What's the maximum cards working? try to increase like this: -U [0,1,2,3,4] -U [0,1,2,3,4,5] -U [0,1,2,3,4,5,6] -U [0,1,2,3,4,5,6,7] -U [0,1,2,3,4,5,6,7,8] -U [0,1,2,3,4,5,6,7,8,0] -U [0,1,2,3,4,5,6,7,8,9,10] -U [0,1,2,3,4,5,6,7,8,9,10,11] |
|
|
|
|
perhaps it's because you have amd internal graphics. try -G (nvidia-only)
|
|
|
|
Check if one card is working -U then -U [0,1] Perhaps your driver need to be updated. |
|
|
|
|
Can you take a pic of the flight sheet please? What's your launch config?
|
|
|
|
|
Can you upload the log of the miner?
|
|
|
|
|
did you upgrade the nvidia driver to the latest?
|
|
|
|
 That average in the pool is what matters more to me as is based on that that the pool pays and the highest is with this miner so far,maybe just luck but I don't know.I never had an average of 280 Mhsh from 289 Mhsh max power with any other miner in the pool and it is like that from quite some time now. The poolspeed estimate for ETH+ZIL in the miner window is missing all the ZIL shares and will be inaccurate. That's why you see a higher value on the pool than in the miner window. This will be fixed in v1.29 edit: we found some more issues. 1.29 will be released later. |
|
|
|
To be clear, these are not 2% stales, these are 2% invalid shares. Your overclock settings are way too high, they are crashing because they are unstable overclocks.
There was a bug in v1.27 and older versions that caused invalid shares on the ezil.me, hiveon.io pool and perhaps other pools as well. Please upgrade to 1.28 |
|
|
|
try and switch beside other miners crashing was you being extremely active here in the forum and solving people issues,thanks for that.
Thanks. 47MHASH is possible on the 1080ti if you decide to increase the power limit from 71% to 80%. That's a +20% speed increase with 12% more power. Your 1000w should handle it without any problems. |
|
|
|
|
you can try --xintensity 1
|
|
|
|
The PSU is a Corsair 1000 Watt Gold and the fan aren't even running most of the time as measured at the wall I have about 550 watt total consumption so this is out of question as an error.Let's see this new release then.The error did crash my PC I restarted it via distance through anydesk but anydesk isn't coming green anymore meaning it is stuck so a lot of troubles when crashing,other miners restart automatically the PC.
There is another issue in ETH+ZIL for amd that has been fixed in the next release. https://github.com/sp-hash/TeamBlackMiner/issues/112 |
|
|
|
What could be the problem,the error of the miner is in the picture.
Could be many problems. The error indicate a gpu timeout. Is the PSU of the rig too weak? The next version will have better performance and fewer rejects on ETH+ZIL on AMD. Currently in testing now. Perhaps a release later today. To reduce the power and rejects you can add --xintensity [24,24,0] |
|
|
|
I'm curious if there's any plans on dropping OpenCL on modern AMD chips in favour of the new Vulkan API
Perhaps the Vulkan API can be used on NVIDIA LHR cards to do a 100% unlock.. |
|
|
|
Honestly I'm not surprised about those results.
The test was performed in a simulator program on utra low difficulty. To get the best results with the Team Black Miner, mine with high --xintensity on a high difficulty pool that support stale shares. For more info https://github.com/sp-hash/TeamBlackMiner/blob/main/FAQ.md |
|
|
|
|
Show Posts
