Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error CL_INVALID_WORK_GROUP_SIZE when calling clEnqueueNDRangeKernel for kernel 0. #93

Open
Fuzzyma opened this issue Sep 3, 2017 · 2 comments

Comments

@Fuzzyma
Copy link

Fuzzyma commented Sep 3, 2017

I get the above error when specifying a worksize > 2. So basically only 1 and 2 are working.

I have an Intel HD Graphics 4600 which I use to mine. I am on win7 and compiled the current dev branch.
Can I somehow circumvent the CL_INVALID_WORK_GROUP_SIZE error so I can increase the worksize?

//EDIT: It seems like the xmr-stak-amd is using my nvidea card instead of the intel HD. What to do against taht?

@psychocrypt
Copy link
Collaborator

If the nvidia card is used please set the correct index or platform. Run clinfo to found the right indices.

@Fuzzyma
Copy link
Author

Fuzzyma commented Sep 13, 2017

Where can I find clinfo? I tried to change the index to 1 - actually first thing i tried. No device found in this case:

"gpu_threads_conf" : [
{ "index" : 1, "intensity" : 100, "worksize" : 2, "affine_to_cpu" : false },
],

[2017-09-13 09:52:52] : Selected OpenCL device index 1 doesn't exist

When changing the platform index to 1 I get

[2017-09-13 10:00:58] : Compiling code and initializing GPUs. This will take a while...
[2017-09-13 10:00:59] : Device 0 work size 2 / 512.
[2017-09-13 10:00:59] : Error CL_INVALID_DEVICE when calling clCreateCommandQueueWithProperties.
Press any key to exit.

bioharz added a commit to bioharz/aeon-stak-amd that referenced this issue Sep 28, 2017
bioharz added a commit to bioharz/aeon-stak-amd that referenced this issue Sep 28, 2017
bioharz added a commit to bioharz/aeon-stak-amd that referenced this issue Sep 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants