I just added support for Intel GPUs. There are 2 versions - 64 bit linux and 64 bit windows, both require openCL 1.1 or higher.

I don't have an Intel GPU, so I can't test them. But it's the same openCL code that works on other GPUs, so in theory they should work. For the linux version, it was just a matter of downloading the Intel openCL SDK and then linking against Intel's include files and libraries. For the windows version, I cross compiled using mingw64 as I do with AMD/Nvidia cards.

Since they are new and untested, I made them beta apps.

No option to select Intel GPU in preferences.
Please can you fix?

No option to select Intel GPU in preferences.
Please can you fix?

I found the problem. The server code assumes the plan class name contains the string "intel_gpu". I was using just "intel".

The option now shows up in the preferences.

Thank you.
I have now set the preferences.
However, my BOINC clients still report "Project has no apps for Intel GPU" under Projects -> Properties.
This is the same under both Windows x86_64 and Linux x86_64.

My device is an i5-7300u running Windows 10. In the preference section I marked "Intel GPU" and "accept test apps". So far I haven't gotten any WU's. This is the only answer I am getting on the message board:

18.11.2021 08:01:10 | NumberFields@home | update requested by user
18.11.2021 08:01:14 | NumberFields@home | Project requested delay of 31 seconds

My device is an i5-7300u running Windows 10. In the preference section I marked "Intel GPU" and "accept test apps". So far I haven't gotten any WU's. This is the only answer I am getting on the message board:

18.11.2021 08:01:10 | NumberFields@home | update requested by user
18.11.2021 08:01:14 | NumberFields@home | Project requested delay of 31 seconds

Not sure what is wrong. I removed the beta designation just in case that is the cause. When I have some time later I will dig deeper into this.

Just had this happen:

18/11/2021 15:36:28 | NumberFields@home | Scheduler request completed: got 42 new tasks
18/11/2021 15:36:28 | NumberFields@home | [sched_op] estimated total Intel GPU task duration: 26357 seconds
18/11/2021 15:36:30 | NumberFields@home | Started download of GetDecics_4.02_windows_x86_64__opencl_intel

The download of the .exe file is going very slowly (21 MB at a speed of 16 KBps), but it's getting there. Should be finished in 15 mins or so. I'll be watching host 1291 - any particular feedback you'd like?

Edit:

18/11/2021 16:05:58 | NumberFields@home | Finished download of GetDecics_4.02_windows_x86_64__opencl_intel
18/11/2021 16:06:04 | NumberFields@home | Starting task wu_sf3_DS-16x271-15_Grp669648of1000000_0

Nearly half an hour to download! A caching server (e.g. Cloudflare) can help with that - otherwise, just have patience. It'll be better when the initial rush has died down.

This doesn't look right. From stderr, in running:

GPU Summary String = [CUDA|NVIDIAGeForceGTX1660SUPER|2|4095MB|47212|300][INTEL|Intel(R)HDGraphics4600|1|1297MB||102].
Loading GPU lookup table from file.
GPU found in lookup table:
  GPU Name = GTX1660.
  numBlocks = 8192.
  threadsPerBlock = 32.
  polyBufferSize = 262144.

The "Intel HD Graphics 4600" is right (present on the machine, OpenCL driver installed, known to BOINC, ready for use), but the GPU Name and (probably) metrics are from the wrong manufacturer.

And this doesn't look right, either.

D:\BOINCdata\slots\5>dir
 Volume in drive D has no label.
 Volume Serial Number is E0ED-E51A

 Directory of D:\BOINCdata\slots\5

18/11/2021  16:06    <DIR>          .
18/11/2021  16:06    <DIR>          ..
18/11/2021  16:06                 0 boinc_lockfile
18/11/2021  16:06               117 GetDecics_4.02_windows_x86_64__opencl_intel
30/01/2021  10:51               349 gpuLookupTable.txt
30/01/2021  10:51            34,028 gpuMultiPrec.h
18/11/2021  16:06               113 in
18/11/2021  16:06            10,923 init_data.xml
30/01/2021  10:51               728 mp_int.h
18/11/2021  16:06               128 out
30/01/2021  10:51            76,646 pdtKernel.cl
18/11/2021  16:06               281 stderr.txt
              10 File(s)        123,313 bytes

I don't see any sign of the app recording progress. I'd expect to see a 'boinc_task_state.xml' file by now.

Initial runtime estimate was 10 min 42 sec (BOINC estimates are notoriously unreliable for a new app): it's been running for 18:30, but I'm not sure it's done anything.

2x Windows i7-4770 with "HD Graphics 4600" now have work underway.
Linux i7-9750H with "Gen9 HD Graphics NEO" managed to pick up a WCG WU,
so will check on it later.

First task has reached an indicated 99% progress after 50 minutes, but I strongly suspect this is BOINC's imaginary 'pseudo progress' from a stalled app. I'll keep an eye on it.

Still running, after an hour and three quarters. I'm even more convinced it's stalled, so I'll have a deeper dig later.

Workunit has settings

             <rsc_fpops_est>30000000000000.000000</rsc_fpops_est>
    <rsc_fpops_bound>700000000000000000000.000000</rsc_fpops_bound>

That means that BOINC will allow it to run for over four centuries before it intervenes to abort it. I don't think I've quite got that much patience...

I am seeing tons of WUs sent out (over 4000) so I am setting the beta flag again.

Most are in the init phase, but there are several successful results, so that is encouraging. The successful ones appear to be "UHD Graphics 630"

Still running, after an hour and three quarters. I'm even more convinced it's stalled, so I'll have a deeper dig later.

Workunit has settings

             <rsc_fpops_est>30000000000000.000000</rsc_fpops_est>
    <rsc_fpops_bound>700000000000000000000.000000</rsc_fpops_bound>

That means that BOINC will allow it to run for over four centuries before it intervenes to abort it. I don't think I've quite got that much patience...

Thanks for the feedback, Richard!

When these tasks stall that is usually a sign that the openCL compiler is hung. And that is probably why the boinc_task_state.xml file is not present, as I am guessing that gets created after the openCL code is built. We saw this same thing with the AMD app version, and it's dependent on the particular openCL driver and also the card.

Probably best to just abort them when you see this behavior.

On my J4105 with Ubuntu 20.04 all wu crashed with:
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found
https://numberfields.asu.edu/NumberFields/result.php?resultid=124652101

After upgrade to Ubuntu 21.04 it run.

On two host with win10 wu are running.

Probably best to just abort them when you see this behavior.

Yes, I'll probably do that before I go to bed this evening, but we may as well get as much information from them as possible.

I have one machine with

02-Nov-2021 12:05:09 [---] OpenCL: Intel GPU 0: Intel(R) HD Graphics 530 (driver version 21.20.16.5103, device version OpenCL 2.0, 1298MB, 1298MB available, 202 GFLOPS peak)

(host 33342)

That has reached

Now starting the targeted Martinet search:
  Num Cvecs = 50.
    Doing Cvec 1.
    Doing Cvec 2.
    Doing Cvec 3.

but it's taken two and a half hours - barely better then an abacus! - but that too has no task_state.xml file. It is, however, showing a steady and appropriate progress value of 5.003%, so maybe that was a false alarm.

I also have UHD 620 machine, but it's not crunching at the moment. Maybe tomorrow.

On my J4105 with Ubuntu 20.04 all wu crashed with:
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found
https://numberfields.asu.edu/NumberFields/result.php?resultid=124652101

After upgrade to Ubuntu 21.04 it run.

On two host with win10 wu are running.

Thanks for the feedback! Yes, looks like the old GLIBC problem is back. I'll put that on my to do list.

I am not familiar with Intel's lineup of GPUs. I did a little research, and it appears they rank pretty low compared to Nvidia and AMD cards. I'm thinking the UHD 630 might be as low as we can go without hanging the GPU. It looks like the soon to be released Arc Alchemist should do very well.

This doesn't look right. From stderr, in running:

GPU Summary String = [CUDA|NVIDIAGeForceGTX1660SUPER|2|4095MB|47212|300][INTEL|Intel(R)HDGraphics4600|1|1297MB||102].
Loading GPU lookup table from file.
GPU found in lookup table:
  GPU Name = GTX1660.
  numBlocks = 8192.
  threadsPerBlock = 32.
  polyBufferSize = 262144.

The "Intel HD Graphics 4600" is right (present on the machine, OpenCL driver installed, known to BOINC, ready for use), but the GPU Name and (probably) metrics are from the wrong manufacturer.

This is just a flaw with the lookup mechanism - it found your GTX1660 in the lookup table and decided to use those parameters. I need to create a separate lookup table for the intel GPUs.

If you're inclined to fiddle with the lookup table, all you need to do is remove the entry for the 1660 and add a line for the Intel gpu. The only requirement is the name must be a substring of the GPU summary string (for example "HD Graphics 4600" would work). You would also want to reduce the numBlocks to something smaller, like 512. ThreadsPerBlock could stay at 32. ( I would need to study the Intel architecture to find more optimal settings).

Note: using the settings for the GTX1660 might be the cause of the problem you are seeing, because the Intel card probably doesn't have the required resources.

If this will help, it ran for 2.5 hours before I aborted all wus.

https://numberfields.asu.edu/NumberFields/result.php?resultid=124654535