mirror of
https://github.com/cloudstack-llc/msty-docs.git
synced 2026-07-18 18:54:38 -04:00
@@ -0,0 +1,139 @@
|
||||
---
|
||||
title: GPU Supported by Msty
|
||||
description: Msty supports a wide range of GPUs for faster inference. Check if your GPU is supported by Msty.
|
||||
---
|
||||
|
||||
# GPU
|
||||
|
||||
## Nvidia
|
||||
|
||||
Msty (and Ollama, the underlying Local AI engine) supports Nvidia GPUs with compute capability 5.0+.
|
||||
|
||||
Check your compute compatibility to see if your card is supported:
|
||||
[https://developer.nvidia.com/cuda-gpus](https://developer.nvidia.com/cuda-gpus)
|
||||
|
||||
| Compute Capability | Family | Cards |
|
||||
|--------------------|---------------------|-------------------------------------------------------------------------------------------------------------------------------|
|
||||
| 9.0 | NVIDIA | `H100` |
|
||||
| 8.9 | GeForce RTX 40xx | `RTX 4090` `RTX 4080 SUPER` `RTX 4080` `RTX 4070 Ti SUPER` `RTX 4070 Ti` `RTX 4070 SUPER` `RTX 4070` `RTX 4060 Ti` `RTX 4060` |
|
||||
| | NVIDIA Professional | `L4` `L40` `RTX 6000` |
|
||||
| 8.6 | GeForce RTX 30xx | `RTX 3090 Ti` `RTX 3090` `RTX 3080 Ti` `RTX 3080` `RTX 3070 Ti` `RTX 3070` `RTX 3060 Ti` `RTX 3060` `RTX 3050 Ti` `RTX 3050` |
|
||||
| | NVIDIA Professional | `A40` `RTX A6000` `RTX A5000` `RTX A4000` `RTX A3000` `RTX A2000` `A10` `A16` `A2` |
|
||||
| 8.0 | NVIDIA | `A100` `A30` |
|
||||
| 7.5 | GeForce GTX/RTX | `GTX 1650 Ti` `TITAN RTX` `RTX 2080 Ti` `RTX 2080` `RTX 2070` `RTX 2060` |
|
||||
| | NVIDIA Professional | `T4` `RTX 5000` `RTX 4000` `RTX 3000` `T2000` `T1200` `T1000` `T600` `T500` |
|
||||
| | Quadro | `RTX 8000` `RTX 6000` `RTX 5000` `RTX 4000` |
|
||||
| 7.0 | NVIDIA | `TITAN V` `V100` `Quadro GV100` |
|
||||
| 6.1 | NVIDIA TITAN | `TITAN Xp` `TITAN X` |
|
||||
| | GeForce GTX | `GTX 1080 Ti` `GTX 1080` `GTX 1070 Ti` `GTX 1070` `GTX 1060` `GTX 1050 Ti` `GTX 1050` |
|
||||
| | Quadro | `P6000` `P5200` `P4200` `P3200` `P5000` `P4000` `P3000` `P2200` `P2000` `P1000` `P620` `P600` `P500` `P520` |
|
||||
| | Tesla | `P40` `P4` |
|
||||
| 6.0 | NVIDIA | `Tesla P100` `Quadro GP100` |
|
||||
| 5.2 | GeForce GTX | `GTX TITAN X` `GTX 980 Ti` `GTX 980` `GTX 970` `GTX 960` `GTX 950` |
|
||||
| | Quadro | `M6000 24GB` `M6000` `M5000` `M5500M` `M4000` `M2200` `M2000` `M620` |
|
||||
| | Tesla | `M60` `M40` |
|
||||
| 5.0 | GeForce GTX | `GTX 750 Ti` `GTX 750` `NVS 810` |
|
||||
| | Quadro | `K2200` `K1200` `K620` `M1200` `M520` `M5000M` `M4000M` `M3000M` `M2000M` `M1000M` `K620M` `M600M` `M500M` |
|
||||
|
||||
### GPU Selection
|
||||
|
||||
If you have multiple NVIDIA GPUs in your system and want to limit Msty to use a subset, you can set
|
||||
`CUDA_VISIBLE_DEVICES` to a comma separated list of GPUs. This value can be set in `Settings` -> `General Settings` ->
|
||||
`Local AI` > `Service Configurations` > `Advanced Configurations`. Numeric IDs may be used, however ordering may vary,
|
||||
so UUIDs are more reliable. You can discover the UUID of your GPUs by running `nvidia-smi -L` If you want to ignore the
|
||||
GPUs and force CPU usage, use an invalid GPU ID (e.g., "-1")
|
||||
|
||||
::image-card{src="/getting-started/gpu-service-config.webp" alt="You can pass extra environment variables to the Local AI service"}
|
||||
::
|
||||
|
||||
### Laptop Suspend Resume
|
||||
|
||||
On Linux, after a suspend/resume cycle, sometimes Msty/Ollama will fail to discover
|
||||
your NVIDIA GPU, and fallback to running on the CPU. You can work around this
|
||||
driver bug by reloading the NVIDIA UVM driver with `sudo rmmod nvidia_uvm &&
|
||||
sudo modprobe nvidia_uvm`
|
||||
|
||||
## AMD Radeon
|
||||
|
||||
Msty/Ollama supports the following AMD GPUs:
|
||||
|
||||
### Linux Support
|
||||
|
||||
| Family | Cards and accelerators |
|
||||
|----------------|------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| AMD Radeon RX | `7900 XTX` `7900 XT` `7900 GRE` `7800 XT` `7700 XT` `7600 XT` `7600` `6950 XT` `6900 XTX` `6900XT` `6800 XT` `6800` `Vega 64` `Vega 56` |
|
||||
| AMD Radeon PRO | `W7900` `W7800` `W7700` `W7600` `W7500` `W6900X` `W6800X Duo` `W6800X` `W6800` `V620` `V420` `V340` `V320` `Vega II Duo` `Vega II` `VII` `SSG` |
|
||||
| AMD Instinct | `MI300X` `MI300A` `MI300` `MI250X` `MI250` `MI210` `MI200` `MI100` `MI60` `MI50` |
|
||||
|
||||
### Windows Support
|
||||
|
||||
With ROCm v6.1, the following GPUs are supported on Windows.
|
||||
|
||||
| Family | Cards and accelerators |
|
||||
|----------------|---------------------------------------------------------------------------------------------------------------------|
|
||||
| AMD Radeon RX | `7900 XTX` `7900 XT` `7900 GRE` `7800 XT` `7700 XT` `7600 XT` `7600` `6950 XT` `6900 XTX` `6900XT` `6800 XT` `6800` |
|
||||
| AMD Radeon PRO | `W7900` `W7800` `W7700` `W7600` `W7500` `W6900X` `W6800X Duo` `W6800X` `W6800` `V620` |
|
||||
|
||||
### Overrides on Linux
|
||||
|
||||
Msty/Ollama leverages the AMD ROCm library, which does not support all AMD GPUs. In
|
||||
some cases you can force the system to try to use a similar LLVM target that is
|
||||
close. For example The Radeon RX 5400 is `gfx1034` (also known as 10.3.4)
|
||||
however, ROCm does not currently support this target. The closest support is
|
||||
`gfx1030`. You can use the environment variable `HSA_OVERRIDE_GFX_VERSION` with
|
||||
`x.y.z` syntax. So for example, to force the system to run on the RX 5400, you
|
||||
would set `HSA_OVERRIDE_GFX_VERSION="10.3.0"` as an environment variable for the
|
||||
server. If you have an unsupported AMD GPU you can experiment using the list of
|
||||
supported types below.
|
||||
|
||||
At this time, the known supported GPU types on Linux are the following LLVM Targets.
|
||||
This table shows some example GPUs that map to these LLVM targets:
|
||||
| **LLVM Target** | **An Example GPU** |
|
||||
|-----------------|---------------------|
|
||||
| gfx900 | Radeon RX Vega 56 |
|
||||
| gfx906 | Radeon Instinct MI50 |
|
||||
| gfx908 | Radeon Instinct MI100 |
|
||||
| gfx90a | Radeon Instinct MI210 |
|
||||
| gfx940 | Radeon Instinct MI300 |
|
||||
| gfx941 | |
|
||||
| gfx942 | |
|
||||
| gfx1030 | Radeon PRO V620 |
|
||||
| gfx1100 | Radeon PRO W7900 |
|
||||
| gfx1101 | Radeon PRO W7700 |
|
||||
| gfx1102 | Radeon RX 7600 |
|
||||
|
||||
AMD is working on enhancing ROCm v6 to broaden support for families of GPUs in a
|
||||
future release which should increase support for more GPUs.
|
||||
|
||||
### GPU Selection
|
||||
|
||||
If you have multiple AMD GPUs in your system and want to limit Msty/Ollama to use a subset, you can set
|
||||
`HIP_VISIBLE_DEVICES` to a comma separated list of GPUs. This value can be set in `Settings` ->
|
||||
`General Settings` -> `Local AI` > `Service Configurations` > `Advanced Configurations`.
|
||||
You can see the list of devices with `rocminfo`. If you want to ignore the GPUs
|
||||
and force CPU usage, use an invalid GPU ID (e.g., "-1")
|
||||
|
||||
::image-plain{src="/getting-started/gpu-model-config.webp" alt="You can pass extra params to a model globally"}
|
||||
::
|
||||
|
||||
You can also pass `main_gpu` parameter to each model to specify which GPU to use for that model. This can be set
|
||||
globally for all models in `Settings` -> `General Settings` -> `Local AI` > `Model Configurations` >
|
||||
`Advanced Configurations` or per model in the model's configuration available when chatting with the model. This value
|
||||
can even be set per chat.
|
||||
|
||||
::image-plain{src="/getting-started/model-extra-configs.webp" alt="You can pass extra params (A) per chat (B) or per model (B)"}
|
||||
::
|
||||
|
||||
### Container Permission
|
||||
|
||||
In some Linux distributions, SELinux can prevent containers from
|
||||
accessing the AMD GPU devices. On the host system you can run
|
||||
`sudo setsebool container_use_devices=1` to allow containers to use devices.
|
||||
|
||||
### Metal (Apple GPUs)
|
||||
|
||||
Msty/Ollama supports GPU acceleration on Apple devices via the Metal API.
|
||||
|
||||
### Windows Troubleshooting
|
||||
|
||||
Check out the [AMD ROCm on Windows Issues](/troubleshooting/amd-rocm-windows-issues) guide for common issues and solutions when using AMD GPUs on Windows.
|
||||
@@ -0,0 +1,59 @@
|
||||
---
|
||||
title: AMD ROCm on Windows Issues
|
||||
description: Troubleshooting common issues with AMD ROCm on Windows
|
||||
---
|
||||
|
||||
Msty supports AMD ROCm on Windows out of the box and we even have a dedicated installer for it. However, sometimes
|
||||
things can go wrong and your GPU card might not be supported or detected at all. Here are some troubleshooting steps you
|
||||
can take to resolve the issue.
|
||||
|
||||
## Get the latest version of Msty
|
||||
|
||||
We are constantly improving Msty and adding support for new GPUs. Make sure you have the latest version of Msty
|
||||
installed on your system. You can download the latest version from the [Msty website](https://msty.app).
|
||||
|
||||
## Try a different installer
|
||||
|
||||
Instead of using the dedicated AMD ROCm on Windows installer, you can try using the generic Auto installer and see if
|
||||
that works for you. You can download the Auto installer from the [Msty website](https://msty.app). Give CPU only
|
||||
installer a try as well if nothing works.
|
||||
|
||||
## Check if your GPU is supported
|
||||
|
||||
Not all AMD GPUs are supported by Msty (and Ollama, the underlying Local AI service ). Check here to see if your GPU is
|
||||
supported: [Supported GPUs](/getting-started/gpu-support).
|
||||
|
||||
## Check if your GPU is detected
|
||||
|
||||
cd into `%appdata%/Msty` from your terminal and run `./msty-local.exe serve` to see if your GPU is detected and for
|
||||
other useful information.
|
||||
|
||||
## Multiple GPUs
|
||||
|
||||
If you have multiple GPUs in your system, you can try passing `main_gpu` parameter to each model to specify which GPU to
|
||||
use for that model. This can be set globally for all models in `Settings` -> `General Settings` -> `Local AI` >
|
||||
`Model Configurations` > `Advanced Configurations` or per model in the model's configuration available when chatting
|
||||
with the model. This value can even be set per chat.
|
||||
|
||||
::image-plain{src="/getting-started/gpu-model-config.webp" alt="You can pass extra params to a model globally"}
|
||||
::
|
||||
|
||||
::image-plain{src="/getting-started/model-extra-configs.webp" alt="You can pass extra params (A) per chat (B) or per
|
||||
model (B)"}
|
||||
::
|
||||
|
||||
## Custom Ollama Build
|
||||
|
||||
If you have an unsupported GPU, or if you just couldn't get Msty to work with your GPU, you can try using a custom build
|
||||
of Ollama:
|
||||
|
||||
1. From https://github.com/likelovewant/ollama-for-amd/releases, download the latest Ollama AMD zipped file
|
||||
`ollama-windows-amd64.7z`.
|
||||
2. Replace `%appdata%\Roaming\Msty\lib\ollama` with the downloaded archive (unzip it first).
|
||||
3. Download the ROCBLAS packages for your GPU model
|
||||
from https://github.com/likelovewant/ROCmLibs-for-gfx1103-AMD780M-APU/releases.
|
||||
4. Rename `%appdata%\Roaming\Msty\lib\ollama\rocblas\library` to `library.bck` as a backup.
|
||||
5. Extract the library folder in the downloaded ROCBLAS packages to `%appdata%\Roaming\Msty\lib\ollama\rocblas\` to
|
||||
replace the old library.
|
||||
6. Run `./msty-local.exe serve` from `%appdata%/Msty` to see if your GPU is detected and for other useful information.
|
||||
7. Stop the server and restart Msty.
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 172 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 256 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 49 KiB |
Reference in New Issue
Block a user