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 endgame.)

Thanks.

-Andy
[EMAIL PROTECTED]



---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


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 probably more.) I'm currently using:

$ X -version

This is a pre-release version of XFree86, and is not supported in any
way.  Bugs may be reported to [EMAIL PROTECTED] and patches submitted
to [EMAIL PROTECTED]  Before reporting bugs in pre-release versions,
please check the latest version in the XFree86 CVS repository
(http://www.XFree86.Org/cvs)

XFree86 Version 4.2.99.2 (DRI trunk) / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 21 October 2002
If the server is older than 6-12 months, or if your card is
newer than the above date, look for a newer version before
reporting problems.  (See http://www.XFree86.Org/)
Build Operating System: Linux 2.4.18 i686 [ELF]
Module Loader present
$

and my dri module is perhaps a couple weeks old (I'm sorry that I can't 
be more specific than this; is there a way that I can tell from my local 
tree when the last time was that I checked it out?). I'm also using 
XFree86 on a Radeon VE (7000; I think this is *also* known as the r100 
(?) ) which has no TCL, so, when running the GL hacks, I get:

$ superquadrics
disabling TCL support
$


I'm also still having the lockup problems I noted in the thread DRI-CVS 
pseudo-lockups on radeon.o (Radeon VE/7000) from several weeks ago. If 
this has been resolved recently in CVS (or if someone thinks it has 
been), I'll be happy to try it out.

Thanks.

Andy
[EMAIL PROTECTED]



---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


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 
TREE=/usr/src/linux-2.4.XX/include option in your make command. Like so:

make -f Makefile.linux TREE=/usr/src/linux-2.4.XX/include MODULE.o

(I've never included the MODULE.o part, but if that works, then sweet. 
No sense in building r128 modules when I've got a Radeon.)

and then as root:
cp MODULE.o /lib/modules/`uname -r`/kernel/drivers/char/drm/
depmod -a


where MODULE.o corresponds to the drm-driver you need


-Andy
[EMAIL PROTECTED]



---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



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 holding the lock. It would be helpful to know where
exactly that is. Unfortunately I don't have a second system at hand to
log in remotely from.

Could you reproduce a lockup with a GL app running in a remote debugger
session. When the system is locked up you press Ctrl+C in the debugger,
get backtrace with the bt command and send it to the list.

I tried to do this from a remote machine and locally, and both times, I 
get errors like:

**

$ gdb
GNU gdb 5.0
Copyright 2000 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB.  Type show warranty for details.
This GDB was configured as i386-slackware-linux.
(gdb) exec-file /usr/local/lib/xscreensaver/endgame
(gdb) set args -display :0
(gdb) run
Starting program: /usr/local/lib/xscreensaver/endgame -display :0
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
warning: shared library handler failed to enable breakpoint

Program received signal SIGFPE, Arithmetic exception.
0x404fc600 in ?? ()
(gdb) quit
The program is running.  Exit anyway? (y or n) y
$

**

A window is created for the hack to run, but nothing ever appears.

It appears to me that I need to compile endgame (and/or other GL hacks) 
with debugging information. I don't know how to do this, though. If you 
could direct me to some information about how I would go about it, I'd 
much appreciate it.

About the flickering when running endgame on the root window, I could
reproduce that too, even with TCL enabled. It looks to me like it is
using a single buffered visual in that case. Curiously this doesn't
happen when xscreensaver runs endgame on the root window.


I was reading a document later about graphics coding and it mentioned 
that erasing the image you wanted to move, and then redrawing it would 
produce flicker and the solution to this was double-buffering and it 
reminded me of the flickering I see when running the GL hacks. I tried, 
and when having xscreensaver run the hacks in the root window, I get 
flickering. Curiouser and curiouser.

Thanks.

-Andy



---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


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  0x405021de in ?? ()
#3  0x4050193e in ?? ()
#4  0x40501bdc in ?? ()
#5  0x40501c4a in ?? ()
#6  0x405147ce in ?? ()
#7  0x40503a7d in ?? ()
#8  0x40503c15 in ?? ()
#9  0x405021de in ?? ()
#10 0x4050193e in ?? ()
#11 0x40501bdc in ?? ()
#12 0x40501c4a in ?? ()
#13 0x405147ce in ?? ()
#14 0x40514c40 in ?? ()
#15 0x405158c5 in ?? ()
#16 0x40516922 in ?? ()
#17 0x404b5c97 in ?? ()
#18 0x4050e1b6 in ?? ()
#19 0x404b445b in ?? ()
#20 0x404ae65c in ?? ()
#21 0x403ecd9e in ?? ()
#22 0x403eeed6 in ?? ()
#23 0x804a56f in ?? ()
#24 0x804ac5b in ?? ()
#25 0x804af80 in ?? ()
#26 0x804b426 in ?? ()
#27 0x8053379 in ?? ()
#28 0x804a3c3 in ?? ()
#29 0x8051cb0 in ?? ()
#30 0x402cc577 in ?? ()


If that's not what is needed (it doesn't look helpful to me), let me 
know. I'm really more of an almost-poweruser, and less a coder.

Thanks.

-Andy



---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


[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 the GL apps window around. Occasionally, my X session locks up 
completely, and I can only move the mouse around, X's 
three-finger-salute doesn't work. What I have been able to do when this 
occurs (other than a hard reset) is to log in over the network and kill 
the offending GL app. Then, my X session is usable again.

I'm currently using:
$ X -version

snip
XFree86 Version 4.2.99.2 (DRI trunk) / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 21 October 2002
snip
Build Operating System: Linux 2.4.18 i686 [ELF]

I updated my dri-cvs tree on the evening of Jan24, 2003 and 
compiled/installed it (and then the kernel modules). My video card is a 
Radeon VE (what is now called a Radeon 7000), I'm using it on the VGA 
head (as opposed to the DVI) on an ASUS CUBX-E at AGP 2, and I've also 
applied Charl Botha's dri_resume patch 
http://cpbotha.net/files/dri_resume/xfree86-dri-resume-v6.patch and I 
have suspended and resumed several times since the last boot. I have 
also, however, restarted X since the last resume. I'm using the 
screenhacks from v 4.06 of xscreensaver 
http://www.jwz.org/xscreensaver/xscreensaver-4.06.tar.gz.

*** UNRELATED (I HOPE) ***
In an unrelated note, when I play these hacks on the root window, they 
flicker a lot, unlike the non-GL, 2D hacks.
**

If anyone's interested in this problem and would like me to provide any 
more information or test some patches, let me know.

Thanks.

Andy
[EMAIL PROTECTED]



---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


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). However, if I load some DRI screenhacks and move their 
windows around a bit, the X server will occasionally lock up. Then, if I 
log in over the network and kill the clients, I can use the X server again.

-Andy



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


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 DMA on, you should get 
30-40MB/s).

-Andy



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


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 
(http://www.reallyslick.com), and move a window over them, my system 
completely locks up. The mouse still works, but the keyboard is 
unuseable, and any usually-updated windows (xload, ascpu) don't update 
anymore.

The other annoying thing that happens when running the screensavers is 
that a message is output onto the terminal telling me that it is 
disabling TCL, which my Radeon VE does not have. Hopefully this will be 
removed prior to any actual release.

The screensavers are nicely accelerated, however, as is playing videos 
with mplayer/xine through the xv extension.

Thanks.

-Andy



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel