Fwd: about latest nvidia cuda driver 275.09.07
Under certain circumstances, especially if the CUDA machine is
shutdown or reboot by commands from a ssh-linked desktop, problems
vanish. I begin to suspect that the combination of mutithreading with
the two gtx-470 cards may find problems with the "composite" extension
of X11. When VMD (an OpenGL viewer CUDA accelerated) is launched from
a gnome terminal it says:
Multithreading, 6 processors
Available two CUDA accelerations
Detected X11 "Composite" extension:if incorrect display occurs, try
disabling this optional X server feature
OpenGL renderer GeForce gtx 470/PCI/SSE2
Full GSL rendering mode available
In this case there were no problems in using VMD with a 8GB file,
using many of its features (removing water, calculating RMSD, making
movie of the MD trajectory, etc. What happens - i.e, what is left
available - if "composite" extension is disabled I have not tried.
francesco
---------- Forwarded message ----------
From: Francesco Pietra <chiendarret@gmail.com>
Date: Thu, Jun 30, 2011 at 10:21 AM
Subject: about latest nvidia cuda driver 275.09.07
To: amd64 Debian <debian-amd64@lists.debian.org>
Following kind guidance by Lennart Sorensen as to the correct
installation of the nvidia driver, I recently got a two GTX-470
computer work perfectly for molecular dynamics simulations with
NAMD-CUDA.
The simulations were launched from linux terminal, without calling the
X server. Command (as root)
nvidia-smi -L
was first needed to activate the GTX 470 cards (udev normal affair)
********************
On 27Jun the system was upgraded from driver 270.41.19 to 275.09.07.
On rebooting, dkms did its job for the existing headers 2.6.38-2.
However, now the above NAMD-CUDA MD launching does not work any more.
Sincerely I can't say if the crash described below occurred
immediately after the driver upgrading, but the dates are very close.
Now, on launching MD as above described, the system hangs, the screen
shows blinking characters and letters, and the power must be shut
down. The log of the simulation says
CUDA error cudaStreamCreate on P2 0
which is a normal message of NAMD when the graphic boards are not
seen. However, the computer should not hang.
Launching NAMD-CUDA from a terminal window of gnome-2, the procedure
runs correctly.
I understand that this report fails to analyze correctly what happens.
It is a simple warning to see if other amd64 users had problems with
the new nvidia driver.
thanks
francesco pietra
Reply to: