On Thursday 03 November 2005 09:46 pm, mailmanmike@sbcglobal.net wrote: > I have been using kdm, but the same thing happens when I do "startx" from a > console. > I have not set any options manually, only by dpkg-reconfigure. I have > looked at my xorg-conf file and can verify the settings are correct. > I am not using module-assistant. > I am not aware of how to "attach my Xorg.0.log file to my mail" , I am > writing this from my windows partition. > I will try and look at that file and see if I can somehow get thatr info > down and then post it. The /var/log/Xorg.0.log file is usually pretty big; if you can't get to it to copy and paste somehow you'll be transcribing for days :- ) Perhaps something is happening with KDE; in my experience, troubles with the NVIDIA driver show up before X even starts, or deep into a session. Try running 'apt-get install twm' , editing your ~/.xsession file to say: exec twm and then run startx from the console. If TWM starts and X doesn't bail out, that will eliminate a lot of things to check for, especially if you're also just using the regular 'nv' driver instead of the 'nvidia' driver. Also, I suggest completely uninstalling the NVIDIA driver, then using module-assistant, available through apt, to build the nvidia-kernel module. module-assistant is very clever, and you won't have to fight with GCC versions because it can handle that (in my experience). The NVIDIA installer does some strange things, and using module-assistant and Debian's nvidia-glx/nvidia-kernel-source packages causes a lot fewer problems. It's possible that the dist-upgrade you did that broke X overwrote some of the files that the NVIDIA installer created, since they wouldn't be tracked by dpkg. -- Ryan Schultz "vi users are mammals, and they flip out and kill people *all the time.*"
Attachment:
pgpAH95lDIV6D.pgp
Description: PGP signature