OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1

[iopq]

Hmm no idea what anyone else thinks, but I think it should be an array of pool details like:

Code:

"pools" : [
{ "http://server2.arsbitcoin.com:8344" : "user:pass" },
{ "http://arsbitcoin.com:8344" : "user:pass" }
],

I agree, I have no interest in matching indeces manually

[1713954730]

1713954730

[ancow]

Hmm no idea what anyone else thinks, but I think it should be an array of pool details like:

Code:

"pools" : [
{ "http://server2.arsbitcoin.com:8344" : "user:pass" },
{ "http://arsbitcoin.com:8344" : "user:pass" }
],

At least the "user:pass" won't work for usernames/passwords that contain colons. They at the very least need to be separated for such a config.

(For the record, I still prefer an XML/ini-format based solution; JSON is crap for configs.)

[BkkCoins]

Yes it would be nice if it was an array of objects but I didn't plan to rewrite the config parsing code completely. SO this is a minimal change patch to get something that works.

I'm working on a config writer feature now but after I'll see how much change is needed for an array of pool objects.

JSON is quite alright for the config since we have a required JSON decoder already linked in and I don't see a reason to bring in xml/ini modules just for this.

[iopq]

Hmm no idea what anyone else thinks, but I think it should be an array of pool details like:

Code:

"pools" : [
{ "http://server2.arsbitcoin.com:8344" : "user:pass" },
{ "http://arsbitcoin.com:8344" : "user:pass" }
],

At least the "user:pass" won't work for usernames/passwords that contain colons. They at the very least need to be separated for such a config.

(For the record, I still prefer an XML/ini-format based solution; JSON is crap for configs.)

it should be "pools" : [
{ URL : "http://server2.arsbitcoin.com:8344", user : "username", pass : "password" },
{ URL : "http://arsbitcoin.com:8344", user : "username", pass: "password" }
],

that allows you to specify other fields later

[kano]

Hmm no idea what anyone else thinks, but I think it should be an array of pool details like:

Code:

"pools" : [
{ "http://server2.arsbitcoin.com:8344" : "user:pass" },
{ "http://arsbitcoin.com:8344" : "user:pass" }
],

At least the "user:pass" won't work for usernames/passwords that contain colons. They at the very least need to be separated for such a config.

(For the record, I still prefer an XML/ini-format based solution; JSON is crap for configs.)

it should be "pools" : [
{ URL : "http://server2.arsbitcoin.com:8344", user : "username", pass : "password" },
{ URL : "http://arsbitcoin.com:8344", user : "username", pass: "password" }
],

that allows you to specify other fields later

True ...
Mine was a short cut (to make it easier to type) but mine isn't as clear either

(aside user:pass was fine unless you put a ':' in your username, but of course, again, separating all fields is better)

[BkkCoins]

Very good, thanks! Keep that up and I'll happily include the patches. Send them to me instead though, my email's in the readme. I'll let you tinker some more, as you're on a roll

Con,
I've emailed you a patch that adds proper array of objects multi-pool support and also adds a Write Config option on the settings menu. Both seem to work ok for me here in my limited testing.

Format for pools is as suggested above:

Code:

"pools" : [
    { "url" : "blah", "user" : "blah", "pass" : "blah" },
   ... etc 
   ],
etc

It writes in this format too and reads back ok for me. Probably some bugs in there but let me know I'll try to fix if it doesn't take my mining down for too long. Lost 4-5 hours today.

[The00Dustin]

I guess I should have said this yesterday, but if the pools need to be in arrays because users can't keep track of their pools and keep the usernames and passwords in order, then wouldn't the same thing be necessary for GPUs?  I don't really care either way and can deal with whatever (if I even start using a config file), but it seems confusing to me to have the pool parameters individualized and then not have the GPU parameters done the same way.

[BkkCoins]

I guess I should have said this yesterday, but if the pools need to be in arrays because users can't keep track of their pools and keep the usernames and passwords in order, then wouldn't the same thing be necessary for GPUs?  I don't really care either way and can deal with whatever (if I even start using a config file), but it seems confusing to me to have the pool parameters individualized and then not have the GPU parameters done the same way.

