Closed ned123 closed 13 years ago
I have the same problem with the most recent, and I also continue to use one from the 20th of June or so. At first my proxy did not support the new code that was implemented and I couldn't use DiabloMiner at all, now DiabloMiner will work but I get %50+ rejects, so I have downgraded back to my copy from June 20th and have no problems (around %3). Mining with no additional settings on a pair of 4850s, Catalyst 11.6 SDK 2.4
slush's pool is incorrectly marking shares as rejects because slush refuses to implement ntime rolling. This is a bug with his pool, not the miner.
Mine is occurring through my bitcoin-mining-proxy to Eligius-3, not slush.
bmp apparently also suffers from the same issue.
With latest versions of Diablo Miner I'm having to many rejected shares (close to 50%). With version from 18-June I get about 5% rejected shares but it is a little slower. I mine with Radeon 6950, Catalyst 11.6 (SDK 2.4), use mostly -v2 -w128 (tried a lot of combinations and this is the fastest) and mine on slush's pool. What would be the issue with the latest versions?