This is why cgminer reports back the actual speeds to you after you set them on the fly in the menu, as the driver can lie, saying it set the speed fine but the card just refuses it.

Well cgminer is reporting 128mhz

Updated above post with 12hour report, seems 128mhz has no effect on utility or hash rates. I'll have to do a proper test on my single card machine as the one below puts out too much heat and is constantly throttled.



I see, but it's probably more beneficial to play with volts and the core for that. I dont think memory clocks use a big amount of power.

Also note that testing how long it will take using a Share count is not consistent.
On the same setup, 1000 Shares can take varying amounts of time.
A share is random, just like a block (it is a difficulty "1" block)
Utility will vary also.
Only the actual average hash rate should be somewhat consistent.

Don't know the *nix equivalent for a bash loop would be, but seems really inefficient to copy-paste the setup over and over, and even then after what 6-8hrs it'd never restart again? I'd think something like


would be wayyyy better and shorter code :]

Stupid Question:
I have an HD6850 running by itself.  If I add a second card, say an HD6750, and fire CGMiner back up, will it detect both cards, or do I need to add something to the .bat file?  I am using Catalyst 11.8 drivers.

I thought for the heck of it I would have my bitcoin wallet accept connections and then set it up as solo mining and only use it as my failover. the idea is cgminer would slip it a few shares every now and then and maybe some day I would get lucky and hit the jackpot (im a gambling man)

I managed to get cgminer to connect to my bitcoin wallet but it says REJECTED for every single share in cgminer

any ideas folks?

thanks

ahh I did not know that. Thank you! Now I feel like an idiot!
nhehehe thanks again.

DISPLAY=:0 cgminer --ndevs

You cannot query it inside cgminer AFAIK, ls *.bin and the bin file well indicate what it's running.

Just a little aside information that some may not realise ...

The value shown after Accept/Reject in the cgminer log is the hex nonce.

If you get a block (pool or solo), then the nonce in the block will match that value exactly.
(this is firstly based on reading the code and working out where the value comes from, and secondly looking at my one and only pool block I have and seeing that it does match as expected)

This means that anyone wondering if they can tell if they got a particular block, they can with reasonable certainty by comparing the block nonce with the log nonce (and of course there should be a LONGPOLL for the block almost straight after it in the log)
Of course it isn't 100% guaranteed since the nonce value is not unique per share, but if it is roughly at the same time as the block and a LONGPOLL shows just after it - it's extremely likely to be the block.

... and another side
My latest pull request makes it show 3/8 of the actual hash rather than the nonce and also says " BLOCK!" after it if it is a valid block difficulty share
(which also may cause some distress if anyone ever actually gets a Rejected block in the log ...)
If you want that branch change before it gets into the main code it's available in my kano branch here:
https://github.com/kanoi/cgminer/tree/kano (main.c, util.c and miner.h)
N.B. that difficulty test code is my original in case anyone wonders where it came from