-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: No device of requested type available #12701
Comments
Hi @Wait1997, I believe Ollama is unable to run on your device due to multiple versions (2025.0) of oneAPI being installed simultaneously. Please refer to our ollama quickstart and llama.cpp quickstart to prepare the environment. |
Hi @sgwhat,I uninstalled versions (2025.0) of oneAPI as you said and use 2024.02 versions, but it seems I still encounter the same problem
|
Please ensure that you have only one ollama serve process running. You can run |
Thanks, but it still doesn't seem to work. |
I am a bit confused 😂, could you please provide more detailed logs? |
I provide you with a document where I recorded this issue. You can take a look at the specific information in it. Intel GPU 上 IPEX-LLM,You can look at this link. |
As my suggestion, you can reinstall ipex-llm ollama in a fresh conda environment, and then run |
Yes, I did reinstall yesterday, but after reinstalling, ollama --version still prompts that the versions are inconsistent. I also mentioned it in the above question; is it possible that the version is too new? when ollama --version will show the following |
As my previous comment in #12701 (comment), I don't think this inconsistent version issue is caused by |
run: ./ollama run qwen2.5-coder:0.5b
Error: llama runner process has terminated: error loading model: No device of requested type available. Please check https://software.intel.com/content/www/us/en/develop/articles/intel-oneapi-dpcpp-system-requirements.html -1 (PI_ERROR_DEVICE_NOT_FOUND)
ollama version is 0.4.6-ipexllm-20250105
system info:
gpu info:
Intel° oneAPl Base Toolkit Info
The text was updated successfully, but these errors were encountered: