There is one issue: after booting the system, when GDM loads, there is only white screen like this < link to the image showing how it looks like.
Edit: forgot to mention, I'm using NVIDIA Corporation NV17 [GeForce4 460 Go] inside of Toshiba Satellite S5200-701

The only way to kill this nag screen is to press ctrl+alt+f1, log in there, sudo rm /tmp/.X0-lock and then startx < after this, nvidia logo is shown, gnome session starts and everyting goes fine:

Code:

$ glxinfo | grep direct
direct rendering: Yes

Content of /etc/X11/xorg.conf here
& the content of /var/log/Xorg.0.log.old here

I've just updated my laptop's BIOS to newest version available (1.20 > 1.50). Problem still persists.

This could be useful: after loading GDM, white screen appears, but GDM works. I can login "on blind"; it accepts username & password, there is sound that shows that gnome session starts (and it really starts), but I can't do anything... can't see anything because of white screen. After killing GDM, logging in, startx, everything goes fine - I'm now writing this post from laptop.

Should I do like this: boot, (white screen), crtl+alt+f2 (let GDM & xorg alive in tty1 and use tty2 instead), login, nvidia-bug-report.sh... ? In this case "logverbose 6" option isn't set (is there a line which could be inserted in xorg.conf for verbose logging?)

I searched this problem for long, but eventually solved it before reading this post. So thanks for confirming

I'm using a Toshiba Satellite 2410 on Opensuse 11.0 with a Gefore4 Go 420, and had:

1. The invalid EDID, which returned weird resolutions. Solved it ok with a manual EDID.
2. The screens in the wrong init order, with the "creamy" screen issue. This thread has the solution.

Now I encounter that "creamy" screen issue when returning from hibernation (s2disk). Entering hibernation is ok, but when I wake the computer, the system boots, the grey splash screen comes up, the progress bar walks up to 80%, then the system freezes with the strange display effect.

I'm no expert, but it seems to me the driver is not using any xorg.conf for resuming? Thus it doesn't use the DFP option. Any idea how I should solve/debug this? There's no log file for the server when resuming, and I don't really know where to insert the logverbose option for debugging the resume procedure (if possible).

Also, this doesn't relate, but suspend to ram works out-of-the-box with the -f switch.