Anyways, I use 11.12 + 2.1 SDK on all my rigs and phoenix 2 miner, no cpu bug

12% cpu indicates you have an 8 core cpu? If its a single core cpu though.. 12% sounds "ok" to me, might have a weird setting which causes exponentially higher cpu with higher aggressions/lower -f flags. I had that for a while, but it eventually fixe ditself with a driver change, but I dont know which. It was a long time ago.

Anyways, I use 11.12 + 2.1 SDK on all my rigs and phoenix 2 miner, no cpu bug

12% cpu indicates you have an 8 core cpu? If its a single core cpu though.. 12% sounds "ok" to me, might have a weird setting which causes exponentially higher cpu with higher aggressions/lower -f flags. I had that for a while, but it eventually fixe ditself with a driver change, but I dont know which. It was a long time ago.

I am sure 11.12 comes with 2.6 sdk, but as stated, I have 12.1 with 2.5 SDK installed.

Yea ppl keep telling me they are using 2.1 with 11.12, dunno how but they are.

Anyways, I use 11.12 + 2.1 SDK on all my rigs and phoenix 2 miner, no cpu bug

12% cpu indicates you have an 8 core cpu? If its a single core cpu though.. 12% sounds "ok" to me, might have a weird setting which causes exponentially higher cpu with higher aggressions/lower -f flags. I had that for a while, but it eventually fixe ditself with a driver change, but I dont know which. It was a long time ago.

I am sure 11.12 comes with 2.6 sdk, but as stated, I have 12.1 with 2.5 SDK installed.

Yea ppl keep telling me they are using 2.1 with 11.12, dunno how but they are.

I have a duel core processor with HT. I3-2100.

So you have Four selectable cores? 12% isnt that bad atall... it would be at 25% if you had a Bug pegging your core, have you tried messing with the -f param?

Anyways, I use 11.12 + 2.1 SDK on all my rigs and phoenix 2 miner, no cpu bug

12% cpu indicates you have an 8 core cpu? If its a single core cpu though.. 12% sounds "ok" to me, might have a weird setting which causes exponentially higher cpu with higher aggressions/lower -f flags. I had that for a while, but it eventually fixe ditself with a driver change, but I dont know which. It was a long time ago.

I am sure 11.12 comes with 2.6 sdk, but as stated, I have 12.1 with 2.5 SDK installed.

Yea ppl keep telling me they are using 2.1 with 11.12, dunno how but they are.

I have a duel core processor with HT. I3-2100.

So you have Four selectable cores? 12% isnt that bad atall... it would be at 25% if you had a Bug pegging your core, have you tried messing with the -f param?

Yea, the cores aren't fully utilized, for core 0 is for workerone, core 1 is for workertwo. If I set core 0 for both workers, either workerone or two will get horrible mhash/s.

Crap, that is what the problem was. I changed the f 1 flag to f 10, I am receiving 00 cpu utilization on both miners. Why would this be?

Lower f number = higher aggression = typically more cpu. It means the GPU is working a larger set of nonces before finishing work and asking for more.

If poclbm -f argument is anything like diablominer -f, it is essentially trying to complete an entire kernel run -f amount of times per second. Assuming a 1 ghash/sec GPU, -f 1 would attempt to complete an 1 billion hashes in a single kernel run before asking for more nonces to hash, which would be about once every second. -f 10 would attempt to complete 100 million hashes per kernel run, requiring new nonce ranges 10 times per second. -f 100 would do 10 million hashes per kernel run and ask for more nonce ranges 100 times/second. Requiring new work more often generally leaves the gpu more open to other requests, such as rendering desktop, or games, or whatever, which means less lag.

Some drivers had a bug that made high cpu usage with higher aggressions.

Lastly, people use 2.1 SDK by installing the standalone SDK here https://dl.dropbox.com/u/9768004/ATIStreamSDK_dev.msi or locating it on AMD's website (The .msi I linked is part of the package that AMD offers for 2.1 SDK, but it is the only thing you need to enable 2.1 sdk. Everything else is useless as far as mining goes). It is an entirely different platform than AMD APP (2.4+) so it can be installed at the same time. Your miner needs to be able to select a different platform though. Some miners don't allow you to do this though, but instead list the same device under a different platform as a different device, so you would mine under the "new" device. Say you had 2 5870's. Generally, your newer SDK would come up first (AMD APP) and you would have device 0 and 1, and maybe device 2 if the miner shows cpu devices as well. SDK 2.1 would be listed after that and show device 3 (cpu) then device 4 and 5 as the 5870's. For some reason, 2.1 SDK lists the CPU as the first device. AMD APP lists the CPU as the last device.

Lower f number = higher aggression = typically more cpu. It means the GPU is working a larger set of nonces before finishing work and asking for more.

