Work size issues on Macbook Pro
Closed this issue · 2 comments
Hi, when I run diablominer, I get an error that the work size is 256 but the required work size is 512. But, if I try to set the work size to 512 with the -w flag, I get an error that the work size is greater than the device can support.
Here's the output without the -w option:
[12/26/11 12:04:00 AM] Started
[12/26/11 12:04:00 AM] Connecting to: http://api.bitcoin.cz:8332/
[12/26/11 12:04:00 AM] Using Apple OpenCL 1.1 (Jul 25 2011 15:56:07)
[12/26/11 12:04:00 AM] Added GeForce 9400M (#1) (2 CU, local work size of 256)
[12/26/11 12:04:01 AM] ERROR: [CL_INVALID_WORK_GROUP_SIZE] : OpenCL Error : clEnqueueNDRangeKernel failed: local_size[0]: (256) != required local_size[0]: (512)
[12/26/11 12:04:01 AM] ERROR: Failed to queue kernel, error -54
And here's the output with the flag -w 512:
[12/26/11 12:08:26 AM] Started
[12/26/11 12:08:26 AM] Connecting to: http://api.bitcoin.cz:8332/
[12/26/11 12:08:26 AM] Using Apple OpenCL 1.1 (Jul 25 2011 15:56:07)
[12/26/11 12:08:26 AM] Added GeForce 9400M (#1) (2 CU, local work size of 512)
[12/26/11 12:08:26 AM] ERROR: [CL_INVALID_WORK_GROUP_SIZE] : OpenCL Error : clEnqueueNDRangeKernel failed: total work group size (512) is greater than the device can support (256)
[12/26/11 12:08:26 AM] ERROR: Failed to queue kernel, error -54
How can I fix this and get diablominer working? Thanks!!
Interestingly, using -w 256 seems to work. I'm guessing that this is an issue with OS X and not diablominer.
Its with OSX, you usually have to use a much smaller -w such as 64 or 128, to get it to work.
It only seems to do it on 10.7, though. 10.6 didn't do this.