Bug 480025
| Summary: | NVIDIA Quadro FX570/FX1700 lose sync on RHEL5U2 and RHEL5U3 Snap5. | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Alan Matsuoka <alanm> | ||||||||||
| Component: | xorg-x11-drv-nv | Assignee: | Adam Jackson <ajax> | ||||||||||
| Status: | CLOSED ERRATA | QA Contact: | desktop-bugs <desktop-bugs> | ||||||||||
| Severity: | high | Docs Contact: | |||||||||||
| Priority: | high | ||||||||||||
| Version: | 5.3 | CC: | cmeadors, cward, jkachuck, mgordon, rdoty, tao, xgl-maint | ||||||||||
| Target Milestone: | rc | ||||||||||||
| Target Release: | 5.4 | ||||||||||||
| Hardware: | All | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: |
NVIDIA Quadro FX 570 and Quadro FX 1700 graphics cards obtain modetimings from the X server for mode validation ("native modesetting"). Previously, xorg-x11-drv-nv did not support native modesetting, and therefore would not work with these cards. With native modesetting supported in xorg-x11-drv-nv, this driver now works with Quadro FX 570 and Quadro FX 1700 graphics cards.
|
Story Points: | --- | ||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2009-09-02 11:11:00 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: | |||||||||||||
| Bug Depends On: | |||||||||||||
| Bug Blocks: | 441909, 483784 | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Alan Matsuoka
2009-01-14 16:21:21 UTC
Created attachment 329018 [details]
syslog
Created attachment 329019 [details]
X.log
Created attachment 329020 [details]
XConfig.test
Hello, This is a note on this issue sent by NVIDIA Engineering: On RH5U2 64b we see a monitor out of range issue with fx570 and fx1700 during x install. Thanks to Andy R for the following summary: - the version of the nv driver which RH backported to RHEL 5.2 completely relies on the mode validation of the core X.org X server in order to get correct modetimings (this is so-called "native modesetting"), as opposed to the modesetting code in the pre-g80 nv driver, which always uses the modetimings which the VBIOS selected at POST time - when we implemented support for this in the nv driver, the X.org server version which the nv driver was implemented against had correct mode validation support, such that native modesetting works properly - for the nv driver to work on this GPU, RH would need to backport the appropriate mode validation fixes in the core X.org X server; RH's X server engineers are much more familiar with the X server's mode validation code than we are, so they will know better than NVIDIA what changes are needed We believe this problem would be present in any open source X driver that uses "native modesetting". We do not know, off hand, if any other X driver backported to RHEL 5.2 takes advantage of native modesetting. Certainly, most of the actively developed X drivers in top of tree X.org use native modesetting. This event sent from IssueTracker by jkachuck issue 255851 Did this work on RHEL 5.2? If so, it should be classified as a regression. Sending old note up to engineering: ------- Comment From ericli.com 2009-01-17 01:21 EDT------- Hi I uploaded sosreport result file, sosreport-localhost-484249-b95119.tar.bz2. I do not think this is a regression issue. This issue also happens on RHEL5.2 and RHEL5.3 RC2. Many thanks. This event sent from IssueTracker by jkachuck issue 255851 This is actually using VESA driver, not NV. Per initial comment 8 (comment 8 in comment 1...), it appears that VESA works but that NV doesn't. Can someone confirm? This is occuring with the NV driver, not the VESA driver. (In reply to comment #9) > This is occuring with the NV driver, not the VESA driver. Attachment 329019 [details] in the comment 2 is from VESA driver. Hello, My understanding is this is may be due to using the VESA module, and not the NV module. The issue is the NV module is also missing appropriate mode validation fixes in the core X.org X server. So the request is to correct the NV module so the VESA module would not be needed. IBM or NVIDIA please comment if this is an incorrect explanation of the current issue. Thank You Joe Kachuck The G80+ code in the nv driver in RHEL5 does use the new modesetting code from upstream. We're quite likely to update that for 5.4, so. Moving to nv component. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. Reporter: Can we get an X log from attempting to run X with the nv driver on this hardware? The driver does claim to support this PCI ID, so I'm curious whether it's just a mode validation failure or something more subtle. ------- Comment From ericli.com 2009-05-05 01:31 EDT------- Hello It can not get an X log from attempting to run X with the nv driver during installing RHEL5.3. The screen went black after loading vmlinuz and initrd.img. Thanks. This event sent from IssueTracker by jkachuck issue 255851 It is not necessary to get an X log from install time. Installing in text mode and running X from the installed system will provide an equivalent X log. Interesting. X log looks quite sane. Does X actually come up and display in that run, or does it fail in the same way as in the installer? ~~ Attention - RHEL 5.4 Beta Released! ~~ RHEL 5.4 Beta has been released! There should be a fix present in the Beta release that addresses this particular request. Please test and report back results here, at your earliest convenience. RHEL 5.4 General Availability release is just around the corner! If you encounter any issues while testing Beta, please describe the issues you have encountered and set the bug into NEED_INFO. If you encounter new issues, please clone this bug to open a new issue and request it be reviewed for inclusion in RHEL 5.4 or a later update, if it is not of urgent severity. Please do not flip the bug status to VERIFIED. Only post your verification results, and if available, update Verified field with the appropriate value. Questions can be posted to this bug or your customer or partner representative.
Release note added. If any revisions are required, please set the
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.
New Contents:
NVIDIA Quadro FX 570 and Quadro FX 1700 graphics cards obtain modetimings from the X server for mode validation ("native modesetting"). Previously, xorg-x11-drv-nv did not support native modesetting, and therefore would not work with these cards. With native modesetting supported in xorg-x11-drv-nv, this driver now works with Quadro FX 570 and Quadro FX 1700 graphics cards.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-1342.html |