this is an update to version 1.0.9.
What does not
nvidia-gpus/cuda is needed
nvidia-libs was needed
This was installed this with cuda11.4.4 which is the latest cuda version supported by the nvidia-drivers (v470.xxx) in Debian11 .
What was not tested
No data processing, or any of the steps not described above.
Unlike in previous versions of wine, dotnet48, and d3dcompiler_47 are not needed anymore.
Further tests are needed to confirm its usability.
|Nov 29 2023
|Dec 22 2022
|Dec 22 2022
|Debian GNU/Linux 11.x "Bullseye" x86_64
|Oct 07 2022
|Other apps affected
|GPU Caps Viewer does not report any CUDA devices starting with version 7.22
|cuda-z and warpem fail in wine-staging 7.22 and later
|Cuda-application M/WarpEM got stuck or crashes in wine-staging/7.21, wine/8.9+nvidia-libs
Using Boxnet  in Warp crashes on machine with RTX2080 cards but works fine on GTX1080 cards (other GPU's were not tested)
This is fixed in recent version of Sveinar's nvidia-libs
Instead of using all of wine-staging, it is sufficient to use only the patches of "nvcuda-CUDA_Support".
The Boxnet module in Warpem seem only usable with older GPU versions like the GTX1080ti
For the RTX2080 an additional patch to wine is needed (see Bug 53809)
When using newer cards like RTX3080, A10, A40, Warpem hangs when trying to load the Boxnet model. I do not know whether this is also the case on Window, so I do not know whether this is a bug in Wine or Warpem.
However, when Boxnet is not needed, Warpem seems to run fine.