CGMiner Runs at kh/s instead of mh/s

[AzureEngineer]

CGMiner runs at kh/s instead of mh/s. I am not using Scrypt. Anyone seen anything like this?




-o api.bitcoin.cz:8332 -u ***.1 -p *** --thread-concurrency 21712 -I 20

Running on Sapphire 7950's.

(I know that Slush uses 3333 for stratum, but for some reason, CGminer won't connect unless I use 8332, it also won't connect to the proxy)

[cp1]

what cards are you using?   and can you try it with default settings?

[AzureEngineer]

what cards are you using?   and can you try it with default settings?

Sapphire 7950s. Default settings result in the same deal, just lower kh/s. The cards are running the exact same way they would if I were trying to mine Litecoins. CGminer creates a poclbm settings file when I run it, so I know it isn't running Scrypt.

[philips]

--thread-concurrency 21712 -I 20

That is scrypt specific.
Remove --thread-concurrency and use a lower intensity like 9.

Do you have by chance a cgminer.conf with LTC settings in your system?

[cp1]

You might try bfgminer or some other miner just real quick to see if it's a setting problem.  I wonder if your cards became way underclocked somehow.

[AzureEngineer]

--thread-concurrency 21712 -I 20

That is scrypt specific.
Remove --thread-concurrency and use a lower intensity like 9

This has fixed my problem, thank you.

[pengoau]

hmm i'm having the same problem and i'm not specifying a tc etc... interesting u had the same problem after switching from ltc to btc like i have...

[-ck]

Setting intensity over 9 is wrong for btc.
Check you don't have a configuration file with scrypt specified in that. The file may be getting loaded without you realising it's there.

[pengoau]

https://bitcointalk.org/index.php?topic=220781.0

no conf file, i run via a batch file or either cgwatcher
so i fixed it, and yeah i just discovered if i use intensity 20 it reverts to kh/sec.

so max of 9 for btc? i swear in the past i was able to use something higher oh well guess you would know since u wrote the program

it seems to do ok with an intensity of 13. still reporting in mh/sec.

ok after having a play at different intensities, 9 seems best