Package: xserver-xorg-video-savage
Version: 1:2.0.2.3-4
Severity: wishlist
Tags: patch
Getting DRI working with the Savage driver in this package is not
documented very well. The main problem I had was that I had not
installed libgl1-mesa-dri, which contains savage_dri.so that is
necessary for DRI acceleration. I would like to add a Suggests: on this
package to control, and I have also documented how to debug these
problems in a new README.Debian for this package. Please could you
consider adding this to the package?
I haven't made libgl1-mesa-dri a Recommends: because it is quite a large
package, and xserver-xorg-video-savage is often installed on machines
where it is not needed.
Chris
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-k7
Locale: LANG=en_GB, [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages xserver-xorg-video-savage depends on:
ii libc6 2.3.6-13 GNU C Library: Shared libraries
ii xserver-xorg-core 1:1.0.2-8.1 X.Org X server -- core server
xserver-xorg-video-savage recommends no packages.
-- no debconf information
diff -u xserver-xorg-video-savage-2.0.2.3/debian/changelog
xserver-xorg-video-savage-2.0.2.3/debian/changelog
--- xserver-xorg-video-savage-2.0.2.3/debian/changelog
+++ xserver-xorg-video-savage-2.0.2.3/debian/changelog
@@ -1,3 +1,9 @@
+xserver-xorg-video-savage (1:2.0.2.3-4.cjh) unstable; urgency=low
+
+ * Add information about debugging 3D acceleration in README.Debian
+
+ -- Chris Halls <[EMAIL PROTECTED]> Thu, 29 Jun 2006 16:35:08 +0100
+
xserver-xorg-video-savage (1:2.0.2.3-4) unstable; urgency=low
* Upload to modular
diff -u xserver-xorg-video-savage-2.0.2.3/debian/rules
xserver-xorg-video-savage-2.0.2.3/debian/rules
--- xserver-xorg-video-savage-2.0.2.3/debian/rules
+++ xserver-xorg-video-savage-2.0.2.3/debian/rules
@@ -70,7 +70,7 @@
dh_testdir
dh_testroot
- dh_installdocs
+ dh_installdocs debian/README.Debian
dh_installchangelogs
dh_install --sourcedir=debian/tmp
dh_link
diff -u xserver-xorg-video-savage-2.0.2.3/debian/control
xserver-xorg-video-savage-2.0.2.3/debian/control
--- xserver-xorg-video-savage-2.0.2.3/debian/control
+++ xserver-xorg-video-savage-2.0.2.3/debian/control
@@ -11,6 +11,7 @@
Depends: ${shlibs:Depends}, ${misc:Depends}, xserver-xorg-core (>= 1:0.99.0-1)
Provides: xserver-xorg-video
Replaces: xserver-xorg (<< 6.8.2-35)
+Suggests: libgl1-mesa-dri
Description: X.Org X server -- Savage display driver
This package provides the driver for the S3/VIA Savage/ProSavage/Twister
family
of chipsets.
@@ -20,4 +21,6 @@
<URL:http://lists.freedesktop.org/mailman/listinfo/xorg>
.
+ You also need to install libgl1-mesa-dri for 3D acceleration of Savage cards
+ .
This module can be found as the module 'driver/xf86-video-savage' at
:pserver:[EMAIL PROTECTED]:/cvs/xorg
only in patch2:
unchanged:
--- xserver-xorg-video-savage-2.0.2.3.orig/debian/README.Debian
+++ xserver-xorg-video-savage-2.0.2.3/debian/README.Debian
@@ -0,0 +1,52 @@
+3D acceleration using Savage drivers
+------------------------------------
+
+If 3D acceleration is working, glxinfo (in package mesa-utils) will report:
+
+ direct rendering: Yes
+
+Also, in your X server log (/var/log/Xorg.0.log) you will find:
+
+ (**) SAVAGE(0): DRI is enabled
+
+
+Troubleshooting 3D acceleration with Savage drivers
+---------------------------------------------------
+
+If can not find this in your X server log:
+
+ (**) SAVAGE(0): DRI is enabled
+
+You should check that your X server really is using the Savage driver, and that
+X acceleration is not disabled. You should find a device section like this in
+/etc/X11/xorg.conf:
+
+Section "Device"
+ Identifier "S3"
+ Driver "savage"
+EndSection
+
+If the X server log shows that DRI is disabled, but glxinfo reports that direct
+rendering is not working, you should check that libgl1-mesa-dri is installed.
+This package contains the savage_dri.so DRI module which is needed for direct
+rendering. If this is installed, look at the output of glxinfo with debug
+information enabled. On a working system you should see something like this:
+
+$ LIBGL_DEBUG=verbose glxinfo
+
+name of display: :0.0
+libGL: XF86DRIGetClientDriverName: 2.0.2 savage (screen 0)
+libGL: OpenDriver: trying /usr/lib/dri/savage_dri.so
+drmOpenByBusid: Searching for BusID pci:0000:01:00.0
+drmOpenDevice: node name is /dev/dri/card0
+drmOpenDevice: open result is 4, (OK)
+drmOpenByBusid: drmOpenMinor returns 4
+drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
+libGL error:
+Can't open configuration file /etc/drirc: No such file or directory.
+libGL error:
+Can't open configuration file /home/chris/.drirc: No such file or directory.
+display: :0 screen: 0
+direct rendering: Yes
+[...]
+
