PS: max temperature for bminer is set to 94 ?! Thats a bit too much for Nvidia...
P.S.
Sorry, but what's that got to do with bminer?
Btw excellent hint about KBomba ccmonitor... can you upload the binary somewhere?
Thanks
Topic: CryptoDredge 0.8.0 — NVIDIA GPU Miner [obsolete] - page 6. (Read 25238 times)
PS: max temperature for bminer is set to 94 ?! Thats a bit too much for Nvidia...
P.S.
Sorry, but what's that got to do with bminer?
Btw excellent hint about KBomba ccmonitor... can you upload the binary somewhere?
Thanks
Then explain how my gpu's were maxed out during the devfee but tdp was set at 80% prior to the devfee mining starting please. They should not have gone above 80% or it would have automatically been throttled back down if it crept above the limit that was set - but the limit was changed to max. They never should have gotten changed to 100% of max power. That's all I'm asking
Of course it was changing PL and by that it was changing overclock. Don't burn your rigs on CD, use another miner, better one 
in both hashrates and stability.
How to set the intensity for per GPU? It is installed for all at once.
No way. As a workaround for this issue, you might use a few CryptoDredge instances with -d option.e.g.:
Code:
CryptoDredge -a -o stratum+tcp:// -u -p -d 0,1,2 -i 5
CryptoDredge -a -o stratum+tcp:// -u -p -d 3,4,5 -i 4
CryptoDredge -a
Then explain how my gpu's were maxed out during the devfee but tdp was set at 80% prior to the devfee mining starting please. They should not have gone above 80% or it would have automatically been throttled back down if it crept above the limit that was set - but the limit was changed to max. They never should have gotten changed to 100% of max power. That's all I'm asking
Of course it was changing PL and by that it was changing overclock. Don't burn your rigs on CD, use another miner, better one in both hashrates and stability.
I have a problem
In one rig receive 1250kh from 1070Ti and 1050kh for 1080Ti
v 0.7 Linux
TDP 60% . OC didn't help.
In one rig receive 1250kh from 1070Ti and 1050kh for 1080Ti
v 0.7 Linux
TDP 60% . OC didn't help.
Seems like the dev keeps dodging the question on the miner manipulating the settings on its own for the devs benefit regardless of what we set. I'd like to hear answers to the questions.
The miner does not change any overclocking settings. Current algorithms have different power consumption and require individual overclock settings from the user. We have compensated for that in v0.7.0. And If you are using Phi2 or Lyra2z, the miner will not switch to another algorithm on the devfee session. Apologies!That doesn't sound right at all. The power limit was changed to 100% when the devfee started.
Yes, different algorithms use different amounts of power, but the tdp set would always be respected. Are you trying to say that the algorithm used would change the tdp from 80% to 100%??? How exactly would that work? Seriously, just admit you were greedy and trying to max out your devfee and modifying the settings. Switching to another algorithm would not change the tdp.
Then explain how my gpu's were maxed out during the devfee but tdp was set at 80% prior to the devfee mining starting please. They should not have gone above 80% or it would have automatically been throttled back down if it crept above the limit that was set - but the limit was changed to max. They never should have gotten changed to 100% of max power. That's all I'm asking
Hi, The miner keeps stopping on my 1060 3gb cards running allium. Is that a known issue?
Could you provide log or screenshot?The miner just stops working after some random amount of time and sits there - no error or crash of the cmd window. I don't see a log in your folder, so I assume you're looking for a windows event log?
There's no error in the log associated with cryptodredge stopping
Thanks for your fast reply
EDIT, it works wonders on my 1050tis - thanks!
starting miner with
-b 127.0.0.1:4068
Is there any way to get status?
opening 127.0.0.1:4068 using webapi.htm from ccminer github returns:
-b 127.0.0.1:4068 --api-type ccminer-ws
I get error from the program
The "histo" method from ccminer API don't implemented yet, sorry! -b 127.0.0.1:4068
Is there any way to get status?
opening 127.0.0.1:4068 using webapi.htm from ccminer github returns:
Quote
Error! Unable to get WebSocket data from 127.0.0.1
If i start using -b 127.0.0.1:4068 --api-type ccminer-ws
I get error from the program
Quote
WARN - ccminer WebSocket API: boost::too_few_args: format-string referred to more arguments than were passed
aaah, so max (-i 6 is default), my bad
Another dumb question - but how to monitor the app?
Port 4068 is used when starting with -b 0.0.0.0 4068, but I cant get anything...
Any hint how to monitor remotely?
PS: max temperature for bminer is set to 94 ?! Thats a bit too much for Nvidia...
The following works fine for me:Another dumb question - but how to monitor the app?
Port 4068 is used when starting with -b 0.0.0.0 4068, but I cant get anything...
Any hint how to monitor remotely?
PS: max temperature for bminer is set to 94 ?! Thats a bit too much for Nvidia...
Code:
CryptoDredge -a -o stratum+tcp:// -u -p -b 0.0.0.0:4068
You might use https://github.com/KBomba/ccmonitor or other third-party scripts/applications.
P.S.
Sorry, but what's that got to do with bminer?
starting miner with
-b 127.0.0.1:4068
Is there any way to get status?
opening 127.0.0.1:4068 using webapi.htm from ccminer github returns:
-b 127.0.0.1:4068 --api-type ccminer-ws
I get error from the program
-b 127.0.0.1:4068
Is there any way to get status?
opening 127.0.0.1:4068 using webapi.htm from ccminer github returns:
Quote
Error! Unable to get WebSocket data from 127.0.0.1
If i start using -b 127.0.0.1:4068 --api-type ccminer-ws
I get error from the program
Quote
WARN - ccminer WebSocket API: boost::too_few_args: format-string referred to more arguments than were passed
Hi, The miner keeps stopping on my 1060 3gb cards running allium. Is that a known issue?
Could you provide log or screenshot?
Hi, The miner keeps stopping on my 1060 3gb cards running allium. Is that a known issue?
Seems like the dev keeps dodging the question on the miner manipulating the settings on its own for the devs benefit regardless of what we set. I'd like to hear answers to the questions.
The miner does not change any overclocking settings. Current algorithms have different power consumption and require individual overclock settings from the user. We have compensated for that in v0.7.0. And If you are using Phi2 or Lyra2z, the miner will not switch to another algorithm on the devfee session. Apologies!That doesn't sound right at all. The power limit was changed to 100% when the devfee started.
Yes, different algorithms use different amounts of power, but the tdp set would always be respected. Are you trying to say that the algorithm used would change the tdp from 80% to 100%??? How exactly would that work? Seriously, just admit you were greedy and trying to max out your devfee and modifying the settings. Switching to another algorithm would not change the tdp.
Seems like the dev keeps dodging the question on the miner manipulating the settings on its own for the devs benefit regardless of what we set. I'd like to hear answers to the questions.
The miner does not change any overclocking settings. Current algorithms have different power consumption and require individual overclock settings from the user. We have compensated for that in v0.7.0. And If you are using Phi2 or Lyra2z, the miner will not switch to another algorithm on the devfee session. Apologies!That doesn't sound right at all. The power limit was changed to 100% when the devfee started.
Yes, different algorithms use different amounts of power, but the tdp set would always be respected. Are you trying to say that the algorithm used would change the tdp from 80% to 100%??? How exactly would that work? Seriously, just admit you were greedy and trying to max out your devfee and modifying the settings. Switching to another algorithm would not change the tdp.
sadly the dev fee crashes all rigs when mining lyra2v2 by switching to whatever it does.
Guess I'll check back once this is fixed for good.
Could you provide more details? It will help to figure out what's wrong. Actually, If you are using Lyra2REv2, Lyra2z or Phi2, the miner will not switch to another algorithm on the devfee session. Guess I'll check back once this is fixed for good.
sadly the dev fee crashes all rigs when mining lyra2v2 by switching to whatever it does.
Guess I'll check back once this is fixed for good.
Guess I'll check back once this is fixed for good.
aaah, so max (-i 6 is default), my bad
Another dumb question - but how to monitor the app?
Port 4068 is used when starting with -b 0.0.0.0 4068, but I cant get anything...
Any hint how to monitor remotely?
PS: max temperature for bminer is set to 94 ?! Thats a bit too much for Nvidia...
Another dumb question - but how to monitor the app?
Port 4068 is used when starting with -b 0.0.0.0 4068, but I cant get anything...
Any hint how to monitor remotely?
PS: max temperature for bminer is set to 94 ?! Thats a bit too much for Nvidia...
what is default intensity per algo?
i want to try setting "1-step below default" on one of my rigs
-i, --intensityi want to try setting "1-step below default" on one of my rigs
Mining intensity (0 - 6) (default: 6)
Example:
CryptoDredge -a lyra2v2-old -o stratum+tcp://
what is default intensity per algo?
i want to try setting "1-step below default" on one of my rigs
i want to try setting "1-step below default" on one of my rigs
Seems like the dev keeps dodging the question on the miner manipulating the settings on its own for the devs benefit regardless of what we set. I'd like to hear answers to the questions.
The miner does not change any overclocking settings. Current algorithms have different power consumption and require individual overclock settings from the user. We have compensated for that in v0.7.0. And If you are using Phi2 or Lyra2z, the miner will not switch to another algorithm on the devfee session. Apologies! Jump to: