-
released this
2026-03-20 09:48:45 +01:00 | 1715 commits to main since this releasefix: detect AMD/no-NVIDIA GPU early in Windows installer and guard unsloth.exe existence (#4478)
- fix(install.ps1): detect AMD/no-NVIDIA GPU early and guard unsloth.exe existence
When a user has an AMD GPU (no nvidia-smi), uv's --torch-backend=auto
resolves to CPU torch, which constrains the solver to unsloth==2024.8.
That ancient release has no unsloth.exe CLI entry point, so the subsequent
& \ studio setup call throws a confusing PowerShell
'module could not be loaded' CommandNotFoundException instead of a
clear error.Two fixes:
- Detect nvidia-smi early; if no NVIDIA GPU is found, print a clear
error explaining AMD/Intel GPUs are unsupported and exit before
wasting time installing the wrong package version. - Guard Test-Path \ before invoking it, so any future case
where the CLI entry point is missing produces a readable error
instead of a cryptic PowerShell exception.
Fixes: unsloth_studio\Scripts\unsloth.exe CommandNotFoundException
on AMD GPU systems (Windows).-
fix(install.ps1): correct GPU support message - AMD is Linux-only via ROCm
-
Slim down to just the unsloth.exe existence guard
Remove the early NVIDIA GPU detection gate -- Studio supports Windows
and Mac without a GPU (finetuning is simply disabled). The GPU gate
was blocking legitimate non-NVIDIA users from installing.Keep only the Test-Path guard on unsloth.exe before invoking it. This
turns the confusing PowerShell CommandNotFoundException into a clear
error message pointing at the likely cause (older unsloth version
resolved by the package solver that does not include the Studio CLI).- Fix quickstart link in unsloth.exe guard message
Co-authored-by: LeoBorcherding LeoBorcherding@users.noreply.github.com
Co-authored-by: Daniel Han danielhanchen@gmail.comDownloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads