So, I've recently begun configuring GUIMiner and Bitcoin client for personal use and experimentation but have run into this issue...
https://i.imgur.com/u3KTj3z.jpgThat was after leaving the machine running for 3 hours. I'm not sure if it's me being impatient or some other problem.
This is a dual GPU machine and once everything is sorted I expect a regular return of 650mh/s (tested to fluctuate from 630-660) once I finish tweaking and fiddling with all those lovely flags.
It happens on Slush's pool and the Eligius pool. Going to test solo after this post goes up.
2013-04-10 14:53:42: Running command: poclbm.exe 18FKFPvbvsVuo1yBZ5wKmALKy5gouN7PGV:x@mining.eligius.st:8337 --device=1 --platform=0 --verbose -r1 -v -w 128 -f 60
2013-04-10 14:53:42: Listener for "ELIG" started
2013-04-10 14:53:44: Listener for "ELIG": mining.eligius.st:8337 10/04/2013 14:53:44, started OpenCL miner on platform 0, device 1 (Cayman)
2013-04-10 14:53:44: Listener for "ELIG": mining.eligius.st:8337 10/04/2013 14:53:44, checking for stratum...
2013-04-10 14:53:46: Listener for "ELIG": mining.eligius.st:8337 10/04/2013 14:53:46, using JSON-RPC (no stratum header)
2013-04-10 14:53:47: Listener for "ELIG": mining.eligius.st:8337 10/04/2013 14:53:47, Verification failed, check hardware! (0:1:Cayman, c52c96c7)
Am I just being impatient? I was under the impression that under a pool there should be some sign of activity after an hour or two, certainly over 200mh/s.
Then again I could be completely wrong about that last bit.
Also, the error seems to be related to the miner and driver disagreeing more than anything else, but the GPU is still pumping out a decent rate of MH/s so I didn't think it to be anything impeding the actual process, rather, a general warning that some piece of code didn't like the other piece of code and went crying to daddy.
...Another case where I could be an idiot/wrong.