Running MFAKTC in WINE?
 

Has anybody tried running mfaktX in Linux via WINE? I've tried the appropriate TF program in straight Linux but it severely affects the display, whereas the Windows version doesn't do this, so I'm wondering if running the Windows version of, say, mfaktc through WINE might work better than the dedicated Linux version.

My first attempt to do this after installing WINE involved running mfaktc from the same Windows directory (it's a dual-boot machine). But I've run into two issues:

[LIST=1][*]For some reason, when running via WINE, mfaktc cannot read the mfaktc.ini file to get the settings, and gives me multiple warnings.[*]And it gives me some business about needing to match the CUDA toolkit version that was used during compile.[/LIST]I ran into the same issue as #2 when I tried to [URL="http://mersenneforum.org/showthread.php?t=21369&page=2"]TF in Linux[/URL], but I'm not certain that the solution here would be the same as in that case.

Any ideas/hints will be appreciated.

Rodrigo

Brief update: I eliminated issue #1 above by launching the Windows cmd.exe in WINE, then running mfaktc-win-32.exe. But part #2 about matching the CUDA toolkit version remains, so suggestions as to what to do about that are welcome.

The OS is Kubuntu.

[QUOTE=Rodrigo;465106]The OS is Kubuntu.[/QUOTE]

Using a GTX 580, I have to stop mfaktc. Using a GTX 1070, I don't even notice it running.

Anyway, go to System Settings -> Notifications -> Notifications -> Screen Saver, and then you can configure scripts to run when the screen is locked and unlocked.

Thanks. I have a question: The idea about the screensaver seems to have to do with running the Linux version of mfaktc. How does changing the screen locking options affect the choppiness of the screen when mfaktc is running? Not sure what one has to do with the other.

I'm still hoping for ideas on how to get mfaktc-win-32 (or -64) to run under WINE. :smile:

Rodrigo

Another update: I copied the MFAKTC folder from the Windows partition over to the WINE pseudo-c: drive. This makes the path to mfaktc-win-32.exe shorter, but it doesn't help with the issue of the CUDA toolkit vs. runtime versions.

Running "mfaktc-win-32.exe -h" works, but anything that requires performing actual calculations (such as the self-test) fails to the above problem.

Rodrigo

Have you tried putting the necessary cuda* dlls in the mfaktc folder if they're not already there?

[QUOTE=wombatman;465138]Have you tried putting the necessary cuda* dlls in the mfaktc folder if they're not already there?[/QUOTE]
Excellent point! That is where I have them. No path problems!

[QUOTE=Rodrigo;465122]Thanks. I have a question: The idea about the screensaver seems to have to do with running the Linux version of mfaktc. How does changing the screen locking options affect the choppiness of the screen when mfaktc is running? Not sure what one has to do with the other.[/quote]

Well the idea is to stop mfaktc when the screen is unlocked. So no interference when you're actually using your computer.

[quote]I'm still hoping for ideas on how to get mfaktc-win-32 (or -64) to run under WINE. :smile:

Rodrigo[/QUOTE]

Can't help you there.

[QUOTE=wombatman;465138]Have you tried putting the necessary cuda* dlls in the mfaktc folder if they're not already there?[/QUOTE]
Yes, I had copied over the whole contents of the MFAKTC directory and it included the files cudart32_42_9.dll and cudart64_42_9.dll.

Any other files that need to be (copied over) there?

Rodrigo

[QUOTE=Mark Rose;465142]Well the idea is to stop mfaktc when the screen is unlocked. So no interference when you're actually using your computer.[/QUOTE]
Ah, I understand the purpose of that now. Thank you. If I can't get MFAKTC-WIN-xx to work under WINE, I'll investigate this approach.

Rodrigo

[QUOTE=Rodrigo;465157]Yes, I had copied over the whole contents of the MFAKTC directory and it included the files cudart32_42_9.dll and cudart64_42_9.dll.

Any other files that need to be (copied over) there?

Rodrigo[/QUOTE]

Sorry, that was the only brilliant idea I had :smile:

Here are screenshots showing what I'm seeing. The first image shows the CUDA runtime and driver information that mfaktc-win-32.exe yields in Windows Vista, while the other is what the same program (copied over from the Vista folder) shows in Kubuntu Linux via WINE.


[ATTACH]16616[/ATTACH]

[ATTACH]16617[/ATTACH]

[QUOTE=Rodrigo;465223]Here are screenshots showing what I'm seeing. The first image shows the CUDA runtime and driver information that mfaktc-win-32.exe yields in Windows Vista, while the other is what the same program (copied over from the Vista folder) shows in Kubuntu Linux via WINE.


[ATTACH]16616[/ATTACH]

[ATTACH]16617[/ATTACH][/QUOTE]

Looks like the cuda kernel modules aren't loaded. Try starting mfaktc.exe in Linux, then try again in WINE.

Thanks, Mark.

I got MFAKTC.EXE (the Linux version) to run the self-test. That's significant progress and I could leave things at that if necessary.

But even after running it, waiting 'til the self-test ended, and then running MFAKTC-WIN-xx.EXE under WINE, this last one is still giving the message about the CUDA runtime version needing to match the toolkit version.

Rodrigo