fix(llamacpp-upstream): bump Windows CUDA-13 backend 13.1 → 13.3 (fixes "Failed to download GPU backend")#42
Merged
Vect0rM merged 1 commit intoJun 3, 2026
Conversation
ggml-org/llama.cpp renamed the Windows CUDA-13 release asset from
`...-bin-win-cuda-13.1-x64.zip` to `...-bin-win-cuda-13.3-x64.zip`
(observed on release b9495). The upstream provider hardcoded the
`13.1` minor as the canonical backend id, so on >= 1.1.95:
- detectIdealBackendType() recommends `win-cuda-13.1-x64` to every
CUDA-13 host ("Better Configuration Available → CUDA 13"), and
- getBackendDownloadUrl() resolves it to
`llama-b9495-bin-win-cuda-13.1-x64.zip` → HTTP 404
("Failed to download GPU backend").
Bump the canonical Windows CUDA-13 minor to 13.3 across the TS
extension and the Rust plugin (recommendation, static variant list,
remote whitelist, cudart sidecar filename, toolkit-version map,
category matcher, priority list, cudart lib lookup). Legacy
`cuda-13.1` is still recognized by the category matcher and migrated
forward by map_old_backend_to_new(), so already-installed
`win-cuda-13.1-x64` folders are not orphaned.
Note: the CUDA-13 driver gate (>= 581.15) is left unchanged — it is
the documented minimum for Toolkit 13.1; CUDA 13.3's minimum driver
should be verified as a follow-up. The runtime device probe already
degrades to 12.4 / Vulkan / CPU if a recommended tier cannot
enumerate a GPU.
Fixes the "Failed to download GPU backend" report on Windows CUDA 13.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Author
|
Root-cause hardening follow-up tracked in #43 (resolve the CUDA-13 asset minor dynamically so this can't recur on the next ggml-org bump). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Since 1.1.95, Windows users on CUDA 13 hosts get "Failed to download GPU backend". The "Better Configuration Available → CUDA 13" prompt offers a backend that 404s on download.
Root cause: ggml-org/llama.cpp renamed the Windows CUDA-13 release asset from
llama-{tag}-bin-win-cuda-13.1-x64.zipto...-cuda-13.3-x64.zip(visible on releaseb9495). Thellamacpp-upstreamprovider hardcodes the13.1minor as the canonical backend id, so:detectIdealBackendType()recommends the literalwin-cuda-13.1-x64to every CUDA-13 host (the prompt), andgetBackendDownloadUrl()turns it into…/b9495/llama-b9495-bin-win-cuda-13.1-x64.zip→ HTTP 404.Observed download attempt from a reporter (1.1.95):
The release only ships
llama-b9495-bin-win-cuda-13.3-x64.zip.Fix (hotfix)
Bump the canonical Windows CUDA-13 minor
13.1 → 13.3everywhere it's treated as an identity string, across the TS extension and the Rust plugin:detectIdealBackendType), static variant list, remote-asset whitelistis_cuda_installedcudart lib lookupmap_old_backend_to_newcanonical targetBack-compat: legacy
cuda-13.1is still recognized by the category matcher and is migrated forward to13.3bymap_old_backend_to_new, so an already-installedwin-cuda-13.1-x64folder is not orphaned. Updated the affected Rust unit tests accordingly.Out of scope / follow-ups
>= 581.15) is the documented minimum for Toolkit 13.1; CUDA 13.3's minimum Windows driver should be verified separately. Low risk here because the runtime device probe already degrades to 12.4 / Vulkan / CPU when a recommended tier can't enumerate a GPU.Testing
cargo testfortauri-plugin-llamacpp-upstream)🤖 Generated with Claude Code