Bug 84123
Summary: | XFree86 nv driver will not display digital interface of dell 1503 | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | Harris Landgarten <harrisl> |
Component: | XFree86 | Assignee: | Mike A. Harris <mharris> |
Status: | CLOSED DUPLICATE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | phoebe | CC: | mharris |
Target Milestone: | --- | Keywords: | MoveUpstream |
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 18:51:45 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Harris Landgarten
2003-02-12 15:28:07 UTC
Can you run 'ddcprobe' as root and paste the output to this report? We should be able to probe the 1503FP. I have a 1702FP at home that can be probed just fine. Perhaps the entries in the MonitorsDB is wrong. Ah, Mike Harris tells me that using DVI with NVidia hardware is currently unsupported. Try running ddcprobe while using the VGA connector instead of the DVI. Does that work? Videocard DDC probe results while in analog mode in gnome Description: NVidia Corporation NV15 Reference Board Memory (MB): 64 Monitor DDC probe results ID: DEL3004 Name: Dell 1503FP (Analog) Horizontal Sync (kHZ): 30-60 Vertical Sync (HZ) : 60-75 Width (mm): 300 Height(mm): 220 while in digital mode init 3 Videocard DDC probe results Description: NVidia Corporation NV15 Reference Board Memory (MB) 64 Monitor DDC probe results Monitor DDC Probe failed Ok, it looks like our database entries are more-or-less correct. The monitor returns 30-60 and 60-75. MonitorsDB says: Dell; Dell 1503FP (Analog); del3004; 31.0-60.0; 60.0-75.0; 1 Dell; Dell 1503FP (Digital); del3003; 31.0-60.0; 60.0-75.0; 1 It looks like I should change the "31" to "30". But that's not the real problem. Does running redhat-config-xfree86 with the analog connector work? It looks like probing the monitor should be correct as long as you aren't using DVI. The monitor runs X fine in analog but I changed Vert to 60-60 because 60hz is optimal. Ok, I'm glad to know that things work ok in analog mode. I'm going to transfer this bug to XFree86 since the bug is actually in the nvidia driver. mharris is probably going to close as 'wontfix' since I think that this bug is due to the lack of hardware specifications from nVidia for their cards. Please report this issue in the "nv" driver upstream to the XFree86 mailing list and bug report address: xfree86 The "nv" driver maintainer, whom works at Nvidia, reads that list and will be able to assess the problem for you, and make official comments on what the driver does and does not support. He will also be potentially able to fix the issue, or to add support if it is missing, since only Nvidia employees have access to the Nvidia hardware specifications and in depth knowledge of the Nvidia hardware. Hopefully a future release of the "nv" driver will support this, or work correctly for DVI displays. Changing bug status to UPSTREAM. I'm processing UPSTREAM flagged bug reports for upstream fixes currently, and noticed that this bug was flagged upstream but has no upstream bug URL, and I was unable to find an upstream bug report of this issue in XFree86 bugzilla located at: http://bugs.xfree86.org Closing bug report as WONTFIX as I'm unable to track upstream until a bug report has been filed upstream, and the URL provided for tracking. If this issue is still relevant in the latest XFree86 packages in rawhide, after reporting upstream at http://bugs.xfree86.org, feel free to add the bug report URL to this report and reopen if you'd like the issue to be tracked and any fixes from upstream investigated for inclusion in future Red Hat XFree86 updates. *** This bug has been marked as a duplicate of 88360 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |