Skip to contentSkip to conversation

DRI doesn't work on 2.4.0 but does on prerelease-ac5

DISCUSSION Michael D. Crawford 7 participants 9 messages Jan 8, 2001 – Jan 10, 2001

lore
Share & tools
lore
#0 lore raw

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

Signature · 10 lines
Michael D. Crawford
GoingWare Inc. - Expert Software Development and Consulting
http://www.goingware.com/
[email protected]

   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 [email protected]
Please read the FAQ at http://www.tux.org/lkml/
#1 lore raw
Quoted 3 lines · Michael D. Crawford

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.

It sounds as if you're using a Mesa lib that doesn't support the X DRI stuff, just the software renderer.

Bill
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

#2 lore raw
In reply to Michael D. Crawford
Quoted 30 lines · Michael D. Crawford

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.

Quoted 7 lines

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?

I have this same problem with a Voodoo 3 2000(tdfx) running 2.4.0 and XFree86 4.0.2.

Signature · 5 lines
L1:	khromy		;khromy(at)khromy.lnuxlab.net
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
#3 lore raw

[OT]: DRI doesn't work on 2.4.0 but does on prerelease-ac5

In reply to Michael D. Crawford

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

Quoted 45 lines · Michael D. Crawford

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/
[email protected]

Quoted 5 lines

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 [email protected]
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 [email protected]
Please read the FAQ at http://www.tux.org/lkml/

#4 lore raw

Re: [OT]: DRI doesn't work on 2.4.0 but does on prerelease-ac5

Quoted 8 lines · J Sloan

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.

Quoted 4 lines

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.

Sounds like the version you blew away was not the one built in 4.0.2. (Mesa is built along with XFree86 now, not as an add-on.)

I will test with my current configuration and see if I can duplicate the slow down.

I am currently using a Matrox G400 max card with 4.0.2cvs. I get about 1285 frames per second on the gears demo currently. We will see if that changes with the 2.4.0 final release version.

[email protected] | Note to AOL users: for a quick shortcut to reply
Alan Olsen | to my mail, just hit the ctrl, alt and del keys.
"In the future, everything will have its 15 minutes of blame."

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

#5 lore raw

Re: [OT]: DRI doesn't work on 2.4.0 but does on prerelease-ac5

In reply to Michael D. Crawford
Quoted 4 lines · J Sloan

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.

Well, the real problem is that (at least Voodoo3) DRI didn't work _before_ with the "latest" test and pre kernels, and X < 4.0.2 (unless there was some combination I didn't manage to find) even if it was using the correct library.

[ If anyone would like some help, feel free to email me directly ]

Signature · 9 lines
____/|  Ragnar Højland     Freedom - Linux - OpenGL      Fingerprint  94C4B
\ o.O|                                                   2F0D27DE025BE2302C
 =(_)=  "Thou shalt not follow the NULL pointer for      104B78C56 B72F0822
   U     chaos and madness await thee at its end."       hkp://keys.pgp.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
#6 lore raw

Re: [OT]: DRI doesn't work on 2.4.0 but does on prerelease-ac5

In reply to Michael D. Crawford
Quoted 11 lines · Ragnar Hojland Espinosa
Quoted 4 lines · J Sloan

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.

Well, the real problem is that (at least Voodoo3) DRI didn't work _before_ with the "latest" test and pre kernels, and X < 4.0.2 (unless there was some combination I didn't manage to find) even if it was using the correct library.

That's odd, perhaps we should compare notes -

I have been getting good accelerated 3D from my voodoo3 since around 2.3.36, except for one brief period around 2.3.99-something where some critical kernel code changed.

I have been using the kernel drm all along.

BTW I am using the X server from 3dfx.com -

jjs

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

#7 lore raw

Re: [OT]: DRI doesn't work on 2.4.0 but does on prerelease-ac5

In reply to Michael D. Crawford
Quoted 7 lines · J Sloan
Quoted 4 lines · Ragnar Hojland Espinosa

Well, the real problem is that (at least Voodoo3) DRI didn't work _before_ with the "latest" test and pre kernels, and X < 4.0.2 (unless there was some combination I didn't manage to find) even if it was using the correct library.

That's odd, perhaps we should compare notes -

Seeing that it _finally_ worked (that qbert spongies xscreensaver thing is hilarious:) I cleaned up all the logs, along with the mesas and glides builds .. so right now all I have is a working setup (which I can't complain about)

Quoted 3 lines

I have been getting good accelerated 3D from my voodoo3 since around 2.3.36, except for one brief period around 2.3.99-something where some critical kernel code changed.

IIRC I started trying to make it work around 2.3.99 but wasn't as fortunate as you since as mentioned it just refused to work.

Quoted 1 line

BTW I am using the X server from 3dfx.com -

Ah, that could have something to do with it, because I always used the (mirrorerd) xfree86.org binaries.

Signature · 8 lines
____/|  Ragnar Højland     Freedom - Linux - OpenGL      Fingerprint  94C4B
\ o.O|                                                   2F0D27DE025BE2302C
 =(_)=  "Thou shalt not follow the NULL pointer for      104B78C56 B72F0822
   U     chaos and madness await thee at its end."
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
#8 lore raw

xircom_tulip + NFS hanging interface

I've been getting problems all along the pre-2.4 series and 2.4 itself when I use NFS to play mp3 files with xmms.

The message in the logs is:
tulip.c: outl_CSR6 too many attempts,csr5=0x60208100

After a few times the network stops working and it only recovers with the following sequence of commands:

ifdown eth0 && ifup eth0 && ifconfig eth0 -promisc

Without ifconfig eth0 -promisc it still doesn't get any packet. I have to stop and start the interface too ad -prmisc doesn't work alone. So this is the only sequence that works.

The modules loaded are:
Module Size Used by

nfs                    75136   1  (autoclean)
lockd                  49680   1  (autoclean) [nfs]
sunrpc                 59392   1  (autoclean) [nfs lockd]
ide-cd                 26608   0  (autoclean)
cdrom                  27104   0  (autoclean) [ide-cd]
rtc                     5520   0  (unused)
ipchains               32544   0  (unused)
apm                     9088   2
parport_pc             18880   1  (autoclean)
lp                      5200   0  (autoclean)
parport                27680   1  (autoclean) [parport_pc lp]
autofs                 10784   1  (autoclean)
xircom_tulip_cb        30832   1  (autoclean)
serial_cb               1360   0  (autoclean) (unused)
serial                 43344   0  (autoclean) [serial_cb]
isa-pnp                29040   0  (autoclean) [serial]
agpgart                16960   0  (unused)
maestro                26880   1
soundcore               3952   2  [maestro]
uhci                   18672   0  (unused)
usbcore                52304   2  [uhci]

Thanks for your help
Pau

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/