Re: [Dri-devel] Rage 128 texmem problems (was Re: Snapshots missing libGL.so?)

2003-06-06 Thread John Sheu
On Thursday 05 June 2003 11:45 am, Leif Delgass wrote: I'm pretty sure I ran into this problem on r128 before when I tried running at 24-bit depth with a high enough resolution. If this is the problem, I think you'd see a message like: Reserved 0 kb for textures at offset 0x0 in the X log.

Re: [Dri-devel] Rage 128 texmem problems (was Re: Snapshots missing libGL.so?)

2003-06-06 Thread John Sheu
On Thursday 05 June 2003 11:45 am, Leif Delgass wrote: I'm pretty sure I ran into this problem on r128 before when I tried running at 24-bit depth with a high enough resolution. If this is the problem, I think you'd see a message like: Reserved 0 kb for textures at offset 0x0 in the X log.

Re: [Dri-devel] Rage 128 texmem problems (was Re: Snapshots missing libGL.so?)

2003-06-05 Thread John Sheu
On Thursday 05 June 2003 07:08 pm, Leif Delgass wrote: Try a lower resolution and/or color depth. We can fix the segfault, but that won't change the fact that there isn't enough on-card memory to use 3D at the configured resolution/depth (at least with the current static shared back buffer

[Dri-devel] Rage 128 texmem problems (was Re: Snapshots missing libGL.so?)

2003-06-05 Thread Ian Romanick
John Sheu wrote: Output of gdb on glxinfo: Starting program: /usr/X11R6/bin/glxinfo (no debugging symbols found)...[New Thread 16384 (LWP 2145)] name of display: :0.0 Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 2145)] 0x4046dee5 in