Screen Freezes In Normal Mode, But Not In Failsave-mode

Recently, I installed the new Opensuse 10.3.
Installation was no problem, but running Suse the ordinary way freezes the screen.
I use KDE and own a nvidia grapic-card Geforce 6200.
At start-up everything is fine, I can move the mouse. But opening something like the start-menue cause my computer to freeze, not even terminating by keyboard and power-button works.
Only hard abort.

Starting in failsave-mode and using "startx" works well. That way KDE doesn't freeze.
I have already read about problems with the nvidia-driver of opensuse, there to solve by updating Nvidia over the Nvidia-support.
But for that I have to download the driver from Nvidia while installing:
http:// www .suse.de/~sndirsch/nvidia-installer-HOWTO.html

In failsave mode I cannot connect to the internet. I tried to activate network-services but it did not work.
How can I reach Internet in failsave mode?
Is there any other possibility than updating the driver?

What possible services causing crashes are not activated in failsave-mode?

Thanks for answers, Ilmsiedler

... opening something like the start-menue cause my computer to freeze, not even terminating by keyboard and power-button works.
Only hard abort.

Starting in failsave-mode and using "startx" works well. That way KDE doesn't freeze.[/b]

If you take a good look at the grub boot menu, when openSUSE starts, you will note that the "fail safe" mode is actually the same as the regular boot, EXCEPT it calls a bunch of additional boot codes. Thats the only difference!

What I recommend you do is determine PRECISELY what boot code is being used in fail safe, that allows your PC to run without the freeze. ie Try each of the different boot codes "one by one". If that doesn't work, then you may have to try a combination of codes.

Once you determine what that exact code might be (that allow your PC to function with out a freeze), then see if you can boot your PC with ONLY that boot code in place and still have internet.

Also, once you have determined what the exact code might be, you can research this further to see if there is a less intrusive boot code you can use, that will allow your PC to function with no freeze, and still have Internet access.

Not sure it is related to nvidia, but also unsure exactly what may be.

I just ran a diff on rc3 and rc5 and got

Only in /etc/rc.d/rc5.d/: K11xdm
Only in /etc/rc.d/rc5.d/: K18earlyxdm
Only in /etc/rc.d/rc5.d/: K21earlysyslog
Only in /etc/rc.d/rc5.d/: S01earlysyslog
Only in /etc/rc.d/rc5.d/: S04earlyxdm
Only in /etc/rc.d/rc5.d/: S11xdm

I've briefly looked but can't see anything network related, that would stop it connecting. Though think that wouldn't really be a fix any way. AFAIK nvidia would still cause you problems, only thing I can perhaps think of is the earlyxdm but did look, except for some NFS checks didn't notice much else.

Perhaps run a diff see if you have some different services but at the moment it seems to be pointing to earlyxdm. Maybe you could try that from runlevel 3 see if it gives any output.

diff -r /etc/rc.d/rc3.d/ /etc/rc.d/rc5.d/

Edit
Try oldcpu's way I suspect he's correct. one of these I suspect ide=nodma apm=off acpi=off