Re: [Dri-devel] Re: [Dri-users] Flashing textures problem with ATIRadeon 7500

2003-02-06 Thread ahaning
Please try the current DRM, I'm curious if recent changes make a difference. Using the DRI-CVS from the evening of Feb 5, 2003, I saw no change. Textures still flicker and it is still possible to lock up the server with endgame (and possibly others. It's just easiest to get that behavior with

Re: [Dri-devel] Re: [Dri-users] Flashing textures problem with ATIRadeon 7500

2003-02-05 Thread ahaning
I'll second this. In some of the screenhacks from xscreensaver 4.06, there is flickering when they are displayed on the root window (as you would normally play them as screensavers). With a quick check, I notice this behavior in superquadrics, atlantis, moebius, queens, and pulsar (there are

Re: [Dri-devel] Confusing..?

2003-02-05 Thread ahaning
cd programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/ make -f Makefile.linux MODULE.o I would just add that if you're using a kernel that uses a better source directory naming scheme (e.g. 2.4.19 unpacks to linux-2.4.19 whereas 2.4.18 unpacks to just linux), you'll want to use the

Re: [Dri-devel] DRI-CVS pseudo-lockups on radeon.o (Radeon VE/7000)

2003-01-26 Thread ahaning
I could reproduce your X lockups with my Radeon 7500 by disabling TCL (RADEON_TCL_FORCE_DISABLE=1) which is as close as I can get to your Radeon VE. I don't use the dri_resume patch. From your telling that it helped to kill the offending GL app it sounds like the GL app gets stuck somewhere while

Re: [Dri-devel] DRI-CVS pseudo-lockups on radeon.o (Radeon VE/7000)

2003-01-26 Thread ahaning
You need to continue here. OpenGL library is trying to determine SSE extension availability. You could have been a bit more explicit, like: At this point, type continue. But, I figured that out, anyway. Here's what I got from a bt: #0 0x4035a1b4 in ?? () #1 0x40503b07 in ?? () #2

[Dri-devel] DRI-CVS pseudo-lockups on radeon.o (Radeon VE/7000)

2003-01-24 Thread ahaning
Hello. I've been having some troubles with dri-cvs for some time when running GL apps (especially the GL hacks that come with JWZs xscreensaver). In particular, I've noticed problems when running endgame and menger on the root and in windows and then running other windows over them or moving

Re: [Dri-devel] full box lockup.

2002-11-24 Thread ahaning
A friend of mine reported something like this (haven't seen it myself). For him, killing the DRI client(s) resumes normal operation. Can you confirm that? If so, that's not an actual lockup. I can confirm that. Testing again, it's not too easily reproduceable here (which doesn't help much).

Re: [Dri-devel] radeon.o DRM modules breaks my CD player (!)

2002-11-24 Thread ahaning
Are you sure your HDD is using DMA? Maybe you could post the result of `hdparm -Tt /dev/hda' (or whatever disk is your root harddisk. -Tt is a nondestructive test and should tell you how many MB/s you can get to your drive. With DMA off, it will be quite low (3MB or so per second), but with

Re: [Dri-devel] full box lockup.

2002-11-23 Thread ahaning
I'm having similar problems. I re-co'ed the CVS tree this evening (Nov 24 2002) and rebuilt it. The build and install went well, when it hadn't earlier. I was hopeful. However, when I run any openGL demo from xscreensaver (http://www.jwz.org/xscreensaver/) or reallyslick