Re: Issues with nvidia 302.17
SOLVED. Although not told by the the tests"dpkg -l |grep nvia| amd
"modinfo nvidia", there was a mismatch between the runtime and the
driver. When this became clear, on a new "apt-get upgrade" a mixture
of versions 302 and 304 was installed, creating a mess. I had to
correct manually by installing the specific version 304 for all
packages with "apt-get install=version".
In face of so much time lost for trivial problems - and posted on NAMD
for NAMD non existing problems (I apologize for that)- I think now
that it would be better (at least for people using the OS for
scientific purposes) to install the driver the "nvidia way" rather
than the "Debian way". In order to have something fixed when upgrading
Debian. As I am presently short of time, I decided for no more
upgrading Debian until I have free time enough to change the "way".
Thanks
francesco Pietra
On Thu, Sep 27, 2012 at 4:30 PM, Francesco Pietra <chiendarret@gmail.com> wrote:
> Looking better, I noticed from the list below
>
> nvidia-xconfig 302.17-2
>
> while all others are 302.17-3
>
> Might that be relevant?
>
>
> The alternative to have all packages exactly the same version is
> upgrading to v 304.48-1
>
> francesco pietra
>
>
> ---------- Forwarded message ----------
> From: Francesco Pietra <chiendarret@gmail.com>
> Date: Thu, Sep 27, 2012 at 12:48 PM
> Subject: Re: Issues with nvidia 302.17
> To: Darac Marjal <mailinglist@darac.org.uk>, amd64 Debian
> <debian-amd64@lists.debian.org>
>
>
> Thanks, I am examining the archive, although, so far, it is not clear
> to me what to do with the nvidia installed version 302.17-3, and how
> DKMS will behave if I intall previous nvidia packages.
>
> At any event, I forgot to indicate that: xserver and nvidia are the
> same version:
>
> francesco@gig64:~$ dpkg -l |grep nvidia
> ii glx-alternative-nvidia 0.2.2
> amd64 allows the selection of NVIDIA as GLX provider
> ii libgl1-nvidia-alternatives 302.17-3
> amd64 transition libGL.so* diversions to
> glx-alternative-nvidia
> ii libgl1-nvidia-glx:amd64 302.17-3
> amd64 NVIDIA binary OpenGL libraries
> ii libglx-nvidia-alternatives 302.17-3
> amd64 transition libgl.so diversions to
> glx-alternative-nvidia
> ii libnvidia-ml1:amd64 302.17-3
> amd64 NVIDIA management library (NVML) runtime library
> ii nvidia-alternative 302.17-3
> amd64 allows the selection of NVIDIA as GLX provider
> ii nvidia-glx 302.17-3
> amd64 NVIDIA metapackage
> ii nvidia-installer-cleanup 20120630+3
> amd64 Cleanup after driver installation with the
> nvidia-installer
> ii nvidia-kernel-common 20120630+3
> amd64 NVIDIA binary kernel module support files
> ii nvidia-kernel-dkms 302.17-3
> amd64 NVIDIA binary kernel module DKMS source
> ii nvidia-smi 302.17-3
> amd64 NVIDIA System Management Interface
> ii nvidia-support 20120630+3
> amd64 NVIDIA binary graphics driver support files
> ii nvidia-vdpau-driver:amd64 302.17-3
> amd64 NVIDIA vdpau driver
> ii nvidia-xconfig 302.17-2
> amd64 X configuration tool for non-free NVIDIA drivers
> ii xserver-xorg-video-nvidia 302.17-3
> amd64 NVIDIA binary Xorg driver
> francesco@gig64:~$
>
>
> root@gig64:/home/francesco# modinfo nvidia
> filename: /lib/modules/3.2.0-2-amd64/updates/dkms/nvidia.ko
> alias: char-major-195-*
> version: 302.17
> supported: external
> license: NVIDIA
> alias: pci:v000010DEd00000E00sv*sd*bc04sc80i00*
> alias: pci:v000010DEd00000AA3sv*sd*bc0Bsc40i00*
> alias: pci:v000010DEd*sv*sd*bc03sc02i00*
> alias: pci:v000010DEd*sv*sd*bc03sc00i00*
> depends: i2c-core
> vermagic: 3.2.0-2-amd64 SMP mod_unload modversions
> parm: NVreg_EnableVia4x:int
> parm: NVreg_EnableALiAGP:int
> parm: NVreg_ReqAGPRate:int
> parm: NVreg_EnableAGPSBA:int
> parm: NVreg_EnableAGPFW:int
> parm: NVreg_Mobile:int
> parm: NVreg_ResmanDebugLevel:int
> parm: NVreg_RmLogonRC:int
> parm: NVreg_ModifyDeviceFiles:int
> parm: NVreg_DeviceFileUID:int
> parm: NVreg_DeviceFileGID:int
> parm: NVreg_DeviceFileMode:int
> parm: NVreg_RemapLimit:int
> parm: NVreg_UpdateMemoryTypes:int
> parm: NVreg_InitializeSystemMemoryAllocations:int
> parm: NVreg_UseVBios:int
> parm: NVreg_RMEdgeIntrCheck:int
> parm: NVreg_UsePageAttributeTable:int
> parm: NVreg_EnableMSI:int
> parm: NVreg_MapRegistersEarly:int
> parm: NVreg_RegisterForACPIEvents:int
> parm: NVreg_RegistryDwords:charp
> parm: NVreg_RmMsg:charp
> parm: NVreg_NvAGP:int
> root@gig64:/home/francesco#
>
>
>
> francesco
> ***********************************
>
> On Thu, Sep 27, 2012 at 11:25 AM, Darac Marjal <mailinglist@darac.org.uk> wrote:
>> On Thu, Sep 27, 2012 at 09:58:40AM +0200, Francesco Pietra wrote:
>>> Hello:
>>>
>>> Following upgrading of amd64 wheezy, version 302.17 of nvidia is
>>> incompatible with software I was using for molecular dynamics on
>>> CPU-GPU.
>>>
>>> On the other hand, amd64 stable offers a version of nvidia that is too
>>> old for the above application.
>>>
>>> Question: is it possible within amd64 wheezy to have a previous
>>> version of nvidia? If yes, a generic guideline on how-to would be much
>>> appreciated.
>>
>> It certainly is. Have a read of the instructions at
>> http://snapshot.debian.org/
>>
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.10 (GNU/Linux)
>>
>> iQIcBAEBCgAGBQJQZBuPAAoJEKB7YbRsd8TGCgYP/19FPqF28+PHpVZq42fQuveK
>> zYZVj6Eus/wvLawTN8BSUwDSuL+JLk/RhUAEwvygzcW5bZuvQ09UkFPLU5V6oZEP
>> YjghVH2fCBbOA1UpidNfYwfLlXiiTNSU55zDVmhNkaRlb1YsRqBQCg5m4X8M1uzy
>> ueJNGiAbkPpMJ80wPYhvKsFdH5qbPceAvL0imdfYdNsLLUrJyF6F9bhmkGeQ9yWV
>> sqr+lgvPPPmv3o3jn1KlsvgbPbQfrj0x64JQWPbfkV1N59d8iwuJYeNspvRSmnnn
>> EzgusvUbDmt1egR6Jm5bUBGnOlu/Qb68TJyEy9RP1dkflKSBBfy+FBEp+dcvpBwq
>> l5cFMlBVJcmcXEVarQ/xgBVtIC1CNRhah4rDoaOTZghADWZ8U9r4x7QnNAZ++8jj
>> u7ONLbrSc+c0ITBjYjzvSRmqYnUg5eZj2W9mKtvj5YDLqx+p3CJPSENbLsCEUATT
>> /M8jOv1OzUjt5A0RGKlTL8KDBCmh5MCItHE8qfNqTH2UpqoeWL8JZWekhNJJacIv
>> ypHk8TXxLukZcD79ol6gB8307vbMLRO87ia0gn0PX9+h9RBk3D2q1wplYOlW6BzM
>> HKbvsHKTsVm2XUjb7KySkbJzuIW5v2X5rOCMCVkHTdIqxavU9cMHzt6rJ96XMsbG
>> qFwZ+40UYs2NYFNQfdrE
>> =UE1U
>> -----END PGP SIGNATURE-----
>>
Reply to: