01-18-2018, 11:18 PM
There are a lot of warnings in your output.
Starting from the timeout patch problem to the "Not a native Intel OpenCL runtime" error.
It's not a good idea to ignore all warnings and don't try to fix them.
Intel has a dedicated OpenCL Runtime (not SDK!) page where you can download the Intel OpenCL Runtime for your CPU.
I also just noticed that this confusion about -D/-d might come from blogs like this one: https://stealthsploit.com/2018/01/04/eth...pu-vs-cpu/
There are a lot of people trying exactly that, i.e. run -D 12 or something like that even through it makes absoultely no sense if you read the --help output (-D only allows 3 different values 1, 2 or 3 and this values are not for the device selection but for the type selection). Therefore in my opinion the whole article (all the -D x recommendation etc) needs to be fixed. Maybe someone can contact the author before we get flooded with several "problems" like this one (see original post of this thread).
Starting from the timeout patch problem to the "Not a native Intel OpenCL runtime" error.
It's not a good idea to ignore all warnings and don't try to fix them.
Intel has a dedicated OpenCL Runtime (not SDK!) page where you can download the Intel OpenCL Runtime for your CPU.
I also just noticed that this confusion about -D/-d might come from blogs like this one: https://stealthsploit.com/2018/01/04/eth...pu-vs-cpu/
There are a lot of people trying exactly that, i.e. run -D 12 or something like that even through it makes absoultely no sense if you read the --help output (-D only allows 3 different values 1, 2 or 3 and this values are not for the device selection but for the type selection). Therefore in my opinion the whole article (all the -D x recommendation etc) needs to be fixed. Maybe someone can contact the author before we get flooded with several "problems" like this one (see original post of this thread).