p.s.: Maybe this just means I now need to run the .run files deposited in /root?

Yours truly, - cudaN00b

Yes, or just invoking the .run file without the -extract option.

[QUOTE=ewmayer;378370][i]cuda-linux64-rel-5.5.22-16488124.run
cuda-samples-linux-5.5.22-16488124.run
NVIDIA-Linux-x86_64-319.37.run[/i][/QUOTE]

Did the first 2 of those, that is more along the lines of what I expected. Do I need the 3rd one for my GUI-less command-line-only setup?

[QUOTE=ewmayer;378380]Did the first 2 of those, that is more along the lines of what I expected. Do I need the 3rd one for my GUI-less command-line-only setup?[/QUOTE]

You don't need the samples. You do need the other two.

[QUOTE=Mark Rose;378383]You don't need the samples. You do need the other two.[/QUOTE]

Thanks- but when I execute NVIDIA-Linux-x86_64-319.37.run,
unlike the other 2 where all was strictly b&w text-only / command-line-only, now - this is via ssh from the Mac, mind you - I get a wild-colored "GUI like" EULA with 2 red accept / decline boxes at top. But double-clicking "Accept" only highlights the text in the box - i.e. I need a way of forcing things back into cmd-line mode.

[QUOTE=ewmayer;378384]Thanks- but when I execute NVIDIA-Linux-x86_64-319.37.run,
unlike the other 2 where all was strictly b&w text-only / command-line-only, now - this is via ssh from the Mac, mind you - I get a wild-colored "GUI like" EULA with 2 red accept / decline boxes at top. But double-clicking "Accept" only highlights the text in the box - i.e. I need a way of forcing things back into cmd-line mode.[/QUOTE]

Thanks, Mike - Tab to toggle between optionss, Enter to confirm works - but now I get
[i]
The CC version check failed:

The compiler used to compile the kernel (gcc 4.3) does not exactly match the current compiler (gcc 4.4). The Linux 2.6 kernel module loader
rejects kernel modules built with a version of gcc that does not exactly match that of the compiler used to build the running kernel.

If you know what you are doing and want to ignore the gcc version check, select "No" to continue installation. Otherwise, select "Yes" to abort
installation, set the CC environment variable to the name of the compiler used to compile your kernel, and restart installation. Abort now?
[/i]
Safe to force continue?

[QUOTE]Thanks, Mike - Tab to toggle between optionss, Enter to confirm works…[/QUOTE]We're just adding this in case this thread is ever useful in the future: The GUI-looking screen is just colored ASCII art and because you are using SSH the mouse works, but only to copy and paste stuff. The remote computer that you are logging into knows nothing about that mouse.

Also, try the -h option on the .run file.
IIRC, there was an option to confirm the agreement with the license from CL.

Can anyone comment on the gcc 4.3 vs 4.4 issue?

Note that my Mlucas-builds-for-Haswell are pretty insensitive to the gcc version, so I'd be fine to downgrade to 4.3 if the CUDA 5.5 install really does have an issue with 4.4.

I've never dealt with this problem, so this is just from what I've read:

Its not CUDA5.5 that has problems with gcc4.4, its that the kernel module loader dislikes modules and kernels built with different gcc versions.

Edit: Its not a problem to have multiple gcc versions.

This shows that 4.4 is what the system "expects": [url]https://packages.debian.org/wheezy/gcc[/url]