about summary refs log tree commit diff
path: root/test
diff options
context:
space:
mode:
authorPjotr <wrk@bosa.lan>2026-10-22 09:02:53 +0000
committerPjotr <wrk@bosa.lan>2026-10-22 09:02:53 +0000
commit4c692148e6de551ef7c83677b5f1e5ca11e05df7 (patch)
treee573ca630ad74810e6e92035936905777486faef /test
parent07298ef6b812cd07a7c505fec12cc765cfaf319b (diff)
downloadhmf-guix-cwl-main.tar.gz
docs: Record the GPU investigation and its two blockers. main
The host does have an RTX 5080 (driver 610.43.02), but it cannot be used
from here and would not work with the packaged DJL stack anyway:

- the sandbox has no nvidia device nodes (/dev is a private tmpfs with
  only null/zero/full/random/urandom/tty/fuse), CapEff=0 so mknod is
  denied, and there is no libcuda.so* anywhere; only the kernel module is
  visible through /proc/driver/nvidia;
- DJL's newest CUDA native is pytorch-native-cu124 (PyTorch 2.5.1), and
  the libtorch_cuda.so in our cu121 bundle carries sm_35..sm_90 kernels
  only - no sm_100/sm_120, which is what Blackwell needs (CUDA 12.8+).

The plausible route is written down for whoever has the device: DJL 0.39
(pytorch-jni 2.7.1; all 17 DJL classes v-chord/v-cuppa import are
unchanged) plus a system libtorch 2.7.1+cu128 via PYTORCH_LIBRARY_PATH.
README's v-chord paragraph now states the same facts instead of "wait for
a cu128 runtime".
Diffstat (limited to 'test')
0 files changed, 0 insertions, 0 deletions