Hide Forgot
Description of problem: Choosing one of the rss-glx modules in the "gnome-screensaver" preferences and clicking the "Preview" button makes a mouse cursor appear in front of a white background - no screensaver is visible though. Hitting a key or clicking the left mouse button has no effect. The screen is actually blocked. Version-Release number of selected component (if applicable): rss-glx-gnome-screensaver-0.8.1.p-3.fc6 How reproducible: Always. Steps to Reproduce: 1. Open "gnome-screensaver" preferences. 2. Choose an "rss-glx" module. 3. Click "Preview" button. Actual results: Screen turns white. It is possible to move the mouse cursor but it's impossible to exit the preview mode gracefully. Expected results: Screensaver should set in and exit upon mouse click or keystroke. Additional info: The screensaver module correctly renders the small preview window in the preferences window but not full-screen.
Seems to be driver issue ("xorg-x11-drv-savage") since on my desktop system with a "Radeon 7200" graphics card, everything works correctly.
*** Bug 195854 has been marked as a duplicate of this bug. ***
After commenting out 'Load "dri"' in "xorg.conf" and restarting the "X" server, the screensaver behaves correctly. Moreover, "glxgears", which otherwise only displays a black window, works again, albeit at an (expected) slow frame rate.
glxgears displaying a black window with DRI enabled is a good indicator for a problem in the driver (IMO).
I had also posted bug #196011 which might be of potential interest and which is related to an issue with "xscreensaver-gl-extras".
I have submitted a patch derived from A. Deucher's suggestion at: https://bugs.freedesktop.org/show_bug.cgi?id=6357 . The Fedora patch can be found here: https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=136548 . It fixes both bug 196011 and bug 195851.
According to the author of the patch, it has been committed upstream: https://bugs.freedesktop.org/show_bug.cgi?id=6357#c30
Updating summary to remind me to take care of this.
Caveat: I have rebuilt the "xorg-x11-drv-savage" package again, this time using a pristine copy of the current "git" tree of the "savage" driver, including the "DRI locking" fix and it turns out that direct rendering is not working anymore. "env LIBGL_DEBUG=verbose glxgears" now reports: ... libGL error: drmMap of framebuffer failed (Invalid argument) libGL error: reverting to (slow) indirect rendering ... So, the task is possibly not as straightforward as one might have thought.
A rather soonish update of the driver by adding the patch submitted above would be highly welcome, as it might also be beneficial for users affected by bug 206710.
(In reply to comment #9) After updating the "savage" driver "RPM" to version "2.1.12" from "Xorg 7.2 RC2" and dropping all patches, one still gets the "drmMap" error message from comment #9. Btw, "Xorg.0.log" has a: (II) SAVAGE(0): Direct rendering enabled so it's rather a "GL" problem. Reverting to "2.1.11" plus A. Deucher's "DRI" patch from comment #6.
The "drmMap" issue of the 2.1.2 driver release has already been reported upstream, see: https://bugs.freedesktop.org/show_bug.cgi?id=8800
The current "rawhide" kernel "2.6.19-1.2911.fc7" still does not have the upstream "DRM" version required to make the "2.1.2" driver of "Xorg 7.2 RC3" work. This suggests to fix settle the issue preliminary according to the procedure outlined in comment #6. The inclusion of the relevant patch [level "easy fix"] has been pending for almost 4 months now (!).
The failure reported in comment #9 still applies to the combination of "kernel-2.6.19-1.2917.fc7" and "xorg-x11-drv-savage-2.1.2-1.fc7".
The failure reported in comment #9 still applies to the combination of "kernel-2.6.20-1.2932.fc7" and "xorg-x11-drv-savage-2.1.2-2.fc7".
This bug is probably no valid anymore: nowadays, it only affects "FC6" [see bug 229979], since the "devel" tree has moved to "Xorg 7.2" and "savage" driver version 2.1.2 which already includes the patch mentioned above. Hardware rendering does not work at all anymore due to a mismatch between the current kernel "DRM" and the one required by the 2.1.2 driver, but this is a kernel issue that I have reported upstream at: http://bugzilla.kernel.org/show_bug.cgi?id=7767 . Therefore closing this bug for "Fedora development".
Direct rendering for driver version 2.1.2 finally working correctly with kernel version "2.6.21-1.3199.fc8".