Quote from: earthsound on May 29, 2012, 08:10:19 PM

Quote from: DiabloD3 on May 24, 2012, 02:54:20 PM

Quote from: earthsound on May 24, 2012, 01:31:19 PM

Quote from: DiabloD3 on May 22, 2012, 08:23:16 PM

Update: Everyone effected by the problem, try the new build.

The new build works well, thanks! What was the issue?

Side note: I can now use a worksize of either 128 or 256 on OS X 10.7.4 and notice a small increase in hashrate over -w 64. May be worth mentioning in the OP instructions. I assume it's because of (one of?) the OpenCL updates Apple has pushed out.

FINALLY THEY FIXED IT! HOLY CRAP APPLE, IT ONLY TOOK TWO YEARS!

Also, the issue on AMD was AMD interprets the specification differently than I do. It costs basically nothing to fix it, and on GCN its measurably nothing.

Well, I spoke too soon. After letting a few boxes run over the weekend with the latest version, the clients report that they are connecting to the pool and shares are accepted, however the hashrate as reported by the pool is much lower with this latest version than the one in March.

The new client was showing an average 34 mhash/s per machine all weekend (looking at Eligius' 3 hr avg & 12 hr avg) vs. 67 mhash/s on the March client (looking at Eligius' 3 hours avg today).

I can confirm that just upgrading to 10.7.4 cause an approximate drop of 8-10 mhash/s. Sad

Goddamnit Apple. Why do you hate OpenCL so much.