Hi, I've ran into the same issues on an old NVidia Quadro FX 360M.
Honestly, i don't know what's going with Debian lately. Wheezy looked promising and has been quite a dissapointment when it comes to package quality. Golden hint include nomodeset in /etc/default/grub on the line GRUB_CMD_LINE_DEFAULT="quiet splash nomodeset" This will greatly improve the speed and stability of your system. Make sure in /etc/modprobe.conf.d/nvidia...... there is a line stating blacklist nouveau What i've done is to download the latest nvidia driver ( long life version ) and run the installer, make sure to remove ANY debian nvidia packages. So far i had to ditch gdm as login manager as it crashed and crashed, using lightdm now. J. On Tue, 24 Dec 2013 10:02:42 -0500, Jon N wrote: > On Mon, Dec 23, 2013 at 11:37 AM, Brad Rogers <b...@fineby.me.uk> wrote: > > <---snip---> > >>>have any trouble doing that. But I don't want to have a package from >>>repository still installed at the same time as the nvidia download. >> >> There are problems with that as you can imagine. Debian packages can >> get confused by a previous nvidia installation. I don't know whether >> the same is true the other way round, but better safe than sorry. >> >> I include here a list of all nvidia specific packages I have installed, >> for the sake of comparison with your own list: >> >> glx-alternative-nvidia_0.4.1 libgl1-nvidia-glx_319.76-1 >> libnvidia-ml1_319.76-1 libvdpau1_0.7-1 libxnvctrl0_319.72-1 >> libxnvctrl0_319.72-1 libxnvctrl0_319.72-1 nvidia-driver_319.76-1 >> nvidia-kernel-dkms_319.76-1 nvidia-settings_319.72-1 >> nvidia-alternative_319.76-1 nvidia-xconfig_319.72-1 >> nvidia-installer-cleanup_20131102+1 * >> nvidia-kernel-common_20131102+1 nvidia-kernel-source_319.76-1 >> nvidia-support_20131102+1 xserver-xorg-video-nouveau_1.0.10-1 >> xserver-xorg-video-nvidia_319.76-1 >> >> * handy for ensuring the nvidia downloaded module stuff doesn't >> conflict with the Debian packages. > > Before I gave up I ran 'dpkg-reconfigure with each package name above > hoping that fix something, or at least generate an error message that > would give some clue. But, no luck. So I uninstalled it all and > rebooted. My desktop came up fine with (I think) the vesa driver. > > But, I often watch HD shows through MythTV, which didn't work well at > all with the vesa driver, nor with the nouveau driver. So, back to the > downloaded nvidia driver. Which had the exact same problem as the > nvidia package loaded through the repository, X would not load. Ouch, I > hadn't expected that. > > Poking around again I noticed a line in Xorg.0.log: > > "Kernel command line: BOOT_IMAGE+/vmlinux-3.11.-2-686-pae > root=/dev/mapper/MyVG-root_LV ro nomodeset nouveau.modeset=0" > > I did notice that earlier, but wasn't worried about nouveau being in > there because it's blacklisted. But with these continuing problems I > guess it's worth looking into. I edited it out in /etc/defaults/grub > and ran 'update-grub'. That was it! I am really puzzled how it got > there. It seem strange to me that uninstalling the downloaded nvidia > drivers (which is the first thing I did when this all started) would add > that. None of the 'grub.*' files in /etc/defaults was newer than 2012, > but it was in there, suggesting it was always in the command line. So > why was it a problem now??? As usual, I figure I must have missed > something, or done something dumb. But, at least it works! > > Oh, and one of my reasons for changing in the first place was to have > the driver automatically configured for each new kernel update that was > installed. Apparently I did not have 'dkms' installed before, but it > got left over. The nvidia driver offered to register with it for > automatic updates. So I still get the main reason for changing. > > Thanks for all your help, > Jon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/l9d86d$mar$1...@ger.gmane.org
