Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 12-04-06, 10:57 PM   #1
alaric
Cyber Jedi
 
alaric's Avatar
 
Join Date: Aug 2003
Location: Amsterdam
Posts: 75
Default Monitor is not detected at all, and ConnectedMonitor / UseDisplayDevice do not help.

I have a CRT monitor that is not detected when connected to the DVI output of an FX5200 (using a DVI->VGA adaptor). Now you might say: then plug it into the VGA output-- but that isn't relevant imho. Moreover, I have reasons to want it to be plugged into the DVI output because I'm trying to set up some multi-monitor case. This didn't work and I've tracked down the problem to this simple case with one monitor.

What I need, for a start, is to find the options that will make this particular set up work.

From the whole Xorg.0.log file, these are therefore the relevant lines:

Code:
(WW) NVIDIA(0): No connected display devices detected; assuming 1 CRT
[...]
(II) NVIDIA(0): Assigned Display Device: CRT-0
[...]
(II) NVIDIA(0): CRT-0 assigned CRTC 0
Apparently, CRTC 0 is the VGA output, while the only monitor that I have is
connected to the DVI output. Therefore I need to convince the nvidia driver
somehow to use the DVI output anyway (instead of CRTC 0).

I'm using a very basic xorg.conf file, the relevant parts of which are:

Code:
Section "Device"
        Identifier      "FX5200_DVI"
        Driver          "nvidia"
        BusID           "PCI:1:0:0"
        Screen          0
        Option          "IgnoreDisplayDevices" "DFP, TV"
EndSection

Section "Monitor"
        Identifier      "VMP17"
        Option          "DPMS"
        HorizSync       27-96
        VertRefresh     50-160
EndSection

Section "Screen"
        Identifier      "Default Screen"
        Device          "FX5200_DVI"
        Monitor         "VMP17"
        DefaultDepth    24
        SubSection "Display"
                Depth           24
                Modes           "1024x768"
        EndSubSection
EndSection
I've tried to use the option "ConnectedMonitor" - but that doesn't
work because that only forces an already detected monitor to change
type (ie, when a CRT is detected you can force to be treated as a DFP).
When no monitor is detected at all - and you only have CRT's, then
using 'Option "ConnectedMonitor" "CRT"' doesn't help one bit: it was
already assuming that it was a CRT anyway. The chosen output is still
the VGA plug.

I've also tried to use the option "UseDisplayDevice" - but that doesn't
help either: What happens is this: first a list of available devices is constructed.
This list would either be "CRT-0, CRT-1" or "DFP-0, CRT-1" or just "CRT-0" or
"DFP-0" (a bug in the driver causes it to be "CRT-0", "DFP-0" in another attempt
of me, which is a bug because it is nonsense-- but that is not relevant for this thread).
Next - you can assign X display(s) to one of that list. In this simple case I have
obviously a single X display, and ... there is only a single device, namely "CRT-0".
So, there is nothing to assign here - and CRT-0 is still happy sending signals to the
wrong output.

Does anyone have a suggestion of how to solve this problem?
Attached Files
File Type: gz nvidia-bug-report.log.gz (20.4 KB, 100 views)
__________________
Get my email address from my homepage.
alaric is offline   Reply With Quote
Old 12-04-06, 11:04 PM   #2
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: Monitor is not detected at all, and ConnectedMonitor / UseDisplayDevice do not help.

I don't see the problem you're reporting in the bug report you attached. The CRT is detected, however its EDID is not:
(--) NVIDIA(0): --- EDID for CRT-0 ---
(--) NVIDIA(0):
(--) NVIDIA(0): No EDID Available.
(--) NVIDIA(0):
(--) NVIDIA(0): --- End of EDID for CRT-0 ---

As 1.0-8776 is no longer supported, if you need further assistance, please clarify the problem, along with a bug report against 1.0-9631 or 1.0-9742.

Thanks,
Lonni
netllama is offline   Reply With Quote
Old 12-04-06, 11:15 PM   #3
alaric
Cyber Jedi
 
alaric's Avatar
 
Join Date: Aug 2003
Location: Amsterdam
Posts: 75
Default Re: Monitor is not detected at all, and ConnectedMonitor / UseDisplayDevice do not he

