this is an update to version 1.0.9.
Used an installation of WarpEM that was installed in WINEPREFIX with wine-staging 7.18.
What does not
When trying to start Warp or M it stops with the error "No cuda devices where found. ..."
What was not tested
could not do any testing because Warp and M do not start.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Current||Debian 11||Dec 22 2022||7.22-staging||Yes||No||No||Garbage||Alois Schlögl|
|Show||Debian 11||Dec 22 2022||7.21-staging||Yes||Yes||Yes||Silver||Alois Schlögl|
|Show||Debian GNU/Linux 11.x "Bullseye" x86_64||Oct 07 2022||7.18-staging||Yes||Yes||No||Silver||Alois Schlögl|
|Bug #||Description||Status||Resolution||Other apps affected|
|54102||GPU Caps Viewer does not report any CUDA devices starting with version 7.21||UNCONFIRMED||View|
|54197||cuda-z and warpem fail in wine-staging 7.22 and later||UNCONFIRMED||View|
|55011||Cuda-application M/WarpEM got stuck or crashes in wine-staging/7.21, wine/8.9+nvidia-libs||UNCONFIRMED||View|
Using Boxnet  in Warp crashes on machine with RTX2080 cards but works fine on GTX1080 cards (other GPU's were not tested)
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.