[QUOTE=storm5510;531824]

This machine has a GPU in it, and I saw a lot of references to Nvidia during the OS install. I looked around here today and I saw no mention of any program which could use the GPU in a Linux environment. I found that rather amazing. Perhaps I did not look where I should have. Is there no such animal?[/QUOTE]

What GPU? Every gpu compute program used for GIMPS is available for linux as well, although you may need to compile some of them.

[QUOTE=kracker;531827]What GPU? Every gpu compute program used for GIMPS is available for linux as well, although you may need to compile some of them.[/QUOTE]

Nvidia GTX 750Ti. Not the sharpest knife in the drawer, but it is consistent.

[QUOTE=storm5510;531851]Nvidia GTX 750Ti. Not the sharpest knife in the drawer, but it is consistent.[/QUOTE]

After installing the drivers, I would try [URL="https://mersenneforum.org/mfaktc/mfaktc-0.21/mfaktc-0.21.linux64.cuda65.tar.gz"]this[/URL], or if that doesn't work the many binaries floating around in the colab thread that might work... if nothing else, you'll have to compile from source(which I doubt).

[QUOTE=kracker;531895]After installing the drivers, I would try [URL="https://mersenneforum.org/mfaktc/mfaktc-0.21/mfaktc-0.21.linux64.cuda65.tar.gz"]this[/URL], or if that doesn't work the many binaries floating around in the colab thread that might work... if nothing else, you'll have to compile from source(which I doubt).[/QUOTE]

I found the archive above. I have it all unpacked into a folder. I try to run it, like this:

[CODE]./mfaktc.exe[/CODE]I get this error message:
[CODE]

./mfaktc.exe error while loading shared libraries libcudart.so.6.5: cannot open shared object file: No such file or directory.
[/CODE]This file is present in a folder called "lib" below the parent just as it is in the archive. :confused:

[QUOTE=storm5510;531909]I found the archive above. I have it all unpacked into a folder. I try to run it, like this:

[CODE]./mfaktc.exe[/CODE]I get this error message:
[CODE]

./mfaktc.exe error while loading shared libraries libcudart.so.6.5: cannot open shared object file: No such file or directory.
[/CODE]This file is present in a folder called "lib" below the parent just as it is in the archive. :confused:[/QUOTE]

I would try moving the libraries from lib to the same folder mfaktc.exe is.

[QUOTE=kracker;531913]I would try moving the libraries from lib to the same folder mfaktc.exe is.[/QUOTE]

If that doesn't work, try the executable [URL="https://mersenneforum.org/showpost.php?p=525235&postcount=19"]I posted way back in September[/URL].

This is the same exec I include in the GPU72 TF Colab bootstrap payload.

[QUOTE=kracker;531913]I would try moving the libraries from lib to the same folder mfaktc.exe is.[/QUOTE]


I tried this earlier. I get icons with a red x and a lock symbol on them. It's trying to create a link instead of moving the file. It says in the properties, "Link (broken)(inode/symlink)."

[QUOTE=chatsall]If that doesn't work, try the executable [URL="https://mersenneforum.org/showpost.php?p=525235&postcount=19"]I posted way back in September[/URL].

This is the same exec I include in the GPU72 TF Colab bootstrap payload.[/QUOTE]

I get the same message, but different library name. libcudart.so.10.0. I believe this refers to CUDA 10. A few months back, on the Windows drive, the 10 version stopped working. I had to revert it back to 80 to get it to run again.

[QUOTE=storm5510;531922]I tried this earlier. I get icons with a red x and a lock symbol on them. It's trying to create a link instead of moving the file. It says in the properties, "Link (broken)(inode/symlink)."



I get the same message, but different library name. libcudart.so.10.0. I believe this refers to CUDA 10. A few months back, on the Windows drive, the 10 version stopped working. I had to revert it back to 80 to get it to run again.[/QUOTE]

Copy just the 6.5.14 file(if you can) and rename it to libcudart.so.6.5
Likely not ideal, but might be the easiest way assuming it eorks.

[QUOTE=kracker;531926]Copy just the 6.5.14 file(if you can) and rename it to libcudart.so.6.5
Likely not ideal, but might be the easiest way assuming it eorks.[/QUOTE]

I have the proper 6.5 file. Copying only creates a broken link, like before. I wonder if this has anything to do with permissions? It seems strange that it is locked in this one place.

[QUOTE=storm5510;531922]I get the same message, but different library name. libcudart.so.10.0. I believe this refers to CUDA 10. A few months back, on the Windows drive, the 10 version stopped working. I had to revert it back to 80 to get it to run again.[/QUOTE]

Ah... OK... Try running "apt-get -y install cuda-cudart-10-0" before running mfaktc.

Colab made a change to their VM a while back, which broke my payload. Naturally this happened just when the power fell out from under me, and I wasn't able to implement a fix (provided by (I believe) kracker) for several days.

I should recompile mfaktc to the new "native" environment. Still running only two screens; after "firing" my previous "kit" supplier, I just now have in hand a new motherboard which should support more than two monitors.

[QUOTE=storm5510;531930]I have the proper 6.5 file. Copying only creates a broken link, like before. I wonder if this has anything to do with permissions? It seems strange that it is locked in this one place.[/QUOTE]

I would try copying the file from bash and not the file manager gui and see what it says.

EDIT: Just try this and see if it works...