If poclbm -f argument is anything like diablominer -f, it is essentially trying to complete an entire kernel run -f amount of times per second. Assuming a 1 ghash/sec GPU, -f 1 would attempt to complete an 1 billion hashes in a single kernel run before asking for more nonces to hash, which would be about once every second. -f 10 would attempt to complete 100 million hashes per kernel run, requiring new nonce ranges 10 times per second. -f 100 would do 10 million hashes per kernel run and ask for more nonce ranges 100 times/second. Requiring new work more often generally leaves the gpu more open to other requests, such as rendering desktop, or games, or whatever, which means less lag.

Some drivers had a bug that made high cpu usage with higher aggressions.

Lastly, people use 2.1 SDK by installing the standalone SDK here https://dl.dropbox.com/u/9768004/ATIStreamSDK_dev.msi or locating it on AMD's website (The .msi I linked is part of the package that AMD offers for 2.1 SDK, but it is the only thing you need to enable 2.1 sdk. Everything else is useless as far as mining goes). It is an entirely different platform than AMD APP (2.4+) so it can be installed at the same time. Your miner needs to be able to select a different platform though. Some miners don't allow you to do this though, but instead list the same device under a different platform as a different device, so you would mine under the "new" device. Say you had 2 5870's. Generally, your newer SDK would come up first (AMD APP) and you would have device 0 and 1, and maybe device 2 if the miner shows cpu devices as well. SDK 2.1 would be listed after that and show device 3 (cpu) then device 4 and 5 as the 5870's. For some reason, 2.1 SDK lists the CPU as the first device. AMD APP lists the CPU as the last device.

Oh, TY for donation too

Ok, I got the standalone installed. I see the extra devices under GUIMiner. It's mining away with 12.1ccc & 2.1 SDK.

From what I can tell for 2.1 & 2.5, either they both seem to mine away at the same speeds or 2.1 might seem more stable at mhash/s or 2.1 seems like it might have lost 1 or 2 mhash/s. Very hard to tell if there is a difference. And actually, my desktop is laggy when 2.1 is used in which I believe you had stated something about this previously. Good to know that I got this working though, with 2.1 and learned about the extra devices.

So, from your experience, what difference can you tell between 2.1 and 2.5?

Lower f number = higher aggression = typically more cpu. It means the GPU is working a larger set of nonces before finishing work and asking for more.

If poclbm -f argument is anything like diablominer -f, it is essentially trying to complete an entire kernel run -f amount of times per second. Assuming a 1 ghash/sec GPU, -f 1 would attempt to complete an 1 billion hashes in a single kernel run before asking for more nonces to hash, which would be about once every second. -f 10 would attempt to complete 100 million hashes per kernel run, requiring new nonce ranges 10 times per second. -f 100 would do 10 million hashes per kernel run and ask for more nonce ranges 100 times/second. Requiring new work more often generally leaves the gpu more open to other requests, such as rendering desktop, or games, or whatever, which means less lag.

Some drivers had a bug that made high cpu usage with higher aggressions.

Lastly, people use 2.1 SDK by installing the standalone SDK here https://dl.dropbox.com/u/9768004/ATIStreamSDK_dev.msi or locating it on AMD's website (The .msi I linked is part of the package that AMD offers for 2.1 SDK, but it is the only thing you need to enable 2.1 sdk. Everything else is useless as far as mining goes). It is an entirely different platform than AMD APP (2.4+) so it can be installed at the same time. Your miner needs to be able to select a different platform though. Some miners don't allow you to do this though, but instead list the same device under a different platform as a different device, so you would mine under the "new" device. Say you had 2 5870's. Generally, your newer SDK would come up first (AMD APP) and you would have device 0 and 1, and maybe device 2 if the miner shows cpu devices as well. SDK 2.1 would be listed after that and show device 3 (cpu) then device 4 and 5 as the 5870's. For some reason, 2.1 SDK lists the CPU as the first device. AMD APP lists the CPU as the last device.

Oh, TY for donation too

Ok, I got the standalone installed. I see the extra devices under GUIMiner. It's mining away with 12.1ccc & 2.1 SDK.

From what I can tell for 2.1 & 2.5, either they both seem to mine away at the same speeds or 2.1 might seem more stable at mhash/s or 2.1 seems like it might have lost 1 or 2 mhash/s. Very hard to tell if there is a difference. And actually, my desktop is laggy when 2.1 is used in which I believe you had stated something about this previously. Good to know that I got this working though, with 2.1 and learned about the extra devices.

So, from your experience, what difference can you tell between 2.1 and 2.5?

2.1 is generally a more aggressive SDK. You will notice more desktop lag and even mouse lag at lower aggressions on 2.1 compared to 2.4/2.5. It's great for dedicated 5xxx/60xx-68xx cards. You may need to use slightly different memory speeds or miner/kernel settings, but for me, its a couple mhash more per card using phoenix + phatk2