Document the preflight check
Browse files
README.md
CHANGED
|
@@ -224,7 +224,21 @@ on PyPI is now a cu130 build and cu130 dropped Volta. Measured on a V100:
|
|
| 224 |
|
| 225 |
That failure arrives at the *first kernel launch*, well after
|
| 226 |
`torch.cuda.is_available()` has returned `True`, so it does not look like an
|
| 227 |
-
installation problem
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 228 |
|
| 229 |
```bash
|
| 230 |
pip install torch --index-url https://download.pytorch.org/whl/cu128
|
|
|
|
| 224 |
|
| 225 |
That failure arrives at the *first kernel launch*, well after
|
| 226 |
`torch.cuda.is_available()` has returned `True`, so it does not look like an
|
| 227 |
+
installation problem — which is why **the loader checks first**. Before reading
|
| 228 |
+
a byte of the 8.46 GB it compares your card against
|
| 229 |
+
`torch.cuda.get_arch_list()` and, on a mismatch, stops with the fix:
|
| 230 |
+
|
| 231 |
+
```
|
| 232 |
+
this torch (2.13.0+cu130) has no kernels for Tesla V100-SXM2-16GB (sm_70).
|
| 233 |
+
It was built for sm_75, sm_80, sm_86, sm_90, sm_100, sm_120, and the first CUDA
|
| 234 |
+
op would fail with 'no kernel image is available for execution on the device'.
|
| 235 |
+
The model is fine - it needs no custom kernels. Install a torch built for your
|
| 236 |
+
card, e.g. for sm_70:
|
| 237 |
+
pip install torch --index-url https://download.pytorch.org/whl/cu128
|
| 238 |
+
or pass device='cpu' to load without touching the GPU.
|
| 239 |
+
```
|
| 240 |
+
|
| 241 |
+
On sm_70 install a cu128 build:
|
| 242 |
|
| 243 |
```bash
|
| 244 |
pip install torch --index-url https://download.pytorch.org/whl/cu128
|