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

[GH-ISSUE #14874] GPU is not used, while using as system service (systemd) #35350

New Issue
Closed
opened 2026-04-22 19:47:39 -05:00 by GiteaMirror · 8 comments
GiteaMirror commented 2026-04-22 19:47:39 -05:00
Owner
Copy Link

Originally created by @schoenid on GitHub (Mar 16, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/14874

What is the issue?

Using Ollama I found, that Ollama uses only the CPU instead of the GPU.

My system:
Operating System: Ubuntu Studio 24.04
KDE Plasma Version: 5.27.12
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13
Kernel Version: 6.17.0-19-generic (64-bit)
Graphics Platform: X11
Processors: 16 × 13th Gen Intel® Core™ i7-13700K
Memory: 62.5 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4060 Ti/PCIe/SSE2
VRAM: 16GiB
Manufacturer: ASUS

Relevant log output

none.

OS

Linux

GPU

Nvidia

CPU

Intel

Ollama version

0.18.0

Originally created by @schoenid on GitHub (Mar 16, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/14874 ### What is the issue? Using Ollama I found, that Ollama uses only the CPU instead of the GPU. My system: Operating System: Ubuntu Studio 24.04 KDE Plasma Version: 5.27.12 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Kernel Version: 6.17.0-19-generic (64-bit) Graphics Platform: X11 Processors: 16 × 13th Gen Intel® Core™ i7-13700K Memory: 62.5 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4060 Ti/PCIe/SSE2 VRAM: 16GiB Manufacturer: ASUS ### Relevant log output ```shell none. ``` ### OS Linux ### GPU Nvidia ### CPU Intel ### Ollama version 0.18.0
GiteaMirror added the bug label 2026-04-22 19:47:39 -05:00
GiteaMirror commented 2026-04-22 19:47:41 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Mar 16, 2026):

Server logs will aid in debugging.

<!-- gh-comment-id:4067155632 --> @rick-github commented on GitHub (Mar 16, 2026): [Server logs](https://docs.ollama.com/troubleshooting) will aid in debugging.
GiteaMirror commented 2026-04-22 19:47:42 -05:00
Author
Owner
Copy Link

@schoenid commented on GitHub (Mar 16, 2026):

I found, that /etc/systemd/system/ollama.service contains:

[Unit]
After=network-online.target

This activates ollama without the GPU being ready. So it uses the fallback to the CPU.

Using:

[Unit]
After=graphical.target

solves the problem.
But after an update the settings are reset to After=network-online.target.

<!-- gh-comment-id:4067178950 --> @schoenid commented on GitHub (Mar 16, 2026): I found, that `/etc/systemd/system/ollama.service` contains: ``` [Unit] After=network-online.target ``` This activates ollama without the GPU being ready. So it uses the fallback to the CPU. Using: ``` [Unit] After=graphical.target ``` solves the problem. But after an update the settings are reset to `After=network-online.target`.
GiteaMirror commented 2026-04-22 19:47:42 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Mar 16, 2026):

Run sudo systemctl edit ollama and add the following after ### Anything between here and the comment below will become the new contents of the file:

[Unit]
After=graphical.target
<!-- gh-comment-id:4067221602 --> @rick-github commented on GitHub (Mar 16, 2026): Run `sudo systemctl edit ollama` and add the following after `### Anything between here and the comment below will become the new contents of the file`: ``` [Unit] After=graphical.target ```
GiteaMirror commented 2026-04-22 19:47:42 -05:00
Author
Owner
Copy Link

@schoenid commented on GitHub (Mar 16, 2026):

Thanks. Works great!
It would be nice, to have this in the install instructions.

<!-- gh-comment-id:4067361746 --> @schoenid commented on GitHub (Mar 16, 2026): Thanks. Works great! It would be nice, to have this in the install instructions.
GiteaMirror commented 2026-04-22 19:47:43 -05:00
Author
Owner
Copy Link

@schoenid commented on GitHub (Mar 16, 2026):

Server logs will aid in debugging.

cat: /home/user/.ollama/logs/server.log: Datei oder Verzeichnis nicht gefunden

Ollama has been installed at: /usr/local/lib/ollama/
No idea, where the logs are. (Not at: "/usr/local/lib/ollama/logs" or "/var/log/")

<!-- gh-comment-id:4067464965 --> @schoenid commented on GitHub (Mar 16, 2026): > [Server logs](https://docs.ollama.com/troubleshooting) will aid in debugging. `cat: /home/user/.ollama/logs/server.log: Datei oder Verzeichnis nicht gefunden` Ollama has been installed at: `/usr/local/lib/ollama/` No idea, where the logs are. (Not at: "/usr/local/lib/ollama/logs" or "/var/log/")
GiteaMirror commented 2026-04-22 19:47:44 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Mar 16, 2026):

It would be nice, to have this in the install instructions.

It's not in the install instructions because this is the first time it's been reported as an issue. The default install works for many users.

No idea, where the logs are. (Not at: "/usr/local/lib/ollama/logs" or "/var/log/")

Follow the instructions after On Linux systems with systemd, the logs can be found with this command:.

<!-- gh-comment-id:4068318667 --> @rick-github commented on GitHub (Mar 16, 2026): > It would be nice, to have this in the install instructions. It's not in the install instructions because this is the first time it's been reported as an issue. The default install works for many users. > No idea, where the logs are. (Not at: "/usr/local/lib/ollama/logs" or "/var/log/") Follow the instructions after `On Linux systems with systemd, the logs can be found with this command:`.
GiteaMirror commented 2026-04-22 19:47:44 -05:00
Author
Owner
Copy Link

@schoenid commented on GitHub (Mar 16, 2026):

Thanks a lot!

<!-- gh-comment-id:4069632902 --> @schoenid commented on GitHub (Mar 16, 2026): Thanks a lot!
GiteaMirror commented 2026-04-22 19:47:45 -05:00
Author
Owner
Copy Link

@BillionClaw commented on GitHub (Mar 17, 2026):

Looking into this — checking systemd service configuration and GPU detection. Happy to submit a fix.

<!-- gh-comment-id:4071876615 --> @BillionClaw commented on GitHub (Mar 17, 2026): Looking into this — checking systemd service configuration and GPU detection. Happy to submit a fix.
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#35350
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?