more info after running sax2 -m 0=fbdev as suggested.
Sax.log had an error listed at the end to the effect of:
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.0.log", Time: Sun Feb 20 12:39:01 2005
(++) Using config file: "/tmp/sax2-4290/XF86Config"
Parse error on line 133 of section Screen in file /tmp/sax2-4290/XF86Config
The Display keyword requires a number to follow it.
(EE) Problem parsing the config file
(EE) Error parsing the config file
Fatal server error:
no screens found
When reporting a problem related to a server crash, please send
the full server output, not just the last messages.
This can be found in the log file "/var/log/XFree86.0.0.log".
Please report problems to http://www.suse.de/feedback.
Then, after looking up what the -m switch does I tried this:
sax2 -m 0=nv
I did not get any errors so I proceeded with startx. X system loaded but only at 640x480. So now at least I'm back in a GUI to continue troubleshooting. The nv is the module/driver name of the original nvidia driver that was used before obtaining the new drivers via YOU. 3Ddiag had told me to change a line in XF86config to 'NVidia' to enable 3d support, which I did and it worked fine. I am assuming at this point the problem was indeed a problem with the kernel update recieved via YOU.
So what does this mean? what do I do next? pilotgi mentioned recompiling nvidia drivers for my new kernel? Do I need to do that? how do I do that? Is it a matter of recompiling the same driver or obtaining a new driver for this particular kernel? Admittedly, last time I compiled any c/c++ code was in college.. and that was over 5 years ago and via a windows nt environment, but I'm ready and willing... someone just point me in the right direction!