Quote:
Originally Posted by netllama
I don't see the problem you're reporting in the bug report you attached. The CRT is detected, however its EDID is not:
(--) NVIDIA(0): --- EDID for CRT-0 ---
(--) NVIDIA(0):
(--) NVIDIA(0): No EDID Available.
(--) NVIDIA(0):
(--) NVIDIA(0): --- End of EDID for CRT-0 ---

As 1.0-8776 is no longer supported, if you need further assistance, please clarify the problem, along with a bug report against 1.0-9631 or 1.0-9742.

Thanks,
Lonni

I'd be happy to go through the trouble of testing this with 1.0-9631 or 1.0-9742
(I can't use your installer because that overwrites libraries - and I've already
needed to buy a new PC(!!!) as a result of that before; see http://www.nvnews.net/vbulletin/show...4&postcount=13)
but this reply is very inaccurate

The CRT is *NOT* detected. You can clearly see that in my bug report.
The part that you quote doesn't prove that any CRT is detected. The whole
problem is that the EDID doesn't work by the way - but that is not relevant
in this simple case: just assume there is no EDID available.

Obviously - with no monitor detected at all - there is no EDID.

The relevant part of the attached debug log file is:

(WW) NVIDIA(0): No connected display devices detected; assuming 1 CRT

This proves that it does not detect this monitor. After *assuming* that CRT-0
exists, it then continues (immediately) with:

(WW) NVIDIA(0): Unable to read EDID for display device CRT-0

which is fine, since it can't read EDID from a non-existent monitor.
__________________
Get my email address from my homepage.
alaric is offline   Reply With Quote
Old 12-04-06, 11:29 PM   #4
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: Monitor is not detected at all, and ConnectedMonitor / UseDisplayDevice do not help.

Sorry, you're correct, no CRTs are being detected. Have you determined whether the CRT is detected when connected to the VGA connector?

Thanks,
Lonni
netllama is offline   Reply With Quote
Old 12-05-06, 12:36 AM   #5
alaric
Cyber Jedi
 
alaric's Avatar
 
Join Date: Aug 2003
Location: Amsterdam
Posts: 75
Default Re: Monitor is not detected at all, and ConnectedMonitor / UseDisplayDevice do not he

Hiya Lonni, thanks for the fast replies.

I have done the following tests now:

1) VMP17 ---> DVI

2) VMP17 --> VGA

3) VMP410 --> DVI

Where VMP17 = "IIyama Vision Master Pro 17",
VMP410 = "IIyama Vision Master Pro 410"

The VMP17 is the one that is not detected.

The only thing that I changed between these three tests is
which monitor was connected to which output (just plugging cables just).

Using startx -- -logverbose 5 I created three output files:

1) Xorg.0.log_VMP17-DVI_NONE
2) Xorg.0.log_VMP17-VGA_NONE
3) Xorg.0.log_VMP410-DVI_NONE

Where the NONE means that the other output is not connected.
These three are attached in full. I've also attached the xorg.conf
that was used (for all three tests).

What is interesting, of course, are the diff's.
The diff between Xorg.0.log_VMP17-DVI_NONE --> org.0.log_VMP17-VGA_NONE
is:

Code:
--- Xorg.0.log_VMP17-DVI_NONE   2006-12-05 06:57:33.000000000 +0100
+++ Xorg.0.log_VMP17-VGA_NONE   2006-12-05 06:57:43.000000000 +0100
@@ -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: Tue Dec  5 06:43:28 2006
+(==) Log file: "/var/log/Xorg.0.log", Time: Tue Dec  5 06:46:00 2006
 (==) Using config file: "/etc/X11/xorg.conf"
 (==) ServerLayout "Default Layout"
 (**) |-->Screen "Default Screen" (0)
@@ -311,8 +311,6 @@
 (==) NVIDIA(0): Using HW cursor
 (**) NVIDIA(0): Enabling RENDER acceleration
 (==) NVIDIA(0): Video key set to default value of 0x101fe
