[Bug 52528] New: cuda 10.0 and 10.2 installation fails with "err:ole:CoRevokeClassObject COM was not initialized"
https://bugs.winehq.org/show_bug.cgi?id=52528 Bug ID: 52528 Summary: cuda 10.0 and 10.2 installation fails with "err:ole:CoRevokeClassObject COM was not initialized" Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alois.schloegl(a)gmail.com Distribution: --- When trying to get warpem http://www.warpem.com/warp/?page_id=65 running, I'm trying to install cuda 10.0 or 10.2, according to these instructions https://gist.github.com/imaami/37105333c0d16210b2cac9d4032155aa on Wine-7.0 (stable), wine 7.1 (devel), and wine 7.1 (Staging). Staging provides some version of cuda, but the application crashes; a possibile reason is Cuda version mismatch. The installation procedure of Cuda 10.x proceedes quite far, but fails at the end always with .... .... 0138:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0138:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0140:fixme:ole:CoInitializeSecurity 00000000, -1, 00000000, 00000000, 0, 3, 00000000, 0, 00000000 stub 0138:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFA, 0032FEAC 0138:err:ole:CoRevokeClassObject COM was not initialized Because I was not sure whether the important parts are installed, I tested with Cuda-Z, too. But Cuda-Z does not recognize the GPU's, in "stable" and "devel" (with "Staging" the gpu is recognized) The host system is Debian11, and two GTX 1080Ti cards, nvidia-driver/libcuda1 460.91. I tested Cuda 10.0 as well as Cuda10.2. In order reproduce this issue, You need to run these commands: URL_100=https://developer.nvidia.com/compute/cuda/10.0/Prod/local_installers/cuda_10... URL_102=http://developer.download.nvidia.com/compute/cuda/10.2/Prod/local_installers... wget -nc $URL_100 wget -nc $URL_102 wineboot -i winetricks msxml3 winetricks win10 wineconsole cmd.exe /c "$(basename $URL_100)" -s \ {cu{dart,objdump,pti},nv{cc,prune,disasm,prof,ml_dev},memcheck, \ {cu{blas,fft,rand,solver,sparse},nvgraph,npp,nvrtc}{,_dev}}_10.0 wineconsole cmd.exe /c "$(basename $URL_102)" -s \ {cu{dart,objdump,pti},nv{cc,prune,disasm,prof,ml_dev},memcheck, \ {cu{blas,fft,rand,solver,sparse},nvgraph,npp,nvrtc}{,_dev}}_10.2 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52528 Sveinar Søpler <cybermax(a)dexter.no> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cybermax(a)dexter.no --- Comment #1 from Sveinar Søpler <cybermax(a)dexter.no> --- Not sure why you are installing CUDA SDK in the prefix, unless you are going to compile cuda apps? Does "Warpem" compile various CUDA apps? The equivalent of "Latest GPU driver from NVIDIA" when it comes to CUDA, is using wine-staging to get "nvcuda". This is a relay library that provides the Wine version of nvcuda.dll that in turn utilizes Linux GPU driver's libcuda.so. To provide anything meaningful in terms of debugging information you need: wine-staging (preferably 7.1) Run with WINEDEBUG=+nvcuda,+nvapi I dunno if this "warpem" software can run some sort of diagnostic upon starting or whatnot? I do not have any particular hardware (Gatan K3 Camera?). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52528 --- Comment #2 from Sveinar Søpler <cybermax(a)dexter.no> --- Oki. Using wine-staging-7.1 (Ubuntu 20.04) i set up prefix, and installed .NET with: winetricks dotnet472 Then i installed warpem according to instructions from your link above, and used winetricks win10 and winetricks renderer=vulkan The last one i needed as it seems OpenGL wined3d just crashed on some stuff. Dunno. Atleast this opened a reasonable window, but not really sure how to proceed from there to actually do anything useful. I tried pressing "Start processing", but that did not seem to make anything but a black window pop up? Am i supposed to load an image or something perhaps? Anyway, i got plenty of loglines from nvcuda, without anything apparent failing for me. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52528 --- Comment #3 from Alois Schlögl <alois.schloegl(a)gmail.com> --- As far as I know it does not need a Camera, but can be used for offline analysis of data, that has been previously acquired with such a camera. warpem does not compile anything. You got much further then me. (I guess I tried with wine-stable and had had difficulties with getting dotnet472 installed, when installing over ssh, no GUI was shown, etc.). You suggestions helped mo to get warpem installed - once. Currently, I've problems reproducing the installation (dotnet472 fails to install). I'm investigating this. But if this works out, the workaround is to use wine-staging, and this bug report would become moot. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52528 --- Comment #4 from Sveinar Søpler <cybermax(a)dexter.no> --- (In reply to Alois Schlögl from comment #3)
But if this works out, the workaround is to use wine-staging, and this bug report would become moot.
Since nvCUDA is a windows low-level library - much like libcuda would be for Linux - you cannot expect the windows version to work by installing that. It is somewhat similar for other things like OpenCL. You cant install some windows driver in wine and expect this to work. Wine-devel does NOT include nvCUDA, so if you do not build/install nvcuda standalone and install it, you have to use wine-staging. There are workarounds to this, but i will not go indepth into this here. Not sure what you mean by "installing over ssh" tho? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52528 --- Comment #5 from Alois Schlögl <alois.schloegl(a)gmail.com> --- (In reply to Sveinar Søpler from comment #4)
(In reply to Alois Schlögl from comment #3)
But if this works out, the workaround is to use wine-staging, and this bug report would become moot.
Since nvCUDA is a windows low-level library - much like libcuda would be for Linux - you cannot expect the windows version to work by installing that. It is somewhat similar for other things like OpenCL. You cant install some windows driver in wine and expect this to work.
Sure, I understand. Some reports seem to suggest that this was possible with cuda 9.x . And when I started to look into this, I was not aware that wine-staging is the proper way of running cuda applications. That's something I learned now.
Wine-devel does NOT include nvCUDA, so if you do not build/install nvcuda standalone and install it, you have to use wine-staging. There are workarounds to this, but i will not go indepth into this here.
Not sure what you mean by "installing over ssh" tho?
I was trying to install warpem on a remote machine, and had difficulties installing dotnet472. The messages from "winetricks dotnet472" were different when I did not use X-tunneling, and this was puzzling me. (Now, I know these difficulties were related to a lack of diskspace and perhaps the winetricks versions). Afterall, I've been able to get warpem running https://appdb.winehq.org/objectManager.php?sClass=version&iId=40620 Your hints were important in getting this to work. Thanks. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla