Direkt vom Baum auf Ihren Tisch in unter 48 Stunden

PUBLI NEWS NATURVALENCIA Wenn nicht, diese Informationen, folgen Sie bitte

upgrade to jessie from wheezy with cuda problems

Hello: I decided to try jessie to get PCIe 3.0 with a recent nvidia driver, thus upgrading from wheezy. wheezy was uname -r 3.2.0-4-amd64 nvidia-smi 304.88 nvcc --version 4.2 (the latter is also the version at which the molecular dynamics code was compiled, and used without calling the

Re: upgrade to jessie from wheezy with cuda problems

On Tue, Nov 12, 2013 at 03:54:32PM +0100, Francesco Pietra wrote: Hello: I decided to try jessie to get PCIe 3.0 with a recent nvidia driver, thus upgrading from wheezy. wheezy was uname -r 3.2.0-4-amd64 nvidia-smi 304.88 nvcc --version 4.2 (the latter is also the version at

Re: upgrade to jessie from wheezy with cuda problems

On Tue, Nov 12, 2013 at 05:22:18PM +0100, Francesco Pietra wrote: Yes. Also, # apt-get remove nvidia-kernel-dkms # apt-get install nvidia-kernel-dkms (which, in the year 2011, served to clear the driver at /lib/modules/2.6.38-2-amd64/updates/dkms. But now the kernel was 3.2.) left the

Re: upgrade to jessie from wheezy with cuda problems

# 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

Re: upgrade to jessie from wheezy with cuda problems

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