-(WW) NVIDIA(0): No connected display devices detected; assuming 1 CRT
-(WW) NVIDIA(0): Unable to read EDID for display device CRT-0
 (II) NVIDIA(0): NVIDIA GPU GeForce FX 5200 at PCI:1:0:0
 (--) NVIDIA(0): VideoRAM: 131072 kBytes
 (II) NVIDIA(0): GPU Architecture: 0x30
@@ -353,172 +351,56 @@
 (II) NVIDIA(0):     Horizontal Total Width   : multiples of 8
 (II) NVIDIA(0):
 (--) NVIDIA(0): Connected display device(s) on GeForce FX 5200 at PCI:1:0:0:
-(--) NVIDIA(0):     CRT-0
-(--) NVIDIA(0): CRT-0: 350.0 MHz maximum pixel clock
+(--) NVIDIA(0):     P@@ &?0?gF (CRT-0)
+(--) NVIDIA(0): P@@ &?0?gF (CRT-0): 350.0 MHz maximum pixel clock
 (--) NVIDIA(0):
-(--) NVIDIA(0): --- EDID for CRT-0 ---
+(--) NVIDIA(0): --- EDID for P@@ &?0?gF (CRT-0) ---
+(--) NVIDIA(0): EDID Version                 : 2.0
+(--) NVIDIA(0): Manufacturer                 : P@@
+(--) NVIDIA(0): Monitor Name                 : P@@ &?0?gF
+(--) NVIDIA(0): Product ID                   : 29123
+(--) NVIDIA(0): 32-bit Serial Number         : 0
+(--) NVIDIA(0): Serial Number String         :
+(--) NVIDIA(0): Manufacture Date             : 52518, week 177
+(--) NVIDIA(0): DPMS Capabilities            :
+(--) NVIDIA(0): Prefer first detailed timing : No
+(--) NVIDIA(0): Supports GTF                 : No
+(--) NVIDIA(0): Maximum Image Size           : 0mm x 0mm
+(--) NVIDIA(0): Valid HSync Range            : 4294967 kHz - 0 kHz
+(--) NVIDIA(0): Valid VRefresh Range         : -1 Hz - 0 Hz
+(--) NVIDIA(0): EDID maximum pixel clock     : 0.0 MHz
 (--) NVIDIA(0):
-(--) NVIDIA(0): No EDID Available.
+(--) NVIDIA(0): --- End of EDID for P@@ &?0?gF (CRT-0) ---
 (--) NVIDIA(0):
-(--) NVIDIA(0): --- End of EDID for CRT-0 ---
-(--) NVIDIA(0):
-(II) NVIDIA(0): Frequency information for CRT-0:
-(II) NVIDIA(0):   HorizSync   : 27.000-96.000 kHz
-(II) NVIDIA(0):   VertRefresh : 50.000-160.000 Hz
-(II) NVIDIA(0):     (HorizSync from HorizSync in X Config Monitor section)
-(II) NVIDIA(0):     (VertRefresh from VertRefresh in X Config Monitor
-(II) NVIDIA(0):     section)
+(II) NVIDIA(0): Frequency information for P@@ &?0?gF (CRT-0):
+(II) NVIDIA(0):   HorizSync   : 4294967.000-0.000 kHz
+(II) NVIDIA(0):   VertRefresh : 4294967296.000-0.000 Hz
+(II) NVIDIA(0):     (HorizSync from EDID)
+(II) NVIDIA(0):     (VertRefresh from EDID)
 (II) NVIDIA(0):
-(II) NVIDIA(0): --- Modes in ModePool for CRT-0 ---
-(II) NVIDIA(0): "nvidia-auto-select"   : 1024 x  768 @  85.0 Hz  (from: X Server, VESA)
-(II) NVIDIA(0): "2048x1536"            : 2048 x 1536 @  60.0 Hz  (from: X Server)
[...cut mode pool..]
-(II) NVIDIA(0): --- End of ModePool for CRT-0: ---
+(II) NVIDIA(0): --- Modes in ModePool for P@@ &?0?gF (CRT-0) ---
+(II) NVIDIA(0): "nvidia-auto-select"   :  800 x  600 @  60.3 Hz  (from: NVIDIA Predefined)
+(II) NVIDIA(0): --- End of ModePool for P@@ &?0?gF (CRT-0): ---
 (II) NVIDIA(0):
 (II) NVIDIA(0): Assigned Display Device: CRT-0
 (II) NVIDIA(0): Requested modes:
 (II) NVIDIA(0):     "1024x768"
