If you have to mix and match, use 5xxx/61xx-67xx and 68xx-69xx OR 79xx. That way you can match sdk's to their optimum card. 2.1 works best with 5xxx/61xx-67xx, 2.4/2.5 works best with 58xx-69xx (2.1 is incompatible), and 2.6 sucks but is required to make 79xx work. You can also install 2.1 plus 2.4 OR 2.5 OR 2.6. You can't have any combo of 2.4, 2.5, and 2.6 installed in the same system because they install to the same path.

Do NOT combine 79xx cards with 68xx-69xx cards; you will lose mhash on your 68xx-69xx cards because you'll be requires to use 2.6 to use 79xx, which also is much slower than 2.4/2.5 for your 68xx-69xx.

I've had issues with pci-e ribbon cables; it's really cold here in wisconsin and I have a miner outside. I had one GPU causing system freezes whenever a load was applied to it. Figures that it was the PCI-E cable. I switched it with another and it worked fine after. When I brought the cable inside, 1 of the wires had disconnected from the pcb. I tried investigated where exactly it disconnected and a bunch more wires ripped off the pcb. Gotta love that chinese quality.

Thanks!

CFSWorks, could you please verify the crc of current windows build of phoenix.exe is 89B9736A ? I keep getting told that the windows build was updated but i'm just not seeing it because the "new" and "old" crc32s are identical, so I don't believe anything was updated/changed.

oh, and I was just going to test this kernel too to see what the hell goffset did for hashes

It may be within 1% performance (see 1% slower), but it also requires using a lot more power than necessary because it requires more electricity to drive memory at 1ghz than 300mhz. 2.1 should still be used when possible, else 2.4/2.5. 2.6 is a last resort.

Are you sure you didn't upload the same exact files as what was up before? I redownloaded and the crc for the "old" phoenix and the "new" phoenix is the same. This also goes for the .zip file itself.

The CRC32 of my copy of phoenix.exe is 89B9736A. The copy inside the zip file I downloaded 20 seconds ago is also 89B9736A and I still get the hash rate bugging out.

Please fix.

youtube it! this is something i wanna hear

Could you update the main post to point to the new updated phoenix2? I cant find the updated compiled windows version.

I see a lot of misuse of settings. phatk2 = true is not valid. autoconfigure is not needed at all when specifying device-specific settings, and so on. Here are some per-device settings I suggest under certain SDK's and certain GPU's. Aggressions are for dedicated miners. If you need to use the miner like a normal PC, suggest using an aggresion anywhere from 4-7, whichever is most comfortable for you. The settings go after each device which is denoted by something like [cl:1:1] where [cl:1:1] is the platform and [cl:1:1] is the device number.

SDK 2.1, Radeon 5xxx, 61xx-67xx, Underclocked memory

SDK 2.4/2.5, Radeon 5xxx, 6xxx, Underclocked memory

SDK 2.6, Radeon 5xxx, 6xxx, Normal memory (1GHz+)

If you are using 2.6 SDK with underclocked memory, I suggest installed 2.1 as well, or rolling back to 2.4/2.5 if you have 6800+'s in your miners as 2.6 is still garbage as far as speed goes. SDK 2.1 is still the fastest. 2.4/2.5 have the same speed as far as I can tell. The reduced aggression for SDK 2.1 is to reduce the chance that TDR will trigger and crash the miner (2.1 is highly aggressive in taking GPU time).

The opposite holds true; If you are stuck with high memory clocks, 2.6 is more efficient than 2.1-2.5.

I underclock my phenom 3Ghz to 800mhz and turn off all cores but 1 and there is still excessive headroom. 50mhz would probably be more than enough (if the OS doesnt choke)

Yeah I did notice rolling every now and then; just didnt occur as often compared to the other pool i listed as an example, and yes indeed that is a monster. Anyways back to mining on bonuspool.

edit: pool is acting up again. i'm connected on 1 miner but cant connect on 3 others.. back to eligius never mind, problem is on my end.
edit2: fixd. had a virus annihilate base filtering engine service and windows firewall and some other stuff on the main pc that shares internet connection to other miners. ran 2 registry fixes, some netsh commands, restored some services back to automatic startup, and good as new.

Something I noticed; when using phoenix 2 beta which supports rollntime, eligius makes the miner roll time a lot, which is good. bonuspool however is -always- sending new work, probably giving the server unnecessary load. just a thought.

FWIW, the ipv6 address is [2a01:4f8:141:30a6:feed:7:d1ce:deed] and this also works in phoenix beta. If it doenst work for you right away automagically, you don't have windows 7 and need to figure out how to enable ipv6

there is no backup pool support (atm)

cant connect at all, sorry but i need to keep mining. back to eligius until update

its because 11.12+ uses sdk 2.6 which is terrible. just dont install the sdk and use the one from 11.1 or whatever one you prefer to use (sdk 2.1)

just got an error. one of my cards is no longer mining (no gpu activity), probably need to restart the phoenix.exe. win7 x64, driver 11.12, sdk 2.6 + sdk 2.1. miner shows abnormal hash rate. 27 ghash wtf?

says they are unavailable

Hi, testing out phoenix 2. Didnt instant crash my computer like some other miners do which is good. Seems to be identical performance too as far as hash rates go, just have to explicitly define all variables since they aren't assumed anymore due to the lack of init.py (my bad, its the bfi_patcher.py thats gone now, probably integrated in phoenix.exe). Is it possible to have better granularity of the hashrate? GUIMiner + Phoenix 1.7.4 is able to show 1.178 ghash, but with phoenix 2, I lose a digit and only shows 1.17 ghash. On another rig, it shows 2 more digits of the hash rate (766.73 mhash, etc). How about giving the same treatment to Ghash?

Thanks for continuing to support multiple OpenCL platforms. Works well for my 2.1 + 2.6 SDK setup.

Also with the upcoming web interface, will it be possible to alter aggression of specific devices on the fly?

Lastly, I took a quick look through the kernel and found BITALIGN. Under what hardware is this supported? I tried this instead of BFI_INT and saw a much lower hash rate on my 5830/5870's. Is it supposed to be faster? Is it supposed to work in conjunction with BFI_INT?

Bananington, VECTORS2 is unused. Use VECTORS or VECTORS 4. Also make sure to define BFI_INT = true for each device that supports it, and don't forget your user/pass combo in the backend. http://user:pass@website:port