diff --git a/doc.zih.tu-dresden.de/docs/software/gpu_programming.md b/doc.zih.tu-dresden.de/docs/software/gpu_programming.md
index af027d612321b45c16b5096b556ff6ed244845c3..2e5b57422a0472650a6fc64c5c4bfeac433e5801 100644
--- a/doc.zih.tu-dresden.de/docs/software/gpu_programming.md
+++ b/doc.zih.tu-dresden.de/docs/software/gpu_programming.md
@@ -200,7 +200,15 @@ detail in [nvcc documentation](https://docs.nvidia.com/cuda/cuda-compiler-driver
 This compiler is available via several `CUDA` packages, a default version can be loaded via
 `module load CUDA`. Additionally, the `NVHPC` modules provide CUDA tools as well.
 
-#### Usage of the CUDA compiler
+For using CUDA with OpenMPI at multiple nodes, the OpenMPI module loaded shall have be compiled with
+CUDA support. If you aren't sure if the module you are using has support for it you can check it as
+following:
+
+```console
+ompi_info --parsable --all | grep mpi_built_with_cuda_support:value | awk -F":" '{print "OpenMPI supports CUDA:",$7}'
+```
+
+#### Usage of the CUDA Compiler
 
 The simple invocation `nvcc <code.cu>` will compile a valid CUDA program. `nvcc` differentiates
 between the device and the host code, which will be compiled in separate phases. Therefore, compiler