Git tree currently doesn't set auto gpu features properly on >1 card. Waiting on someone to git bisect the exact commit responsible before I can move forward with this code to a new release.

sudo aticonfig --initial --adapter=all

As I said...

It will take a new kernel to work.

Specifically I suspect you'd need to disable bfi int patching and play with vectors and worksize

Probably in ocl.c this line 320:
      clState->hasBitAlign = patchbfi = 1;
would need to become:
      clState->hasBitAlign = 1;

Then  you'd need to start with something like -v 1 -w 64

To do this cleanly I'd need to play with the hardware myself to detect if/when it should do this and so on... and I don't.

cgminer has no support for 79xx yet.

It already searches for it in the current directory. You want yet more paths to be checked?

Sounds like orc mischief to me! They come with fire, they come with axes, gnawing biting hacking breaking burning. Destroyers and usurpers, curse them!

Regardless of what this error looks like, try to solve it the same way you would if you had 4 cards installed but cgminer only worked on one. It just so happens that the ATI display library is getting the right number of cards, but the ATI driver is only giving you 1 for opencl use for some reason.

Some devices only report fan percent, not RPM. cgminer tries to report the RPM but only if it's supported by the device, and then defaults back to percentage if it supports that.

Good idea.

I'd say the votes are pretty conclusive. Thanks everyone for your input. For simplicity I'll be making it a compile time selection for now, default off. This has already been committed to the git tree and will be in the next version. I will no longer be releasing binaries with CPU mining support built in and if it proves innocuous in this fashion, it will be left that way. Should issues arrive, it will be deprecated entirely in a future version.

No, I didn't ask for donations to get one and I don't own one and I have no idea what's required to get one working or optimised. As far as I can tell, by default, it won't even run on cgminer. That said, there is someone who offered to tune "for diablominer and cgminer" who got paid megaBTC to buy one for himself who promised to do so. Having said that, I have yet to see any code for cgminer out of it...

At the moment I don't even have a machine that can mine on GPU. Eventually should nothing come from an outside source, I will do the work myself to get 79xx working.

This is most certainly not intentional and I cannot do anything about it since cgminer consciously changes settings back to default, but windows decides that cgminer should crash every time instead.

Massively updated git tree (new minor version coming soon):

    Display what support is built in.

    BitForce FPGA support
   
    cgminer will scan for and mine BitForce FPGAs on USB ports by providing the
    new --scan-serial <device> option, or autodetect them by searching
    /dev/serial/by-id for *BitFORCE_SHA256*

    Update copyright dates.

    Update README.

    Configure out building and support of all CPU mining code unless --enable-cpumining is enabled.

    Add configuration option for CPU mining which will default to off.

    Update example conf with 1% donation.

    Allow parsed values to be zero which will allow 0 values in the config file to work.

    Advertise that we can make our own midstate, so the pool can skip generating it for us

    Refactor the CPU scanhash_* functions to use a common API. Fixes bugs.
   
    - Before, some returned bool, and others returned int (which was then turned
      into a bool with a comparison); now, everything returns a bool
    - Before, some set hashes_done to nonce - 1 when a share was found and others
      set it to nonce + 1 or 2. This caused some algorithms to scan/submit shares
      twice with the new cpu_scanhash function. Now, it has all been replaced with
      last_nonce, which is set to the final nonce checked by the scanhash_* func.
    - VIA needs the full data, and cannot use midstate. All the others were
      expecting midstate and data+64 for their parameters. Now, we pass midstate
      and the full data pointer, and let the scanhash_* function choose which to
      use.

    Don't consider a pool lagging if a request has only just been filed.
    This should decrease the false positives for "pool not providing work fast enough".

    Invalidating work after longpoll made hash_pop return no work giving a false positive for dead pool.
    Rework hash_pop to retry while finds no staged work until the abstime timeout really expires.

    Remove TCP_NODELAY from curl options as many small packets may be contributing to network overload.

    Refactor miner_thread to be common code for any kind of device
   
    This expands on the device API, by taking the actual main thread out of the
    device's code, and calling the API only for specific tasks. This brings
    various changes that were made to the GPU thread code into the CPU miner.
    It also fixes a bug where shares found on old GPU work were discarded when
    it switched to a new work.

    Simplify submit_nonce loop and avoid potentially missing FOUND - 1 entry. Reported by Luke-Jr.

    Micro-optimisation in sha256_sse2 code courtesy of Guido Ascioti guido.ascioti@gmail.com

    Typo in readme.

   Refactor to abstract device-specific code

The volt config bug is fixed in git. Same with any value that is zero.

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.

Ohhh now I see it in my wallet instead, lol. Thanks!

From the land of rhetorical questions  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):
<conman> !worker ckolivas.donation
<ozco> Worker ckolivas.donation hashrate is 401 is active: yes and is being monitored: no

Yes, thanks!  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 

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.

Yes siree, I do hate merged mining.