Leif Delgass writes:
Have you tried a lower resolution?
Not yet.
If it's some sort of memory leak, I'd
expect that you'd run into it eventually even at a lower resolution. If
it doesn't happen at lower resolutions, maybe you really just don't have
enough offscreen memory at 1280x1024.
Problem:
If lighting and color sum are disabled, the secondary color is not used. If
secondary color is set (via one of the glSecondaryColor3*EXT functions), the
radeon and r200 will segfault.
Detailed description:
This only happens if the vtxfmt paths are enabled. That is, if either
On Tue, 26 Nov 2002 22:04:59 +
Keith Whitwell [EMAIL PROTECTED] wrote:
Felix Kühling wrote:
Hi,
clipping of lines at the edges of the viewing volume doesn't seem to
work. The problem occurs both with RADEON_TCL_FORCE_DISABLE and with
LIBGL_ALWAYS_INDIRECT. If I use a glOrtho
Hi,
the circuit demo segfaults with direct and indirect rendering. It could
be a bug in circuit, but I didn't ever see this before the Mesa 5.0
merge. My xscreensaver version is 4.05.
With direct rendering it always occurs after about 45 seconds if I run
it with -delay 0 on my Radeon 7500. This
On Tue, Nov 26, 2002 at 07:51:26PM -0500, Roland Glenn McIntosh wrote:
Gentlemen: I'm having considerable difficulty with my current kernel compile.
gcc exists with code 1 every time on i810_dma.c.
I was hoping someone could check and make sure that this is compatible with gcc 3.2.
If this
On Wed, 2002-11-27 at 11:25, José Fonseca wrote:
But if I undertsood correctly, you refering to the modules included in
the kernel source (linux-2.4.19-gentoo-r9 in this case). I don't know
about these, but as long as you're using = XFree86 4.2.0 you should
compile the ones in
On Wed, Nov 27, 2002 at 12:32:46PM +, Alan Cox wrote:
On Wed, 2002-11-27 at 11:25, José Fonseca wrote:
But if I undertsood correctly, you refering to the modules included in
the kernel source (linux-2.4.19-gentoo-r9 in this case). I don't know
about these, but as long as you're using =
On Wed, 2002-11-27 at 12:46, José Fonseca wrote:
I confess that I'm never sure how the modules in the linux kernel tree and
xfree/dri cvs compare. For a long time 4.2 modules weren't found in the
linux tree. Since which version were they included?
2.4.1something-ac and 2.4.20-rc now has them
Brian Paul wrote:
D. Hageman wrote:
Is anyone else experiencing unresolved symbols from GLcore from CVS?
It seems that it can't resolve fabsf and xf86strncat (or some variant
of).
I unfortunately trashed my logs when I reverted back to my previous
build of XFree86. I will try again today
For years, women of all ages have suffered embarrassment from
having small, sagging or underdeveloped breasts which often leads to
low self esteem. Until now, solutions to this problem required
On Wed, 27 Nov 2002, Svante Signell wrote:
Leif Delgass writes:
Have you tried a lower resolution?
Not yet.
Try restarting X with 1024x768@16bpp for a while and see if you still have
the same problem.
If it's some sort of memory leak, I'd
expect that you'd run into it eventually
Never mind. I tracked it down, it's not a Mesa or DRI error. In fact it
was fixed in the new upstream version 4.06. The strange backtrace is
because a function overwrites its own return address with 0.
Regards,
Felix
On Wed, 27 Nov 2002 10:55:45 +0100
Felix Kühling [EMAIL PROTECTED] wrote:
I have a dual video adapter system:
Primary: ATI Rage 128
Secondary: NVidia Geforce2
System boots on R128 and then runs X on Geforce.
If I run ddcprobe from a virtual console (on R128) it
works fine. If I run it on an xterm it fails (see
below).
What should the correct behavior be? I would
We're trying to build X with everything in for debugging but I get an error during
compilation saying no target found for xc/lib/GL/mesa/dri, does anybody know what
could be causing this or has tried building X witheverything in themselves???
The only thing I've uncommented in host.def is:
On Mon, 2002-11-25 at 17:33, Bruno CARBONARA wrote:
after install dri r200 and extra-4.2.99.2 glx and dri ok
but if call gtk-demo crash imediatly
gtk-demo crashes, or the X server, or what?
if not call gtk-demo after quit wmaker
wmaker warning: internal X error: BadAccess (attempt to
On Wed, 27 Nov 2002, Brian Paul wrote:
Brian Paul wrote:
D. Hageman wrote:
Is anyone else experiencing unresolved symbols from GLcore from CVS?
It seems that it can't resolve fabsf and xf86strncat (or some variant
of).
I unfortunately trashed my logs when I reverted back to my
Sorry, I forgot to include the actual error message:
make[5]: *** No rule to make target `../../../lib/GL/mesa/dri/?*.o', needed by
`libGL.so.1.2'.
Thanks
Tom
We're trying to build X with everything in for debugging but I get an error during
compilation saying no target found for
Title: RE: [Dri-devel] CVS issue - unresolved symbols from GLcore?
I did notice that rendering has
slowed down on the r200 driver by a magnitude of about 5
times. This of
course isn't a very accurate measure purely based of glxgears
frame rates,
but it does make me raise an
18 matches
Mail list logo
