Visible to Intel only — GUID: ihh1528499703743
Ixiasoft
1. About This Document
2. Introduction
3. Getting Started
4. Installing the OPAE Software Package
5. Identifying the Flash Image and BMC Firmware
6. Running FPGA Diagnostics
7. Running the OPAE in a Non-Virtualized Environment
8. Running the OPAE in a Virtualized Environment
9. Intel® Acceleration Stack Quick Start Guide for Intel® Programmable Acceleration Card with Intel® Arria® 10 GX FPGA Archives
10. Document Revision History for Intel® Acceleration Stack Quick Start Guide for Intel® Programmable Acceleration Card with Intel® Arria® 10 GX FPGA
A. Updating the FIM and BMC Firmware
B. Handling Graceful Thermal Shutdown
C. FPGA Device Access Permission
D. Memlock Limit
E. Hugepage Settings
F. Troubleshooting Frequently Asked Questions (FAQ)
G. Documentation Available for the Intel® Acceleration Stack for Intel® Xeon® CPU with FPGAs 1.2.1 Release
F.1. Why do I see a 'No Suitable slots found' message when running fpgaconf on my AFU image?
F.2. How do I flash the FIM or program the AFU in a multicard system?
F.3. Which environment variables are required?
F.4. What actions do I take if I see the error message 'Error enumerating resources: no driver available'?
F.5. Troubleshooting OPAE Installation on RHEL
Visible to Intel only — GUID: ihh1528499703743
Ixiasoft
3.4.1. Installing the Intel Acceleration Stack Runtime Package on the Host Machine
- Extract the runtime archive file:
tar xvf *rte_installer.tar.gz
- Change to the installation directory.
cd *rte_installer
- This step only applies to RHEL 7.6 (skip this step if you are using Ubuntu 18.04). Install extra packages for Enterprise Linux (EPEL):
sudo yum install https://dl.fedoraproject.org/pub/epel/\ epel-release-latest-7.noarch.rpm
sudo subscription-manager repos --enable "rhel-*-optional-rpms"\ --enable "rhel-*-extras-rpms"
- Run setup.sh.
./setup.sh
- If you receive a prompt with the message: Intel® Acceleration Stack Runtime Package is only supported on RHEL 7.6.* kernel 3.10.* or Ubuntu 18.04.* kernel 4.15.* , then you are currently using an unsupported operating system/kernel combination.
Next, a prompt appears with the following question: Do you want to continue to install the software? Answering Yes allows the setup script to attempt to install OPAE onto this unsupported operating and kernel version.
For complete operating system support information, refer to section System Requirements .
- Next, a prompt appears with the following question: Do you wish to install the OPAE?
Option Description Answer Yes If you require the use of PACSign to sign bitstreams prior to loading on a Intel® FPGA PAC, admin and network access is required. Answer No If you do not have admin and network access. After the installation, follow the manual steps listed in the Installing the OPAE Software Package section. - Next, a prompt appears with the following question: Do you wish to install OPAE PACsign package?
Option Description Answer Yes If you have admin and network access. Answer No If you do not have admin and network access. After the installation, follow the manual steps listed in the Installing the OPAE PACSign section. - Accept the license.
- When you receive an installation directory prompt for the Intel® PAC with Intel® Arria® 10 GX FPGA release package, you can specify an install directory. Otherwise, the installer uses the default directory at /home/<username>/intelrtestack.
- When you receive an installation directory prompt for the Intel® FPGA RTE OpenCL package, you can specify an install directory. Otherwise, the installer uses the default directory at /opt/opencl_rte.
Next, a prompt appears stating the following: Warning: Elevated permissions are required in order to write to directory /opt. Do you want to proceed? Answer Yes.Note: If there is not enough available storage under /opt for the OpenCL RTE, the installer fails and halts execution.
- Source the initialization script after installation completes to set the required environment variables.
source /home/<username>/intelrtestack/init_env.sh
Note: To avoid having to setup the environment variables after every reboot, you can save this command to your shell initialization script.
Related Information