01-server: fix ollama Vulkan JIT sandbox breakage + pin NVIDIA ICD #22
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/ollama-vulkan-fixes"
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?
The 'painfully slow' root cause — the nixpkgs ollama unit runs with
MemoryDenyWriteExecute=true, which denies the W+X mprotect Vulkan's shader JIT needs. Ollama logs showJIT session error: Permission denied; GPU layers fall back to software rendering, and qwen3:8b Q4 crawls at ~0.5 tok/s despite all 8 M10 dies being reserved.Two changes in
hosts/nixos/the k3s master node/default.nix:systemd.services.ollama.serviceConfig.MemoryDenyWriteExecute = lib.mkForce false— lets the shader JIT workVK_ICD_FILENAMESpinned to the NVIDIA ICD — Mesa's lavapipe (software Vulkan) is enumerated on this host and can steal layersValidated:
nix build .#nixosConfigurations.the k3s master node.config.system.build.toplevelexit 0.Expected: ~0.5 → 10–25 tok/s for 8B Q4 on the M10s. If we still want more after measuring, next step is a custom CUDA 12.8 build (nixpkgs ollama-cuda is CUDA 13 = cannot target sm_50).