someone please tell me the best os for mining 
Linux, though it doesn't matter these days since most miners come with or expect images on controllers like the Rpi (all running linux.)
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 13. (Read 5805639 times)
August 20, 2017, 07:51:33 PM
August 20, 2017, 07:50:50 PM
someone please tell me the best os for mining
Linux, though it doesn't matter these days since most miners come with or expect images on controllers like the Rpi (all running linux.) August 20, 2017, 05:43:26 PM
someone please tell me the best os for mining
Linux, though it doesn't matter these days since most miners come with or expect images on controllers like the Rpi (all running linux.) August 20, 2017, 09:36:34 AM
someone please tell me the best os for mining
August 17, 2017, 08:02:20 AM
I try start CGminer with mining some coins,and command line dont show my hashrate,I dont know why,I have radeon r4 graphics.
Because cgminer hasn't been a GPU miner in many years. It only controls bitcoin mining ASICs. August 17, 2017, 08:01:21 AM
I try start CGminer with mining some coins,and command line dont show my hashrate,I dont know why,I have radeon r4 graphics.
August 14, 2017, 04:30:37 AM
And why not? Don't know what "no-submit-stale" means.
August 12, 2017, 10:03:53 PM
I'm not sure if someone is going senile or what,
BUT a reminder about cgminer:
NEVER set "no-submit-stale" : true,
like this guy did here:
https://bitcointalksearch.org/topic/m.20829032
Set it to: false
(or don't set it at all)
BUT a reminder about cgminer:
NEVER set "no-submit-stale" : true,
like this guy did here:
https://bitcointalksearch.org/topic/m.20829032
Set it to: false
(or don't set it at all)
August 08, 2017, 03:54:34 PM
Does every USB port have an ID that can be optained via cgminer in order to see which of your ASIC miners is broken?
No,they're assigned randomly by the operating system. August 08, 2017, 01:47:23 PM
Does every USB port have an ID that can be optained via cgminer in order to see which of your ASIC miners is broken?
August 05, 2017, 01:12:59 PM
Every 2 minutes or so the device reports a nonce error.
What is the definition of such a nonce error? Why does it happen?
What is the definition of such a nonce error? Why does it happen?
August 02, 2017, 08:00:38 AM
isdupnonce() tests whether a found nonce was already found.
I wonder under what circumstances such a dupe nonce ever can happen at all.
Can it ever happen with solo mining?
I wonder under what circumstances such a dupe nonce ever can happen at all.
Can it ever happen with solo mining?
July 31, 2017, 11:06:49 PM
I am not ck but the answer to that question is:
you can use older cgminer Versions, but not an old core version.
So you need as minimum core version 14.0.0 (Segwit support)
AND
you have to add a patch to it so you are not building up on wrong blocks!
Can -ck confirm this please?you can use older cgminer Versions, but not an old core version.
So you need as minimum core version 14.0.0 (Segwit support)
AND
you have to add a patch to it so you are not building up on wrong blocks!
July 31, 2017, 11:04:47 PM
I am not ck but the answer to that question is:
you can use older cgminer Versions, but not an old core version.
So you need as minimum core version 14.0.0 (Segwit support)
AND
you have to add a patch to it so you are not building up on wrong blocks!
Can -ck confirm this please? you can use older cgminer Versions, but not an old core version.
So you need as minimum core version 14.0.0 (Segwit support)
AND
you have to add a patch to it so you are not building up on wrong blocks!
July 31, 2017, 10:03:44 PM
Just registered to chime in as I happened to be running into this myself and had thought it might be a quirk from compiling/running with MacOSX. I haven't done much digging into it, and when I get a chance I'll try the debug backtrace mentioned already. I can also confirm that on my system the problem arises between 4.9.2 and 4.10.0 releases.
In case it might be useful to those more familiar with the code, a few crude tests by way of re-building seem to isolate the problem to setting '--enable-icarus' during configuration. That is, including all of the non-standalone drivers minus icarus seems to have a functioning write_config on my system. So do not think this is something to do with all parsing/writing for settings, but may be specific to one or more introduced with icarus support.
Sounds feasible. It's likely to be missing save for the options added to icarus post 4.9.2In case it might be useful to those more familiar with the code, a few crude tests by way of re-building seem to isolate the problem to setting '--enable-icarus' during configuration. That is, including all of the non-standalone drivers minus icarus seems to have a functioning write_config on my system. So do not think this is something to do with all parsing/writing for settings, but may be specific to one or more introduced with icarus support.
Hmm, I think I found it after that suggestion - it looks like a line is needed in the write_config of cgminer.c for the newly introduced 'set_float_100_500', such as at L5459:
if (opt->type & OPT_HASARG &&
((void *)opt->cb_arg == (void *)set_float_125_to_500 ||
(void *)opt->cb_arg == (void *)set_float_100_to_500 ||
(void *)opt->cb_arg == (void *)set_float_100_to_250)) {
fprintf(fcfg, ",\n\"%s\" : \"%.1f\"", p+2, *(float *)opt->u.arg);
continue;
}
This was necessitated upon expanding the Compac GekkoScience frequency range here: https://github.com/ckolivas/cgminer/commit/702b37007caa9605d3adabf646f8df47fe86e83c
Making that change now has config writing when setting '--enable-icarus' during configuation for me.
July 31, 2017, 09:38:52 PM
Just registered to chime in as I happened to be running into this myself and had thought it might be a quirk from compiling/running with MacOSX. I haven't done much digging into it, and when I get a chance I'll try the debug backtrace mentioned already. I can also confirm that on my system the problem arises between 4.9.2 and 4.10.0 releases.
In case it might be useful to those more familiar with the code, a few crude tests by way of re-building seem to isolate the problem to setting '--enable-icarus' during configuration. That is, including all of the non-standalone drivers minus icarus seems to have a functioning write_config on my system. So do not think this is something to do with all parsing/writing for settings, but may be specific to one or more introduced with icarus support.
Sounds feasible. It's likely to be missing save for the options added to icarus post 4.9.2 In case it might be useful to those more familiar with the code, a few crude tests by way of re-building seem to isolate the problem to setting '--enable-icarus' during configuration. That is, including all of the non-standalone drivers minus icarus seems to have a functioning write_config on my system. So do not think this is something to do with all parsing/writing for settings, but may be specific to one or more introduced with icarus support.
July 31, 2017, 09:34:50 PM
Is it only me or others also constantly getting messages about testing pool on solo mining?
One more issue to mention, 4.10.0 does not write config file and does not load working in v.4.9.2 (and pretty trivial one) config file.
One more issue to mention, 4.10.0 does not write config file and does not load working in v.4.9.2 (and pretty trivial one) config file.
Dear CK,
I am experiencing a Segmentation Fault (core dumped) error when trying to write config file in version 4.10.0. (I do not have this error with version 4.9.2).
(it seems to write over cgminer.conf with an empty file, then crash)
I am running on R-PI, ARCH.
Any advice?
Thanks!
I am experiencing a Segmentation Fault (core dumped) error when trying to write config file in version 4.10.0. (I do not have this error with version 4.9.2).
(it seems to write over cgminer.conf with an empty file, then crash)
I am running on R-PI, ARCH.
Any advice?
Thanks!
This didn't seem to get any kind of acknowledgement. I'm following it up here to see if anyone can help??
Just registered to chime in as I happened to be running into this myself and had thought it might be a quirk from compiling/running with MacOSX. I haven't done much digging into it, and when I get a chance I'll try the debug backtrace mentioned already. I can also confirm that on my system the problem arises between 4.9.2 and 4.10.0 releases.
In case it might be useful to those more familiar with the code, a few crude tests by way of re-building seem to isolate the problem to setting '--enable-icarus' during configuration. That is, including all of the non-standalone drivers minus icarus seems to have a functioning write_config on my system. So do not think this is something to do with all parsing/writing for settings, but may be specific to one or more introduced with icarus support.
July 31, 2017, 11:58:19 AM
Hey, it's been a while but I'm going to finally update the compiled version of cgminer for mac I distribute and update MacMiner with it (the link you provide for Mac versions only goes up to 4.3.3 btw, I distribute mine at http://macminer.fabulouspanda.com/commandline/cgminer/ )
Since it's been so long, could you please let me know which devices I can --enable for maximum support without causing any conflicts?
Sorry to be an idiot, found the readme suggesting
--enable-avalon
--enable-avalon2
--enable-avalon4
--enable-bflsc
--enable-bitfury
--enable-cointerra
--enable-drillbit
--enable-hashfast
--enable-hashratio
--enable-icarus
--enable-klondike
Sorry to be an idiot, found the readme suggesting
--enable-avalon
--enable-avalon2
--enable-avalon4
--enable-bflsc
--enable-bitfury
--enable-cointerra
--enable-drillbit
--enable-hashfast
--enable-hashratio
--enable-icarus
--enable-klondike
July 29, 2017, 01:48:05 PM
I am not ck but the answer to that question is:
you can use older cgminer Versions, but not an old core version.
So you need as minimum core version 14.0.0 (Segwit support)
AND
you have to add a patch to it so you are not building up on wrong blocks!
you can use older cgminer Versions, but not an old core version.
So you need as minimum core version 14.0.0 (Segwit support)
AND
you have to add a patch to it so you are not building up on wrong blocks!
July 29, 2017, 01:17:24 PM
Is it only me or others also constantly getting messages about testing pool on solo mining?
One more issue to mention, 4.10.0 does not write config file and does not load working in v.4.9.2 (and pretty trivial one) config file.
One more issue to mention, 4.10.0 does not write config file and does not load working in v.4.9.2 (and pretty trivial one) config file.
Don't know if related, but the parameter --fix-protocol seems to prevent switching from gbt to stratum if the http server offers both.
Regarding the other issues: don't know, haven't tried yet; I'm passing all parameters via commandline (actually in a batch script file).
I see the release notes for 4.10.0 regarding the segwit support, but it has memory leak in windows build in solo mode and I would prefer 4.9.2 to continue to use.
Theoretically, segwit could be implemented totally in bitcoin core, under the RPC calls so that the miner software would not need any changes to support it. My question (and my setup in general) is for learning purposes mainly.
So do I get correctly, that cgminer 4.9.2 does not have (requiring) segwit support and blocks found would be discarded now?
Many thanks.
Jump to: