Message boards :
Number crunching :
Intel GPU App ready?
Message board moderation
Author | Message |
---|---|
James W Send message Joined: 26 May 12 Posts: 51 Credit: 4,956,027 RAC: 13 |
I have the INTEL Intel(R) HD Graphics 2500 onboard in my Dell OptiPlex. As Intel GPU has not been supported, have only been crunching with CPU, and BOINC would only request CPU work units. However, today notice BOINC has also started to request Intel GPU work (01/29/2014 1:35:58 PM | SETI@home | Requesting new tasks for CPU and intel_gpu) Still have only received CPU work (running Windows 7). Are Intel GPU tasks now available? Thanks. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
Intel GPU app is available as stock app now. Tasks are the same as before, no difference in tasks for different hardware, only apps to process them differ. SETI apps news We're not gonna fight them. We're gonna transcend them. |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
In your Project preferences is Use Intel GPU (Enforced by version 7.2+) set to Yes? Looking at the project apps it was just published, or updated today. Also see your machine says "INTEL Intel(R) HD Graphics 2500 (1624MB) OpenCL: 1.01" OpenCL 1.2 is listed as a requirement. I'm not sure if that GPU supports 1.2, or if a driver update will get you 1.2 support. SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
I'm not sure if that GPU supports 1.2, or if a driver update will get you 1.2 support. It should be just a driver update, But since it's a Dell there may or maynot be a OpenCL 1.2 driver available for a particular model. Claggy |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
I'm not sure if that GPU supports 1.2, or if a driver update will get you 1.2 support. If Dell does not provide an updated driver. As they just redistribute such drivers for hardware that they don't put their name on. The two most recent, 15.33.8.64.3345 & 15.31.17.64.3257, from Intel do list OpenCL 1.2 support. SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
S197Mach1 Send message Joined: 16 Jan 11 Posts: 9 Credit: 20,120,713 RAC: 0 |
running into same issue. Running latest lunatics and wasn't pulling any intel units. Downloaded the MB app and gen up the following and still haven't seen anything come my way. Preferences are accepting tasks. <app> <name>setiathome_v7</name> </app> <file_info> <name>MB7_win_x86_SSE_OpenCL_Intel_r2061.exe</name> <executable/> </file_info> <file_info> <name>libfftw3f-3.dll</name> <executable/> </file_info> <file_info> <name>mb_cmdline_win_x86_SSE_OpenCL_Intel.txt</name> </file_info> <app_version> <app_name>setiathome_v7</app_name> <version_num>703</version_num> <platform>windows_intelx86</platform> <file_ref> <file_name>MB7_win_x86_SSE_OpenCL_Intel_r2061.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3.dll</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE_OpenCL_Intel.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> <app_version> <app_name>setiathome_v7</app_name> <version_num>703</version_num> <platform>windows_x86_64</platform> <file_ref> <file_name>MB7_win_x86_SSE_OpenCL_Intel_r2061.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3.dll</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE_OpenCL_Intel.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> |
James W Send message Joined: 26 May 12 Posts: 51 Credit: 4,956,027 RAC: 13 |
I'm no expert on GPUs, but in pulling up your computers on SETI site, this shows you have 2 NVIDIA cards in each machine. No mention of an INTEL GPU. On my machine, IntelCore(TM) i5-3470 CPU with Intel(R) HD Graphics 2500 shown as the coprocessor (GPU). I take it you also have an HD Graphics onboard? I'm working on upgrading my GPU/video driver to get the required OpenCL 1.2. I only have OpenGL 1.01 on now, which is the latest video driver Dell supplies. Intel's site has a much newer update, though the .exe for it won't install on my OptiPlex because of Dell's supposed "customizations." Intel gives a workaround for this, downloading the zip file and manually installing. Not sure how much of Dell's customizing is legit or just advertising hype? I'm not sure if your system will recognize both your NVIDIA cards and the Intel. I'd need to defer to someone with more experience with GPU, BOINC, and SETI's apps. Good Luck. |
Ulrich Metzner Send message Joined: 3 Jul 02 Posts: 1256 Credit: 13,565,513 RAC: 13 |
For intel GPUs to be recognized by BOINC, you need an OpenCL 1.2 capable driver and the intel GPU must be connected to a monitor or used as primary display device. If the device is not active, it will not be recognized by BOINC. Nvidia devices are recognized even without a monitor connected or being primary device. You can see it in my computers, the (Dell) notebook with intel and Nvidia graphics is using the intel GPU as primary device and the Nvidia as secondary without connected monitor. If i use the Nvidia device as primary, the intel device is dormant and not discoverable by BOINC. It is this one: http://setiathome.berkeley.edu/show_host_detail.php?hostid=7068094 You can also try <use_all_gpus>1</use_all_gpus> in cc_config.xml Aloha, Uli |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14645 Credit: 200,643,578 RAC: 874 |
OpenCL 1.2 is not needed for BOINC to detect the Intel HD GPUs, but it is strongly recommended for crunching - Einstein won't even allocate tasks if 1.1 is detected. That may be the case here too - I'm still on anonymous platform for now. When I've transitioned back to stock, and got the definitive file-set, I'll post some instructions and an aistub for adding Intel to an existing Lunatics installation. May take a day or two to shake off this dose of man-flu, and catch some of the next batch of APs. |
Ulrich Metzner Send message Joined: 3 Jul 02 Posts: 1256 Credit: 13,565,513 RAC: 13 |
(...) I'll post some instructions and an aistub for adding Intel to an existing Lunatics installation. (...) You can already get the executable and all necessary files including aistub from Mike's site: http://mikesworldnet.de/produkte.html Direct download: http://mikesworldnet.de/mb7_win_x86_sse_opencl_intel_r2061.7z There is also an intel astropulse V6 executable available. Aloha, Uli |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14645 Credit: 200,643,578 RAC: 874 |
(...) I'll post some instructions and an aistub for adding Intel to an existing Lunatics installation. (...) There's something a bit odd about the <platform> tags in that AIstub. I'd be wary about upgrading over stock download tasks on a 32-bit platform with that version. Let's keep testing until we get it right. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14645 Credit: 200,643,578 RAC: 874 |
Also watch out that Mike's download references the Beta plan_classes. If you install it on the Main project while you have stock work cached, that work will be trashed. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
Well, failed to enable Intel GPU crunching under anonymous platform on own host: 2/1/2014 11:09:22 AM | SETI@home | [sched_op] Starting scheduler request 2/1/2014 11:09:22 AM | SETI@home | Sending scheduler request: To fetch work. 2/1/2014 11:09:22 AM | SETI@home | Reporting 36 completed tasks 2/1/2014 11:09:22 AM | SETI@home | Requesting new tasks for CPU and NVIDIA and intel_gpu 2/1/2014 11:09:22 AM | SETI@home | [sched_op] CPU work request: 4337136.12 seconds; 0.00 devices 2/1/2014 11:09:22 AM | SETI@home | [sched_op] NVIDIA work request: 2124284.16 seconds; 0.00 devices 2/1/2014 11:09:22 AM | SETI@home | [sched_op] intel_gpu work request: 1296000.00 seconds; 1.00 devices 2/1/2014 11:09:26 AM | SETI@home | Scheduler request completed: got 36 new tasks 2/1/2014 11:09:26 AM | SETI@home | [sched_op] Server version 703 2/1/2014 11:09:26 AM | SETI@home | Project requested delay of 303 seconds 2/1/2014 11:09:26 AM | SETI@home | [sched_op] estimated total CPU task duration: 149939 seconds 2/1/2014 11:09:26 AM | SETI@home | [sched_op] estimated total NVIDIA task duration: 127940 seconds 2/1/2014 11:09:26 AM | SETI@home | [sched_op] estimated total intel_gpu task duration: 0 seconds app_info part is: <app> <name>setiathome_v7</name> </app> <file_info> <name>MB7_win_x86_SSE_OpenCL_Intel_r2116.exe</name> <executable/> </file_info> <file_info> <name>libfftw3f-3.dll</name> <executable/> </file_info> <file_info> <name>mb_cmdline_win_x86_SSE_OpenCL_Intel.txt</name> </file_info> <app_version> <app_name>setiathome_v7</app_name> <version_num>703</version_num> <platform>windows_intelx86</platform> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>opencl_intel_gpu_sah</plan_class> <cmdline></cmdline> <coproc> <type>intel_gpu</type> <count>1</count> </coproc> <file_ref> <file_name>MB7_win_x86_SSE_OpenCL_Intel_r2116.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3.dll</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE_OpenCL_Intel.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> Any ideas? P.S. BOINC initial log: 2/1/2014 11:08:56 AM | | CUDA: NVIDIA GPU 0: GeForce 9600 GSO (driver version 263.06, CUDA version 3.2, compute capability 1.1, 370MB, 347MB available, 490 GFLOPS peak) 2/1/2014 11:08:56 AM | | CUDA: NVIDIA GPU 1: GeForce 9400 GT (driver version 263.06, CUDA version 3.2, compute capability 1.1, 498MB, 486MB available, 67 GFLOPS peak) 2/1/2014 11:08:56 AM | | OpenCL: NVIDIA GPU 0: GeForce 9600 GSO (driver version 263.06, device version OpenCL 1.0 CUDA, 370MB, 347MB available, 490 GFLOPS peak) 2/1/2014 11:08:56 AM | | OpenCL: NVIDIA GPU 1: GeForce 9400 GT (driver version 263.06, device version OpenCL 1.0 CUDA, 498MB, 486MB available, 67 GFLOPS peak) 2/1/2014 11:08:56 AM | | OpenCL: Intel GPU 0: Intel(R) HD Graphics 2500 (driver version 9.18.10.3257, device version OpenCL 1.2, 1496MB, 1496MB available, 17 GFLOPS peak) 2/1/2014 11:08:56 AM | | OpenCL CPU: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 1.2, device version OpenCL 1.2 (Build 66956)) 2/1/2014 11:08:56 AM | SETI@home | Found app_info.xml; using anonymous platform 2/1/2014 11:08:56 AM | | Processor: 4 GenuineIntel Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz [Family 6 Model 58 Stepping 9] 2/1/2014 11:08:56 AM | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 cx16 sse4_1 sse4_2 popcnt aes syscall nx lm vmx smx tm2 pbe 2/1/2014 11:08:56 AM | | OS: Microsoft Windows 7: Professional x64 Edition, Service Pack 1, (06.01.7601.00) 2/1/2014 11:08:56 AM | | Memory: 3.69 GB physical, 7.38 GB virtual 2/1/2014 11:08:56 AM | | Disk: 48.83 GB total, 47.76 GB free 2/1/2014 11:08:56 AM | | Local time is UTC +4 hours 2/1/2014 11:08:56 AM | | Config: use all coprocessors SETI apps news We're not gonna fight them. We're gonna transcend them. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14645 Credit: 200,643,578 RAC: 874 |
Any ideas? Give it a chance? There's no guarantee - never has been - that every part of a work request will be filled on every request. And turn down that stupid cache size - 15 days is way too long. You've probably filled your quota of 100 GPU tasks with NVidia work. Try deselecting NV in preferences for a few hours to let some burn off and make space. Edit - I assume we're talking host 6915997 - the only one in your list with both types of GPU. 200 tasks in progress: you're stuffed full, as surmised. Wait until there's some space, and then you'll find out if it works. Edit 2 - sorry, I'm waking up slowly here. Post #8000, and another round million credits... |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
??? I have 3 different device types: 4-cores CPU, 2 NV GPUs and 1 Intel GPU. From where 200 limit came? Should it be at least 300, not ?? How my Intel GPU can have any work then at all if fastest device (GSO9600 in my case) should be filled first ? P.S. and congrats with 8k post, lets go further and do 8001th ;D SETI apps news We're not gonna fight them. We're gonna transcend them. |
Mike Send message Joined: 17 Feb 01 Posts: 34250 Credit: 79,922,639 RAC: 80 |
4-cores CPU, 2 NV GPUs and 1 Intel GPU. From where 200 limit came? Task limit is 100 for CPU and 100 for GPU`s. No matter how many GPU´s are attached. Thats it. So lower your cache settings the better the chance to get work for slow GPU. With each crime and every kindness we birth our future. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
OMG, those limits even worse than I thought ... SETI apps news We're not gonna fight them. We're gonna transcend them. |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
4-cores CPU, 2 NV GPUs and 1 Intel GPU. From where 200 limit came? and No matter how many GPUs from different vendors a host has, To keep both GPUs fed you need to have a small enough cache set that both GPUs get work, beware of shortie storms, the fastest app_version will get all the work, and the cache level will have to be lowered more. Claggy |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
Yes, I understood. But such limits are ... (censored). It's much more unfair approach than all that could rise from so hated re-scheduling... SETI apps news We're not gonna fight them. We're gonna transcend them. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
But it repeated again: 2/1/2014 9:32:56 PM | SETI@home | [sched_op] Starting scheduler request 2/1/2014 9:32:56 PM | SETI@home | Sending scheduler request: To fetch work. 2/1/2014 9:32:56 PM | SETI@home | Reporting 43 completed tasks 2/1/2014 9:32:56 PM | SETI@home | Requesting new tasks for CPU and NVIDIA and intel_gpu 2/1/2014 9:32:56 PM | SETI@home | [sched_op] CPU work request: 1284986.07 seconds; 0.00 devices 2/1/2014 9:32:56 PM | SETI@home | [sched_op] NVIDIA work request: 569324.72 seconds; 0.00 devices 2/1/2014 9:32:56 PM | SETI@home | [sched_op] intel_gpu work request: 518400.00 seconds; 1.00 devices 2/1/2014 9:33:00 PM | SETI@home | Scheduler request completed: got 43 new tasks 2/1/2014 9:33:00 PM | SETI@home | [sched_op] Server version 703 2/1/2014 9:33:00 PM | SETI@home | Project requested delay of 303 seconds 2/1/2014 9:33:00 PM | SETI@home | [sched_op] estimated total CPU task duration: 212585 seconds 2/1/2014 9:33:00 PM | SETI@home | [sched_op] estimated total NVIDIA task duration: 110451 seconds 2/1/2014 9:33:00 PM | SETI@home | [sched_op] estimated total intel_gpu task duration: 0 seconds Ok, it can be coincidence still. Now I set cache to 0.1 day to completely inhibit work requests from CPU and CUDA. Will see if Intel GPU get some work asking alone and under limits. Will try after few hours when some tasks will be finished. SETI apps news We're not gonna fight them. We're gonna transcend them. |
©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.