On Sun, 22 Feb 2004 01:20:37 -0500
Chris King <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I've successfully gotten 3D rendering working with my ProSavage DDR chip
> using the savage-2-0-0 CVS from 2004-21-02, but I've encountered a
> couple of problems:
>
> 1) 2D rendering is EXTREMELY slow. Almost as if it were using the Vesa
> driver. I'd previously used the savage40 driver with no problems - has
> this been merged into CVS yet, or should I get Alex's driver?
I have a ProSavageDDR too. No problems here. But I havn't tried 32bpp
yet. How does it work with 16bpp?
>
> My X log has this to say:
> (EE) SAVAGE(0): Memory manager initialization to (0,0) (1024,478) failed
> (==) SAVAGE(0): Backing store disabled
I get this in my X log:
(II) SAVAGE(0): Memory manager initialized to (0,0) (1024,1791)
(II) SAVAGE(0): Largest offscreen area available: 1024 x 1023
(II) SAVAGE(0): Reserved back buffer at offset 0x380000
(II) SAVAGE(0): Reserved depth buffer at offset 0x500000
(II) SAVAGE(0): Reserved 25980 kb for textures at offset 0x680000
(II) SAVAGE(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Indirect CPU to Screen color expansion
Solid Lines
Image Writes
Offscreen Pixmaps
Setting up tile and stipple cache:
28 128x128 slots
7 256x256 slots
So you're probably running out of memory and XAA is left disabled. Try
16bpp as suggested above or maybe you can setup more shared video memory
in the BIOS setup. FYI, DRI requires a lot of video memory for back and
depth buffers. That would explain why this configuration worked with
Tim's driver but fails now.
>
> And /proc/mtrr reads thusly:
> reg00: base=0x00000000 ( 0MB), size= 256MB: write-back, count=1
> reg01: base=0x0f800000 ( 248MB), size= 8MB: uncachable, count=1
> reg02: base=0xd8000000 (3456MB), size= 8MB: write-combining, count=2
> reg03: base=0xde000000 (3552MB), size= 16MB: write-combining, count=1
> reg04: base=0xdc000000 (3520MB), size= 32MB: write-combining, count=1
> reg05: base=0xda000000 (3488MB), size= 32MB: write-combining, count=1
>
> X is running at 1024x768x32.
>
> 2) Fullscreen 3D stuff (TuxRacer) creates snow; windowed stuff creates
> both snow and blinking artifacts on the lower half of the screen (it
> looks almost as if some double-buffered memory is being overwritten). Is
> this 'normal' (being in development), or is something wrong with my setup?
As Alex pointed out the driver does very little checking when it sets up
memory for 3D acceleration. On an 8MB SavageIX it even caused lockups
here if I had the resolution set too high. The driver should probably do
better checking and fail if there is not enough memory. For now try
making more memory available (see above).
>
> Thanks!
>
> - Chris K
>
Regards,
Felix
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
