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 issue unaltered. > > # modinfo nvidia > ERROR: module nvidia not found > > $ dpkg -l |grep nvidia |less > > shows > > libl1-nvidia-glx:amd64 319.60 > > and > > libg1-nvidia-legacy-304xx--glx:amd64 304.108-4 > > NVIDIA metapackage rc nvidia-glx 304.88-1-deb7u1 > > nvidia-legacy-304xx-driver 304.108-4 > > > nvidia-legacy-304xx-kernel-dkms 304.108-4 > > nvidia-settings-legacy-303xx 304.108-2 > > xserver-xorg-video-nvidia-legacy-304xx 304.108-4 > > > Everything else 319.60-1 and cuda 5.0 > > I don't understand why these 304xx are threatening. > > I had also run > # nvidia-xconfig
I think you should remove all packages with legacy-304xx in the name, and install the current ones (nvidia-kernel-dkms, nvidia-glx, etc). legacy-304xx will never move beyond version 304.xx after all as the name implies. -- 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/20131112165947.ge20...@csclub.uwaterloo.ca