Issues & Solutions for OpenVINO™ Installation & Configuration¶

This page lists issues that you may encounter during the installation and configuration of OpenVINO™, as well as their possible solutions.

Errors with Installing via PIP for Users in China¶

Users in China might encounter errors while downloading sources via PIP during OpenVINO™ installation. To resolve the issues, try one of the following options:

Add the download source using the -i parameter with the Python pip command. For example:
```
pip install openvino-dev -i https://mirrors.aliyun.com/pypi/simple/
```
Use the --trusted-host parameter if the URL above is http instead of https. You can also run the following command to install specific framework. For example:
```
pip install openvino-dev[tensorflow2] -i https://mirrors.aliyun.com/pypi/simple/
```
For C++ developers, if you have installed OpenVINO Runtime via APT, YUM, or the archive file, and then installed OpenVINO Development Tools via PyPI, you may run into issues. To resolve that, install the components in requirements.txt by using the following command:
```
pip install -r <INSTALL_DIR>/tools/requirements.txt
```
For APT and YUM users, replace the INSTALL_DIR with /usr/share/openvino.

Issues with Installing OpenVINO on Linux from Docker¶

Proxy Issues¶

If you met proxy issues during the installation with Docker, you need set up proxy settings for Docker. See the Set Proxy section in DL Workbench Installation for more details.

Permission Errors for /dev/shm¶

If you encounter a permission error for files in /dev/shm (see hddldaemon.log). A possible cause is that the uid and gid of the container user are different from the uid and gid of the user who created hddldaemon service on the host.

Try one of these solutions:

Create the user in the Docker container with the same uid and gid as the HDDL daemon user.
Set the container user umask to 0000: umask 000.
(NOT RECOMMENDED) Start HDDL daemon on the host as root and start the container as root with the -u root:root option.

Issues with Configurations for Intel® Vision Accelerator Design with Intel® Movidius™ VPUs¶

Unable to run inference with the MYRIAD Plugin after running with the HDDL Plugin¶

Running inference with the MYRIAD Plugin after running with the HDDL Plugin is failed with the following error generated:

E: [ncAPI] [    965618] [MainThread] ncDeviceOpen:677   Failed to find a device, rc: X_LINK_ERROR

Possible solutions (use one of the following):

Reboot the host system and run with the MYRIAD Plugin

Kill the HDDL Plugin backend service (hddldaemon) and reset all Intel® Movidius™ VPUs before running an application that uses the MYRIAD Plugin:

kill -9 $(pidof hddldaemon autoboot)
pidof hddldaemon autoboot # Make sure none of them is alive
source /opt/intel/openvino_2022/setupvars.sh
${HDDL_INSTALL_DIR}/bin/bsl_reset

“No space left on device” error while loading a network¶

When the application runs inference of a network with a big size(>4MB) of input/output or if the system is running out of the DMA buffer, the HDDL Plugin will fall back to use shared memory. In this case, if the application exits abnormally, the shared memory is not released automatically. To release it manually, remove files with the hddl_ prefix from the /dev/shm directory:

sudo rm -f /dev/shm/hddl_\*

Solutions to the permission issue¶

Make sure that the following udev rules exist:

/etc/udev/rules.d/97-myriad-usbboot.rules
/etc/udev/rules.d/98-hddlbsl.rules
/etc/udev/rules.d/99-hddl-ion.rules
/etc/udev/rules.d/99-myriad-vsc.rules

Also make sure that the current user is included in the users groups. If not, run the command below to include:

sudo usermod -a -G users "$(whoami)"

Host machine reboots after running an inference application with the HDDL plugin¶

Symptom: Boot up the host machine, run the inference application with the HDDL plugin. System reboots in a uncertain time.

Root Cause: The I2C address of the reset device of the Intel® Vision Accelerator Design with Intel® Movidius™ VPUs conflicts with another device I2C address in 0x20-0x27 range. If the target Intel® Vision Accelerator Design with Intel® Movidius™ VPUs device needs to be reset (for example, in case of device errors), the libbsl library, which is responsible for reset, expects that the target reset device I2C address is in the 0x20-0x27 range on SMBUS. If there is another device on SMBUS in this address range, libbsl treats this device as the target reset device and writes an unexpected value to this address. This causes system reboot.

Solution: Detect if there is any I2C device on SMBUS with address in 0x20-0x27 range. If yes, do the following:

Change the DIP switch on the target PCIE card
Disable autoscan for the reset device by setting "autoscan": false in ${HDDL_INSTALL_DIR}/config/bsl.json
Set the correct address of the I2C reset device (for example, 0x21) in ${HDDL_INSTALL_DIR}/config/bsl.json

{
  "autoscan": false,
  "ioexpander": {
    "enabled": true,
    "i2c_addr": [ 33 ]
  }
}

Cannot reset VPU device and cannot find any 0x20-0x27 (Raw data card with HW version Fab-B and before) I2C addresses on SMBUS (using i2c-tools)¶

Please contact your motherboard vendor to verify SMBUS pins are connected to the PCIe slot.

“Error: ipc_connection_linux_UDS : bind() failed” in hddldaemon log¶

You may have run hddldaemon under another user. Run the command below and try again:

sudo rm -rf /var/tmp/hddl_\*

“I2C bus: SMBus I801 adapter at not found!” in hddldaemon log¶

Run the following command to check if a SMBUS I801 adapter can be found:

i2cdetect -l

Then run:

sudo modprobe i2c-i801

“open /dev/ion failed!” in hddldaemon log¶

Check if myd_ion kernel module is installed by running the following command:

lsmod | grep myd_ion

If you do not see any output from the command, you can use the following command to reinstall the myd_ion module:

sudo modprobe myd_ion

Constantly getting “_name_mapping open failed err=2,No such file or directory” in hddldaemon log¶

Check if myd_vsc kernel module is installed by running the following command:

lsmod | grep myd_vsc

If you do not see any output from the command, you can use the following command to reinstall the myd_vsc module:

sudo modprobe myd_vsc

“Required key not available” appears when trying to install the myd_ion or myd_vsc modules¶

Run the following commands:

sudo apt install mokutil

sudo mokutil --disable-validation

Issues with Creating a Yocto Image for OpenVINO¶

Error while adding “meta-intel” layer¶

When using the bitbake-layers add-layer meta-intel command, the following error might occur:

NOTE: Starting bitbake server...
ERROR: The following required tools (as specified by HOSTTOOLS) appear to be unavailable in PATH, please install them in order to proceed: chrpath diffstat pzstd zstd

To resolve the issue, install the chrpath diffstat zstd tools:

sudo apt-get install chrpath diffstat zstd