Linux install of CUDA toolkit for GT 430 card, maybe… - Page 3

ewmayer · 2014-07-17, 23:45

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

Yours truly, - cudaN00b

owftheevil · 2014-07-18, 00:19

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

ewmayer · 2014-07-18, 01:22

Quote:

Originally Posted by ewmayer

cuda-linux64-rel-5.5.22-16488124.run
cuda-samples-linux-5.5.22-16488124.run
NVIDIA-Linux-x86_64-319.37.run

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?

Mark Rose · 2014-07-18, 01:36

Quote:

Originally Posted by ewmayer

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?

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

ewmayer · 2014-07-18, 01:46

Quote:

Originally Posted by Mark Rose

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

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.

ewmayer · 2014-07-18, 01:53

Quote:

Originally Posted by ewmayer

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.

Thanks, Mike - Tab to toggle between optionss, Enter to confirm works - but now I get

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?

Safe to force continue?

Xyzzy · 2014-07-18, 02:31

Quote:

Thanks, Mike - Tab to toggle between optionss, Enter to confirm works…

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.

Batalov · 2014-07-18, 02:35

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

ewmayer · 2014-07-18, 02:38

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.

owftheevil · 2014-07-18, 02:48

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.

Xyzzy · 2014-07-18, 02:51

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

2014-07-18, 02:48	#32
owftheevil "Carl Darby" Oct 2012 Spring Mountains, Nevada 13B₁₆ Posts	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. Last fiddled with by owftheevil on 2014-07-18 at 02:49

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
How to install v25.9 on Linux?	Unregistered	Information & Answers	10	2018-07-04 09:13
CUDA Install errors...HELP...never mind	petrw1	GPU Computing	2	2016-03-06 13:39
TF fetching/reporting toolkit for Linux	swl551	PrimeNet	20	2014-06-19 15:00
CUDA Toolkit for OpenSUSE 11.2--gcc 4.5 and up are not supported	patrik	GPU Computing	9	2012-04-07 03:50
NVIDIA CUDA C toolkit for G80 GPU available	dsouza123	Programming	2	2007-02-18 12:50

2014-07-17, 23:45	#23
ewmayer ∂²ω=0 Sep 2002 República de California 2²×2,939 Posts	p.s.: Maybe this just means I now need to run the .run files deposited in /root? Yours truly, - cudaN00b

2014-07-18, 00:19	#24
owftheevil "Carl Darby" Oct 2012 Spring Mountains, Nevada 473₈ Posts	Yes, or just invoking the .run file without the -extract option.

2014-07-18, 02:35	#30
Batalov "Serge" Mar 2008 San Diego, Calif. 3²·7·163 Posts	Also, try the -h option on the .run file. IIRC, there was an option to confirm the agreement with the license from CL.

2014-07-18, 02:38	#31
ewmayer ∂²ω=0 Sep 2002 República de California 2²·2,939 Posts	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.

2014-07-18, 02:51	#33
Xyzzy Aug 2002 21D2₁₆ Posts	This shows that 4.4 is what the system "expects": https://packages.debian.org/wheezy/gcc