GPU Detection
NVIDIA GPUs
llmfit detects NVIDIA GPUs via two methods:1. nvidia-smi (Primary)
- NVIDIA drivers installed
- nvidia-smi.exe in PATH (usually
C:\Program Files\NVIDIA Corporation\NVSMI\)
- Aggregates same-model GPUs (e.g., 2x RTX 4090 → count=2, per-card VRAM=24GB)
- Total VRAM = per-card VRAM × count
2. WMI (Windows Management Instrumentation)
Fallback method when nvidia-smi is unavailable or for non-NVIDIA GPUs:- NVIDIA (GeForce, RTX, Quadro, Tesla) → CUDA backend
- AMD (Radeon, RX) → Vulkan backend
- Intel (Arc, Iris) → SYCL backend
- Microsoft Basic Display Adapter
- Virtual/Remote display adapters
AdapterRAM is a 32-bit field capped at ~4 GB. For GPUs with >4 GB VRAM, llmfit estimates from GPU name:
Installation Methods
Scoop (Recommended)
From Source
Prerequisites:- Rust toolchain: https://rustup.rs/
- Git for Windows: https://git-scm.com/download/win
Binary Download
Download the latest Windows binary from GitHub Releases:- Download
llmfit-windows-x64.zip - Extract
llmfit.exe - Move to a directory in PATH (e.g.,
C:\Program Files\llmfit\) - Add to PATH via System Properties → Environment Variables
WSL (Windows Subsystem for Linux)
llmfit can run natively on Windows or inside WSL. Each has trade-offs:Running in WSL2
Advantages:- Native Linux environment
- Better support for ROCm (AMD) if needed
- Consistent with Linux instructions
- WSL2 (not WSL1)
- NVIDIA CUDA drivers for WSL: https://docs.nvidia.com/cuda/wsl-user-guide/
- AMD ROCm not officially supported in WSL
- Intel Arc support limited in WSL
Running Natively on Windows
Advantages:- Direct GPU access (no virtualization overhead)
- Better NVIDIA GPU support
- WMI fallback for non-NVIDIA GPUs
Troubleshooting
GPU Not Detected
NVIDIA GPU
-
Check if nvidia-smi works:
-
If nvidia-smi not found:
-
Reinstall NVIDIA drivers:
- Download from https://www.nvidia.com/Download/index.aspx
- Use “Clean Install” option
-
Check WMI fallback:
-
Manual override:
AMD/Intel GPU
AMD and Intel GPUs rely on WMI detection:VRAM Shows Incorrect Value
WMI 32-bit limitation: WMI reports wrong VRAM for GPUs with >4 GB:nvidia-smi Works But llmfit Doesn’t Detect GPU
PATH issue:nvidia-smi as a subprocess. Check for permission issues:
WSL-Specific Issues
nvidia-smi not working in WSL:-
Install CUDA drivers for WSL:
- Download from https://developer.nvidia.com/cuda-downloads?target_os=Linux&target_arch=x86_64&Distribution=WSL-Ubuntu
- Follow WSL-specific installation steps
-
Restart WSL:
-
Verify GPU access:
Performance Issues
High VRAM usage: Check VRAM usage via Task Manager:- Task Manager → Performance → GPU
- Watch “Dedicated GPU memory” usage
- Close GPU-intensive apps (browsers, games)
- Use
--max-contextto limit context length:
Known Limitations
AMD GPU Support
- No ROCm on Windows: AMD GPUs use Vulkan backend (slower than ROCm on Linux)
- VRAM detection: Relies on WMI (may be inaccurate for >4 GB GPUs)
- Workaround: Use manual override for accurate VRAM:
Intel Arc Support
- Limited detection: Relies on WMI
- SYCL backend: Requires Intel oneAPI runtime (not auto-detected)
- Recommendation: Use NVIDIA GPU or run in WSL2 for better Intel Arc support
Multi-GPU Limitations
- Different vendors: llmfit uses the GPU with most VRAM as primary
- Mixed NVIDIA + AMD: Only NVIDIA detected via nvidia-smi, AMD via WMI
- Check detection:
