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

[kano]

Does the API actually reorder the pools or just change the priority?  I don't see any need for the pools to be reordered, I'm just curious.  In fact, if I have pools 1,2,3,4 and they are at default priority but I want to make the priority order 3,2,4 with 1 disabled, I simply disable 1 from the UI and then set 3 to priority 0. A t this point, the priority order is technically 3,1,2,4, but 1 is disabled, so it's fine.  Once one is familiar with the priority changing it should never take more priority changes than you have pools in order to achieve the priority he wants.

The API currently just changes the priority of a single chosen pool to '0' and enables it.
(Just like the switch command in the keyboard interface)

[omo]

I'm interested in AMDOverdriveCtrl  you talked about,
I downloaded the package and find out that it is a GUI software,
I wonder if it can be used remotely to control clock/voltage?

[DeathAndTaxes]

I'm interested in AMDOverdriveCtrl  you talked about,
I downloaded the package and find out that it is a GUI software,
I wonder if it can be used remotely to control clock/voltage?

AMdOverdriveCtrl can't change anything that cgminer can't.  
cgminer already gives you remote access to clock/voltage/fan/inensity/etc.

This to answer the question while AMDOverdriveCtrl has a GUI component it can also be used from the command line (like bitcoin vs bitcoind) so you could control it remotely via scripts, web applications, etc.

However given cgminer does everything and already has an API ...

[kano]

I'm interested in AMDOverdriveCtrl  you talked about,
I downloaded the package and find out that it is a GUI software,
I wonder if it can be used remotely to control clock/voltage?

AMdOverdriveCtrl can't change anything that cgminer can't.  cgminer already gives you remote access to clock/voltage/fan/inensity/etc.

Straight from my script:

14) An OC option:
 This is no longer needed since cgminer 2.* includes OC, however:

[QuantumFoam]

A number of niggling issues cause drop in hashrate over longpolls and network outages in 2.2.7. Fixed in next version.  Hold on to your hats...

Awesome. I'll wait to see how the next version reacts to the main pool going offline and back online multiple times per minute.

[DeathAndTaxes]

A number of niggling issues cause drop in hashrate over longpolls and network outages in 2.2.7. Fixed in next version.  Hold on to your hats...

Awesome. I'll wait to see how the next version reacts to the main pool going offline and back online multiple times per minute.

While hopefully the next version works better,  why would you mine at a pool that goes offline once a day much less multiple times per minute?

I mean even if cgminer handles the drop perfectly you are still looking at a massive drop in aggregate output.

[stevegee58]

If your primary is p2pool it won't go down at all anyway (unless your p2pool client crashes).

[QuantumFoam]

While hopefully the next version works better,  why would you mine at a pool that goes offline once a day much less multiple times per minute?

I mean even if cgminer handles the drop perfectly you are still looking at a massive drop in aggregate output.

It doesn't always do that, it does it when the server has issues or when the pool ops are working on it. I completely agree with the aggregate output part, that's why it would be nice to have an option that would kick over to the backup pool for a while instead of constantly trying to submit work to a failing main pool.

As for why I continue to mine at this pool, it is because it pays ~140% pps.

[bulanula]

While hopefully the next version works better,  why would you mine at a pool that goes offline once a day much less multiple times per minute?

I mean even if cgminer handles the drop perfectly you are still looking at a massive drop in aggregate output.

It doesn't always do that, it does it when the server has issues or when the pool ops are working on it. I completely agree with the aggregate output part, that's why it would be nice to have an option that would kick over to the backup pool for a while instead of constantly trying to submit work to a failing main pool.

As for why I continue to mine at this pool, it is because it pays ~140% pps.

What pool is that

[P_Shep]

Anyone have cgminer compiles for windows with cpu mining enabled?... want to do some testing.

[QuantumFoam]

it is a fairly well known one on here but running in beta right now (hence the server problems). I am being vague due to the inflammatory nature of > 100% pps on this forum in the past and don't want to derail this thread.

[leveer]

Any chance the pool settings could be stored in a separate configuration file? It would sure make changing those in bulk/on multiple rigs a lot easier, when my pool preference order changes... distribute one pools.conf to each rig.

It also would be nice to have an ability to re-order pools from within cgminer.

I've got 3 BTC in bounty for each.

Can I have the 2nd one
With the API, you simply move any pool of choice to position 0 (highest priority).
The number of moves to get the required order is at maximum, the number of pools.
How many pools do you have anyway?

Frankly, I have no idea how to use the API. Have started cgminer with the --api-listen command, and can get 127.0.0.1:4028 to return a file called "download," but that's as much as I can get. Would prefer to use miner.php based on the description, but opening it in a browser just yields the text contents of the file...

EDIT: Notably, using Windows...

Well you can actually do it from within cgminer anyway:
Press "P" for Pool management
"S" for Switch pool
and then the number of the pool -> this will make it the top priority pool

So if you have pools 0, 1 & 2 but want the priority to be 2, 1, 0
You would first switch to 1 then switch to 2

As for the other half
I've just put up a pull request to ckolivas (after I asked him if he was interested in it - he said no)
to allow one "include":"filename" in the json file (which is allowed to be recursive - up to 10 times - to avoid infinite loops)
It's simple and will not be made more complex.

If you save the configuration from within cgminer, the output will contain ALL settings (except will not contain the "include" setting)
The reasoning behind this is that if you change anything within cgminer, there could be complex multiple definition issues and all settings loaded and changed would need attributes about where they came from and if they were changed - way too complex.
Also, if you set a setting within cgminer that was in an included file, the included file would always override it, your setting would never stick.

Separating just the pools and only having them in their own file would be a backward compatibility problem.

Hopefully the simple solution is enough, coz I can't see a more complex version ever being implemented (since it would require a major redesign of how configuration settings are handled within cgminer)

We'll see if he allows it in or not

3 sent for 2 half solutions. Thanks!

[bulanula]

it is a fairly well known one on here but running in beta right now (hence the server problems). I am being vague due to the inflammatory nature of > 100% pps on this forum in the past and don't want to derail this thread.

Does it start with G ?

I think some people are having loads of issues with cgminer and that pool you are talking about so I think this is pretty on topic.

Maybe there is some networking / share submitting bug in cgminer that is not in phoenix that only affects pool G ?

[kano]

...
Hopefully the simple solution is enough, coz I can't see a more complex version ever being implemented (since it would require a major redesign of how configuration settings are handled within cgminer)

We'll see if he allows it in or not

3 sent for 2 half solutions. Thanks!

3 BTC received - thank you very much
ckolivas also accepted the pull request so it's in the master git also.

[P_Shep]

Just wondering... is there an issue with the way cgminer caches work?
I don't know what goes on inside, but one plausable explanation to what I'm seeing is:
CGM gets work from all pools.
When Primary pool goes down, work starts on the secondary.
But CGM doesn't get new work, uses what is has, which is old.
Old work submitted, and promptly rejected.

Alternatively:
When Primary pool goes down, work from that pool is submitted to the secondary pool.

Any of these scenarios occur? Because my secondary and tertiary pools end up with a greater number of rejected shares, than accepted.

[phorensic]

it is a fairly well known one on here but running in beta right now (hence the server problems). I am being vague due to the inflammatory nature of > 100% pps on this forum in the past and don't want to derail this thread.

Does it start with G ?

I think some people are having loads of issues with cgminer and that pool you are talking about so I think this is pretty on topic.

Maybe there is some networking / share submitting bug in cgminer that is not in phoenix that only affects pool G ?

I mine on pool "G" with the aforementioned ~140% pps    Yes, it is in beta.  Yes my cgminer will fall back to my BTC Guild often.  However, it tends to fall back gracefully.  Not sure which problems others are having?  The developer of pool "G" is making changes to his servers all the time.  He announces them in the thread with pretty clear warnings that the service will be up and down....BECAUSE IT IS BETA!!!111one

[QuantumFoam]

The original point was cgminer choking when the pool goes up and down frequently/multiple times per minute. I understand that the pool is in beta, I just want to improve the problem of cgminer getting hung up when the server runs into problems.

[johnyj]

I'm interested in AMDOverdriveCtrl  you talked about,
I downloaded the package and find out that it is a GUI software,
I wonder if it can be used remotely to control clock/voltage?

AMdOverdriveCtrl can't change anything that cgminer can't.  cgminer already gives you remote access to clock/voltage/fan/inensity/etc.

Straight from my script:

14) An OC option:
 This is no longer needed since cgminer 2.* includes OC, however:

I use AMDoverdriveCtrl for 2 reason:

1. I want cgminer to focus on the mining without caring about the GPU management, it will be much easy to trouble shooting when something went wrong

2. The fan speed control of AMDoverdriveCtrl is more convenient to use. In cgminer, the fan speed keeps shooting up and down, lagging the real change in GPU temperature

Actually I did build cgminer once without ADL_SDK, but then I'm not able to see the GPU info, especially when doing ssh into the machine. So the function  of monitoring the GPU is still very useful

