Is it possible to turn on the --submit-stale option in the *.conf file?
What is the exact format the entry needs to be in the file?
thanks,
Sigg
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 698. (Read 5805728 times)
January 18, 2012, 02:43:58 PM
January 18, 2012, 11:21:56 AM
I am having a hard time finding this and i'm sure its posted but i'll ask anyways. I have a 4 5850 setup and one of the 4 card's fan speed is showing 0RPM (sometimes 20RPM) for its fan speed. the rest are showing 2000-3000RPMish. the fan speed set in the conf file is 0-85 with auto-fan turned off. Below is an example of my config minus the user info. Also. i removed that card (card 4)and then the next card (card 3) is showing 0 - 20 RPM for its fan speed. GPUz and Afterburner show 85 percent and in the 2000-3000RPM range.
is there something that i am missing?
intensity" : "9,9,9,9",
"gpu-engine" : "0-920,0-920,0-920,0-920",
"gpu-fan" : "0-50,0-80,0-80,0-80",
"gpu-memclock" : "500,500,500,500",
"gpu-powertune" : "0,0,0,0",
"gpu-vddc" : "1.200,1.200,1.200,1.200",
"temp-cutoff" : "95,95,95,95",
"temp-overheat" : "85,85,85,85",
"temp-target" : "75,75,75,75",
"algo" : "c",
"api-port" : "4028",
"expiry" : "120",
"gpu-threads" : "2",
"log" : "5",
"queue" : "1",
"retry-pause" : "5",
"scan-time" : "60",
"temp-hysteresis" : "3",
"worksize" : "0",
"donation" : "0.00",
"shares" : "0",
"kernel-path" : "/usr/local/bin"
is there something that i am missing?
intensity" : "9,9,9,9",
"gpu-engine" : "0-920,0-920,0-920,0-920",
"gpu-fan" : "0-50,0-80,0-80,0-80",
"gpu-memclock" : "500,500,500,500",
"gpu-powertune" : "0,0,0,0",
"gpu-vddc" : "1.200,1.200,1.200,1.200",
"temp-cutoff" : "95,95,95,95",
"temp-overheat" : "85,85,85,85",
"temp-target" : "75,75,75,75",
"algo" : "c",
"api-port" : "4028",
"expiry" : "120",
"gpu-threads" : "2",
"log" : "5",
"queue" : "1",
"retry-pause" : "5",
"scan-time" : "60",
"temp-hysteresis" : "3",
"worksize" : "0",
"donation" : "0.00",
"shares" : "0",
"kernel-path" : "/usr/local/bin"
January 18, 2012, 09:04:37 AM
If you successfully close cgminer properly it *should* return to the default values on shutdown. That said, the windows version has this knack of not closing properly. How/why, remains a mystery. Nonetheless the settings will go back to default on a reboot. None of the settings cgminer uses tell the card to keep settings across a reboot.
Thanks. Upon selling and removing my second graphics card I'll reinstall the drivers and will see whether this changes anything and then report back to you.
January 18, 2012, 07:50:14 AM
Thanks a lot! The poor performance with donation on was my fault initially 
I've since fixed it but it doesn't matter. I haven't made a decision about enabling donations by default but for now it's not a high priority issue.
If you successfully close cgminer properly it *should* return to the default values on shutdown. That said, the windows version has this knack of not closing properly. How/why, remains a mystery. Nonetheless the settings will go back to default on a reboot. None of the settings cgminer uses tell the card to keep settings across a reboot.
I've since fixed it but it doesn't matter. I haven't made a decision about enabling donations by default but for now it's not a high priority issue.If you successfully close cgminer properly it *should* return to the default values on shutdown. That said, the windows version has this knack of not closing properly. How/why, remains a mystery. Nonetheless the settings will go back to default on a reboot. None of the settings cgminer uses tell the card to keep settings across a reboot.
January 18, 2012, 07:47:41 AM
Agreed, you should just enable it and make sure it is stated clearly (and the same message should include explanation how to disable it, e.g. "to disable add -donation 0" flag), especially since the buggy donations are fixed.
It's not like a) people aren't given a choice or instructions how to disable it, and b) everyone who uses knows so much as to enable the donations.
I like the phrase "I believe in the exploitation of the stupid", so if users aren't clever enough to disable donations - well, thanks for their support
On a side note, a question - if I set a GPU voltage in CGminer, then restart the PC and start cgminer without the flag, does the voltage go back to default or stay at the previously set voltage? Because the BIOS says (with Radeon BIOS Editor) GPU voltage at load should be 1.1V, but cgminer and FurMark read it as 1V. That will hinder my overclocking results in the future.
It's not like a) people aren't given a choice or instructions how to disable it, and b) everyone who uses knows so much as to enable the donations.
I like the phrase "I believe in the exploitation of the stupid", so if users aren't clever enough to disable donations - well, thanks for their support
On a side note, a question - if I set a GPU voltage in CGminer, then restart the PC and start cgminer without the flag, does the voltage go back to default or stay at the previously set voltage? Because the BIOS says (with Radeon BIOS Editor) GPU voltage at load should be 1.1V, but cgminer and FurMark read it as 1V. That will hinder my overclocking results in the future.
January 18, 2012, 07:37:07 AM
I turned on donation when it was first introduced but somehow my performance dropped, lots of
'pool not responding' errors
That's the main reason I turned it off back then, I much rather prefer to send some coins once in a while
That said, i am forgetting a lot these days (must be old age lol), so there are some coins coming your way as I type this !
Thanks for your hard and above all very good work
Brat
'pool not responding' errors
That's the main reason I turned it off back then, I much rather prefer to send some coins once in a while
That said, i am forgetting a lot these days (must be old age lol), so there are some coins coming your way as I type this !
Thanks for your hard and above all very good work
Brat
January 18, 2012, 07:29:01 AM
Heh, you know I tried to make --donation default but there was outrage and threats of forking cgminer and death threats. All right, perhaps not the last but the others.
I say, let them be outraged and threaten. No one is forcing them to use cgminer, no one preventing them from disabling the option. And if someone wants to fork, again, let them. Why would anyone switch to a poorly supported fork which only advantage is that you dont have to change a default setting (assuming you wouldnt want to donate) ?
FWIW, when I first tried cgminer, I wasnt opposed to donating but confused how it worked. I didnt look in to it, and kept it disabled. I bet there are lots people like that.
January 18, 2012, 07:20:06 AM
you wantz moar?
Ohhh now I see it in my wallet instead, lol. Thanks! 
January 18, 2012, 06:56:39 AM
Yes siree, I do hate merged mining.
Yeah it does complicate things BUT I would argue that things are going to get more complicated anyways. Pools will eventually need to use to provide a mechanism to update miners when transactions change (when fees becoming more importantly). p2pool needs a method to track when the share chain has changed. Likely in the future there will be other as of yet implemented events which will require altering the work being done.
Using LP for everything is an ugly hack but it works. However what all this ugliness is pointing to is the fact that the pool-miner communication protocol needs to be more robust. Miners today are relatively "dumb" and rely too much on the server.
There is no proper protocol definition, however some before have mentioned deepbit's web page where they have 'a' definition.
And that definition is the problem - it's next to useless.
It needs to be designed (not hacked), then standardised and then placed/updated in the wiki.
I still do not understand why it is true that a very high % of miners use pools but the wiki is useless in defining the pool protocol.
(damn I need to hurry up and find the time to get around to writing my own and testing/implementing it ...)
January 18, 2012, 04:34:52 AM
I'm currently getting ~450Mhash of donations. Since my mining rig is still in the workshop, this is actually all the mining I'm doing at the moment 
But of course, I would never turn them down!If you want to check out what my donation rate is, simply drop into irc.freenode.net #ozcoin
Here is the way to test it, and the current returned value (it fluctuates a lot):
January 18, 2012, 03:26:12 AM
Heh, you know I tried to make --donation default but there was outrage and threats of forking cgminer and death threats. All right, perhaps not the last but the others.
Set it to 1% in example.conf file with a note to comment it out if donations aren't desired. I hope you're at least getting a reasonable trickle from those who do have it enabled.
I'm currently getting ~450Mhash of donations. Since my mining rig is still in the workshop, this is actually all the mining I'm doing at the moment January 17, 2012, 11:54:00 PM
Heh, you know I tried to make --donation default but there was outrage and threats of forking cgminer and death threats. All right, perhaps not the last but the others.
Set it to 1% in example.conf file with a note to comment it out if donations aren't desired. I hope you're at least getting a reasonable trickle from those who do have it enabled.
I'm currently getting ~450Mhash of donations. Since my mining rig is still in the workshop, this is actually all the mining I'm doing at the moment January 17, 2012, 11:06:44 PM
Heh, you know I tried to make --donation default but there was outrage and threats of forking cgminer and death threats. All right, perhaps not the last but the others.
Set it to 1% in example.conf file with a note to comment it out if donations aren't desired. I hope you're at least getting a reasonable trickle from those who do have it enabled.
January 17, 2012, 10:53:26 PM
Well good since I was using --submit-stale, merged mining, and was completely backwards on scantime, I'll consider that strike 3 for the day and just push the default button on cgminer...too bad --donation isn't default 
Heh, you know I tried to make --donation default but there was outrage and threats of forking cgminer and death threats. All right, perhaps not the last but the others. 
January 17, 2012, 10:51:11 PM
Well good since I was using --submit-stale, merged mining, and was completely backwards on scantime, I'll consider that strike 3 for the day and just push the default button on cgminer...too bad --donation isn't default
January 17, 2012, 10:28:36 PM
Yes siree, I do hate merged mining.
Yeah it does complicate things BUT I would argue that things are going to get more complicated anyways. Pools will eventually need to use to provide a mechanism to update miners when transactions change (when fees becoming more importantly). p2pool needs a method to track when the share chain has changed. Likely in the future there will be other as of yet implemented events which will require altering the work being done.
Using LP for everything is an ugly hack but it works. However what all this ugliness is pointing to is the fact that the pool-miner communication protocol needs to be more robust. Miners today are relatively "dumb" and rely too much on the server.
January 17, 2012, 10:15:23 PM
Yes siree, I do hate merged mining.
January 17, 2012, 10:13:49 PM
4) if you submit it you gain a valid share.
This. It won't be considered valid if I'm not mistaken.It depends on the pool. Some (most?) pools track validity of shares on each chain separately. I know on Bitminter for example after an LP due to NMC block change the share is still valid for BTC purposes (but not NMC).
A pool could handle multiple chains in three ways
a) only given credit for a share if it is valid for all chains
b) given credit if it is valid for master chain (BTC)
c) track each chain separately and give credit is it is a valid share for that chain (each chain has separate share count).
Slush uses method B. Bitminter uses method C. You are correct if the pool uses method A then there is no value in submit-stale option.
January 17, 2012, 09:55:55 PM
4) if you submit it you gain a valid share.
This. It won't be considered valid if I'm not mistaken. January 17, 2012, 09:54:20 PM
This will show you shares that might have otherwise been valid if you were not mining merged. cgminer does not submit them so your stale rate actually will not go up as DeathAndTaxes suggested unless you enable the --submit-stale option. (I don't suggest you do).
Any reason why?
Also background on why I recommend enabling "--submit-stale" for those who may not know is for the following scenario:
1) your find a BTC share
2) the pool detects a change in NMC block and issues an LP
3) if you discard the work you discard a valid BTC share
4) if you submit it you gain a valid share.
now if the LP is because BTC block is invalid then yes you are submitting a stale share but you don't lose anything. Instead of a SS locally you get a R but it doesn't negatively affect how many valid shares.
Jump to: