Originally posted by undeaf
I reinstalled, and this time I left the monitor on 1024*85hz. But after I did an online update of everything recomended by Yast plus the nvidia drivers, next time I rebooted, I got the same problem again!
So I reinstalled again, and this time I didn't turn on autologgin so that if it happens again I'll know if it locks up when X starts, or when KDE starts. I guess I should install fluxbox or something in case this is a KDE problem.
Wow, I know exactly what happened to you, it happens to so many people. Forget about all the other stuff that happened afterward and remember one thing, anytime you edit XF86Config, XF86Config-4 or xorg.conf or run a config program that does it for you and rebooting causes your system to "lock up" (screen goes blank when X starts), believe me when I tell you it's not locked up. In fact, X is actually running. The reason you don't "see" anything is cause your monitor resolutions are wrong...period. Here's the way it works. If X fails to load, it always
bounces you to a command prompt. Anytime you boot and you see nothing after X starts loading (or GDM/KDM), your monitor refresh rates are wrong, I can't stress this enough. Many people interpret this as a crash or lock-up but it is not
. If X fails to load, it will bounce you back to a command prompt and spit out an error log. And, I can assure you that Linux rarely "locks up", it's not like Windows, the kernel is always running once it boots and it is extremely difficult to bring down. Save yourself some frustration in the future, always back up your /etc/X11/XF86Config-4 (xorg.conf) file before tinkering with it. That way, you can always Ctrl-Alt-F1 into a command session and log in as root to copy the backup file to its original file name if somthing goes wrong. In fact, I keep a copy of the file in my home folder just in case. Trust me, I know what I'm talking about when it comes to this issue.