github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-06 08:02:14 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #7817] Missing ROCm Library Files In ollama-linux-amd64-rocm.tgz #67058

New Issue
Closed
opened 2026-05-04 09:23:45 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-04 09:23:45 -05:00
Owner
Copy Link

Originally created by @admpalma on GitHub (Nov 24, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/7817

Originally assigned to: @dhiltgen on GitHub.

What is the issue?

Issue Description:

From Ollama v0.4.0 onwards, the libhipblas.so.2 and libhipblas.so.2.1.60102 files are no longer present in the ollama-linux-amd64-rocm.tgz archive.
This makes the library unusable by the ollama instance.

Original Issue

Ollama v0.3.14:

libhipblas.so.2 -> libhipblas.so.2.1.60102
libhipblas.so.2.1.60102

Ollama v0.4.0:

libhipblas.so -> libhipblas.so.2 (broken link)

Found Evidence:

Looking at the build logs ("Run ./scripts/build_linux.sh" step):

v0.3.14:

libhipblas:

libhipblas.so.2 and libhipblas.so.2.1.60102 are copied to the linux-amd64-rocm/lib/ollama path:

linux-amd64-rocm/lib/ollama:
#43 2018.8 + cp -a /opt/rocm/lib/libhipblas.so.2 /opt/rocm/lib/libhipblas.so.2.1.60102 ../../dist/linux-amd64//../linux-amd64-rocm/lib/ollama
...
#43 2018.8 + cp /opt/rocm-6.1.2/lib/libhipblas.so.2.1.60102 ../../dist/linux-amd64//../linux-amd64-rocm/lib/ollama

v0.4.0:

libhipblas:

libhipblas.so.2 and libhipblas.so.2.1.60102 are now copied into linux-amd64/lib/ollama and only libhipblas.so is copied into linux-amd64-rocm/lib/ollama, causing the broken link.

linux-amd64/lib/ollama:
#19 1826.4 cp -af /opt/rocm/lib/libhipblas.so.2.1.60102 /go/src/github.com/ollama/ollama/dist/linux-amd64/lib/ollama/
#19 1826.4 cp -af /opt/rocm/lib/libhipblas.so.2 /go/src/github.com/ollama/ollama/dist/linux-amd64/lib/ollama/
linux-amd64-rocm/lib/ollama:
#19 1828.5 cp -af /opt/rocm/lib//libhipblas.so /go/src/github.com/ollama/ollama/dist/linux-amd64-rocm/lib/ollama/

librocblas:

Additionally, the librocblas related files are copied into linux-amd64/lib/ollama when they should only be present in linux-amd64-rocm/lib/ollama:

linux-amd64/lib/ollama:
#19 1826.4 cp -af /opt/rocm/lib/librocblas.so.4.1.60102 /go/src/github.com/ollama/ollama/dist/linux-amd64/lib/ollama/
#19 1827.7 cp -af /opt/rocm/lib/librocblas.so.4 /go/src/github.com/ollama/ollama/dist/linux-amd64/lib/ollama/
linux-amd64-rocm/lib/ollama:
#19 1828.7 cp -af /opt/rocm/lib//librocblas.so /go/src/github.com/ollama/ollama/dist/linux-amd64-rocm/lib/ollama/
#19 1828.7 cp -af /opt/rocm/lib//librocblas.so.4 /go/src/github.com/ollama/ollama/dist/linux-amd64-rocm/lib/ollama/
#19 1828.8 cp -af /opt/rocm-6.1.2/lib//librocblas.so.4.1.60102 /go/src/github.com/ollama/ollama/dist/linux-amd64-rocm/lib/ollama/

v0.4.4:

In v0.4.4 we can observe the same behavior as in v0.4.0:

libhipblas:

linux-amd64/lib/ollama:
#19 1292.4 cp -af /opt/rocm/lib/libhipblas.so.2.1.60102 /go/src/github.com/ollama/ollama/dist/linux-amd64/lib/ollama/
#19 1292.4 cp -af /opt/rocm/lib/libhipblas.so.2 /go/src/github.com/ollama/ollama/dist/linux-amd64/lib/ollama/
linux-amd64-rocm/lib/ollama:
#19 1425.8 cp -af /opt/rocm/lib//libhipblas.so /go/src/github.com/ollama/ollama/dist/linux-amd64-rocm/lib/ollama/

librocblas:

linux-amd64/lib/ollama:
#19 1292.4 cp -af /opt/rocm/lib/librocblas.so.4.1.60102 /go/src/github.com/ollama/ollama/dist/linux-amd64/lib/ollama/
...
#19 1293.7 cp -af /opt/rocm/lib/librocblas.so.4 /go/src/github.com/ollama/ollama/dist/linux-amd64/lib/ollama/
linux-amd64-rocm/lib/ollama:
#19 1753.5 cp -af /opt/rocm/lib//librocblas.so /go/src/github.com/ollama/ollama/dist/linux-amd64-rocm/lib/ollama/
#19 1753.6 cp -af /opt/rocm/lib//librocblas.so.4 /go/src/github.com/ollama/ollama/dist/linux-amd64-rocm/lib/ollama/
#19 1753.6 cp -af /opt/rocm-6.1.2/lib//librocblas.so.4.1.60102 /go/src/github.com/ollama/ollama/dist/linux-amd64-rocm/lib/ollama/

OS

Linux

GPU

AMD

CPU

AMD

Ollama version

v0.4.4

Originally created by @admpalma on GitHub (Nov 24, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/7817 Originally assigned to: @dhiltgen on GitHub. ### What is the issue? ## Issue Description: From Ollama v0.4.0 onwards, the `libhipblas.so.2` and `libhipblas.so.2.1.60102` files are no longer present in the `ollama-linux-amd64-rocm.tgz` archive. This makes the library unusable by the ollama instance. [Original Issue](https://github.com/Jeffser/Alpaca/issues/139#issuecomment-2494935019) > Ollama [v0.3.14](https://github.com/ollama/ollama/releases/tag/v0.3.14): > > ``` > libhipblas.so.2 -> libhipblas.so.2.1.60102 > libhipblas.so.2.1.60102 > ``` > > Ollama [v0.4.0](https://github.com/ollama/ollama/releases/tag/v0.4.0): > > ``` > libhipblas.so -> libhipblas.so.2 (broken link) > ``` ## Found Evidence: Looking at the build logs ("Run ./scripts/build_linux.sh" step): ### [v0.3.14](https://github.com/ollama/ollama/actions/runs/11432081098/job/31801985394): ### libhipblas: `libhipblas.so.2` and `libhipblas.so.2.1.60102` are copied to the `linux-amd64-rocm/lib/ollama` path: ##### `linux-amd64-rocm/lib/ollama`: ``` #43 2018.8 + cp -a /opt/rocm/lib/libhipblas.so.2 /opt/rocm/lib/libhipblas.so.2.1.60102 ../../dist/linux-amd64//../linux-amd64-rocm/lib/ollama ... #43 2018.8 + cp /opt/rocm-6.1.2/lib/libhipblas.so.2.1.60102 ../../dist/linux-amd64//../linux-amd64-rocm/lib/ollama ``` ### [v0.4.0](https://github.com/ollama/ollama/actions/runs/11706618932/job/32604128986): ### libhipblas: `libhipblas.so.2` and `libhipblas.so.2.1.60102` are now copied into `linux-amd64/lib/ollama` and only `libhipblas.so` is copied into `linux-amd64-rocm/lib/ollama`, causing the broken link. ##### `linux-amd64/lib/ollama`: ``` #19 1826.4 cp -af /opt/rocm/lib/libhipblas.so.2.1.60102 /go/src/github.com/ollama/ollama/dist/linux-amd64/lib/ollama/ #19 1826.4 cp -af /opt/rocm/lib/libhipblas.so.2 /go/src/github.com/ollama/ollama/dist/linux-amd64/lib/ollama/ ``` ##### `linux-amd64-rocm/lib/ollama`: ``` #19 1828.5 cp -af /opt/rocm/lib//libhipblas.so /go/src/github.com/ollama/ollama/dist/linux-amd64-rocm/lib/ollama/ ``` ### librocblas: Additionally, the `librocblas` related files are copied into `linux-amd64/lib/ollama` when they should only be present in `linux-amd64-rocm/lib/ollama`: ##### `linux-amd64/lib/ollama`: ``` #19 1826.4 cp -af /opt/rocm/lib/librocblas.so.4.1.60102 /go/src/github.com/ollama/ollama/dist/linux-amd64/lib/ollama/ #19 1827.7 cp -af /opt/rocm/lib/librocblas.so.4 /go/src/github.com/ollama/ollama/dist/linux-amd64/lib/ollama/ ``` ##### `linux-amd64-rocm/lib/ollama`: ``` #19 1828.7 cp -af /opt/rocm/lib//librocblas.so /go/src/github.com/ollama/ollama/dist/linux-amd64-rocm/lib/ollama/ #19 1828.7 cp -af /opt/rocm/lib//librocblas.so.4 /go/src/github.com/ollama/ollama/dist/linux-amd64-rocm/lib/ollama/ #19 1828.8 cp -af /opt/rocm-6.1.2/lib//librocblas.so.4.1.60102 /go/src/github.com/ollama/ollama/dist/linux-amd64-rocm/lib/ollama/ ``` ### [v0.4.4](https://github.com/ollama/ollama/actions/runs/11982171234/job/33409747042): In `v0.4.4` we can observe the same behavior as in `v0.4.0`: ### libhipblas: ##### `linux-amd64/lib/ollama`: ``` #19 1292.4 cp -af /opt/rocm/lib/libhipblas.so.2.1.60102 /go/src/github.com/ollama/ollama/dist/linux-amd64/lib/ollama/ #19 1292.4 cp -af /opt/rocm/lib/libhipblas.so.2 /go/src/github.com/ollama/ollama/dist/linux-amd64/lib/ollama/ ``` ##### `linux-amd64-rocm/lib/ollama`: ``` #19 1425.8 cp -af /opt/rocm/lib//libhipblas.so /go/src/github.com/ollama/ollama/dist/linux-amd64-rocm/lib/ollama/ ``` ### librocblas: ##### `linux-amd64/lib/ollama`: ``` #19 1292.4 cp -af /opt/rocm/lib/librocblas.so.4.1.60102 /go/src/github.com/ollama/ollama/dist/linux-amd64/lib/ollama/ ... #19 1293.7 cp -af /opt/rocm/lib/librocblas.so.4 /go/src/github.com/ollama/ollama/dist/linux-amd64/lib/ollama/ ``` ##### `linux-amd64-rocm/lib/ollama`: ``` #19 1753.5 cp -af /opt/rocm/lib//librocblas.so /go/src/github.com/ollama/ollama/dist/linux-amd64-rocm/lib/ollama/ #19 1753.6 cp -af /opt/rocm/lib//librocblas.so.4 /go/src/github.com/ollama/ollama/dist/linux-amd64-rocm/lib/ollama/ #19 1753.6 cp -af /opt/rocm-6.1.2/lib//librocblas.so.4.1.60102 /go/src/github.com/ollama/ollama/dist/linux-amd64-rocm/lib/ollama/ ``` ### OS Linux ### GPU AMD ### CPU AMD ### Ollama version v0.4.4
GiteaMirror added the installamdbug labels 2026-05-04 09:23:46 -05:00
GiteaMirror commented 2026-05-04 09:23:50 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Nov 24, 2024):

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.

<!-- gh-comment-id:2496190008 --> @dhiltgen commented on GitHub (Nov 24, 2024): 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.
GiteaMirror commented 2026-05-04 09:23:50 -05:00
Author
Owner
Copy Link

@admpalma commented on GitHub (Nov 24, 2024):

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.

<!-- gh-comment-id:2496209360 --> @admpalma commented on GitHub (Nov 24, 2024): > 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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label amd bug install
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#67058
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?