You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm attempting to run the intelanalytics/ipex-llm-inference-cpp-xpu container on an Intel Celeron J4125 (Gemini Lake) CPU with integrated UHD Graphics 600 GPU.
When the ollama_llama_server program runs, it crashes due to an illegal instruction:
Do you intend to support CPUs without AVX? Or where can I find out how the files under /usr/local/lib/python3.11/dist-packages/bigdl/cpp/libs/ are compiled so I can rebuild them without AVX instructions?
The text was updated successfully, but these errors were encountered:
We build the GPU libraries with AVX enabled to ensure that if not all
layers fit on the GPU we get better performance in a mixed mode.
If the user is using a virtualization/emulation system that lacks AVX
this used to result in an illegal instruction error and crash before this
fix. ...
Thanks @sgwhat. You would have to build Ollama with CUSTOM_CPU_FLAGS='' to build a runner without the AVX instructions. I'm not sure the invocation to build multiple runners with different processor features.
I don't think it's going to work on Gemini Lake anyway, the oneAPI requires "Intel® UHD Graphics for 11th generation Intel processors or newer." Looks like this processor is generation "9.5" according to Wikipedia.
I'm attempting to run the
intelanalytics/ipex-llm-inference-cpp-xpu
container on an Intel Celeron J4125 (Gemini Lake) CPU with integrated UHD Graphics 600 GPU.When the
ollama_llama_server
program runs, it crashes due to an illegal instruction:It looks like
libollama_ggml.so
is compiled with AVX instructions, but my processor doesn't support AVX (despite the log message that says "AVX = 1").Do you intend to support CPUs without AVX? Or where can I find out how the files under
/usr/local/lib/python3.11/dist-packages/bigdl/cpp/libs/
are compiled so I can rebuild them without AVX instructions?The text was updated successfully, but these errors were encountered: