Open admpalma opened 5 days ago
The ollama-linux-amd64-rocm.tgz bundle is not self-sufficient and requires the payloads from ollama-linux-amd64.tgz to be complete. We'll get the dangling link fixed in the future so at least each tar file is self-consistent, but with the current packaging, you need both for AMD systems.
you need both for AMD systems.
Indeed, to clarify, the Alpaca flatpak packages the contents of ollama-linux-amd64.tgz
and ollama-linux-amd64-rocm.tgz
onto separate folders, whereas the default Ollama installation method merges them.
Fixing the dangling link should therefore fix the original issue.
What is the issue?
Issue Description:
From Ollama v0.4.0 onwards, the
libhipblas.so.2
andlibhipblas.so.2.1.60102
files are no longer present in theollama-linux-amd64-rocm.tgz
archive. This makes the library unusable by the ollama instance.Original Issue
Found Evidence:
Looking at the build logs ("Run ./scripts/build_linux.sh" step):
v0.3.14:
libhipblas:
libhipblas.so.2
andlibhipblas.so.2.1.60102
are copied to thelinux-amd64-rocm/lib/ollama
path:linux-amd64-rocm/lib/ollama
:v0.4.0:
libhipblas:
libhipblas.so.2
andlibhipblas.so.2.1.60102
are now copied intolinux-amd64/lib/ollama
and onlylibhipblas.so
is copied intolinux-amd64-rocm/lib/ollama
, causing the broken link.linux-amd64/lib/ollama
:linux-amd64-rocm/lib/ollama
:librocblas:
Additionally, the
librocblas
related files are copied intolinux-amd64/lib/ollama
when they should only be present inlinux-amd64-rocm/lib/ollama
:linux-amd64/lib/ollama
:linux-amd64-rocm/lib/ollama
:v0.4.4:
In
v0.4.4
we can observe the same behavior as inv0.4.0
:libhipblas:
linux-amd64/lib/ollama
:linux-amd64-rocm/lib/ollama
:librocblas:
linux-amd64/lib/ollama
:linux-amd64-rocm/lib/ollama
:OS
Linux
GPU
AMD
CPU
AMD
Ollama version
v0.4.4