Gentoo Archives: gentoo-sparc

From: Ferris McCormick <fmccor@g.o>
To: gentoo-sparc@l.g.o
Subject: [gentoo-sparc] xorg-x11-6.8.0-r1 stable + [Bug 65348] New: libGL (DRI for Creator graphics) sometimes fails with xorg-x11-6.8.0-r1 (fwd)
Date: Sat, 25 Sep 2004 20:44:43
Hash: SHA1

As threatened, xorg-x11-6.8.0-r1 is stable for sparc as of earlier today.
I have mentioned before that with Creator graphics and libGL, you now get
a sort-of working for direct rendering.

Rather than rehash what is going on with it, I am forwarding a copy
of a bug I have opened for tracking libGL+ffb status.  If you are a
Creator graphics user, you might want to review the bug, and please
post your experiences to it.  Please do not open a new bug, because that
makes tracking much harder, and so more likely to get lost.


- --
Ferris McCormick (P44646, MI) <fmccor@g.o>
Developer, Gentoo Linux (sparc)

- ---------- Forwarded message ----------
Date: Sat, 25 Sep 2004 20:37:02 +0000
From: bugzilla-daemon@g.o
To: sparc@g.o
Subject: [Bug 65348]  New: libGL (DRI for Creator graphics) sometimes fails
    with xorg-x11-6.8.0-r1

           Summary: libGL (DRI for Creator graphics) sometimes fails with
           Product: Gentoo Linux
           Version: unspecified
          Platform: Sparc
        OS/Version: All
            Status: NEW
          Keywords: Tracker
          Severity: minor
          Priority: P4
         Component: Applications
        AssignedTo: fmccor@g.o
        ReportedBy: fmccor@g.o
                CC: sparc@g.o,x11@g.o

New with xorg-x11-6.8.0-r1, the direct rendering module for use with
libGL (mesa) and Sun Creator graphics cards actually loads and runs.

However, it is incomplete at this point.  This means that some applications can use it
with no problems (and run much faster as a result), but others do not run correctly.
(Example:  glxgears runs very fast, but is black-on-black so doesn't show anything.
The Mesa 'stars' demo runs fine and is much faster.)

On sparc, it is always built, and if in your xorc.conf file, you load dri and glx,
it is used for libGL applications.  Quick check:  glxinfo starts out like this:
================ferris@terciopelo:PROJECTS/SIMULATION/ALL-IN-ONE [246]% glxinfo|more
name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
    GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
    GLX_EXT_import_context, GLX_OML_swap_method, GLX_SGI_make_current_read, 
    GLX_SGIS_multisample, GLX_SGIX_fbconfig
client glx vendor string: SGI
client glx version string: 1.4
(The key being that 'direct rendering: Yes')

If your application happens to fail, you can disable direct rendering for ffb
with the LIBGL_ALWAYS_INDIRECT environment variable; e.g.,
fmccor@terciopelo ferris $ LIBGL_ALWAYS_INDIRECT='yes' glxinfo
name of display: terciopelo:0.0
display: terciopelo:0  screen: 0
direct rendering: No

If you set this in your environment, libGL behaves the same way as it did with

This is a known problem addressing current limitations in a work in progress.
If you run into the problem, please report it on this bug and try to show what fails for you.
We need that information to work on making this feature more robust.

(By the way, if you are kernel-2.6.7, this does not apply.  You can't get at drm
for ffb at all, and that is a kernel problem/feature.)

- ------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
Version: GnuPG v1.2.4 (GNU/Linux)


gentoo-sparc@g.o mailing list