I think it was renamed. No idea why. modinfo nvidia-current should
work though.
Yes, it does.
Do you have the cuda libraries for the 319 version installed?
Yes
I don't play around with GPU computations, but from what I have read it
does need a certain size job before the overhead of
My answer seems to have disappeared. I summarize here.
modinfo nvidia-curred works well. CUDA libraries are installed.
For nvidia-cuda-toolkit, nvidia offers SDK packages for Ubuntu, not for
Debian. I don't like to get into troubles with Ubuntu, which, unlike
LinuxMINT, is not compatible with
On Wed, Nov 13, 2013 at 10:13:15AM +0100, Francesco Pietra wrote:
I think it was renamed. No idea why. modinfo nvidia-current should
work though.
Yes, it does.
Do you have the cuda libraries for the 319 version installed?
Yes
I don't play around with GPU computations, but
On Wed, Nov 13, 2013 at 10:32:26AM +0100, Francesco Pietra wrote:
My answer seems to have disappeared. I summarize here.
modinfo nvidia-curred works well. CUDA libraries are installed.
For nvidia-cuda-toolkit, nvidia offers SDK packages for Ubuntu, not for
Debian. I don't like to get into
francesco@gig64:~/tmp$ export LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/
francesco@gig64:~/tmp$ ./CUDA-Z-0.7.189.run
CUDA-Z 0.7.189 Container
Starting CUDA-Z...
/home/francesco/tmp/CUDA-Z-95b0-7943-3edd-827e/cuda-z: error while loading
shared libraries: libXrender.so.1: wrong ELF class: ELFCLASS64
Sorry, I had not noticed the suggestion, however I had already what inthe
meantime became obvious. The executable is said for both 64 and 32 bit but
apparently the lib has to be 32. I have no 32, nor multiarch, to avoid
complications for a box used for MD only. No luck for me on investigating
the
On Wed, Nov 13, 2013 at 07:40:10PM +0100, Francesco Pietra wrote:
francesco@gig64:~/tmp$ export LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/
That is unnecesary. That is already in the library path. The local
directory is not. Windows implicitly looks in the current directory
for files, linux
Em 13-11-2013 16:40, Francesco Pietra escreveu:
francesco@gig64:~/tmp$ export LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/
francesco@gig64:~/tmp$ ./CUDA-Z-0.7.189.run
CUDA-Z 0.7.189 Container
Starting CUDA-Z...
/home/francesco/tmp/CUDA-Z-95b0-7943-3edd-827e/cuda-z: error while
loading shared
francesco@gig64:~$ file
/home/francesco/tmp/CUDA-Z-95b0-7943-3edd-827e/cuda-z
/home/francesco/tmp/CUDA-Z-95b0-7943-3edd-827e/cuda-z: ERROR: cannot open
`/home/francesco/tmp/CUDA-Z-95b0-7943-3edd-827e/cuda-z' (No such file or
directory)
francesco@gig64:~$
On Wed, Nov 13, 2013 at 8:18 PM, Fabricio
What does 'file ./CUDA-Z-0.7.189.run' say?
francesco@gig64:~/tmp$ file ./CUDA-Z-0.7.189.run
./CUDA-Z-0.7.189.run: data
francesco@gig64:~/tmp$
On Wed, Nov 13, 2013 at 7:52 PM, Lennart Sorensen
lsore...@csclub.uwaterloo.ca wrote:
On Wed, Nov 13, 2013 at 07:40:10PM +0100, Francesco Pietra
On Wed, Nov 13, 2013 at 10:53:30PM +0100, Francesco Pietra wrote:
francesco@gig64:~/tmp$ file ./CUDA-Z-0.7.189.run
./CUDA-Z-0.7.189.run: data
francesco@gig64:~/tmp$
OK that's weird. I expected to see x86 32 or 64bit binary.
Seems to be a shell scripts with compressed code in it. Yuck. :)
On Wed, Nov 13, 2013 at 05:43:47PM -0500, Lennart Sorensen wrote:
On Wed, Nov 13, 2013 at 10:53:30PM +0100, Francesco Pietra wrote:
francesco@gig64:~/tmp$ file ./CUDA-Z-0.7.189.run
./CUDA-Z-0.7.189.run: data
francesco@gig64:~/tmp$
OK that's weird. I expected to see x86 32 or 64bit
12 matches
Mail list logo
