I've upgrade a *potential* fix for the phatk kernel in here:
http://ck.kolivas.org/apps/cgminer/temp
Make sure to right click on phatk110817.cl and choose save link as to avoid your browser turning into html falsely. 79x0 Try replacing the file with that one with the new exe and see if that submits valid shares...

I like the fact, that with Phoenix I don't have to fiddle around with a compiler, headers, paths and so on. I can edit a plain text file to change things I need for initialisation (even if I dislike Python ^^) and simply start phoenix.exe without recompiling after every small change + I can redistribute my changes without the need for a new executable.

In no way I want to say Phoenix is better or worse than CGMINER (I know you work hard and do a great job), but for the things I do it's easier for me to use Phoenix .

Dia

You only would need to compile and shit if you change the API. If the API is static and you're just fiddling with the cl code, modify the cl file, just delete any .bins generated and start the app again.

Thanks again Con!

As he reported, the windows .exe is working perfectly on my windows box with a 5970 -- reporting fan RPMs for both GPUs.  Pulling from git also fixes that on my dedicated linux miners.

On a completely different side of things - regarding the USB install script that I wrote that's with cgminer (that's always in my sig also)
For the 3rd time in 6 months having to redo it (so yeah only 2 failures in 6 months seemed pretty good actually) I finally had it just keep messing up on me while trying to make the 3rd one.

So I worked out why there are problems with it for some and am working on a new version of the script.
(the problem details were found googling something rather non-obvious!)

Note of course that the current version includes (at the end) the details to do an HDD install - and that is basically how the new version will work, but onto a USB.

It seems that the problems with the USB creator program have been known for 4.5 years (f#&king hell that long!) and still they haven't bothered to fix them!
Basically there are 2:
1) The USB key is ejected during shutdown and some (most?) BIOS's don't reinitialise the USB during a restart, only (of course) during a power off and on, so it's random if it actually works on a reboot or not
2) The casper filesystem (that's the persistent storage) often doesn't properly write all changes to the casper file (yeah I've seen that happen on rare occasions with small system settings) and that can even sometimes mess up the whole USB - like it did for me the other day.

Anyway after failing over and again with a new USB, I ran a full check of the 2nd one that had just failed and found the USB itself was 100% OK just the data was messed up.
So I used that one instead with the new procedure and it is working (and rebooting) fine without any problems or errors.

I'll have it finished (documented) in the next few days and that should hopefully get rid of the biggest issue with the USB install for most people who have had problems with it and don't know why.

Did it lower just the 5830 or did the 5970 individual hash rates drop also.  Each model has different # of ALU and thus respond differently to differently to changes in vector & work size.    Really all the v & w flags are doing is trying to optimize the # of ALU used in each clock cycle.  So if the 5970 rose but 5830 tanked it likely is just due to chip differences.  There is no "perfect" setting as each chip has different # of ALUs.

If the 5970 individual hashrate dropped on Win7 and rose on Linux then provide the driver & SDK versions used on both platforms.  It most likely is driver/SDK dependent.

I noticed it immediately on the 5970's.  down to like 320ish.  I think the 580 was lower too but was inconsequential since the clock on the box is 800/300 for all cards. ( I bump the 5830 up manually if I feel like it )

I noticed it immediately on the 5970's.  down to like 320ish.  I think the 580 was lower too but was inconsequential since the clock on the box is 800/300 for all cards. ( I bump the 5830 up manually if I feel like it )
[/quote]

jjimm64: where do you put the -v -w 256 - I have 15 5870s and would like to try this , when I use -v -w 256 with cgminer it does load for me

thanks!

After the pool logon's and before CGMiner specific switch's.  Also my 5830 would only accept -w 128 NOT -w 256.  So you may have to specify each GPU independently if your 5970 does accept it but 58xx doesn't.
Sam
[/quote]

I put the flags in the conf file. 

"vectors" : "2",
"worksize" : "256",