Intel integrated GPU - Page 3

kracker · 2013-10-01, 19:12

Looks like clinfo lists it now, maybe try fidding with -d again see if it picks it up?

Prime95 · 2013-10-01, 22:47

Still no luck. I looked very briefly at the source code and the startup code is quite a bit different than the Intel sample source code. It would be sad if AMD and Intel require different startup code, but it would not surprise me.

Bdot · 2013-10-01, 23:14

Quote:

Originally Posted by Prime95

Still no luck. I looked very briefly at the source code and the startup code is quite a bit different than the Intel sample source code. It would be sad if AMD and Intel require different startup code, but it would not surprise me.

I'll have a look at the Intel examples, maybe I can spot some important difference. From your clinfo output, -d12 should be the option to use.

Edit: I checked "SimpleOptimizations". The very first OpenCL call it does, is clGetPlatformIDs - just like mfakto. But I see that you now got the first few self-tests running on your CPU device. This means that the OCL libs are found now. Still weird that it does not see device #2, which should be the GPU.

Do the Intel examples run on your GPU?

Prime95 · 2013-10-02, 00:09

Quote:

Originally Posted by Bdot

Do the Intel examples run on your GPU?

I don't have a C compiler on this machine to build the Intel examples.

Prime95 · 2013-10-02, 00:11

Quote:

Originally Posted by Bdot

From your clinfo output, -d12 should be the option to use.

I assume you are talking about the clinfo output after installing the Intel SDK.

Here is some output:

Code:

C:\Users\george\Desktop\mfakto-0.13win>mfakto_x64 -d 12
mfakto 0.13-Win (64bit build)


Runtime options
  Inifile                   mfakto.ini
  Verbosity                 1
  SieveOnGPU                yes
  GPUSievePrimes            82486
  GPUSieveSize              64Mi bits
  GPUSieveProcessSize       16Ki bits
  WorkFile                  worktodo.txt
  ResultsFile               results.txt
  Checkpoints               enabled
  CheckpointDelay           300s
  Stages                    enabled
  StopAfterFactor           class
  PrintMode                 compact
  V5UserID                  none
  ComputerID                none
  TimeStampInResults        yes
  VectorSize                4
  GPUType                   AUTO
  SmallExp                  no
Compiletime options
  MORE_CLASSES              enabled
Select device - Error: Only 1 devices found. Cannot use device 2 (bad parameter to option -d).
init_CL(1, 12) failed

Code:

C:\Users\george\Desktop\mfakto-0.13win>mfakto_x64 -d 11
mfakto 0.13-Win (64bit build)


Runtime options
  Inifile                   mfakto.ini
  Verbosity                 1
  SieveOnGPU                yes
  GPUSievePrimes            82486
  GPUSieveSize              64Mi bits
  GPUSieveProcessSize       16Ki bits
  WorkFile                  worktodo.txt
  ResultsFile               results.txt
  Checkpoints               enabled
  CheckpointDelay           300s
  Stages                    enabled
  StopAfterFactor           class
  PrintMode                 compact
  V5UserID                  none
  ComputerID                none
  TimeStampInResults        yes
  VectorSize                4
  GPUType                   AUTO
  SmallExp                  no
Compiletime options
  MORE_CLASSES              enabled
Select device - Get device info - Error -35 (Invalid queue properties): clCreateCommandQueue(dev#1)
init_CL(1, 11) failed

kracker · 2013-10-02, 00:51

My clinfo output:

kracker · 2013-10-02, 01:59

Only useful output seems with -d 11

Code:

Error -35 (Invalid queue properties): clCreateCommandQueue(dev#1) 
init_CL(1, 11) failed

Prime95 · 2013-10-02, 02:02

This opencl benchmark works on my haswell:
http://compubench.com/result.jsp

That should be promising.

Bdot · 2013-10-03, 00:24

Quote:

Originally Posted by Prime95

This opencl benchmark works on my haswell:
http://compubench.com/result.jsp

That should be promising.

Indeed.

It seems mfakto now selects the proper device, but it does not support CL_QUEUE_OUT_OF_ORDER_EXEC_MODE_ENABLE.

Please try the attached version (with -d 11). Lets see what the next error is. If you run it with additional -v 2, then it will also print the device info.

kracker · 2013-10-03, 00:56

-d 11 output. Hmm.

Prime95 · 2013-10-03, 02:47

My output matches kracker's.

2013-10-02, 01:59	#29
kracker "Mr. Meeseeks" Jan 2012 California, USA 887₁₆ Posts	Only useful output seems with -d 11 Code: Error -35 (Invalid queue properties): clCreateCommandQueue(dev#1) init_CL(1, 11) failed

2013-10-02, 02:02	#30
Prime95 P90 years forever! Aug 2002 Yeehaw, FL 17·487 Posts	This opencl benchmark works on my haswell: http://compubench.com/result.jsp That should be promising. Last fiddled with by Prime95 on 2013-10-02 at 02:02

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Can I run my CPU's integrated GPU along with my discrete GPU?	Red Raven	GPU Computing	9	2014-10-24 02:01
New integrated CPU-GPU programming paradigm	Dubslow	GPU Computing	1	2012-02-15 08:45
Ivy Bridge integrated GPU?	Dubslow	GPU Computing	7	2011-11-18 23:36
Can I use integrated graphics alongside a GPU?	mdettweiler	GPU Computing	9	2010-09-15 19:41
turn off your integrated Snd card in CMOS	nngs	Hardware	0	2005-05-20 01:31

2013-10-01, 19:12	#23
kracker "Mr. Meeseeks" Jan 2012 California, USA 37·59 Posts	Looks like clinfo lists it now, maybe try fidding with -d again see if it picks it up?

2013-10-01, 22:47	#24
Prime95 P90 years forever! Aug 2002 Yeehaw, FL 17×487 Posts	Still no luck. I looked very briefly at the source code and the startup code is quite a bit different than the Intel sample source code. It would be sad if AMD and Intel require different startup code, but it would not surprise me.

2013-10-03, 02:47	#33
Prime95 P90 years forever! Aug 2002 Yeehaw, FL 17·487 Posts	My output matches kracker's.