--vectors 1 as a boot parameter or "vectors" : "1", in .json config will give you correct hashrate. For 5xxx and 6xxx AMD's, CL kernel binaries uses vectors "2" as default build parameter if its not defined manually as "1". I'm getting 550khs with a 6870, vectors 1 and 1100 with vectors 2. it just doubles the calculated hashrate in this case. Hope this helps!
its calculating lots of numbers, i wouldnt believe anything i see until you give the pool a chance to catch up, give it an hour or so then try, might be updates from OC as we know he is currently working hard with it.
quick switch on and off [2016-02-08 18:59:00] Started at [2016-02-08 18:10:58] [2016-02-08 18:59:00] Pool: http://dcr.suprnova.cc:9110 [2016-02-08 18:59:00] Runtime: 0 hrs : 48 mins : 2 secs [2016-02-08 18:59:00] Average hashrate: 768.2 Megahash/s [2016-02-08 18:59:00] Solved blocks: 5 [2016-02-08 18:59:00] Best share difficulty: 1.98K [2016-02-08 18:59:00] Share submissions: 534 [2016-02-08 18:59:00] Accepted shares: 93 [2016-02-08 18:59:00] Rejected shares: 441 [2016-02-08 18:59:00] Accepted difficulty shares: 93 [2016-02-08 18:59:00] Rejected difficulty shares: 441 [2016-02-08 18:59:00] Reject ratio: 82.6% [2016-02-08 18:59:00] Hardware errors: 0 [2016-02-08 18:59:00] Utility (accepted shares / min): 1.94/min [2016-02-08 18:59:00] Work Utility (diff1 shares solved / min): 0.00/min [2016-02-08 18:59:00] Stale submissions discarded due to new blocks: 2 [2016-02-08 18:59:00] Unable to get work from server occasions: 2 [2016-02-08 18:59:00] Work items generated locally: 962 [2016-02-08 18:59:00] Submitting work remotely delay occasions: 2 [2016-02-08 18:59:00] New blocks detected on network: 50 [2016-02-08 18:59:00] Summary of per device statistics: [2016-02-08 18:59:00] GPU0 | (5s):767.8M (avg):768.2Mh/s | A:93 R:441 HW:0 WU:0.0/m [2016-02-08 18:59:00] [2016-02-08 18:59:00] Pool 0 communication failure, caching submissions
The pools frontend is still lagging a bit, fixing this as we speak, but the backend is fine. Lots of blocks were found already, thanks for the trust guys. Stats and Hashrate should be fine too now, there was a change from testnet -> mainnet which I've now recalculated. Happy mining !
yes ddosed typically, your wasting hash someone else is getting it, best mine something more profitable