From: Dan O. <do...@ra...> - 2000-09-22 20:27:22
|
Hello, After a hard time installing DRI (mostly due to my own errors, and not the documentation) I am now having problems getting the 3D acceleration to work. Last night, the mga.o module would not load. I was getting an error message about not being able to allocate memory for it. I ran 'strip mga.o' (even though I did not compile with debugging symbols), which reduced the size of the module and allowed me to 'insmod' it properly. Please observe: pc045106:/home/dolson# lsmod Module Size Used by mga 100200 0 (unused) The '(unused)' bothers me a little, but not as much as it not loading did. :) Now, I start my DRI X server, and still get Mesa Indirect rendering. Looking at the log, I see these messages: -------------------------------------------- (==) MGA(0): Write-combining range (0xe4000000,0x1000000) (--) MGA(0): 16 DWORD fifo (==) MGA(0): Default visual is TrueColor (II) MGA(0): [drm] bpp: 16 depth: 16 (II) MGA(0): [drm] Sarea 2176+632: 2808 (0): [drm] drmOpen failed (EE) MGA(0): [drm] DRIScreenInit Failed (II) MGA(0): Using 9885 lines for offscreen memory. (II) MGA(0): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits Solid filled rectangles Solid filled trapezoids 8x8 mono pattern filled rectangles 8x8 mono pattern filled trapezoids Indirect CPU to Screen color expansion Screen to Screen color expansion Solid Lines Dashed Lines Scanline Image Writes Offscreen Pixmaps Setting up tile and stipple cache: 32 128x128 slots 32 256x256 slots 16 512x512 slots (==) MGA(0): Backing store disabled (==) MGA(0): Silken mouse enabled (II) MGA(0): direct rendering disabled (II) MGA(0): Using overlay video --------------------------------------- So then, is this enough information for anyone to determine just what my problem is? Thank you very much. -- Dan Olson (theoddone33) "It takes a big man to cry, and an even bigger man to laugh at that man" |