I have 1 card that is half full of x's in low clock mode (x x x x x x x x o o o o o o o o). If I switch to high clock mode and restart, it goes to all o's. But when I switch back to low and restart, the x's return.
Anyone know what's going on or how to fix it?
Also, is it normal to always get these "WARNING proxy getwork_listener._on_submit" messages? I seem to be getting a lot of work accepted (27 gh/s on slush's pool), but I'm getting lots of WARNING spam.
Sounds like the card might not be seated well, and restarting the cube (regardless of clock mode changes) must give it a bit more (or less) signal. I'd double check that the card is seated.
As for slush's pool, your running this through a stratum proxy right? If you use the old get-work network, you're wasting your time since they've actually discontinued it.
Thanks for the reply. Yeah I'm running it through the stratum proxy from Slush's pool here:
http://mining.bitcoin.cz/mining-proxy-howto. I just followed the guide in the OP, set up the miner and run mining_proxy.exe with no parameters. Is that the old get-work network?
Also, I took all the cards out, tightened the heat sink screws and reseated all the cards. But that didn't seem to fix the 8 x's problem. Any other ideas?
Oh and all the cards had some crusty blotches of film on them, like somebody sneezed all over them and there's a bunch of dried mucus leftover. What is that about?
UPDATE: Well now the card stays half full of "x" in both low and high clock modes.