OpenCL™ Runtimes for Intel® Processors

Published: 03/02/2020 Last Updated: 09/08/2020

Deploy OpenCL™ Runtimes

Obtain runtimes to execute or develop OpenCL™ applications on Intel­® Processors

Important Change

There is a change in OpenCL™ CPU runtime for Windows* distribution in the 2020 February release to be consistent with Linux* distribution. The OpenCL CPU runtime is removed from the OpenCL driver for Windows starting in the 2020 February release version «igfx_win10_100.7870.exe».

• But the installer of the new driver did not remove the old OpenCL CPU runtime when you upgrade the newer driver, so you may have two OpenCL CPU runtimes on your system. This issue is already fixed in the installation script on github here.
• To download the OpenCL CPU runtime for Windows, please follow any of the following methods:
  • Follow the section «Intel® CPU Runtime for OpenCL™ Applications 18.1 for Windows* OS (64bit or 32bit)» below to download and install.
  • Github: https://github.com/intel/llvm/releases
    • Search for «oneAPI DPC++ Compiler dependencies» and find latest release to download, e.g. https://github.com/intel/llvm/releases/tag/2020-WW20
    • Following the installation instructions to install

Intel® Graphics Technology Runtimes

Execute OpenCL™ applications on Intel® Processors with Intel® Graphics Technology.

• Specifically target Intel® HD Graphics, Intel® Iris® Graphics, and Intel® Iris® Pro Graphics if available on Intel® Processors.
• Runtimes for Intel® Graphics Technology are often deployed in tandem with an Intel® CPU runtime.
• Consider graphics runtimes when developing OpenCL™ applications with the Intel® SDK for OpenCL™ Applications or Intel® System Studio.

Check release notes to ensure supported targets include your target device. For Intel® processors older than supported targets, please see the legacy deployment page.

Linux* OS

Note: The latest OpenCL runtime for CPU requires GNU* gcc version 7.3 or newer.

Intel® Graphics Compute Runtime for OpenCL™ Driver is deployed with package managers for multiple distributions. Please see the documentation on the GitHub* portal for deployment instructions.

Considerations for deployment:

• Ensure the deployment system has the (libOpenCL.so) ICD loader runtime from either:
  • Your system package manager (for example with the unofficial ocl-icd )
    • Useful package manager search hints:
      • apt update; apt-file find libOpenCL.so
      • yum provides «*/libOpenCL.so»
  • Build from the official Khronos ICD Loader reference repository.
  • Part of the Intel® SDK for OpenCL™ Applications.
• The Intel® Graphics Compute Runtime for OpenCL™ Driver depends on the i915 kernel driver. Necessary i915 features are available with relatively recent Linux* OS kernels. The recommended kernel is the validation kernel cited in documentation. In general, deployments after the 4.11 kernel should be OK. Make sure to review the release notes and documentation for more specifics.

Windows* OS

• Intel® Graphics Compute Runtime for OpenCL™ Driver is included with the Intel® Graphics Driver package for Windows* OS.
• Download Options
  • System Vendor
    • See your vendor website for a graphics or video driver download for the system
  • Intel® Download Center
    • Navigate to “Graphics Drivers” for recent releases.
    • Try the system vendor first in consideration of vendor support. System vendors may disable Intel® Graphics Driver install.
  • Intel® Driver Update Utility
  • The graphics driver package is built in with Windows* 10 OS install. However, the built-in default deployment may not contain latest features.
• Release Notes
  • In the Download Center navigate to “Graphics Drivers” for Release Notes.

Intel® Xeon® Processor OR Intel® Core™ Processor (CPU) Runtimes

Execute OpenCL™ kernels directly on Intel® CPUs as OpenCL™ target devices.

• Consider an OpenCL™ CPU implementation for Intel® systems without Intel® Graphics Technology.
• Systems with Intel® Graphics Technology can simultaneously deploy runtimes for Intel® Graphics Technology and runtimes for Intel® CPU (x86-64).
• For application developers, the CPU-only runtime is pre-included with the Intel® SDK for OpenCL™ Applications or Intel® System Studio: OpenCL™ Tools component.

Check release notes to ensure supported targets include your target device. For Intel® processors older than supported targets, see the legacy deployment page.

Intel® CPU Runtime for OpenCL™ Applications 18.1 for Linux* OS (64bit only)

• Size 125 MB
• See supported platform details in the Release Notes.
• Ubuntu* install uses an rpm translator
• The Linux* OS CPU runtime package also includes the ICD loader runtime (libOpenCL.so). The runtime installer should set the deployment system to see this ICD loader runtime by default. When examining system libraries, administrators may observe ICD loader runtimes obtained from other places. Examples include the system package manager (for example with ocl-icd) or as part of the Intel® SDK for OpenCL™ Applications.
• Maintenance and updates are now provided in the Experimental Intel® CPU Runtime for OpenCL™ Applications with SYCL support implementation. This implementation is listed later in this article.
• MD5 83c428ab9627268fc61f4d8219a0d670
• SHA1 5f2fa6e6bc400ca04219679f89ec289f17e94e5d

Intel® CPU Runtime for OpenCL™ Applications 18.1 for Windows* OS (64bit or 32bit)

• Size 60 MB
• CPU-only deployments should use the .msi installer linked in the Download button, and consider removal of the Intel® Graphics Technology drivers where applicable.
• CPU & Graphics deployments should use the Intel® Graphics Technology driver package, which contains both CPU (x86-64) and Intel® Graphics Technology implementations.
• See supported operating system details in the Release Notes
• Maintenance and updates are now provided in the Experimental Intel® CPU Runtime for OpenCL™ Applications with SYCL support implementation. This implementation is listed later in this article.
• MD5 8e24048001fb46ed6921d658dd71b8ff
• SHA1 451d96d37259cb111fe8832d5513c5562efa3e56

Intel® CPU Runtime for OpenCL™ Applications with SYCL support

Please visit the Intel® CPU Runtime for OpenCL™ Applications with SYCL support to download and install the runtime for Windows or Linux.

Develop OpenCL™ Applications

Tools to develop OpenCL™ applications for Intel® Processors

Intel® oneAPI: DPC++ Compiler

• DPC++/SYCL programs can run SYCL kernels by way of underlying OpenCL™ implementations.
• OpenCL-C kernels can also be directly ingested and run by a SYCL runtime. Users of the OpenCL C++ API wrapper may find the SYCL specification particularly appealing.
• Explore the Intel® oneAPI: DPC++ Compiler, Github* hosted DPC++/SYCL code samples, OpenCL™ injection tests, as well as training videos part1 and part2 on techdecoded.intel.io.
• As of article publication, this compiler is in Beta.

Intel® System Studio

• For compilation, cross-platform, IoT, power considerate development, and performance analysis.
  • OpenCL™ development tools component:
    • Develop OpenCL™ applications targeting Intel® Xeon® Processors, Intel® Core™ Processors, and/or Intel® Graphics Technology.
    • Develop applications with expanded IDE functionality, debug, and analysis tools.
      • Note: Some debug and analysis features have been removed from recent versions of the SDK.
    • Earlier versions of the SDK contain an experimental OpenCL™ 2.1 implementation. Intel® CPU Runtime for OpenCL™ Applications 18.1 was intended as a replacement for the experimental implementation.
• Visit the Intel® System Studio portal

Intel® SDK for OpenCL™ Applications

• Standalone distribution of Intel® System Studio: OpenCL™ Tools component.
• Develop OpenCL™ Applications targeting Intel® Xeon® Processors, Intel® Core™ Processors, and/or Intel® Graphics Technology.
• Develop applications with expanded IDE functionality, debug, and analysis tools.
  • Note: Some debug and analysis features have been removed from recent versions of the SDK.
  • Earlier versions of the SDK contain an experimental OpenCL™ 2.1 implementation suitable for development testing on CPU OpenCL™ targets. Intel® CPU Runtime for OpenCL™ Applications 18.1 was intended as a replacement for that experimental implementation.
• See release notes, requirements, and download links through the Intel® SDK for OpenCL™ Applications portal.

Intel® FPGA SDK for OpenCL™ Software Technology

• Build OpenCL™ Applications and OpenCL™ kernels for Intel® FPGA devices.
• See release notes, requirements, and download links through the SDK’s portal webpage.
• For OpenCL™ runtimes and required system drivers, visit Download Center for FPGAs.

Intel® Distribution of OpenVINO™ toolkit

• The Intel® Distribution of OpenVINO™ toolkit is available for vision and deep learning inference. It benefits from OpenCL™ acceleration for each of these components:
  • Intel® Deep Learning Deployment Toolkit
  • OpenCV
  • OpenVX*
• For a developer oriented overview, see videos on the techdecoded.intel.io training hub.

Intercept Layer for Debugging and Analyzing OpenCL™ Applications

• The Intercept Layer for Debugging and Analyzing OpenCL™ Applications (clIntercept) can intercept, report, and modify OpenCL™ API calls.
• No application-level modifications nor OpenCL™ implementation modifications are necessary.
• clIntercept functionality can supplement removed functionality from recent releases of the Intel® SDK for OpenCL™ Applications.

