-The 'splash' kernel command line is never used.

-I Tried with and without vga=0x31A and it makes no difference. In both
case the "nv" driver fails and screen is all garbled. This parameters
(vga=0x31A ) is for using the video frame buffer and have high
resolution font at the console.

-I Found out something very interesting. If I change the video driver in
xorg.conf to "nv" and restart X.org it is working only if "nv" is
immediately used after the proprietary driver "nvidia" (from nVidia) is
used (no computer reboot in between).

This look like something on the video card is not initialized properly
by "nv" but this thing is left initalized properly after proprietary
"nvidia" ran just before "nv" is used. If I try to launch a second time
Xorg with "nv", it fails miserably. BUT if I relaunch X.org with the
proprietary "nvidia" and then relaunch with "nv" it works again.

Here is how I proceed;
1-Boot the PC and go "telinit 1"

2-Edit /etc/X11/xorg.conf and set driver to "nvidia" then launch X.org
(by invoking startx ). Xorg start properly. Then exit X.org (CTRL-
Backspace) (computer is NOT rebooted).

3-clear /var/log/Xorg.0 and edit /etc/X11/xorg.conf and set driver to
"nv" then launch X.org (by invoking startx ). HO SURPRISE, "NV" DRIVER
WORKS!! I capture the /var/log/Xorg.0.log as "nvafternvidiaok", then
exit X.org (CTRL-Backspace)  (computer is NOT rebooted)

4-Launch X.org again (by invoking startx ). NOW "NV" DRIVER FAILS AND
SCREEN IS GARBLED!! I capture the /var/log/Xorg.0.log as "nvafternvbad",
then exit X.org (CTRL-Backspace)  (computer is NOT rebooted)

Every time "nv" is used either after "nv" or "vesa", it fails to works.
Every time "nv" is used after "nvidia" it works.

The video card works with "vesa" driver all the time.

Note that I know "nv" was working in the test above as the refresh rate
was different than proprietary driver so visually I can see it's not the
"nVidia" driver.

If you look at the difference of both logs file you see this;

$ diff -Nur nvafternvidiaok nvafternvbad
--- nvafternvidiaok     2007-04-05 22:03:24.000000000 -0400
+++ nvafternvbad        2007-04-05 22:05:01.000000000 -0400
@@ -11,7 +11,7 @@
 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: Thu Apr  5 22:00:22 2007
+(==) Log file: "/var/log/Xorg.0.log", Time: Thu Apr  5 22:04:28 2007
 (==) Using config file: "/etc/X11/xorg.conf"
 (==) ServerLayout "Default Layout"
 (**) |-->Screen "Default Screen" (0)
@@ -429,7 +429,7 @@
 (II) Reloading /usr/lib/xorg/modules//libddc.so
 (II) NV(0): I2C bus "DDC" initialized.
 (II) NV(0): Probing for analog device on output A...
-(--) NV(0):   ...found one
+(--) NV(0):   ...can't find one
 (II) NV(0): Probing for analog device on output B...
 (--) NV(0):   ...found one
 (II) NV(0): Probing for EDID on I2C bus A...
@@ -496,8 +496,8 @@
 (II) NV(0): I2C device "DDC:ddc2" registered at address 0xA0.
 (II) NV(0): I2C device "DDC:ddc2" removed.
 (II) NV(0):   ... none found
-(--) NV(0): CRTC 0 appears to have a CRT attached
-(II) NV(0): Using CRT on CRTC 0
+(--) NV(0): CRTC 1 appears to have a CRT attached
+(II) NV(0): Using CRT on CRTC 1
 (II) NV(0): Using hsync ranges from config file
 (II) NV(0): Using vrefresh ranges from config file
 (II) NV(0): Printing DDC gathered Modelines:

In summary for some reason when the "nv" driver fails it seems it fails
at "Probing for analog device on output A". Also, it seems that when it
fails, it think it must use CRTC 1. I only have one monitor attached to
the video card. I don't know what this means.

Is there anything else I can do? Do you want me to try one instrumented
"nv" driver you can give me?

thanks


** Attachment added: "nvafternvbad"
   http://librarian.launchpad.net/7176573/nvafternvbad

-- 
xorg won't start on nvida 6600 card due to nv driver not supporting 6600's
https://bugs.launchpad.net/bugs/102683
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to