Skip to content

Commit ee809e7

Browse files
authored
add troubleshooting section (#12755)
1 parent 5fb87d7 commit ee809e7

File tree

1 file changed

+23
-3
lines changed

1 file changed

+23
-3
lines changed

docs/mddocs/Quickstart/bmg_quickstart.md

+23-3
Original file line numberDiff line numberDiff line change
@@ -13,15 +13,17 @@ This guide demonstrates how to install and use IPEX-LLM on the Intel Arc B-Serie
1313
1.1 [Install Prerequisites](#11-install-prerequisites)
1414
1.2 [Install IPEX-LLM](#for-pytorch-and-huggingface) (for PyTorch and HuggingFace)
1515
1.3 [Install IPEX-LLM](#for-llamacpp-and-ollama) (for llama.cpp and Ollama)
16-
3. [Windows](#2-windows)
16+
2. [Windows](#2-windows)
1717
2.1 [Install Prerequisites](#21-install-prerequisites)
1818
2.2 [Install IPEX-LLM](#for-pytorch-and-huggingface-1) (for PyTorch and HuggingFace)
1919
2.3 [Install IPEX-LLM](#for-llamacpp-and-ollama-1) (for llama.cpp and Ollama)
20-
5. [Use Cases](#3-use-cases)
20+
3. [Use Cases](#3-use-cases)
2121
3.1 [PyTorch](#31-pytorch)
2222
3.2 [Ollama](#32-ollama)
2323
3.3 [llama.cpp](#33-llamacpp)
24-
3.4 [vLLM](#34-vllm)
24+
3.4 [vLLM](#34-vllm)
25+
4. [Troubleshooting](#4-troubleshooting)
26+
4.1 [RuntimeError: could not create an engine](#41-runtimeerror-could-not-create-an-engine)
2527
---
2628

2729
## 1. Linux
@@ -180,3 +182,21 @@ For instructions on how to run **llama.cpp** with IPEX-LLM, refer to the [llama.
180182

181183
To set up and run **vLLM**, follow the [vLLM Quickstart guide](https://github.com/intel-analytics/ipex-llm/blob/main/docs/mddocs/Quickstart/vLLM_quickstart.md).
182184

185+
## 4. Troubleshooting
186+
187+
### 4.1 RuntimeError: could not create an engine
188+
189+
![image](https://github.com/user-attachments/assets/757f0704-9240-46d0-bceb-661fecc96182)
190+
191+
If you encounter a `RuntimeError` like the output shown above while working on Linux after running `conda deactivate` and then reactivating your environment using `conda activate env`, the issue is likely caused by the `OCL_ICD_VENDORS` environment variable.
192+
193+
To fix this on Linux, run the following command:
194+
195+
```bash
196+
unset OCL_ICD_VENDORS
197+
```
198+
199+
This will remove the conflicting environment variable and allow your program to function correctly.
200+
201+
**Note:** This issue only occurs on Linux systems. It does not affect Windows environments.
202+

0 commit comments

Comments
 (0)