From 9ba59faee1932bc36c1cf5b245010a2b5629db11 Mon Sep 17 00:00:00 2001 From: Kenneth Hoste Date: Thu, 21 Dec 2023 20:57:44 +0100 Subject: [PATCH] show expected and problematic output produced by deviceQuery in GPU docs --- docs/gpu.md | 28 +++++++++++++++++++++++++--- 1 file changed, 25 insertions(+), 3 deletions(-) diff --git a/docs/gpu.md b/docs/gpu.md index 16009ba79..cde980084 100644 --- a/docs/gpu.md +++ b/docs/gpu.md @@ -152,10 +152,32 @@ The only scenario where this would be required is if `$LD_LIBRARY_PATH` is modif ### Testing the GPU support {: #gpu_cuda_testing } -The quickest way to test if software installations included in EESSI can access and use your GPU is to run the +The quickest way to test if software installations included in EESSI can access and use your GPU is to run the `deviceQuery` executable that is part of the `CUDA-Samples` module: -``` +```{ .bash .copy } module load CUDA-Samples deviceQuery ``` -If both are successful, you should see information about your GPU printed to your terminal. +If both are successful, you should see information about your GPU printed to your terminal, for example: + +``` +$ deviceQuery +deviceQuery Starting... + + CUDA Device Query (Runtime API) version (CUDART static linking) + +Detected 1 CUDA Capable device(s) + +Device 0: "NVIDIA A2" + CUDA Driver Version / Runtime Version 12.2 / 12.1 + CUDA Capability Major/Minor version number: 8.6 +... +``` + +If the `deviceQuery` command can not access your GPU, you will see an error message like: +``` +cudaGetDeviceCount returned 35 +-> CUDA driver version is insufficient for CUDA runtime version +Result = FAIL +``` +```