Re: [Dri-devel] Rage 128 texmem problems (was Re: Snapshots missing libGL.so?)
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. Right, that appears in the logs. So what to do? --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Rage 128 texmem problems (was Re: Snapshots missing libGL.so?)
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. Right, that appears in the logs. So what to do? --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Rage 128 texmem problems (was Re: Snapshots missing libGL.so?)
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 allocation scheme). Right then, it works. But being the person I am, I just can't leave well enough alone The box on my card (XPert 128 [r128 chip, 16 MB RAM] ) claims 1280 * 1024 @ 16 bbp. Is that then OS- or driver-specific? I would think the card has at least those capabilities. Currently in Linux I'm at 1152 * 864 @ 16 bbp (1280 * 1024 segfaults) and the logs claim: (II) R128(0): Reserved 832 kb for textures at offset 0xf3 Seems awful low to me. (Of course, I wouldn't have the background to know better). So is this a DRI driver issue? --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Rage 128 texmem problems (was Re: Snapshots missing libGL.so?)
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 driSetTextureSwapCounterLocation (heap=0x0, counter=0x8051c18) at texmem.c:584 584 texmem.c: No such file or directory. in texmem.c Hmm...looking at the code, my guess is that rmesa-nr_heaps is 2 on Rage 128 even on PCI cards. In gdb you can 'print rmesa-nr_heaps' to see. You might also try 'print r128scrn-texSize[0]' and (if nr_heaps is 2) 'print r128scrn-texSize[1]'. Since I don't have a Rage 128, that would help. :) Perhaps Leif can take a look at this. Note that this has *NOTHING* to do with your libGL.so. This is 100% in the driver. --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
