Re: [Dri-users] How to build the new cvs
On Mon, 2006-02-27 at 16:42 -0500, Felix Kühling wrote: What do you mean with unmerge? I think he is referring to un-intalling, the Gentoo way :) --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Rage 128 texmem problems
I think it's a been a decent interval to resend The problem was with a PCI Rage128 card (16 MB video RAM) which seemed to have problems with memory allocation (i.e. 0 kb texture memory allocated at 1280 * 1024, only 4MB at 1024768). Since the box claims 3D performance at 1280 in Windows, I was wondering if this was just a driver issue. On Friday 06 June 2003 08:56 am, Ian Romanick wrote: Hmmm...that is odd. The resolution should only require 7.5MB for the front, back, and depth-buffers. That should leave about 8MB for textures, not 800KB. Are you sure it's at 16-bpp? ~800KB left is about rigth if you were running at 24-bpp. I'm sure (or my system is sure) it's 16 bpp. Switching to 1024 * 768 @ 16, I see only 4MB. Would this figure be on-card or system memory? More stuff from the XFree logs: Found a line: (--) Depth 24 pixmap format is 32 bpp After XAA is loaded. Then we have the perhaps useful lines here: (II) R128(0): [drm] loaded kernel module for r128 driver (II) R128(0): [drm] created r128 driver at busid PCI:1:14:0 (II) R128(0): [drm] added 8192 byte SAREA at 0xd2a22000 (II) R128(0): [drm] mapped SAREA 0xd2a22000 to 0x40018000 (II) R128(0): [drm] framebuffer handle = 0xf800 (II) R128(0): [drm] added 1 reserved context for kernel (II) R128(0): [pci] 8192 kB allocated with handle 0xd3b17000 (II) R128(0): [pci] ring handle = 0xd3b17000 (II) R128(0): [pci] Ring mapped at 0x411b2000 (II) R128(0): [pci] Ring contents 0x (II) R128(0): [pci] ring read ptr handle = 0xd3c18000 (II) R128(0): [pci] Ring read ptr mapped at 0x4001a000 (II) R128(0): [pci] Ring read ptr contents 0x (II) R128(0): [pci] vertex/indirect buffers handle = 0xd3c19000 (II) R128(0): [pci] Vertex/indirect buffers mapped at 0x412b3000 (II) R128(0): [pci] Vertex/indirect buffers contents 0x (II) R128(0): [drm] register handle = 0xf0104000 (II) R128(0): [dri] Visual configs initialized (II) R128(0): CCE in BM mode (II) R128(0): Using 8 MB AGP aperture (II) R128(0): Using 1 MB for the ring buffer (II) R128(0): Using 2 MB for vertex/indirect buffers (II) R128(0): Using 1 MB for AGP textures (II) R128(0): Memory manager initialized to (0,0) (1024,3072) (II) R128(0): Reserved area from (0,768) to (1024,770) (II) R128(0): Largest offscreen area available: 1024 x 2302 (II) R128(0): Reserved back buffer from (0,770) to (1024,1538) (II) R128(0): Reserved depth buffer from (0,1538) to (1024,2307) (II) R128(0): Reserved depth span from (0,2306) offset 0x902000 (II) R128(0): Reserved 4096 kb for textures at offset 0xc0 (II) R128(0): Using XFree86 Acceleration Architecture (XAA) Maybe that will help. (this is at 1024 x 768 @ 16 bpp) --- --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ 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
[Dri-devel] Test
Just a testI think my e-mail might not be getting through --- 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
On Friday 06 June 2003 08:56 am, Ian Romanick wrote: Hmmm...that is odd. The resolution should only require 7.5MB for the front, back, and depth-buffers. That should leave about 8MB for textures, not 800KB. Are you sure it's at 16-bpp? ~800KB left is about rigth if you were running at 24-bpp. I'm sure (or my system is sure) it's 16 bpp. Switching to 1024 * 768 @ 16, I see only 4MB. Would this figure be on-card or system memory? --- 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
On Friday 06 June 2003 10:39 am, you wrote: On Friday 06 June 2003 08:56 am, Ian Romanick wrote: Hmmm...that is odd. The resolution should only require 7.5MB for the front, back, and depth-buffers. That should leave about 8MB for textures, not 800KB. Are you sure it's at 16-bpp? ~800KB left is about rigth if you were running at 24-bpp. I'm sure (or my system is sure) it's 16 bpp. Switching to 1024 * 768 @ 16, I see only 4MB. Would this figure be on-card or system memory? More stuff from the XFree logs: Found a line: (--) Depth 24 pixmap format is 32 bpp After XAA is loaded. Then we have the perhaps useful lines here: (II) R128(0): [drm] loaded kernel module for r128 driver (II) R128(0): [drm] created r128 driver at busid PCI:1:14:0 (II) R128(0): [drm] added 8192 byte SAREA at 0xd2a22000 (II) R128(0): [drm] mapped SAREA 0xd2a22000 to 0x40018000 (II) R128(0): [drm] framebuffer handle = 0xf800 (II) R128(0): [drm] added 1 reserved context for kernel (II) R128(0): [pci] 8192 kB allocated with handle 0xd3b17000 (II) R128(0): [pci] ring handle = 0xd3b17000 (II) R128(0): [pci] Ring mapped at 0x411b2000 (II) R128(0): [pci] Ring contents 0x (II) R128(0): [pci] ring read ptr handle = 0xd3c18000 (II) R128(0): [pci] Ring read ptr mapped at 0x4001a000 (II) R128(0): [pci] Ring read ptr contents 0x (II) R128(0): [pci] vertex/indirect buffers handle = 0xd3c19000 (II) R128(0): [pci] Vertex/indirect buffers mapped at 0x412b3000 (II) R128(0): [pci] Vertex/indirect buffers contents 0x (II) R128(0): [drm] register handle = 0xf0104000 (II) R128(0): [dri] Visual configs initialized (II) R128(0): CCE in BM mode (II) R128(0): Using 8 MB AGP aperture (II) R128(0): Using 1 MB for the ring buffer (II) R128(0): Using 2 MB for vertex/indirect buffers (II) R128(0): Using 1 MB for AGP textures (II) R128(0): Memory manager initialized to (0,0) (1024,3072) (II) R128(0): Reserved area from (0,768) to (1024,770) (II) R128(0): Largest offscreen area available: 1024 x 2302 (II) R128(0): Reserved back buffer from (0,770) to (1024,1538) (II) R128(0): Reserved depth buffer from (0,1538) to (1024,2307) (II) R128(0): Reserved depth span from (0,2306) offset 0x902000 (II) R128(0): Reserved 4096 kb for textures at offset 0xc0 (II) R128(0): Using XFree86 Acceleration Architecture (XAA) Maybe that will help. (this is at 1024 x 768 @ 16 bpp) --- 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] Re: [Dri-users] Snapshots missing libGL.so?
Managed to get my r128 working by lowering res/bpp (duh moment) One more thing I noticed: in my wide journeys in getting my DRI to work one of the things I did was to replace my distro-supplied (Mandrake 9.1) libGL.so with the one off the DRI download site. Now that I have working 3D accel, I find that I hit a segfault if I try to go back to the Mandrake libGL.so . Try replacing the Mandrake-supplied one, maybe it will work (and make sure the symbolic links get sorted out). Good luck --- 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] Re: [Dri-users] Snapshots missing libGL.so?
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 --- 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] Re: [Dri-users] Snapshots missing libGL.so?
Some relevant background: About a month ago, I clean-installed Mandrake 9.1 on the system. XFree + DRI works great, except for the fact that the r128 driver was an old system and evidently had problems with my PCI Rage128 card. So I downloaded the binary driver packages and installed, with the result of a segfault with anything hardware-accelerated (glxinfo, glxgears, tuxracer, etc.) So I tried compiling from scratch, etc, then doing the driver packages again. No luck as usual. Along the way I noticed that with the (Mandrake packaged) system came libGL.so.1.4.500 but with the self-compiled comes libGL.so.1.2 . Perhaps this could be a problem? --- 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] Re: [Dri-users] Snapshots missing libGL.so?
On Wednesday 04 June 2003 03:56 am, José Fonseca wrote: Please do: # gdb glxgears run ... bt And send the resulting backtrace to pinpoint the problem. Didn't notice you wanted the backtrace. Here it is (whole) [start] Starting program: /usr/X11R6/bin/glxinfo (no debugging symbols found)...[New Thread 16384 (LWP 2817)] name of display: :0.0 Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 2817)] 0x4046dee5 in driSetTextureSwapCounterLocation (heap=0x0, counter=0x8051c18) at texmem.c:584 584 texmem.c: No such file or directory. in texmem.c (gdb) (gdb) (gdb) (gdb) bt #0 0x4046dee5 in driSetTextureSwapCounterLocation (heap=0x0, counter=0x8051c18) at texmem.c:584 #1 0x4046e8a9 in r128CreateContext (glVisual=0xb410, driContextPriv=0x804d698, sharedContextPrivate=0x1) at r128_context.c:151 #2 0x4037329b in driCreateContext (dpy=0x804c618, vis=0x8051870, sharedPrivate=0x0, pctx=0x8054814, fbconfig=0x0) at dri_util.c:1007 #3 0x4008c756 in CreateContext (dpy=0x804c618, vis=0x8051870, shareList=0x0, allowDirect=1, contextID=0) at glxcmds.c:220 #4 0x4008c8ad in glXCreateContext (dpy=0x804c618, vis=0x8051870, shareList=0x0, allowDirect=1) at glxcmds.c:264 #5 0x08048fd0 in strcpy () #6 0x0804a1aa in strcpy () #7 0x402347f7 in __libc_start_main () from /lib/i686/libc.so.6 [end] --- 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] Bin. driver packages
Two questions... 1. Are the wrapped binary driver packages ever coming back? 2. It seems with an old one I got (binary driver packages) it was missing the libGL's so that once installed, (for example) glxinfo segfaults as it tries to load old libGL's. An oversight or purposeful omission? Thanks John --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
