I was beaten to the punch. Before I could roll back to 304.88, 319.17 came out. I upgraded to it, and am now running with nvidia on 3.8.12.
--b On Thu, May 16, 2013 at 7:47 PM, Brad Alexander <stor...@gmail.com> wrote: > Had a chance to look in to this this evening. Apparently the nvidia-smi > nvidia-settings nvidia-kernel-source libnvidia-ml1:amd64 packages are still > at 304.88 rather than 313.30. > > I guess I'm going to try rolling everything back to 304.88... > > > On Thu, May 16, 2013 at 4:54 AM, Brad Alexander <stor...@gmail.com> wrote: > >> Well, I upgraded, which installed a newer version of the nvidia drivers >> (313-30). So I gave them a spin on 3.8-1. Booted up on it, and did a >> dpkg-reconfigure nvidia-kernel-dkms. >> >> It built fine, but at the end, a message popped up saying >> >> nvidia: >> Running module version sanity check. >> Error! Module version 313.30 for nvidia.ko >> is not newer than what is already found in kernel 3.8-1-amd64 (313.30). >> You may override bhy specofying --force. >> >> And when I try to insert the module, I get: >> >> # modprobe nvidia >> [ 229.364270] Module len 8728526 truncated >> ERROR: could not insert nvidia: Exec format error >> >> Any ideas? >> --b >> >> >> >> On Wed, May 15, 2013 at 11:14 AM, Brad Alexander <stor...@gmail.com>wrote: >> >>> In my case, possibly my upgrades from experimental. I think I have seen >>> a couple of other threads where pulling previous updates from experimental >>> has lead to problems once the freeze ended. >>> >>> I'm going to downgrade to the nvidia drivers in sid and try 3.8 again. >>> >>> >>> On Wed, May 15, 2013 at 2:46 AM, Mark Allums <m...@allums.com> wrote: >>> >>>> On a Dell Precision M4600 laptop, I installed a clean Wheezy release, >>>> installed nvidia drivers along with the dkms packages that go with. Because >>>> of network driver trouble, I took the kernel from sid. >>>> After that, everything works fine. I mean, video is fine. Networking >>>> still a problem. Here is my version information: >>>> >>>> $ dpkg -l | grep nvidia >>>> ii glx-alternative-nvidia 0.2.2 >>>> amd64 allows the selection of NVIDIA as GLX provider >>>> ii libgl1-nvidia-alternatives 304.88-1 >>>> amd64 transition libGL.so* diversions to >>>> glx-alternative-nvidia >>>> ii libgl1-nvidia-glx:amd64 304.88-1 >>>> amd64 NVIDIA binary OpenGL libraries >>>> ii libglx-nvidia-alternatives 304.88-1 >>>> amd64 transition libgl.so diversions to glx-alternative-nvidia >>>> ii libxvmcnvidia1:amd64 304.88-1 >>>> amd64 NVIDIA binary XvMC library >>>> ii nvidia-alternative 304.88-1 >>>> amd64 allows the selection of NVIDIA as GLX provider >>>> ii nvidia-glx 304.88-1 >>>> 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 304.88-1 >>>> amd64 NVIDIA binary kernel module DKMS source >>>> ii nvidia-settings 304.88-1 >>>> amd64 Tool for configuring the NVIDIA graphics driver >>>> ii nvidia-support 20120630+3 >>>> amd64 NVIDIA binary graphics driver support files >>>> ii nvidia-vdpau-driver:amd64 304.88-1 >>>> amd64 NVIDIA vdpau driver >>>> ii xserver-xorg-video-nvidia 304.88-1 >>>> amd64 NVIDIA binary Xorg driver >>>> >>>> linux-image-3.8-1-amd64 3.8.12-1 >>>> amd64 Linux 3.8 for 64-bit PCs >>>> ii linux-image-amd64 3.8+47 >>>> amd64 Linux for 64-bit PCs (meta-package) >>>> >>>> >>>> Thanks. That's good to know. Only some folks are affected. I wonder >>>> why? >>>> >>>> >>>> >>>> >>>> >>>> >>> >> >
