All good, you're on 2.5. You probably got the dud kernel in the first packaged release which is why I upgraded to 2.3.0-1

I'll probably release a 2.3.1 pretty soon today, reverting a few of the kernel changes that were dubious and based on what diablo and others said. I should have trusted myself 

Make sure you're using the slightly upgrade 2.3.0-1

If you still have a hashrate drop like that then you're doing the SDK2.6 dance. cgminer -n will tell me what openCL you're using.

It's a fairly sensitive tuning tool. The difference between the default 7 and 1 should be quite significant to the interface. Don't get too hung up on what the intensity setting reported is since that's done once every 5 seconds but at dyninterval of 1 the value is updated 1000 times per second. 1 is very interactive desktop with lower hashrate, 1000 for example is higher hashrate less dynamic dekstop.

Dunno anything about windows, but on linux...

Try this:


then look for the device in the listing
Bus 002 Device 003: SOME KIND OF AWESOME MINING DEVICE NAME

Then based on the values of bus and device 2 and 3 above.



Just a guess since I didn't really do the bitforce code. Note it's meant to detect devices automatically though, but I have no experience with them...

Heh, you're not a coder are you? That's still two branches unless it's positive on the first branch.

Updated the 2.3.0 package with -1 extension which includes a fixed phatk kernel. Links in top post. This shouldn't affect other kernels...

If it ends up affecting other kernels, I'll have to release a full new version tomorrow.

Read what it says at startup when you run dynamic intensity... sigh.

No, you're doing two branches on the common path now. We want as few branches as possible in the common path. It doesn't matter if we do 2 extra checks in the uncommon (i.e. found share) path.

Goddamn. Thanks for that. The any() function is meant to be faster than manually unrolling it the way I did in the old version. I guess I shouldn't put any faith in their hardware functions...

sigh...

The old kernel is simply not compatible with the current one.

Well this makes me fucking angry. All I can do is shake my fist even harder at ATI for the changes just SHOULD NOT CAUSE THIS as they're meant to be trivial changes. Well more fucking quick fucking releases to deal with fucking ATI fucking fail. Rollback phatk fucking time.

That doesn't mean you can't try -k phatk -v 2 -w 256
Based on what tenzor says, 960/1030 * 230 means you should be able to get 214

edit: He changed that to 220-225?  * 960/103 is 205 which is not far off what you're getting... Try it anyway  

edit2: DONT FORGET SDK MATTERS!

Excellent, that's more the sort of news I was hoping for 

That, unfortunately, does not make sense... and this hashrate drop is more than a little disturbing since there is no real valid explanation for it.

edit: it's so big it's like one has an intensity set and the other is running dynamic.

Now that's a serious groaner since the phatk kernel is only trivially changed it should not perform any differently   Try -v 2 -w 256 since you're grossly underclocking memory.

If you start it from a dos prompt window the window won't close...

Cannot do. You can only make 32 bit kernels from running on 32 bit OS I'm afraid.

What does:
cgminer -n
report? And what kernel .bin file is being generated for you by default?

Woah now there is nothing that should stop it compiling a bitalign kernel. It just stops CALLING it bitalign. You're not doing the SDK 2.6 dance are you?

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

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...

Heh you couldn't wait till I finished it Yeah I'm still working on the code, thanks.

edit: Yes I know I shouldn't leave the master branch in an unworkable state but I had to rush off and didn't want to lose my work to date.