Try combinations manually with other vectors and worksize, -v 1, -v 2, -v 4, -w 64 -w 128 , -w 256
But if it fails by default there's a good change it's simply broken for now.

Oh and start it with -D -T and post output please?

I hope you deleted any .bins first. That means it's not working at all then. Oh well guess I wait till I get one myself to figure out wtf is wrong.

I committed a little more 79x0 specific code and built a windows binary. Again, no idea if it works, nor if it performs, but here is a windows build:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

Just drop it into a 2.1.2 directory, replacing the existing exe.

I committed a little more 79x0 specific code and built a windows binary. Again, no idea if it works, nor if it performs, but here is a windows build:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

Just drop it into a 2.1.2 directory, replacing the existing exe.

That's fantastic thanks so much 

I committed a little more 79x0 specific code and built a windows binary. Again, no idea if it works, nor if it performs, but here is a windows build:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

Just drop it into a 2.1.2 directory, replacing the existing exe.

Not at all. I think you may have discovered the cause of yet another random unexplained failure that has yet to be mentioned on this thread.

Default intensity is actually dynamic which is designed for regular desktop use, so the intensity needs to actually be set to -I 9.

I'll try and find access and time to get a windows binary tomorrow.

Thanks. The GCN compatible phatk kernel that's in the tree should be even faster than that hardcoded poclbm which is reassuring... assuming it works as planned  Alas building on windows is an absolutely pain in the arse and as I've said before even I can't remember what I installed in the end to get it building  I'll see if I can build one maybe tomorrow.

You didn't happen to change driver versions between moving from guiminer to cgminer?

Maybe. That's what I was wondering about too. The perennial mining favourite, the GD70.

Take a good look at the pic of the case being used:
http://ck.kolivas.org/pictures/Mining/IMG_1048.JPG

(ignore the crossfire bridges, they've been removed).

All the heat in that case goes out vertically upwards with reference cards that blow in that direction.
The case fan underneath is 180mm (there are 2) and blows directly into the cards with no obstruction whatsoever when closed.
The PSU is not even effectively *in* the case, having its own section so not contributing to case heat nor having to suck any heat out of its own accord.
The back is massively ventilated as well.
The case is a full sized tower, not a mini or midi tower.
The cards have spacers between them as shown in the earlier photo.
All the cards have their memory underclocked to exactly 125 below their optimal engine clock speeds (the cards run engines from 950-1005).
The cards were ordered so that the fastest ones were put in slot 0 and 3 since they generated the most heat they needed the best ventilation.
cgminer basically ran in all its auto settings to keep the fans running optimal.
Virtually all GPU fans ran in the 45-75% range during winter and most ran at 85% in summer (none ever needed to go to 100%), yet the temps were targetted and kept at 75 degrees.
This is all I can remember offhand.


...All in all this is a purpose built rig with a lot of thought into making it work within a case, and the case was carefully chosen. It is not just components slapped together. It ran 6 months without a single hiccup. What *has* taken this rig down, though, is a dead motherboard. Not sure what I could have done to prevent that one though.

This should be fixed on the next version (which is still a work in progress) and it will be more relaxed about typos/dud entries and skip over them.

I Heartily Endorse This Event Or Product

http://www.youtube.com/watch?v=lsiuxim8vsM

But seriously, wow, thanks! Though I'm partial to Sapphire cards, I guess I really shouldn't complain at all. These things cost 700+ dollars in .au where I am so I still wouldn't dream of buying one for myself.

http://www.pccasegear.com/index.php?main_page=index&cPath=193_1309

Great!

They're... pegs... as in clothes pegs, for a clothes line. I just pulled them apart. You get them... everywhere and these particular ones are made of... plastic.

I believe the standard defines 1.5cm of movement or something like that. This is only .5cm yet makes a massive difference to temperatures.

And this is why cgminer peaks autofan at 85% and reserves 100% only for overheat situations.

False positive for picking up twin cards is a problem. False negative is not. Anyway I need access to more hardware to see what else I need to do.

Well, after much poking and prodding and asking on forums and scouring APIs and lots of ridiculous documents, I can see there is no official way to tell that two GPUs on a dual GPU card belong to the same device. There is nothing shared between the two. However, having access to an actual device I was able to come u p with the following. This has been committed to the git tree:

Detect dual GPU cards via the indirect information of - 1st card has a fan controller. 2nd card does not have a fan controller, cards share the same device name, and are one bus ID apart. Use this information to create paired devices, displaying the fan speed on both devices and using the hottest temperature from either GPU to control the overall fanspeed.

I have confirmed this works on 5970s. Next would be the 6990s...

Now I better get some sleep 

Well, I think I've gotten the current cgminer git tree to support 79xx cards, but I have no one to test them. I certainly am not expecting any kind of magic performance out of the box. Anyone not afraid to try a git build care to give it a go? At this stage I'd at least like it to actually work rather than produce garbage which the current stable release does.