As far as -v goes, I'm not entirely sure, but I think it just allows the calculations to take place in a wider field.  -f controls how long an instance of the miner can run for on the GPU (inverted to work on the concept of frame rate).  The larger the parameter, the more opportunities other tasks (such as updating the desktop) have at actually executing.  You may also want to mess with -w (work size).  For your GPU, I would probably guess 128 is best, but 64 might work as well.  I'm fairly certain 256 will spew randomly large hash/s at you and crash shortly thereafter.

If you haven't done so yet, at least check out puddinpop's RPC CUDA miner as this may net you a small boost in performance.  It won't be much at first, but you can do some tweaking to get more.

Hello,

I want use poclbm with my HD 5770 vapor-x.

You know the tools at install with poclbm ?


Thanks

With the latest version while mining for myself, I seem to be getting intermittent "problems communicating with bitcoin rpc" errors. They appear and disappear seemingly randomly...

Working much better for me now. Before this update, I had the miner restart if it threw a RPCError in getwork.
Now I see a bunch of "warning: job finished, miner is idle," but it keeps chugging along.
I haven't looked at the new code yet, but would some pre-fetching help?

Eh, do I have to disable crossfire for my 5970(1 card) using this miner guys ?

There is a change in the way '-f' works. Simply said, just use lower '-f' now to achieve same performance/desktop lag as before. 5% seems too much though, what's your setup? Is the first card faster?

On the contrary, on my 2x5970 Linux mining rig, no difference in hashspeed compared to older versions. Everything works fine.

Crossfire disabled?

try sdk 2.2 instead