Unfortunately this new driver did not fix the problem. The problem is still there and there is no behavior change with this new driver.
This new driver work only ONCE and it's when it's used IMMEDIATELY after the proprietary nVidia driver from the company nVidia.
In all other circumstance it fails like described above.
I proved I installed the driver like this;
$ dpkg -i xserver-xorg-video-nv_2.0.0-0ubuntu3.1_i386.deb
I proved I used this new driver;
$ diff /usr/lib/xorg/modules/drivers/nv_drv.so nv_drv.so.bak
Binary files /usr/lib/xorg/modules/drivers/nv_drv.so and nv_drv.so.bak differ
The diff below shows the /var/log/Xorg.0.log difference when the new "nv" driver worked after being invoked after nVidia proprietary driver ran (attached file: Xorg.0.log_nvafternvidia.txt). The other file is after "nv" was relaunched after "nv" ran once, in this scenario the "nv" didn't found the Analog device port A and found the wrong CRTC (attached file: Xorg.0.log_nvafternv.txt).
You can see that the file Xorg.0.log_nvafternv.txt is showing you that the driver failed to find "analog device on output A" and it was mistaken by finding there was a monitor CRTC 1. I have only one monitor attached to port 0 as it's detected when "nv" had detected when it worked (after running after nvidia driver). When "nv" ran without problem it found "analog device on output A" and found monitor 0 "Using CRT on CRTC 0".
$ diff -Nur Xorg.0.log_nvafternvidia.txt Xorg.0.log_nvafternv.txt
--- Xorg.0.log_nvafternvidia.txt 2007-04-12 20:21:05.000000000 -0400
+++ Xorg.0.log_nvafternv.txt 2007-04-12 20:21:46.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 12 20:19:44 2007
+(==) Log file: "/var/log/Xorg.0.log", Time: Thu Apr 12 20:21:21 2007
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
@@ -428,7 +428,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...
@@ -495,8 +495,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:
@@ -848,5 +848,3 @@
Could not init font path element /usr/X11R6/lib/X11/fonts/misc, removing from list!
Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/Type1, removing from list!
-(II) Open ACPI successful (/var/run/acpid.socket)
-(II) Configured Mouse: ps2EnableDataReporting: succeeded
Unfortunately this new driver did not fix the problem. The problem is still there and there is no behavior change with this new driver.
This new driver work only ONCE and it's when it's used IMMEDIATELY after the proprietary nVidia driver from the company nVidia.
In all other circumstance it fails like described above.
I proved I installed the driver like this; xorg-video- nv_2.0. 0-0ubuntu3. 1_i386. deb
$ dpkg -i xserver-
I proved I used this new driver; xorg/modules/ drivers/ nv_drv. so nv_drv.so.bak xorg/modules/ drivers/ nv_drv. so and nv_drv.so.bak differ
$ diff /usr/lib/
Binary files /usr/lib/
The diff below shows the /var/log/Xorg.0.log difference when the new "nv" driver worked after being invoked after nVidia proprietary driver ran (attached file: Xorg.0. log_nvafternvid ia.txt) . The other file is after "nv" was relaunched after "nv" ran once, in this scenario the "nv" didn't found the Analog device port A and found the wrong CRTC (attached file: Xorg.0. log_nvafternv. txt).
You can see that the file Xorg.0. log_nvafternv. txt is showing you that the driver failed to find "analog device on output A" and it was mistaken by finding there was a monitor CRTC 1. I have only one monitor attached to port 0 as it's detected when "nv" had detected when it worked (after running after nvidia driver). When "nv" ran without problem it found "analog device on output A" and found monitor 0 "Using CRT on CRTC 0".
$ diff -Nur Xorg.0. log_nvafternvid ia.txt Xorg.0. log_nvafternv. txt log_nvafternvid ia.txt 2007-04-12 20:21:05.000000000 -0400 log_nvafternv. txt 2007-04-12 20:21:46.000000000 -0400 Xorg.0. log", Time: Thu Apr 12 20:19:44 2007 Xorg.0. log", Time: Thu Apr 12 20:21:21 2007 xorg.conf" xorg/modules/ /libddc. so lib/X11/ fonts/misc, removing from list! fonts/X11/ cyrillic, removing from list! lib/X11/ fonts/Type1, removing from list! acpid.socket) porting: succeeded
--- Xorg.0.
+++ Xorg.0.
@@ -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/
+(==) Log file: "/var/log/
(==) Using config file: "/etc/X11/
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
@@ -428,7 +428,7 @@
(II) Reloading /usr/lib/
(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...
@@ -495,8 +495,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:
@@ -848,5 +848,3 @@
Could not init font path element /usr/X11R6/
Could not init font path element /usr/share/
Could not init font path element /usr/X11R6/
-(II) Open ACPI successful (/var/run/
-(II) Configured Mouse: ps2EnableDataRe
Is there another driver you want me to test?
thanks very much
P.S. I attach the two new log files;