I'm assuming your talking about dynamic mode?

If so it's not an error.  Dynamic mode adjusts your GPU in an attempt to keep your desktop GUI responsive so you can use your computer while mining.  Dynamic mode only uses one thread instead of the default 2 so it's disabling the unused one.

--intensity|-I Intensity of GPU scanning (d or -10 -> 10, default: d to maintain desktop interactivity)

p2pool.info isn't measuring your hash rate, it is estimating it from a random process.  Variations in that process lead to variations in the estimated hashrate.  p2pool.info has to rely on actual shares, so the variance there will be much higher than your local estimates, which are estimated from pseudoshares.

it means you either haven't mined for a whole day, you've been unlucky, your efficiency is low

or some combo of those three

Because no blocks have been found for ~1d18h

I have two 7970 in an antec 900 case (closed, 5 fans running 100%) and these things are 86c and 97c.

That's with stock settings no overclocking.  Yes, they run about 550Mhash each per the spec.

Guess I need to open the box and blast them with a fan or plunge into water cooling...

I changed the program I am running from guiminer to cgminer and increased my hashrate by 10 mhash/s per card that way.

Is there anything I can do to increase my hash rate at this point? Or is this rig just going to be stuck at this rate, 20% below target?

Here are my cgminer settings which I copied from the forum:

"intensity" : "9",
"gpu-engine" : "0-1125",
"gpu-fan" : "0-85",
"temp-cutoff" : "90",
"temp-overheat" : "85",
"temp-target" : "75",
"auto-gpu" : true,
"auto-fan" : true,
"expiry" : "120",
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"gpu-threads" : "2",
"log" : "5",
"queue" : "1",
"retry-pause" : "5",
"scan-time" : "60",
"temp-hysteresis" : "3",
"shares" : "0",

Fix protocol simply prevents CGminer/bfgminer from attempting to auto-switch any getwork pools to stratum/gbt. I think you would would only use this in special cases where you only want to use getwork. If anything, using fix protocol could decrease your hash rate since getwork is less efficient than stratum or gbt.

And the issue I described with p2pool only applies to BFL single FPGAs, not GPUs, so you should be fine.
(Yes, you can use it 24/7 with GPUs and it will work fine)

@Lacan82 Which card do you have?

@supwang Yes, only BTC.

It might very briefly decrease your mining hashrate because of the time required to fetch new work from the pool/start working on the new work.  There's nothing you can really do about it though, other than switch to a conventional pool but that might not really make a huge difference in your hashrate so I think you're fine. (it should be noted that p2pool has 10-second blocks so you'll see this message about once every 10 seconds.  That's why you can't use p2pool with devices that take a long time to start new work like BFL singles.)

The short version is that the work to produce the "next" block depends on the previous block.  The moment a new block is found, any in-progress searching is aborted because it won't produce anything useful.  This is important because it encourages a "found" block to be used and distributed quickly.

You should see this message each time the bitcoin network as a whole finds a new block.

宣傳一下台灣的p2pool

網址 http://9332.linkin.tw:9332
帳號 收款位置
密碼 任意