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

[PR #5820] [MERGED] Track GPU discovery failure information #11935

New Issue
Closed
opened 2026-04-12 23:42:59 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-12 23:42:59 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/5820
Author: @dhiltgen
Created: 7/20/2024
Status: ✅ Merged
Merged: 10/14/2024
Merged by: @dhiltgen

Base: main ← Head: gpu_info

📝 Commits (2)

  • 45f6b32 Expose GPU discovery failure information
  • 0cfe8c9 Remove exposed API for now

📊 Changes

5 files changed (+242 additions, -92 deletions)

View changed files

📝 gpu/amd_linux.go (+66 -26)
📝 gpu/amd_windows.go (+42 -31)
📝 gpu/gpu.go (+110 -35)
📝 gpu/gpu_darwin.go (+12 -0)
📝 gpu/types.go (+12 -0)

📄 Description

When ollama is unable to utilize a GPU on the users system, figuring out why can be tricky for many users to figure out. We log various messages (some at debug) and often have to ask users to re-run the server with OLLAMA_DEBUG=1 and share the server logs and manually look through the logs to figure out and explain the problem.

This PR lays some initial foundation to record general discovery errors, as well as per-device unsupported information.

I'm making this draft for now as the API probably isn't something we want to expose in its current form.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/ollama/ollama/pull/5820 **Author:** [@dhiltgen](https://github.com/dhiltgen) **Created:** 7/20/2024 **Status:** ✅ Merged **Merged:** 10/14/2024 **Merged by:** [@dhiltgen](https://github.com/dhiltgen) **Base:** `main` ← **Head:** `gpu_info` --- ### 📝 Commits (2) - [`45f6b32`](https://github.com/ollama/ollama/commit/45f6b32183723fa290110656f20cfc0a93ea7742) Expose GPU discovery failure information - [`0cfe8c9`](https://github.com/ollama/ollama/commit/0cfe8c980a3ff8d1a5ae4c2a104b06c15acf7749) Remove exposed API for now ### 📊 Changes **5 files changed** (+242 additions, -92 deletions) <details> <summary>View changed files</summary> 📝 `gpu/amd_linux.go` (+66 -26) 📝 `gpu/amd_windows.go` (+42 -31) 📝 `gpu/gpu.go` (+110 -35) 📝 `gpu/gpu_darwin.go` (+12 -0) 📝 `gpu/types.go` (+12 -0) </details> ### 📄 Description When ollama is unable to utilize a GPU on the users system, figuring out why can be tricky for many users to figure out. We log various messages (some at debug) and often have to ask users to re-run the server with OLLAMA_DEBUG=1 and share the server logs and manually look through the logs to figure out and explain the problem. This PR lays some initial foundation to record general discovery errors, as well as per-device unsupported information. I'm making this draft for now as the API probably isn't something we want to expose in its current form. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-12 23:43:00 -05:00
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 pull-request
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#11935
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?