Nvidia 96.31 problem, white (black) screen while loading GDM (and after)

[daniel1988]

Nvidia driver 96.31 was successfully installed on Ubuntu 6.10 (Edgy Eft) using Envy script (http://albertomilone.com/nvidia_scripts1.html)

There is one issue: after booting the system, when GDM loads, there is only white screen like this (http://img443.imageshack.us/img443/5905/nvidiaew6.jpg) < 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:
$ glxinfo | grep direct
direct rendering: Yes

Content of /etc/X11/xorg.conf here (http://paste.ubuntu-nl.org/558/)
& the content of /var/log/Xorg.0.log.old here (http://paste.ubuntu-nl.org/559/)

I tried to sudo /etc/init.d/gdm restart < same thing: white (or black, which becomes white after hitting keys for rising display brightness - Fn+F7) screen appears... solution: kill it with ctrl+alt+f1 and login

Not sure, but this could be usefull: diff -U6 /var/log/Xorg.0.log.old /var/log/Xorg.0.log
--- /var/log/Xorg.0.log.old 2007-01-05 17:17:23.000000000 +0100
+++ /var/log/Xorg.0.log 2007-01-05 17:45:41.000000000 +0100
@@ -8,13 +8,13 @@
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
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/Xorg.0.log", Time: Fri Jan 5 17:15:55 2007
+(==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 5 17:17:35 2007
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) | |-->Monitor "Generic Monitor"
(**) | |-->Device "NVIDIA Corporation NV17 [GeForce4 460 Go]"
(**) |-->Input Device "Generic Keyboard"
@@ -69,13 +69,13 @@
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules/libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.0
-(++) using VT number 7
+(--) using VT number 9

(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,1a30 card 1179,0001 rev 04 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 8086,1a31 card 0000,0000 rev 04 class 06,04,00 hdr 01
(II) PCI: 00:1d:0: chip 8086,2482 card 1179,0001 rev 02 class 0c,03,00 hdr 00
(II) PCI: 00:1e:0: chip 8086,2448 card 0000,0000 rev 42 class 06,04,00 hdr 01
@@ -402,37 +402,27 @@
[33] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
(II) Setting vga for screen 0.
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
-(**) NVIDIA(0): Option "ExactModeTimingsDVI"
-(**) NVIDIA(0): Option "UseEdidDpi" "FALSE"
-(**) NVIDIA(0): Option "ModeValidation" "NoEdidDFPMaxSizeCheck, NoVesaModes"
(**) NVIDIA(0): Enabling RENDER acceleration
-(WW) NVIDIA(0): Unrecognized ModeValidation token "NoEdidDFPMaxSizeCheck";
-(WW) NVIDIA(0): ignoring.
-(WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
(II) NVIDIA(0): NVIDIA GPU GeForce4 460 Go at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 32768 kBytes
(--) NVIDIA(0): VideoBIOS: 04.17.00.59.d3
(II) NVIDIA(0): Detected AGP rate: 4X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce4 460 Go at PCI:1:0:0:
-(--) NVIDIA(0): CRT-0
(--) NVIDIA(0): TOSHIBA Internal Panel (DFP-0)
-(--) NVIDIA(0): CRT-0: 350.0 MHz maximum pixel clock
(--) NVIDIA(0): TOSHIBA Internal Panel (DFP-0): 224.0 MHz maximum pixel clock
(--) NVIDIA(0): TOSHIBA Internal Panel (DFP-0): Internal Dual Link LVDS
-(II) NVIDIA(0): Mode Validation Overrides for CRT-0:
-(II) NVIDIA(0): NoVesaModes
-(II) NVIDIA(0): Assigned Display Device: CRT-0
+(II) NVIDIA(0): Assigned Display Device: DFP-0
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "1024x768"
(II) NVIDIA(0): Virtual screen size determined to be 1024 x 768
-(==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
+(++) NVIDIA(0): DPI set to (100, 100); computed from -dpi X commandline option
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] 0 0 0xd7f80000 - 0xd7ffffff (0x80000) MX[B]
[1] 0 0 0xd8000000 - 0xdfffffff (0x8000000) MX[B]
[2] 0 0 0xfd000000 - 0xfdffffff (0x1000000) MX[B]
@@ -590,8 +580,9 @@
No such file or directory.
Error opening /dev/wacom : No such file or directory
(II) Configured Mouse: ps2EnableDataReporting: succeeded
Could not init font path element /usr/share/fonts/X11/TTF/, removing from list!
Could not init font path element /usr/share/fonts/X11/OTF, removing from list!
Could not init font path element /usr/share/fonts/X11/CID/, removing from list!
-AUDIT: Fri Jan 5 17:17:23 2007: 3928 X: client 4 rejected from local host
- Auth name: MIT-MAGIC-COOKIE-1 ID: -1
+SetGrabKeysState - disabled
+SetGrabKeysState - enabled
+SetClientVersion: 0 9


This was already discussed on ubuntu forums (http://www.ubuntuforums.org/showthread.php?t=330657); plz read that topic for more info.

That's all from me for now...

Cheers,
Daniel

[netllama]

Please start X with the following command:
startx -- -logverbose 6

and then generate a new bug report.

Also, have you verified that you're using the latest BIOS?

Thanks,
Lonni

[daniel1988]

Please start X with the following command:
startx -- -logverbose 6

and then generate a new bug report.
Done, in attachment

Also, have you verified that you're using the latest BIOS?

Thanks,
Lonni
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.

[netllama]

Was this new bug report generated while the problem was present?

[daniel1988]

Was this new bug report generated while the problem was present?
boot, (white screen), ctrl+alt+f1, login, sudo rm /tmp/.X0-lock, startx -- - logverbose 6, nvidia-bug-report.sh ...

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?)

Regards,
Daniel

[netllama]

I'd just like to see a bug report generated while the problem is present.

thanks

[daniel1988]

This is it... but keep in mind that -- - logverbose 6 isn't set

[netllama]

Try adding the following option to the Device section of xorg.conf:
Option "UseDisplayDevice" "DFP"

thanks,
Lonni

[daniel1988]

Try adding the following option to the Device section of xorg.conf:
Option "UseDisplayDevice" "DFP"

thanks,
Lonni
It helped. Now it works like a charm.

Thank you

--Daniel

[TfM]

Hi,

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.

Thanks for your help,