Re: [Dri-devel] Caught signal 11, with bleeding-edge, radeon 8500 LE

2002-11-17 Thread José Fonseca
Ingo, On Sun, Nov 17, 2002 at 12:27:12PM +0100, Ingo Molnar wrote: > > i'm getting segfaults with the latest bleeding-edge XFree86 binary. > > the system is using the latest Red Hat rawhide rpms, i've used the latest > extras snapshot (and the libxaa from the extras tarball), plus the > r200-200

Re: [Dri-devel] Caught signal 11, with bleeding-edge, radeon 8500 LE

2002-11-17 Thread Jacek Popławski
On Sun, Nov 17, 2002 at 12:27:12PM +0100, Ingo Molnar wrote: > 7c1cb25d8b5a42c9e1e6b30530b9d469 /usr/X11R6/bin/XFree86 This binary is very unstable on my system (Voodoo3), too. Looks like this is early beta, or it needs more files from XFree86-3.2.99 (not just XFree86 binary). -- http://decopt

Re: [Dri-devel] Caught signal 11, with bleeding-edge, radeon 8500 LE

2002-11-17 Thread Felix Kühling
Hi Ingo, I think I read something about problems with the module loader some weeks ago on dri-devel. Bad things happen when the same module is loaded twice. In your config this happens with GLcore which is automatically (re)loaded by the glx module. Do you still get segfaults if you remove the Loa

[Dri-devel] Caught signal 11, with bleeding-edge, radeon 8500 LE

2002-11-17 Thread Ingo Molnar
i'm getting segfaults with the latest bleeding-edge XFree86 binary. the system is using the latest Red Hat rawhide rpms, i've used the latest extras snapshot (and the libxaa from the extras tarball), plus the r200-20021116 radeon driver. I've attached: - rpm -qa output - the XF86Config - stra