would the windows version run on Linux via wine?
No - it accesses the GPU, which requires the driver libs, which call into the driver running in the Windows kernel mode eventually. Not fucking happening.
It's fucking happened already.
I've done it and confirmed I get full hash rate.
The GPU doesn't care what the host OS is, it's just given a binary file to run in it's own run time
environment. All it needs is a common driver interface to talk to the host.
As an FYI you can also compile cuda in a VM, either windows or linux. You don't need the drivers,
just the cuda tools. I've done that too.
Yeah, no shit - I know this. I also know at least in the case of AMD, you need to call into the driver to load the binary ONTO the GPU. How exactly does Wine handle this without explicitly catching the calls and making sure it calls into the Linux lib, which will properly handle it from there? Maybe Nvidia has a different system for this, I don't know.
Sounds like an inferiour design on AMD. Linux sits between wine and and the driver, it just provides an api
to direct windows system calls to the linux versions. The gpu talks to the windows ccminer via apis in wine
but all it has to do is obey the command to accept a cuda binary file and run it, then send the results back
to ccminer on the host. Nothing more than a simple command interface and data transfer are needed.
I don't know why it's so difficult for AMD. The GPU talks to the host driver so it can talk to any linux process,
that's it's access to the file system. Wine doesn't need to handle it. Wine only gets involed when giving
commands to the gpu or talking to windows processes like the file system when retrieving the results.
It's probably the shitty AMD drivers. Maybe the GPU thinks it's running on windows and thinks it's the
victim of spoofing or something.
)
