Bug 134238
Summary: | DRI missing from XFree86-4.3.0-62 to XFree86-4.3.0-68 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | John Bullock <jbullock> |
Component: | XFree86 | Assignee: | X/OpenGL Maintenance List <xgl-maint> |
Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-10-05 11:32:18 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
John Bullock
2004-09-30 14:54:04 UTC
Nvidia's drivers overwrite XFree86 supplied X server modules with custom proprietary modules specific to their hardware, however they are not installed properly via rpm, so this causes an rpm inconsistency. Later, if you upgrade XFree86, it will put the XFree86 supplied module back. In this case, it is the GLX module (libglx.a) which gets overwritten. Since the XFree86 supplied GLX module is for DRI, when you try to run OpenGL applications under the proprietary Nvidia driver, this will cause the XFree86 GLX to be opened, which then attempts to use the DRI extension, however the proprietary Nvidia driver uses it's own proprietary interface which requires Nvidia's proprietary GLX, so you see this error message. The solution to this problem, is to either use Nvidia proprietary drivers in rpm package format, such as those available from livna.org, or to just reinstall the proprietary driver every time you upgrade XFree86, which will cause the Nvidia GLX to be reinstalled. If you require further assistance, please contact the hardware vendor for technical support. Setting status to "NOTABUG" (this is a common proprietary driver installation and configuration issue) |