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 -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131112223724.gf20...@csclub.uwaterloo.ca