We have so far not been able to determine a reliable cure for the cuModuleLoadDataEx failed
problem. That said, my next suggestion would be to run CryoSPARC in a simplified environment.
Caution: Following this suggestion is not guaranteed to establish the desired CryoSPARC functionality and may adversely affect other functionality. Moreover, according to the related post 2d classification kernel error - #8 by sheff_diamond_em, simplification was apparently not necessary to resolve cuModuleLoadDataEx failed
.
But, in case you want to try it:
- Omit cuda directories in
PATH
orLD_LIBRARY_PATH
definitions (outside thecryosparcw
environment).cryosparcw
alone should handle inclusion of cuda-related directories on those variables’ definitions. /sbin/ldconfig -p
output should not include any libraries inside cuda directories. I would I aim for output like this (note the absence of libraries under/usr/local/cuda
):
$ $ /sbin/ldconfig -p|grep -e libcu -e cuda
libicudata.so.70 (libc6,x86-64) => /lib/x86_64-linux-gnu/libicudata.so.70
libcurl.so.4 (libc6,x86-64) => /lib/x86_64-linux-gnu/libcurl.so.4
libcurl-gnutls.so.4 (libc6,x86-64) => /lib/x86_64-linux-gnu/libcurl-gnutls.so.4
libcudadebugger.so.1 (libc6,x86-64) => /lib/x86_64-linux-gnu/libcudadebugger.so.1
libcuda.so.1 (libc6,x86-64) => /lib/x86_64-linux-gnu/libcuda.so.1
libcuda.so (libc6,x86-64) => /lib/x86_64-linux-gnu/libcuda.so
I wonder whether the presence of i386 libraries could be a problem (it apparently wasn’t in the aforementioned related post):
See ubuntu or Linux documentation for information on ldconfig
and related configuration files.
To keep track of experimental changes to configuration files, you may find etckeeper
helpful.