+(WW) NVIDIA(0): No valid modes for "1024x768"; removing.
+(WW) NVIDIA(0):
+(WW) NVIDIA(0): Unable to validate any modes; falling back to the default mode
+(WW) NVIDIA(0):     "nvidia-auto-select".
+(WW) NVIDIA(0):
 (II) NVIDIA(0): Validated modes:
-(II) NVIDIA(0): MetaMode "1024x768":
-(II) NVIDIA(0):     Bounding Box: [0, 0, 1024, 768]
-(II) NVIDIA(0):     CRT-0: "1024x768"
-(II) NVIDIA(0):         Size          : 1024 x 768
+(II) NVIDIA(0): MetaMode "nvidia-auto-select":
+(II) NVIDIA(0):     Bounding Box: [0, 0, 800, 600]
+(II) NVIDIA(0):     P@@ &?0?gF (CRT-0): "nvidia-auto-select"
+(II) NVIDIA(0):         Size          : 800 x 600
 (II) NVIDIA(0):         Offset        : +0 +0
-(II) NVIDIA(0):         Panning Domain: @ 1024 x 768
-(II) NVIDIA(0):         Position      : [0, 0, 1024, 768]
-(II) NVIDIA(0): Virtual screen size determined to be 1024 x 768
-(WW) NVIDIA(0): Unable to get display device CRT-0's EDID; cannot compute DPI
-(WW) NVIDIA(0):     from EDID.
+(II) NVIDIA(0):         Panning Domain: @ 800 x 600
+(II) NVIDIA(0):         Position      : [0, 0, 800, 600]
+(II) NVIDIA(0): Virtual screen size determined to be 800 x 600
+(WW) NVIDIA(0): No size information available in CRT-0's EDID; cannot compute
+(WW) NVIDIA(0):     DPI from EDID.
 (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
 (--) Depth 24 pixmap format is 32 bpp
 (II) do I need RAC?  No, I don't.
@@ -551,7 +433,7 @@
 (II) NVIDIA(0): kernel module enabled successfully
 (II) NVIDIA(0): Memory mapped
 (II) NVIDIA(0): Interrupts enabled
-(II) NVIDIA(0): Setting mode "1024x768"
+(II) NVIDIA(0): Setting mode "nvidia-auto-select"
 (II) NVIDIA(0): CRT-0 assigned CRTC 0
 (II) NVIDIA(0): First mode initialized
 (II) Loading extension NV-GLX
The only really relevant part here is:

-(WW) NVIDIA(0): No connected display devices detected; assuming 1 CRT

meaning that it is detected when connected to the VGA plug.
However, most interesting is that the EDID from it is garbled (it is not noise,
the output is 100% reproducable). Because the monitor is connected to
the VGA plug - garbled or not - the result is assigned to CRT-0.

Note that *-0 is the VGA plug, and *-1 is the DVI plug.

Next, the diff between Xorg.0.log_VMP17-DVI_NONE --> Xorg.0.log_VMP410-DVI_NONE:

Code:
--- Xorg.0.log_VMP17-DVI_NONE   2006-12-05 06:57:33.000000000 +0100
+++ Xorg.0.log_VMP410-DVI_NONE  2006-12-05 06:57:53.000000000 +0100
@@ -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: Tue Dec  5 06:43:28 2006
+(==) Log file: "/var/log/Xorg.0.log", Time: Tue Dec  5 06:44:27 2006
 (==) Using config file: "/etc/X11/xorg.conf"
 (==) ServerLayout "Default Layout"
 (**) |-->Screen "Default Screen" (0)
@@ -311,8 +311,7 @@
 (==) NVIDIA(0): Using HW cursor
 (**) NVIDIA(0): Enabling RENDER acceleration
 (==) NVIDIA(0): Video key set to default value of 0x101fe
-(WW) NVIDIA(0): No connected display devices detected; assuming 1 CRT
-(WW) NVIDIA(0): Unable to read EDID for display device CRT-0
+(WW) NVIDIA(0): Unable to read EDID for display device CRT-1
 (II) NVIDIA(0): NVIDIA GPU GeForce FX 5200 at PCI:1:0:0
 (--) NVIDIA(0): VideoRAM: 131072 kBytes
 (II) NVIDIA(0): GPU Architecture: 0x30
@@ -353,23 +352,23 @@
 (II) NVIDIA(0):     Horizontal Total Width   : multiples of 8
 (II) NVIDIA(0):
 (--) NVIDIA(0): Connected display device(s) on GeForce FX 5200 at PCI:1:0:0:
-(--) NVIDIA(0):     CRT-0
-(--) NVIDIA(0): CRT-0: 350.0 MHz maximum pixel clock
+(--) NVIDIA(0):     CRT-1
+(--) NVIDIA(0): CRT-1: 350.0 MHz maximum pixel clock
 (--) NVIDIA(0):
-(--) NVIDIA(0): --- EDID for CRT-0 ---
+(--) NVIDIA(0): --- EDID for CRT-1 ---
 (--) NVIDIA(0):
 (--) NVIDIA(0): No EDID Available.
 (--) NVIDIA(0):
-(--) NVIDIA(0): --- End of EDID for CRT-0 ---
+(--) NVIDIA(0): --- End of EDID for CRT-1 ---
 (--) NVIDIA(0):
-(II) NVIDIA(0): Frequency information for CRT-0:
+(II) NVIDIA(0): Frequency information for CRT-1:
 (II) NVIDIA(0):   HorizSync   : 27.000-96.000 kHz
 (II) NVIDIA(0):   VertRefresh : 50.000-160.000 Hz
 (II) NVIDIA(0):     (HorizSync from HorizSync in X Config Monitor section)
 (II) NVIDIA(0):     (VertRefresh from VertRefresh in X Config Monitor
 (II) NVIDIA(0):     section)
 (II) NVIDIA(0):
-(II) NVIDIA(0): --- Modes in ModePool for CRT-0 ---
+(II) NVIDIA(0): --- Modes in ModePool for CRT-1 ---
 (II) NVIDIA(0): "nvidia-auto-select"   : 1024 x  768 @  85.0 Hz  (from: X Server, VESA)
 (II) NVIDIA(0): "2048x1536"            : 2048 x 1536 @  60.0 Hz  (from: X Server)
 (II) NVIDIA(0): "2048x1536_60"         : 2048 x 1536 @  60.0 Hz  (from: X Server)
@@ -503,21 +502,21 @@
 (II) NVIDIA(0): "320x200d85"           :  320 x  200 @  85.3 Hz DoubleScan  (from: X Server)
 (II) NVIDIA(0): "320x175"              :  320 x  175 @  85.3 Hz DoubleScan  (from: X Server)
 (II) NVIDIA(0): "320x175d85"           :  320 x  175 @  85.3 Hz DoubleScan  (from: X Server)
-(II) NVIDIA(0): --- End of ModePool for CRT-0: ---
+(II) NVIDIA(0): --- End of ModePool for CRT-1: ---
 (II) NVIDIA(0):
-(II) NVIDIA(0): Assigned Display Device: CRT-0
+(II) NVIDIA(0): Assigned Display Device: CRT-1
 (II) NVIDIA(0): Requested modes:
 (II) NVIDIA(0):     "1024x768"
 (II) NVIDIA(0): Validated modes:
 (II) NVIDIA(0): MetaMode "1024x768":
 (II) NVIDIA(0):     Bounding Box: [0, 0, 1024, 768]
-(II) NVIDIA(0):     CRT-0: "1024x768"
+(II) NVIDIA(0):     CRT-1: "1024x768"
 (II) NVIDIA(0):         Size          : 1024 x 768
 (II) NVIDIA(0):         Offset        : +0 +0
 (II) NVIDIA(0):         Panning Domain: @ 1024 x 768
 (II) NVIDIA(0):         Position      : [0, 0, 1024, 768]
 (II) NVIDIA(0): Virtual screen size determined to be 1024 x 768
-(WW) NVIDIA(0): Unable to get display device CRT-0's EDID; cannot compute DPI
+(WW) NVIDIA(0): Unable to get display device CRT-1's EDID; cannot compute DPI
 (WW) NVIDIA(0):     from EDID.
 (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
 (--) Depth 24 pixmap format is 32 bpp
@@ -552,7 +551,7 @@
 (II) NVIDIA(0): Memory mapped
 (II) NVIDIA(0): Interrupts enabled
 (II) NVIDIA(0): Setting mode "1024x768"
-(II) NVIDIA(0): CRT-0 assigned CRTC 0
+(II) NVIDIA(0): CRT-1 assigned CRTC 1
 (II) NVIDIA(0): First mode initialized
 (II) Loading extension NV-GLX
 (II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
where the only really interesting thing is:

-(WW) NVIDIA(0): No connected display devices detected; assuming 1 CRT
-(WW) NVIDIA(0): Unable to read EDID for display device CRT-0
+(WW) NVIDIA(0): Unable to read EDID for display device CRT-1

which means that the Vision Master Pro410 *is* detected while on the
DVI plug. Moreover, no garbled EDID is read: it is correctly(?) detected
that there is no EDID.

Finally, one more interesting case.
If I remove the
Code:
Option "IgnoreDisplayDevices" "DFP, TV"
from the xorg.conf, and connect the VMP17 to the DVI output,
the result is that (attached as Xorg.0.log_VMP17-DVI_NONE_2):

1) The monitor is detected.
2) Garbled EDID is read as before, but
3) The monitor is assigned to DFP-0 !?!

