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. > > > > > > >
