about summary refs log tree commit diff
path: root/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'README.md')
-rw-r--r--README.md16
1 files changed, 11 insertions, 5 deletions
diff --git a/README.md b/README.md
index 4b01029..a759e92 100644
--- a/README.md
+++ b/README.md
@@ -281,11 +281,17 @@ The scores are meaningless biologically (the circos PNG is a stub), but
 every stage of the DJL pipeline exercises: `libtorch` dlopen, TorchScript
 deserialisation, forward pass, output translation.
 
-The GPU leg needs a DJL runtime with kernels for the installed card.
-CUDA 12.1 (the newest DJL native published for PyTorch 2.2.2) has no
-`sm_120` images, so RTX 50-series (Blackwell) cards fail with *"no kernel
-image is available for execution on the device"*; either wait for a cu128
-runtime or point `PYTORCH_LIBRARY_PATH` at a system libtorch.
+The GPU leg needs a DJL runtime with kernels for the installed card, and
+no DJL release has them for RTX 50-series (Blackwell, `sm_120`): the
+newest native DJL publishes is `pytorch-native-cu124` 2.5.1, i.e. CUDA
+12.4, whose `libtorch_cuda.so` carries `sm_35` … `sm_90` kernels only
+(checked against the 2.2.2/cu121 bundle here).  Blackwell needs CUDA 12.8+
+(PyTorch 2.7+), so the card fails with *"no kernel image is available for
+execution on the device"*.  The plausible route is a newer DJL
+(`pytorch-jni` 2.7.1 exists for DJL 0.34–0.39, and every DJL class v-chord
+uses is unchanged in 0.39) plus a system libtorch 2.7.1+cu128 pointed at
+by `PYTORCH_LIBRARY_PATH` — that has to be tried on a host where the GPU
+device is actually visible.
 
 ## Related