From: J Sloan <jjs@toyota.com>
To: "Michael D. Crawford" <crawford@goingware.com>
Cc: linux-kernel@vger.kernel.org, newbie@xfree86.org
Subject: [OT]: DRI doesn't work on 2.4.0 but does on prerelease-ac5
Date: Mon, 08 Jan 2001 14:56:05 -0800 [thread overview]
Message-ID: <3A5A4585.5036A11C@toyota.com> (raw)
In-Reply-To: <3A5A087F.F1C45380@goingware.com>
This is a little OT for linux-kernel, but I'll take a swing at it
since I'm running 2.4 and Xfree 4 with a voodoo 3.
After upgrading to Red Hat 7.0, I noticed 3D screensavers
and Quake 3 Arena were dog slow - in the end, I basically
had to make sure the mesa libs didn't get found before the
real opengl libs.
In my case, that meant nuking mesa from my system and
letting Linux use what was left, which got me back the good
accelerated performance - you may choose a less drastic
option. I don't see any breakage from the absence of mesa.
Hope this helps,
jjs
"Michael D. Crawford" wrote:
> OK, I built XFree86 4.0.2 and DRI seems to be working for me now under
> 2.4.0-ac4. (Starting with 2.4.0, it wouldn't, this is with an ATI XPert 2000
> AGP).
>
> BUT - although /var/log/XFree86.0.log documents the startup of DRI, DRM and AGP,
> and states the info about their initialization and stuff so that it looks like
> they're working, I don't notice any performance difference running any of the
> Mesa-3.4 demos whether or not I use DRI, and whether I run 4.0.1 or 4.0.2.
>
> This makes me suspect it's not really working, or else my build of the Mesa-3.4
> library wasn't configured right - but note that if I disable DRI, one of the
> Mesa demos will comment that it's not available.
>
> A specific example is Mesa-3.4/demos/gloss. It's a rotating textured cylinder
> that is partially reflective of what seems to be a landscape that is in front of
> the screen being reflecting back to the viewer. I get a pretty consistent 7.5
> frames per second:
>
> - in 4.0.1 with no DRI
> - in 4.0.1 with DRI
> - in 4.0.2 with no DRI
> - in 4.0.2 with DRI
>
> Having agpgart and drm/r128 compiled in or as modules also doesn't appear to
> make a difference.
>
> The frame rate for gloss drops to about 3.5 if I run geartrain (another demo)
> alongside it. Geartrain by itself seems to be about the same speed in all
> cases, though it doesn't report a number.
>
> There are a couple benchmarking tools in Mesa if someone wanted hard numbers
> from me.
>
> Can anyone suggest any 3D code that I can download that does more complex things
> than the mesa demos that I can test this with?
>
> Is my DRI really working? If not, any tips on getting it to do so?
>
> Mike
> --
> Michael D. Crawford
> GoingWare Inc. - Expert Software Development and Consulting
> http://www.goingware.com/
> crawford@goingware.com
>
> Tilting at Windmills for a Better Tomorrow.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-08 22:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 18:35 DRI doesn't work on 2.4.0 but does on prerelease-ac5 Michael D. Crawford
2001-01-08 22:06 ` Bill Nottingham
2001-01-08 22:55 ` khromy
2001-01-08 22:56 ` J Sloan [this message]
2001-01-08 23:57 ` [OT]: " Ragnar Hojland Espinosa
2001-01-09 0:37 ` J Sloan
2001-01-09 16:11 ` Ragnar Hojland Espinosa
2001-01-10 7:41 ` xircom_tulip + NFS hanging interface Pau
2001-01-09 8:20 ` [OT]: DRI doesn't work on 2.4.0 but does on prerelease-ac5 Alan Olsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A5A4585.5036A11C@toyota.com \
--to=jjs@toyota.com \
--cc=crawford@goingware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=newbie@xfree86.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox