Bug 229979
Summary: | Update Savage driver to fix DRI hang | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Joachim Frieben <jfrieben> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 6 | CC: | extras-qa, mcepl, nphilipp, xgl-maint |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-10-20 19:47:39 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
Joachim Frieben
2007-02-25 12:04:49 UTC
Still broken for "FC6" due to missing update of "xorg-x11-drv-savage" by adding the "fodoraized" patch submitted at: https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=136548 Hi Ajax, could you be somewhat more specific about why this bug report got closed as "NOTABUG"? There were several issues with "Xorg 7.1" such as black "glxgears" windows, non-functional screensavers, etc. A. Deucher's patch actually managed to make things work correctly. Moreover, it has been included upstream in version 2.1.2 of the "savage" driver. I can only wonder how this issue can be judged to be -no- bug then .. ? Ajax, is totally innocent in this -- this was mistake by me, desktop team bugmaster. Sorry, the bug is alive and kicking again. xorg-x11-drv-savage-2.1.2-3.fc6 has been pushed for fc6, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report. (In reply to comment #4) Update "xorg-x11-drv-savage-2.1.2-3.fc6" from "Fedora Test Updates" was doomed to fail, as I had already reported above that driver version "2.1.2" is -incompatible- with the currrent kernel "DRM". Therefore, after the update, the error message: "libGL error: drmMap of framebuffer failed (Invalid argument) libGL error: reverting to (slow) indirect rendering" pops up when launching "glxgears" which does not really come as a surprise. Again, please consider my request from comment #1. "Why" do you put "quote" marks around "arbitrary" words? Sounds like the remainder of this bug is a kernel issue, so, reassigning. Quote(In reply to comment #6) > "Why" do you put "quote" marks around "arbitrary" words? > >Sounds like the remainder of this bug is a kernel issue, so, reassigning. Well, I do like quoting proper names or citations [when suitable] but not ordinary nouns [e.g. when reporting an error message] because I find text more readable. What is so so uncommon or arbitrary about this? You see: there is not a single quote in my reply ... ;o) Btw, assigning the bug to the kernel maintainers is not a good idea and rather suitable for the "rawhide" package. For the latter, bug 195851 is more appropriate because it already targets the development tree [needs to be reopened though]. I had reported the kernel issue upstream at http://bugzilla.kernel.org/show_bug.cgi?id=7767 , and I hope it will be fixed sometime soon. *This* bug report is about "FC6" and a *different* issue. If I remember correctly, the corresponding "Xorg" release is 7.1.1 whereas driver version 2.1.2 is part of "Xorg" release 7.2. The correct driver version is 2.1.1 and this one actually *is* compatible with the currrent "FC6" kernels. It would thus simply suffice to answer my prayers and incorporate A. Deucher's patch that I had attached above more than half a year ago. I cannot understand this obstinate refusal to make the "savage" work again when such an easy fix [in terms of investment] has been available for ages! (In reply to comment #7) > Btw, assigning the bug to the kernel maintainers is not a good idea and rather > suitable for the "rawhide" package. For the latter, bug 195851 is more > appropriate because it already targets the development tree [needs to be > reopened though]. I had reported the kernel issue upstream at > > http://bugzilla.kernel.org/show_bug.cgi?id=7767 , > > and I hope it will be fixed sometime soon. *This* bug report is about "FC6" > and a *different* issue. If I remember correctly, the corresponding "Xorg" > release is 7.1.1 whereas driver version 2.1.2 is part of "Xorg" release 7.2. > The correct driver version is 2.1.1 and this one actually *is* compatible with > the currrent "FC6" kernels. It would thus simply suffice to answer my prayers > and incorporate A. Deucher's patch that I had attached above more than half a > year ago. I cannot understand this obstinate refusal to make the "savage" work > again when such an easy fix [in terms of investment] has been available for > ages! What are you going on about? That patch is already included in savage 2.1.2. The patch is included in 2.1.2 but for this version the "DRM" interface is known to be busted or at least is doesn't play correctly with current kernels [see above]. Before the update, accelerated "OpenGL" was at least working partially for "FC6" - now it's completely broken. What is the point of updating a package, when it's already known in advance that it won't work by the time it gets released? For A. Deucher's patch it was confirmed half a year ago, that it actually works. I have mailed my patched package to several users who requested it, and they were all happy. To summarize: (1) The direct rendering capability of "xorg-x11-drv-savage-2.1.1-5.fc6" is affected by an issue solved by A. Deucher's patch which I had attached above on 2006-09-18. (2) Package "xorg-x11-drv-savage-2.1.2-3.fc6" [backported from "Xorg" 7.2] incorporates this patch but it's "DRM" interface is incompatible with the current kernel "DRM". I had reported this fact above on 2006-09-21. This issue applies both to the "Fedora" development tree and "FC6" making driver version 2.1.2 even more useless than 2.1.1. (3) I had reported the "DRM" issue upstream at http://bugzilla.kernel.org/show_bug.cgi?id=7767, and it's completely unclear when the kernel tree might get an update to solve this issue. Still, such a future kernel would have to make its way into "FC6" yet. Under these circumstances, updating the "savage" driver to version 2.1.2 for "FC6" is quite audacious. It has introduced a new issue, and the result is negative as expected ["..libGL error: drmMap of framebuffer failed .."]. Fixed in "xorg-x11-drv-savage-2.1.2-3.fc6" and recent kernels with updated "DRM". |