Additional resources

*OpenCL and the OpenCL logo are trademarks of Apple Inc. used by permission by Khronos.

Manually download Windows Subsystem for Linux distro packages

There are several scenarios in which you may not be able (or want) to, install WSL Linux distros via the Microsoft Store. Specifically, you may be running a Windows Server or Long-Term Servicing (LTSC) desktop OS SKU that doesn’t support Microsoft Store, or your corporate network policies and/or admins to not permit Microsoft Store usage in your environment.

In these cases, while WSL itself is available, how do you download and install Linux distros in WSL if you can’t access the store?

Note: Command-line shell environments including Cmd, PowerShell, and Linux/WSL distros are not permitted to run on Windows 10 S Mode. This restriction exists in order to ensure the integrity and safety goals that S Mode delivers: Read this post for more information.

Downloading distributions

If the Microsoft Store app is not available, you can download and manually install Linux distros by clicking these links:

This will cause the .appx packages to download to a folder of your choosing. Follow the installation instructions to install your downloaded distro(s).

Downloading distros via the command line

If you prefer, you can also download your preferred distro(s) via the command line:

Download using PowerShell

To download distros using PowerShell, use the Invoke-WebRequest cmdlet. Here’s a sample instruction to download Ubuntu 16.04.

If the download is taking a long time, turn off the progress bar by setting $ProgressPreference = ‘SilentlyContinue’

Download using curl

Windows 10 Spring 2018 Update (or later) includes the popular curl command-line utility with which you can invoke web requests (i.e. HTTP GET, POST, PUT, etc. commands) from the command line. You can use curl.exe to download the above distros:

In the above example, curl.exe is executed (not just curl ) to ensure that, in PowerShell, the real curl executable is invoked, not the PowerShell curl alias for Invoke-WebRequest

Note: Using curl might be preferable if you have to invoke/script download steps using Cmd shell and/or .bat / .cmd scripts.

Installing your distro

If you’re using Windows 10 you can install your distro with PowerShell. Simply navigate to folder containing the distro downloaded from above, and in that directory run the following command where app_name is the name of your distro .appx file.

If you are using Windows server, or run into problems running the command above you can find the alternate install instructions on the Windows Server documentation page to install the .appx file by changing it to a zip file.

Once your distribution is installed, follow the normal instructions to * Update from WSL 1 to WSL 2 or create a new user account and password.

Как установить Виндовские драйвера на мой любимый Линукс?

Как установить Виндовские драйвера на мой любимый Линукс? (Lubuntu) Драйвера звуковухи моей есть только на Шиндовс, Альтернативные драева тоже только на Шиндовс, что делать?

Экстрасенсы в отпуске, поэтому модель звуковой карты тебе придётся назвать, если хочешь получить хоть какой-то полезный ответ.

Назвать модель звуковой карты, показать вывод

В последнем случае, если драйверы под Linux не будут найдены, то ставьте VirtualBox, в него Windows, пробрасывайте туда USB звуковую карту и слушайте звук там.

Звуковуха встроена в мою материнку (Albatron PX915PC Pro-G) Самый стабильный драйвер Realtek High Definition Driver 5.10.0.5024

PCI тоже можно пробрасывать, если железо не совсем старое.

Реалтек должен работать из коробки сразу. Не слишком старый какой нибудь дистрибутив ставишь?

Ага, из коробки ставится не рабочая хрень, последний раз драйвер выходил в далеком 2004

Показывай вывод lspci.

На сайтах производителей не выкладываются драйверы для Linux, все они есть в составе ядра, за исключением некоторых редких звуковых карт.

Для твоей карты, скорее всего есть драйвер и он уже работает.

А у тебя, просто в alsamixer выкручены вниз уровни громкости или стоит mute на канале вывода звука, ну либо в pulseaudio всё выкручено вниз.

Для помещения на форум выводов команд используй тег [code][/code]

Будет выглядеть как в моём сообщении.

Предварительно используй кнопку «Предпросмотр» перед помещением сообщения.

Значит он есть в ядре. Проверяй, у тебя, скорее всего, просто уровни громкости в самом низу, либо просто отключен канал вывода звука, либо, если есть видео карта с HDMI, либо ещё одна звуковая карта, то выбрана не эта карта для вывода звука.

потому их (драйверов) для линукса и нет, так как они уже давным давно в ядре CONFIG_SND_HDA_CODEC_REALTEK добавлены и поддерживаются самим вендором, включил и пользуйся, единственный затык — кривоголовые мейтейнеры не включившие его в ядре, для этого можно просто пересобрать его с нужными опциями.