This, imho is a real bug. If it is detected then it should have
assigned to either CRT-1 or DFP-1. DFP-0 doesn't even exist
(*-0 is the VGA plug)!

Knowing the closed source code, do you have any idea how this
can happen? Is it possible that this is caused by the garbled EDID so
that we can concentrate entirely on that fact?

PS This exact same monitor and card had a working EDID in the
past with a much older nvidia driver. I have reported this when things
started to go wrong for me but never got a reply from an nvidia employee
on that. I started to use a work around with Options to entirely disable
the results of the EDID and manually feed it the needed info. I'd still
like to work with you on fixing this, of course.
Attached Files
File Type: txt Xorg.0.log_VMP17-DVI_NONE.txt (33.2 KB, 111 views)
File Type: txt Xorg.0.log_VMP17-VGA_NONE.txt (22.5 KB, 105 views)
File Type: txt Xorg.0.log_VMP410-DVI_NONE.txt (33.1 KB, 94 views)
File Type: txt xorg.conf.txt (2.6 KB, 127 views)
File Type: txt Xorg.0.log_VMP17-DVI_NONE_2.txt (22.7 KB, 102 views)
__________________
Get my email address from my homepage.
alaric is offline   Reply With Quote
Old 12-05-06, 12:43 AM   #6
alaric
Cyber Jedi
 
alaric's Avatar
 
Join Date: Aug 2003
Location: Amsterdam
Posts: 75
Default Re: Monitor is not detected at all, and ConnectedMonitor / UseDisplayDevice do not he

As it is 7:40 AM here now, I have to go to bed.
I'm looking forward to your reply when I wake up (about 3 PM), at which
point I will have all day (~ 15 hours) to debug this

Good night,
Alaric
__________________
Get my email address from my homepage.
alaric is offline   Reply With Quote
Old 12-05-06, 10:57 AM   #7
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: Monitor is not detected at all, and ConnectedMonitor / UseDisplayDevice do not help.

I'm afraid that its not clear to me from your response whether the IIyama Vision Master Pro 17 is detected when connected to the VGA connector.

Please perform the following:
0) Attach the IIyama Vision Master Pro 17 to the (primary) VGA connector
1) As root, run:
mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup
nvidia-xconfig
startx -- -logverbose 5
nvidia-bug-report.sh

And then attach the resulting bug report.

Thanks,
Lonni
netllama is offline   Reply With Quote
Old 12-05-06, 05:56 PM   #8
alaric
Cyber Jedi
 
alaric's Avatar
 
Join Date: Aug 2003
Location: Amsterdam
Posts: 75
Default Re: Monitor is not detected at all, and ConnectedMonitor / UseDisplayDevice do not he

Hmm, I wrote
Quote:
The only really relevant part here is:

-(WW) NVIDIA(0): No connected display devices detected; assuming 1 CRT

meaning that it is detected when connected to the VGA plug.
Nevertheless, I did what you asked
I'm afraid there really is no significant difference with
the Xorg.0.log_VMP17-VGA_NONE.txt that I attached
in my previous post: it's detected and the EDID is garbled.

Can you please answer my previous question?

Quote:
1) The monitor is detected.
2) Garbled EDID is read as before, but
3) The monitor is assigned to DFP-0 !?!

This, imho is a real bug. If it is detected then it should have
assigned to either CRT-1 or DFP-1. DFP-0 doesn't even exist
(*-0 is the VGA plug)!

Knowing the closed source code, do you have any idea how this
can happen? Is it possible that this is caused by the garbled EDID so
that we can concentrate entirely on that fact?
Attached Files
File Type: gz nvidia-bug-report.log.gz (18.9 KB, 99 views)
__________________
Get my email address from my homepage.
alaric is offline   Reply With Quote

Old 12-05-06, 06:09 PM   #9
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: Monitor is not detected at all, and ConnectedMonitor / UseDisplayDevice do not help.

Yes, the EDID is garbled in the latest bug report. That plus the fact that the CRT isn't even detected when plugged into the DVI connector leads me to wonder whether the VGA cable or the CRT itself is faulty.

Was anything displayed on the CRT after starting X in the last experiment?

Does the behavior change with 1.0-9631 or 1.0-9742?

Thanks,
Lonni
netllama is offline   Reply With Quote
Old 12-05-06, 06:20 PM   #10
alaric
Cyber Jedi
 
alaric's Avatar
 
Join Date: Aug 2003
Location: Amsterdam
Posts: 75
Default Re: Monitor is not detected at all, and ConnectedMonitor / UseDisplayDevice do not he

Yes, X started in 800x600@60 Hz. I'm working in that now

It is not the cable or the monitor.

For a start, I get the exact same results (down to the bit) with
another cable. But MUCH more important is this (as I already
said before - but you seem to read rather diagonal )

IMPORTANT:

1) This EXACT same set up (cable + monitor + card) did have a working EDID in the past.

2) The EDID broke as a result of an nvidia driver upgrade. If you want I can find back which driver worked last for me.

3) Directly after upgrading the driver (that resulted in the garbled EDID) I have switched back and forward between the old and new driver: the old driver consistently worked, the new driver consistently gives the EXACT SAME EDID output (garbled).

4) The garbled EDID is NOT random. It is reproduced 100%.

5) In a verbose log level 6 (I think) you can see the RAW EDID output from the monitor. This raw data was still the same with the new driver as it was with the old driver. This led me, of course, to the conclusion that the new driver was broken.

6) I reported this to nvidia - never got a reply.

I also wrote before, in this thread, that I'm still more than willing to work together with you to find and fix this particular bug.

Regards,
Alaric
__________________
Get my email address from my homepage.
alaric is offline   Reply With Quote
Old 12-05-06, 06:26 PM   #11
alaric
Cyber Jedi
 
alaric's Avatar
 
Join Date: Aug 2003
Location: Amsterdam
Posts: 75
Default Re: Monitor is not detected at all, and ConnectedMonitor / UseDisplayDevice do not he

Quote:
Originally Posted by netllama
Does the behavior change with 1.0-9631 or 1.0-9742?
I have been working this all day (10 hours now). It is not
very easy to create debian packages for those versions,
and I refuse to install the drivers in another way. Moreover,
I am automating it (writing a script) and writing a HOWTO
about how I do this that I'll put on the web (so, it's not
as fast as a quick hack would be).

Anyone interested, preliminary results can be found here
(the script already does a lot more than the text says):
http://www.xs4all.nl/~carlo17/howto/nvidia.html
__________________
Get my email address from my homepage.
alaric is offline   Reply With Quote
Old 12-05-06, 06:36 PM   #12
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: Monitor is not detected at all, and ConnectedMonitor / UseDisplayDevice do not help.

Yes, I'd like to know the last driver where this broken EDID issue did not exist.

However, what is more important right now is whether the problem persists in 1.0-9631 or 1.0-9742. How you install those versions is up to you.

Thanks,
Lonni
netllama is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 11:14 AM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.