I think with the new code I wrote it will accept either way. I haven't really tested that but the way the array handling works it should treat them as consecutive values and they get set for devices in order. The current string method is easier since the code is already present and tested, and my config writer outputs them as a string not array.

I'm hoping that the "Write Config" option makes it unnecessary to hand write any config file anyway. You should be able to start cgminer, adjust values to suit and save the config. I'm adding some load default config code so that (on linux) I don't have to use "-c" at all and it will find the defaults. Then it's just a matter of saving the config when you want them to become default.

[Red Emerald]

So I have been running cgminer with --auto-fan and --gpu-engine 835,835,1020 for my rig.  Everything was working fine.  Then I rebooted and when I restarted cgminer, my hashrates act like they are standard clocks (980MHash instead of 1080) and I don't get any indication of fan speed (it used to say the rpms next to the hash rate).  I thought the problem might be related to going from 2.0.5 to 2.0.6, but switching to the older version didn't change anything. Any ideas as to why my flags are being ignored?

[DeathAndTaxes]

I like this

Code:

 "pools" : [ 
{ URL : "http://server2.arsbitcoin.com:8344", user : "username", pass : "password" },
{ URL : "http://arsbitcoin.com:8344", user : "username", pass: "password" }
],

Anytime a config is self descriptive is a good thing.

[jjiimm_64]

Firstly:  AWSOME PROGRAM.

I am sorry if this has been answered, but I could not find it. 

When manually changing the settings of the GPU.  The programs asks "Select GPU to change settings on:"  How do I select all gpus?  I tried all  a

I have 8 gpus per rig, so one at a time is not good. 

[DeathAndTaxes]

Firstly:  AWSOME PROGRAM.

I am sorry if this has been answered, but I could not find it.  

When manually changing the settings of the GPU.  The programs asks "Select GPU to change settings on:"  How do I select all gpus?  I tried all  a

I have 8 gpus per rig, so one at a time is not good.  

Not possible.  Just set them from the command line.  I just stop the miner change the batch file (which has all command line flags) and run it again.  Alternatively you can use a config file.

[jjiimm_64]

Thax DAT.  I just found this in the documentation:

All settings can all be changed within the menu on the fly on a
per-GPU basis.

[critical]

how do i set each gpu, a different  account name, because now 4 gpu seems to be mining on the same account name

[MadHacker]

how do i set each gpu, a different  account name, because now 4 gpu seems to be mining on the same account name

myself i think that is the best part...
however if u want to use 4 diffrent accounts i think u need to run 4 instances of CGMiner with the GPU specified

question. why would u want to run each gpu on a different account?
myself i think it simplifies things.

[jjiimm_64]

I am very interested in the pools part of the config file. 

How exactly do you manage pools with the config files with the current built version?  (not prepared to compile source at this juncture.)

[DeathAndTaxes]

how do i set each gpu, a different  account name, because now 4 gpu seems to be mining on the same account name

You can't.  Although this is one of the features I like the most about cgminer (it very effectively can keep 8 GPU continually "full" from a single worker account). Some older miners had difficulty requesting work fast enough and would result in times when one or more GPU was idle for a couple of clock cycles. 

I hated having 26 "workers" for each pool I used plus running multiple instances on miner software on same rig.
Now I have one worker and point all 26 GPU (across 5 rigs) at it.

[critical]

how about this, once detected, a gpu is SICK or DEAD, restart the whole cgiminer, can that be done?

[MadHacker]

how about this, once detected, a gpu is SICK or DEAD, restart the whole cgiminer, can that be done?

when a GPU is dead then it is posible that it is an ATI driver problem..
when you restart CGMiner, the whole system can lock up.
at least with gpu just marked as dead the rest of teh cards continue mining...
when i see a gpu dead... i just reboot the machine...

you can just log to file then every 5-10 minutes grep the file and check if the workd DEAD is there.
then just reboot your machine.

only problem i have is getting logging to work.
if i manualy execute the batch file that runs the cgminer then logging works.
however when i run the batch file from another batch file logging doesn't....
no clue as to why.

[abracadabra]

At least for me, whenever a GPU shows up as dead, a restart of cgminer ALWAYS works.

*shrug*