Fwd: upgrade to jessie from wheezy with cuda problems

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 bandwidth.
thanks
francesco pietra

---------- Forwarded message ----------
From: Francesco Pietra <[email protected]>
Date: Wed, Nov 13, 2013 at 7:40 PM
Subject: Fwd: upgrade to jessie from wheezy with cuda problems
To: amd64 Debian <[email protected]>



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
francesco@gig64:~/tmp$

---------- Forwarded message ----------
From: Francesco Pietra <[email protected]>
Date: Wed, Nov 13, 2013 at 10:32 AM
Subject: Re: upgrade to jessie from wheezy with cuda problems
To: Lennart Sorensen <[email protected]>
Cc: amd64 Debian <[email protected]>


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 Debian.

I tried GNU "CUDA-Z-07.189.run" (don't remember from where it was
downloaded). However it does not find the shared libXrender.so.1, even if
made available into the same folder of CUDA-Z.

Actually

root@gig64:/home/francesco# apt-file search libXrender.so.1
libxrender1: /usr/lib/x86_64-linux-gnu/libXrender.so.1
libxrender1: /usr/lib/x86_64-linux-gnu/libXrender.so.1.3.0
libxrender1-dbg: /usr/lib/debug/usr/lib/x86_64-linux-gnu/libXrender.so.1.3.0
root@gig64:/home/francesco#

francesco@gig64:~$ echo $PATH
/opt/namd2.9_cuda4.0_2012-09-26/bin:/opt/namd2.9_cuda4.0_2012-09-26/bin:/opt/namd2.9_cuda4.0_2012-09-26/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/opt/amber12/bin:/opt/amber10/bin:/opt/UCSF/Chimera64-2012-10-10/bin:/opt/namd2.9_cuda4.0_2012-09-26/bin/namd2:/opt/amber12/bin:/opt/amber10/bin:/opt/UCSF/Chimera64-2012-10-10/bin:/opt/namd2.9_cuda4.0_2012-09-26/bin/namd2:/opt/amber12/bin:/opt/amber10/bin:/opt/UCSF/Chimera64-2012-10-10/bin:/opt/namd2.9_cuda4.0_2012-09-26/bin/namd2
francesco@gig64:~$

Should /usr/lib/x86_64-linux-gnu be put on my path explicitly?

Thanks

francesco pietra


On Tue, Nov 12, 2013 at 11:37 PM, Lennart Sorensen <
[email protected]> wrote:

> On Tue, Nov 12, 2013 at 10:35:53PM +0100, Francesco Pietra wrote:
> > # apt-get --purge remove *legacy*
> > did the job.
> >
> > I wonder how these legacy packages entered the scene while
> > updating/upgrading from a clean wheezy.
> >
> > The bad news are that with the new driver 319.60 there was no
> acceleration
> > of molecular dynamics for a job of modest size (150K atoms) and slight
> > acceleration (0.12 s/step vs 0.14 s/step) for a heavy job (500K atoms).
> > Weather bringing from PCIe 2.0 (with the 304.xx driver of wheezy) to PCIe
> > 3.0 (with driver 319.60 of jessie)  (increasing the bandwidth from GPUs
> to
> > RAM from 5 to 8GB/s) has not the effect that I hoped on the calculations,
> > or PCIe is still 2.0 with jessie.
> >
> > Now, with cuda 5.0, it should be easy to measure the bandwidth directly.
> I
> > have to learn how and I'll report about in due course.
> >
> >
> > Now
> > nvidia-smi activates the GPUs for normal work,
> > nvidia-smi -L tells about the GPUs,
> > dpkg -l |grep nvidia shows all 319.60 or 5.0.35-8,
> > the X-server can be started and gnome loaded (startx, gnome-session),
> > nvcc --version gives 5.0,  however
> >
> >
> > # modinfo nvidia
> > ERROR: module nvidia not found
> >
> > In analogy with wheezy 3.2.0-4, I expected
> > /lib/modules/3.10-3-amd64/updates/dkms/nvidia.ko
> >
> > Instead, there is
> >
> > /lib/modules/3.10-3-amd64/nvidia/nvidia-current.ko
> >
> > is that a feature of jessie or something wrong?
>
> I think it was renamed.  No idea why.  modinfo nvidia-current should
> work though.
>
> Do you have the cuda libraries for the 319 version installed?
>
> 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 transfering the
> data and managing the GPU makse it worthwhile, but for large jobs the
> high core count and memory bandwidth makes a big difference.
>
> --
> Len Sorensen
>