From f77713bf1f566771127bcdec79b9840e9cf539ca Mon Sep 17 00:00:00 2001 From: Daniel Hiltgen Date: Thu, 23 May 2024 09:33:25 -0700 Subject: [PATCH] Add isolated gpu test to troubleshooting --- docs/troubleshooting.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 729ec96c..60d63c7d 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -76,6 +76,7 @@ Make sure you've set up the container runtime first as described in [docker.md]( Sometimes the container runtime can have difficulties initializing the GPU. When you check the server logs, this can show up as various error codes, such as "3" (not initialized), "46" (device unavailable), "100" (no device), "999" (unknown), or others. The following troubleshooting techniques may help resolve the problem +- Is the container runtime working? Try `docker run --gpus all ubuntu nvidia-smi` - if this doesn't work, Ollama wont be able to see your NVIDIA GPU. - Is the uvm driver not loaded? `sudo nvidia-modprobe -u` - Try reloading the nvidia_uvm driver - `sudo rmmod nvidia_uvm` then `sudo modprobe nvidia_uvm` - Try rebooting