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) On Fri, May 10, 2013 at 6:43 AM, Brad Alexander <stor...@gmail.com> wrote: > Thanks, Mark, > > I'm glad it wasn't just me. I was lucky. I managed to boot back into > 3.2.0, which is where I am now. Had to reinstall the nvidia driver, but all > is good for now. > > --b > > > > On Thu, May 9, 2013 at 10:36 PM, Mark Allums <m...@allums.com> wrote: > >> I upgraded yesterday, and also installed 3.8. I was wondering, has anyone >> else run into issues with the nvidia drivers with this kernel? I realize I >> have a kind of franken-driver situation: >> >> ii glx-alternative-nvidia 0.3.0 >> amd64 allows the selection of NVIDIA as GLX provider >> ii libgl1-nvidia-alternatives 304.88-2 >> amd64 transition libGL.so* diversions to glx-alternative-nvidia >> ii libgl1-nvidia-alternatives-ia32 304.88-2 >> amd64 simplifies replacing MESA libGL with GPU vendor libraries >> (32-bit) >> ii libgl1-nvidia-glx:amd64 313.30-1 >> amd64 NVIDIA binary OpenGL libraries >> ii libgl1-nvidia-glx:i386 313.30-1 >> i386 NVIDIA binary OpenGL libraries >> ii libglx-nvidia-alternatives 304.88-2 >> amd64 transition libgl.so diversions to glx-alternative-nvidia >> ii libnvidia-ml1:amd64 304.88-2 >> amd64 NVIDIA management library (NVML) runtime library >> rc libxvmcnvidia1:amd64 304.84-1 >> amd64 NVIDIA binary XvMC library >> ii nvidia-alternative 313.30-1 >> amd64 allows the selection of NVIDIA as GLX provider >> ii nvidia-glx 313.30-1 >> amd64 NVIDIA metapackage >> ii nvidia-installer-cleanup 20130505+1 >> amd64 cleanup after driver installation with the nvidia-installer >> ii nvidia-kernel-common 20130505+1 >> amd64 NVIDIA binary kernel module support files >> ii nvidia-kernel-dkms 313.30-1 >> amd64 NVIDIA binary kernel module DKMS source >> ii nvidia-kernel-source 304.88-2 >> amd64 NVIDIA binary kernel module source >> ii nvidia-settings 304.88-1 >> amd64 Tool for configuring the NVIDIA graphics driver >> ii nvidia-smi 304.88-2 >> amd64 NVIDIA System Management Interface >> ii nvidia-support 20130505+1 >> amd64 NVIDIA binary graphics driver support files >> ii nvidia-vdpau-driver:amd64 313.30-1 >> amd64 NVIDIA vdpau driver >> ii xserver-xorg-video-nvidia 313.30-1 >> amd64 NVIDIA binary Xorg driver >> but that was a result of the driver bug a couple of months ago which made >> the VTs go away, and the fix was to use the nvidia driver from experimental. >> Has anyone seen any issues with 3.8, or is it my driver craziness? >> Thanks, >> --b >> >> >> The 3.8 kernel, designated "-trunk" in experimental worked well. When >> they moved it to sid, stuff broke for a lot of people, including people who >> were already running it. It's gone from experimental now, so we can't >> easily roll back. You can consider reinstalling the nvidia driver, but it >> didn't work for me. Is nvidia really the problem, or is it the usb driver? >> The usb functionality broke for me, and I can't log in using lightdm, >> because my keyboard and mouse are usb. ssh is not running, so logins from >> the network are out. Hitting the power button for a soft shutdown reset the >> computer instead of performing a shutdown, and I lost a RAID partition out >> of the deal. I put that machine aside and used the enforced downtime as a >> reason to put together a new machine, and I will postpone upgrading to 3.8 >> for a while until this gets straightened out. >> >> So I am urging everyone to exercise caution going to 3.8 for a while. >> >> >> >> >> >> >> > -- Paul E. Johnson Professor, Political Science Assoc. Director 1541 Lilac Lane, Room 504 Center for Research Methods University of Kansas University of Kansas http://pj.freefaculty.org http://quant.ku.edu
