I don't really think I need to compare my mining on two different pools to know that a 10% - 12% stale ratio is high...

I also don't see why the pool name is relevant being that my cpu miners in the exact same pool have a stale rate of less than 1.5% but if you insist, I am on OzCoin.

During an LP the screen shows what it is supposed to show, it tells me when the long polling has detected a new block, it tells me when a share has been accepted or when a share has been rejected.

What numbers would you like me to provide you other than the ratio of stales I am getting? Are there other numbers which would be relevant to the number of stales I am getting?

GPU - Geforce gt 520 (yes, I am aware that it is a piece of crap in relation to mining)
OS - Windows 7 64-bit
cgminer version - 2.7.5

I am not using the --no-submit-stale flag (i'm not using ANY flags actually) and yes, I AM getting stales as opposed to rejects. cgminer specifically says that they are stales ("prevhash submitted" or something along those lines).

What information did you request that I did not supply other than comparing the mining between two different pools (which is useless because I am 99.99% sure that the problem is not with the pool, otherwise my cpuminers would be affected as well)?

I have supplied all the information you asked me for with the exception of the "actual numbers" from the cgminer screen which I asked you for clarification on because I can't provide you with numbers unless I know which numbers you need, especially when I can not find a relative correlation between the other numbers output by the miner and my stale ratio...

When do I get the stales...? I get the stales when my miner attempts to submit a solved share and is answered by the server with a message that reads something like:


Then it prints something like:

According to the readme, you have to use --scan-serialdev/ttyUSBn (where n is the device ID).

FYI, if you are mining LTC wit the CPUs and BTC with the GPU, you are mining on different pools.  With the same name (ozcain), and even if they are at the same IP, they are not the same pool, because they are running on different daemons.  Also, with a GPU with a hash speed that slow, you aren't going to find a lot of shares, so that rate might not be so high.  Trying a different pool will confirm the problem is or isn't with ozcoin.  Then, either additional information can be used to find the problem or the GPU can be blamed.  Incidentally, if you try another pool and get less rejects, but the same U: (which might take weeks to normalize depending on how low your hashrate is), then these shares being submitted and rejected don't matter.  I'm sure the hashrate would be helpful in determining whether or not the higher reject rate is related.  When the shares occur might also be, for instance, do you see an LP or new block detected and then rejects, or are they random without LPs or new blocks detected?  If the problem is in the software, I'm guessing it's very likely to be related to the fact that you're using an nVidia card, so that information might have been useful much earlier on.

I don't know if this will work for you or not, but when I built my Debian box to run all my BFL's I was running into the same type of issue. I am a linux novice but I like to learn and take a lot of notes. I ran across this command on some obscure post on the forums. I don't know exactly what this does, but it worked for me anyway. I eventually added as the last line in theetc/rc.local file so it would start automatically on boot. Hope it works for you.

FYI, this is bad advice and is likely to screw up your system.

Indeed that wouldn't, but the commands Kano suggests also removes you from every other group. Including sudo. (BFGMiner has suggested almost idential but with the -a option for a few releases now)

Hello,

I've been testing Windows 8 Consumer Preview but I am having a few issues getting cgminer 2.7.4 working properly.

Main problem: While running cgminer, I get spammed with "New block detected on network before longpoll" ( 1000s of these displaying the same exact time) and the hashrate begin to slowly decrease over time (drops from 550 Mh/s to 350 Mh/s per GPU after about an hour or so).

Minor problem: I am unable to get cgminer running with 5 GPUs, it doesn't even work with "cgminer -n". The OS, catalyst, MSI Afterburner, GPU-Z all recognize the 5 GPUs.

Thanks in advance for your reply.

Never mind, I'm an idiot. I just needed to wait a few minutes...