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

[GH-ISSUE #8207] Documentation for manual Linux installation is outdated/doesn't work for AMD GPU setup #67296

New Issue
Closed
opened 2026-05-04 09:53:22 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-04 09:53:22 -05:00
Owner
Copy Link

Originally created by @lwasyl on GitHub (Dec 21, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/8207

What is the issue?

The documentation for manual Linux installation provides the following instructions to set up AMD gpu: download an additional archive and extract it using

sudo tar -C /usr -xzf ollama-linux-amd64-rocm.tgz

However, this will put the libraries under /usr/lib/ollama/ directory. This seems to be wrong, as the ollama binary searches for compatible libraries in the following directories, according to debug output:

/usr/local/lib/ollama
/opt/rocm/lib
/usr/lib64
/usr/share/ollama/lib/rocm

I'm not sure if the /usr/lib/ollama is ever used for anything, but only after moving usr/lib/ollama to /usr/local/lib/ollama, I get working amd gpu support. This is highly annoying because the documentation suggests that I need to install ROCm, which I did and which didn't help either

OS

Linux

GPU

AMD

CPU

AMD

Ollama version

0.5.4

Originally created by @lwasyl on GitHub (Dec 21, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/8207 ### What is the issue? [The documentation for manual Linux installation](https://github.com/ollama/ollama/blob/d8bab8ea4403d3fb05a9bf408e638195b72bebf9/docs/linux.md) provides the following instructions to set up AMD gpu: download an additional archive and extract it using ``` sudo tar -C /usr -xzf ollama-linux-amd64-rocm.tgz ``` However, this will put the libraries under `/usr/lib/ollama/` directory. This seems to be wrong, as the ollama binary searches for compatible libraries in the following directories, according to debug output: ``` /usr/local/lib/ollama /opt/rocm/lib /usr/lib64 /usr/share/ollama/lib/rocm ``` I'm not sure if the `/usr/lib/ollama` is ever used for anything, but only after moving `usr/lib/ollama` to `/usr/local/lib/ollama`, I get working amd gpu support. This is highly annoying because the documentation suggests that I need to install ROCm, which I did and which didn't help either ### OS Linux ### GPU AMD ### CPU AMD ### Ollama version 0.5.4
GiteaMirror added the bug label 2026-05-04 09:53:22 -05:00
GiteaMirror commented 2026-05-04 09:53:29 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Feb 9, 2026):

ollama looks for libraries relative to the location of the binary, similar to $(dirname $(dirname $(which ollama)))/lib/ollama. So in this case, your ollama binary is in /usr/local/bin/ollama but the library was installed in /usr/lib/ollama.

<!-- gh-comment-id:3872757467 --> @rick-github commented on GitHub (Feb 9, 2026): ollama looks for libraries relative to the location of the binary, similar to `$(dirname $(dirname $(which ollama)))/lib/ollama`. So in this case, your ollama binary is in `/usr/local/bin/ollama` but the library was installed in `/usr/lib/ollama`.
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 bug
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#67296
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?