Bug 67934
| Summary: | nforce hardlocks with generic Geforce2 MX XFree86 driver | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Public Beta | Reporter: | Eric Hattemer <hattenator+bugzilla> | ||||
| Component: | XFree86 | Assignee: | Mike A. Harris <mharris> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | limbo | CC: | hattenator+bugzilla, wtogami | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | athlon | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2005-04-20 12:45:59 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: | |||||||
| Attachments: |
|
||||||
|
Description
Eric Hattemer
2002-07-04 14:02:59 UTC
Would it be possible for the Open Source Geforce driver to support 2D graphics on nForce? That may be ideal rather than forcing nForce to use the generic frame buffer driver. Unfortunately, the way the hardware probing works, it's not really practical to blacklist card <foo> only in combination with PCI chipset <bar>. Blacklisting would not be an ideal situation here, because nForce is a very popular chipset within many integrated Athlon motherboards sold within retail Micron and Compaq desktops. It would be really nice if the onboard Geforce2 video and ethernet controller could work "out of the box" in Red Hat with at least 2D graphics. It is not possible for Red Hat or anyone else to add support to the open source "nv" driver for any Nvidia hardware. Nvidia explicitly does not release the technical specifications for their hardware to anyone even under NDA for the development of new hardware support. Any Nvidia hardware not supported by the "nv" driver, is simply not supported. It requires Nvidia themselves to write support since they're the only ones with their technical specs for their hardware. Support in the "nv" driver for new Nvidia hardware only appears in XFree86 once Nvidia writes the support and contributes it to XFree86 CVS. Such support then will be available in XFree86 when the new release of X comes out, and will be picked up by Red Hat in a future distribution release. While I agree that having nForce boards "just work" out of the box in Red Hat Linux is an amiable goal, it is not possible for us to implement code to do such without having the technical specifications to do so. Forcing a given PCI ID to use the "vesa" driver instead of the "nv" driver merely because it doesn't work on the nForce chipset is not acceptable since many users do not use the nForce chipset. Creating blacklist/whitelists is a large undertaking and requires a lot of maintenance that is simply not worth spending the time on, when it is likely that the real problem will be fixed in XFree86 CVS in the next release, or perhaps the one after that. If the video chip itself has a unique PCI ID that can be detected, then we can do something about it, however if the ID is identical to that on boards which do not have this problem, then there is nothing we can do about it in a realistic and efficient manner. Please attach the full "lspci -n" output to the bug report for investigation. The ultimate solution, is to not purchase hardware that is unsupported, or supported only by binary only drivers. Vote with your wallet and purchase hardware which is made by companies that actively support open source. Created attachment 65025 [details]
lspci, -n, -vv
Please report this bug/issue to XFree86.org and Nvidia so that the people who have both the hardware, and the documentation for that hardware both know of the problem, and can fix it. Nobody else can. xpert / xfree86 / support I'm defering this bug until a new XFree86 release is available which hopefully the people who can actually fix this, have done so. I'll reopen it once new packages are available for testing in a future Red Hat Linux release. If you come across a bug fix patch or somesuch, please update the report to accelerate the fix. Since this bugzilla report was filed, there have been several major
updates to the X Window System, which may resolve this issue. Users
who have experienced this problem are encouraged to upgrade to the
latest version of Fedora Core, which can be obtained from:
http://fedora.redhat.com/download
If this issue turns out to still be reproduceable in the latest
version of Fedora Core, please file a bug report in the X.Org
bugzilla located at http://bugs.freedesktop.org in the "xorg"
component.
Once you've filed your bug report to X.Org, if you paste the new
bug URL here, Red Hat will continue to track the issue in the
centralized X.Org bug tracker, and will review any bug fixes that
become available for consideration in future updates.
Setting status to "CURRENTRELEASE".
|