Intel Integrated GPU not working

Message boards : Number crunching : Intel Integrated GPU not working
Message board moderation

To post messages, you must log in.

Previous · 1 · 2

AuthorMessage
Profile HAL9000
Volunteer tester
Avatar

Send message
Joined: 11 Sep 99
Posts: 6534
Credit: 196,805,888
RAC: 57
United States
Message 1657860 - Posted: 27 Mar 2015, 19:13:49 UTC - in response to Message 1657844.  
Last modified: 27 Mar 2015, 19:17:58 UTC

So the latest status is that Intel GPU is detected by Boinc but no crunching on it.

Actually BOINC has not detected your iGPU. I think you might have mistaken this line for the iGPU.
27/03/2015 20:38:56 | | OpenCL CPU: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 3.0.1.10878, device version OpenCL 1.2 (Build 76413))

Which is just the CPU. Also a good way to tell is by the messages stating there is no iGPU.
27/03/2015 20:38:56 | | app version refers to missing GPU type intel_gpu

If BOINC had detected the iGPU you would see something along the lines of this:
3/27/2015 3:13:02 PM OpenCL: Intel GPU 0: Intel(R) HD Graphics 2500 (driver version 10.18.10.4061, device version OpenCL 1.2, 1298MB, 1298MB available, 53 GFLOPS peak)
3/27/2015 3:13:02 PM OpenCL CPU: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 3.0.1.10878, device version OpenCL 1.2 (Build 76413))
SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[
ID: 1657860 · Report as offensive
Mark Lybeck

Send message
Joined: 9 Aug 99
Posts: 245
Credit: 216,677,290
RAC: 173
Finland
Message 1657871 - Posted: 27 Mar 2015, 19:27:29 UTC

Ok. So boinc does not detect the intel gpu. However the Intel gpu is now showing on the device manager among installed devices.

from gpu-z

rops 4 / tmu 8
shaders 16
picel fillrate 2.6gpxels/s
ddr3 bus with 128bit
memory size 0MB

gpu clock 650mhz
memory clock 933mhz
multi-gpu disabled

open cl is unchecked
cuda unchecked
physx checked
direct compute unchecked
ID: 1657871 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14653
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1657872 - Posted: 27 Mar 2015, 19:28:51 UTC - in response to Message 1657871.  

Ok. So boinc does not detect the intel gpu. However the Intel gpu is now showing on the device manager among installed devices.

from gpu-z

rops 4 / tmu 8
shaders 16
picel fillrate 2.6gpxels/s
ddr3 bus with 128bit
memory size 0MB

gpu clock 650mhz
memory clock 933mhz
multi-gpu disabled

open cl is unchecked
cuda unchecked
physx checked
direct compute unchecked

Then try installing the GPU driver now.
ID: 1657872 · Report as offensive
OzzFan Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Apr 02
Posts: 15691
Credit: 84,761,841
RAC: 28
United States
Message 1657874 - Posted: 27 Mar 2015, 19:29:00 UTC - in response to Message 1657871.  

open cl is unchecked


You may need to reload the graphics driver. OpenCL is required to crunch.
ID: 1657874 · Report as offensive
Mark Lybeck

Send message
Joined: 9 Aug 99
Posts: 245
Credit: 216,677,290
RAC: 173
Finland
Message 1657875 - Posted: 27 Mar 2015, 19:29:17 UTC

which of these should i download and install?
https://software.intel.com/en-us/articles/opencl-drivers
ID: 1657875 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14653
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1657876 - Posted: 27 Mar 2015, 19:31:20 UTC - in response to Message 1657875.  
Last modified: 27 Mar 2015, 19:34:25 UTC

which of these should i download and install?
https://software.intel.com/en-us/articles/opencl-drivers

OUCH. None of those - those are for developers, not end users. What OS were you running again?

You were looking at https://downloadcenter.intel.com/download/24593, which is a pretty good one. Go back and read what I wrote at message 1654640 - with the GPU enabled in BIOS, that should work now.
ID: 1657876 · Report as offensive
Mark Lybeck

Send message
Joined: 9 Aug 99
Posts: 245
Credit: 216,677,290
RAC: 173
Finland
Message 1658306 - Posted: 28 Mar 2015, 16:41:42 UTC - in response to Message 1657876.  

I just followed the rules and the intel drivers for IGPU are installed. The question is should some additional drivers in addition to the standard device drivers be installed?
ID: 1658306 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14653
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1658323 - Posted: 28 Mar 2015, 17:27:46 UTC - in response to Message 1658306.  

I just followed the rules and the intel drivers for IGPU are installed. The question is should some additional drivers in addition to the standard device drivers be installed?

You may find that a monitor needs to be connected to the iGPU output, and/or the Windows desktop extended to include the iGPU. Claggy is the expert on this.
ID: 1658323 · Report as offensive
Mark Lybeck

Send message
Joined: 9 Aug 99
Posts: 245
Credit: 216,677,290
RAC: 173
Finland
Message 1658336 - Posted: 28 Mar 2015, 17:56:43 UTC - in response to Message 1658323.  

This is what I am afraid of. Getting a connector to the igpu port. I hope it does not need to be permanent.
ID: 1658336 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 5 Jul 99
Posts: 4654
Credit: 47,537,079
RAC: 4
United Kingdom
Message 1658347 - Posted: 28 Mar 2015, 18:31:36 UTC - in response to Message 1658323.  

I just followed the rules and the intel drivers for IGPU are installed. The question is should some additional drivers in addition to the standard device drivers be installed?

You may find that a monitor needs to be connected to the iGPU output, and/or the Windows desktop extended to include the iGPU. Claggy is the expert on this.

Hal6000 did a How too:

http://www.hal6000.com/seti/manual_display_detect.htm

Claggy
ID: 1658347 · Report as offensive
Profile HAL9000
Volunteer tester
Avatar

Send message
Joined: 11 Sep 99
Posts: 6534
Credit: 196,805,888
RAC: 57
United States
Message 1658618 - Posted: 29 Mar 2015, 6:32:46 UTC - in response to Message 1658347.  

I just followed the rules and the intel drivers for IGPU are installed. The question is should some additional drivers in addition to the standard device drivers be installed?

You may find that a monitor needs to be connected to the iGPU output, and/or the Windows desktop extended to include the iGPU. Claggy is the expert on this.

Hal6000 did a How too:

http://www.hal6000.com/seti/manual_display_detect.htm

Claggy

I found that I only had to extended the desktop when starting BOINC. Once BOINC was running I could switch back to a normal desktop until I restarted the system or BOINC.
SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[
ID: 1658618 · Report as offensive
Mark Lybeck

Send message
Joined: 9 Aug 99
Posts: 245
Credit: 216,677,290
RAC: 173
Finland
Message 1658743 - Posted: 29 Mar 2015, 13:27:15 UTC

I found an extra HDMI cable. Intel graphics settings popped up after plugging it in. Then a boinc restart did the trick. I changed config so that it runs only one WU at a time. Previously the config was set to 3. A long time (calendar-wise) to get the Intel IGPU working. Thank you for your help. Now it will be easier to replicate the process for the next workstation.

In hindsight I would summarize it into 3 key steps prior running Boinc:
1. Enable the IGPU in bios.
2. Install the drivers.
3. Connect the HDMI port.

Step 1. took longest time to work out.
ID: 1658743 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14653
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1658749 - Posted: 29 Mar 2015, 13:40:07 UTC - in response to Message 1658743.  

I found an extra HDMI cable. Intel graphics settings popped up after plugging it in. Then a boinc restart did the trick. I changed config so that it runs only one WU at a time. Previously the config was set to 3. A long time (calendar-wise) to get the Intel IGPU working. Thank you for your help. Now it will be easier to replicate the process for the next workstation.

In hindsight I would summarize it into 3 key steps prior running Boinc:
1. Enable the IGPU in bios.
2. Install the drivers.
3. Connect the HDMI port.

Step 1. took longest time to work out.

That's a useful summary - thanks, Mark. Well done on getting there in the end.
ID: 1658749 · Report as offensive
Mark Lybeck

Send message
Joined: 9 Aug 99
Posts: 245
Credit: 216,677,290
RAC: 173
Finland
Message 1660071 - Posted: 1 Apr 2015, 3:07:59 UTC
Last modified: 1 Apr 2015, 3:09:11 UTC

I installed the drivers on another workstation. The Intel IGPU errors out.
I temporarily connected the HDMI port to activate the IGPU when starting boinc and disconnected it from the monitor. Does the HDMI need to be connected all the time for the computation to work?


<result>
<name>25au12ad.6250.245271.438086664208.12.97_1</name>
<final_cpu_time>0.000000</final_cpu_time>
<final_elapsed_time>0.000000</final_elapsed_time>
<exit_status>-226</exit_status>
<state>3</state>
<platform>windows_intelx86</platform>
<version_num>703</version_num>
<plan_class>opencl_intel_gpu_sah</plan_class>
<stderr_out>
<![CDATA[
<message>
too many boinc_temporary_exit()s
</message>
<stderr_txt>
Running on device number: 0

Priority of worker thread raised successfully

Priority of process adjusted successfully, below normal priority class used

WARNING: boinc_get_opencl_ids failed with code -1

OpenCL platform detected: NVIDIA Corporation

OpenCL platform detected: Intel(R) Corporation

WARNING: BOINC supplied wrong platform!

ERROR: OpenCL kernel/call 'clGetDeviceIDs' call failed (-1) in file ..\..\..\src\GPU_lock.cpp near line 738.

Waiting 30 sec before restart...

Running on device number: 0

Priority of worker thread raised successfully

Priority of process adjusted successfully, below normal priority class used

WARNING: boinc_get_opencl_ids failed with code -1

OpenCL platform detected: NVIDIA Corporation

OpenCL platform detected: Intel(R) Corporation

WARNING: BOINC supplied wrong platform!

ERROR: OpenCL kernel/call 'clGetDeviceIDs' call failed (-1) in file ..\..\..\src\GPU_lock.cpp near line 738.

Waiting 30 sec before restart...
ID: 1660071 · Report as offensive
Profile HAL9000
Volunteer tester
Avatar

Send message
Joined: 11 Sep 99
Posts: 6534
Credit: 196,805,888
RAC: 57
United States
Message 1660105 - Posted: 1 Apr 2015, 4:14:47 UTC - in response to Message 1660071.  

http://setiathome.berkeley.edu/forum_thread.php?id=76542&postid=1658618#1658618
SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[
ID: 1660105 · Report as offensive
Previous · 1 · 2

Message boards : Number crunching : Intel Integrated GPU not working


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.