XvMC is an extension for Xvideo that does things like motion compensation and iDCT in hardware. I'm not sure if that has anything to do with your problem. Also I'm not sure if the savage mx/ix cards even have hw motion comp, etc. that might have been added in the savage4 and 2000 cores. regardless, it seems to be disabled due to lack of memory.
a few other users have S3's driver working on on 4.2.0. read more here: http://probo.probo.com/pipermail/savage40/2003-July/date.html I have a savage/IX laptop, but someone is borrowing it at the moment so I don't have access to it, otherwise I'd help out with the driver. Alex --- Maximo <[EMAIL PROTECTED]> wrote: > Rick, > > I'm currently working on savage driver to make it work on > xfree86 > 4.3.0 but i didn't test it on xfree86 4.2.0 i only know that it > compiles on > that version. Looking at your log i found this message: > (--) SAVAGEInitMC: There is no enough memory! > (**) SAVAGE(0): XvMC is not enabled > > It's probably here where your problem lies. does your card has enough > > memory? People here probably will give you an better explanation than > i, so > i'll let them explain. > > bye. > Maximo > At 06:28 AM 30/8/2003, Rick Harris wrote: > >Hi all, > > > >Just a quick note to put the feelers out on how the S3 Savage DRI > Driver > >is coming along. > > > >Am particularly interested in getting this to work on a Savage/IX-MV > >chipset (M7 BIOS) found in many older laptops. > > > >These are my experiences thus far using the S3.zip package from > >http://www.linux.org.uk/~alan/S3.zip > > > >All drivers compile/install fine using 4.2.0 XFree source, 2.4.21 > >Kernel, 2.95.3 Gcc after editing the file > >xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/savage_drv.c > > and force it to use the do_munmap function that only takes 2 > > parameters not 3 (by commenting out #ifdef) > >AND > >running dos2unix on the source files in > >xc/programs/Xserver/hw/xfree86/drivers/savage/ > > > >No editing pte_offset to pte_offset_kernel was required. > > > >Nothing new there, it's all in this list's archives, but here comes > the > >juicy part. > > > > > >After starting X, it gives the errors: > >(EE) SAVAGE(0): DRI isn't enabled > >(EE) SAVAGE(0): Direct rendering disabled > > > >An 'lsmod' while X was running indicated that the savage.o DRM > kernel > >module isn't being used: > >Module Size Used by Not tainted > >savage 45312 0 > >agpgart 16048 1 > > > >A 'glxinfo' confirms this: > >direct rendering: No > > > >Looking at the lines 773 to 778 in > >/xc/programs/Xserver/hw/xfree86/drivers/savage/savage_driver.c > >It seems that if the Chipset used isn't either a S3_TWISTER or an > >S3_PROSAVAGE, then DRI is disabled. > >Deleting lines 773-774 & 777-778 bypassed the check & DRI is now > forced. > > > >startx > > > >The desktop is garbled, only the bottom inch of it is visible, & has > >been re-located to the top of the screen. Below this is just > blackness, > >like the whole screen has been shifted upwards. > >Here is a pic of what the garbledness looks like, you can see the > whole > >desktop in this picture however -> > >http://mightylegends.zapto.org/downloads/S3_driver/root.jpeg > >Switching to a console VT & then back to X fixes the problem. > > > >The previous '(EE) DRI disabled' errors have disappeared to be > replaced > >with one new one: > >(EE) SAVAGE(0): Memory manager initialization to (0,0) (1024,-1) > failed. > > > >Running 'glxgears' kills X with the error: > >X connection to :0.0 broken (explicit kill or server shutdown) > >xterm: fatal IO error 32 (Broken pipe) or KillClient on X server > ":0.0" > >login: fatal IO error 32 (Broken pipe) or KillClient on X server > ":0.0" > >xterm: fatal IO error 32 (Broken pipe) or KillClient on X server > ":0.0" > >xinit: fatal IO error 32 (Broken pipe) or KillClient on X server > ":0.0" > > > > > >This is where I've hit a wall on what it could be, or how in heck I > go > >about debugging it. Maybe problems within > >/xc/programs/Xserver/hw/xfree86/drivers/savage/savage_accel.c > >where X's Memory Manager appears to be set-up, or something further > up > >the chain. > > > >I'd be willing to hear from anyone who has come up against this, can > >help, or of similar works to get DRI supported under IX-MV chipsets. > >Do let me know if I maybe going completely the wrong way about this. > > > __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