[-ck]

New version: Version 2.3.0 - February 23, 2012

Human readable summary:
New kernels across the board, including Diablo kernel. Selection is carefully designed to be optimal by default according to device and SDK combination.
Much better coping with SDK 2.6 so it no longer warns excessively about it, but note it's STILL faster with most cards on earlier SDKs.
Fixed the huge dip in hashrate with all the extra longpolls.
Fixed the number of extra longpolls during pool switch.
Hopefully fixed the device OFF problem.
Added Icarus FPGA support.
Can set kernel, vector and worksize per device now with -k diablo,phatk,phatk,poclbm -v 2,2,2,1 -w 128,256,256,64 for example
Hashrate at startup should be more meaningful sooner.
New --benchmark feature to test hashrate. Leave it running for ~3 mins to get reliable results, then quit and check the summary! Great for testing multiple same devices with different kernels, vectors etc. Produces NO HASHES so don't leave it running  
Engine clock speed should ramp up instantly after a period of network outage which drops the profile to low power.
New API commands for pool management.
Fixes to API code to shut down cleanly.


Full changelog:
- Consider extra longpoll work items as staged_extra so as to make sure we queue
more work if queueing regular work items as longpolls.
- Use diablo kernel on all future SDKs for Tahiti and set preferred vector width
to 1 on poclbm kernel only.
- Explicitly type the constants in diakgcn kernel as uint, to be in line with
poclbm kernel.
- Reset all hash counters at the same time as resetting start times to get
accurate hashrates on exiting which is mandatory for benchmarking.
- Report thread out before it starts to avoid being flagged as sick when waiting
for the first work item.
- Don't disable and re-enable devices as they may recover and in the meantime
have their status set to OFF.
- API new commands enablepool and disablepool (version already incremented)
- Tolerate new-format temperature readings for bitforce
- Modify cgminer.c pool control to allow API to call it
- Bugfix: Fix BitFORCE driver memory leak in debug logging
- Extra byte was being unused in poclbm leading to failure on some platforms.
- Explicitly type the constants in poclbm kernel as uint.
- Don't save 'include' when saving the configuration
- Allow configuration file to include another recursively
- Use the SDK and hardware information to choose good performing default
kernels.
- Move phatk kernel to offset vector based nonce bases as well.
- Add a --benchmark feature which works on a fake item indefinitely to compare
device performance without any server or networking influence.
- Allow writing of multiple worksizes to the configuration file.
- Allow writing of multiple vector sizes to the configuration file.
- Allow writing of multiple kernels to the configuration file.
- Allow multiple different kernels to be chosen per device.
- Allow the worksize to be set per-device.
- Allow different vectors to be set per device.
- If we're well below the target temperature, increase gpu engine speed back to
maximum in case we have gotten lost between profiles during an idle period.
- We should be setting the value of fan_optimal, not its address.
- As all kernels will be new versions it's an opportunity to change the .bin
format and make it simpler. Specifying bitalign is redundant and long can be l.
- Use any() in kernel output code.
- Put the nonce for each vector offset in advance, avoiding one extra addition
in the kernel.
- Reset times after all mining threads are started to make estimating hashrates
easier at startup.
- Bugfix: allow no-exec (NX) stack
- Fix minor warning.
- fix the bitforce.c code style follow 1TBS
- fix icarus.c compile warning
- small changes to speedup no vec for AMD 898.1 OCL runtime
- Update licensing to GPL V3.
- Reset the longpoll flag after it's been used once to prevent it restarting
work again.
- Begin import of DiabloMiner kernel.
- Modify API debug messages to say API instead of DBG
- When API shuts down cgminer don't kill itself
- Don't make rolled work from the longpoll be seen as other longpoll work items.
- API add 'privileged' command so can verify access level
- Set the lp_sent variable under lock since there will almost always be a race
on setting this variable, potentially leading to multiple LPs being sent out.
- API restrict access to all non display commands by default
- Update API version to 1.2 for new 'Log Interval'
- API add --log Interval to 'config' reply
- --api-allow special case 0/0 means all

[Vbs]

New version: Version 2.3.0 - February 23, 2012

Thanks for the update mate, but this version doesn't compile a bitalign kernel for my cards (5850's), it's the non-bitalign kernel which is much slower (~320MH/s vs ~400MH/s).

Copying over the bin from the previous version and renaming it from "phatk120213Cypressbitalignv2w256long4" to "phatk120222Cypressv2w256l4" doesn't work also (HW failures).