sigh, X won't start after upgrading to newest X packages..

[[P]Diablos]

I'm running debian woody with the 2.4.13 kernel I compiled from source, and today I just did a standard apt-get upgrade. I ran into a little problem getting the new X packages 4.1.0-8 working because I remeoved xdm from my /etc/init.d/ folder and that was preventing xdm and thus x-windows-system for setting up their new versions. Anyways, I put xdm back in there, and the upgrade goes as normal after that. I thought everything was working, but boy was I wrong. I can't startx anymore, because when I do I get a ton of errors with the last, most noticeable ones, being this:

(II) MGA(0): Not using default mode "1280x1024" (Hsync out of range)
(This above error is outputted several times for different, higher, resolutions, and my xf86config file is setup for 1152x864, so I have no idea why this message is displayed..)
Symbol fbPictureInit from module /usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Symbol XAA_888_plus_PICT_a8_to_8888 from module /usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved!
Fatal server error:
Caught signal 11. server is aborting.

Can anyone tell me what the deal is? I am so angry at this, everything was going great on my box, had 3d acceleration going, a new kernel up and running, and then a standard no brainer apt-get upgrade destroys my X. thanks for any help..

[[P]Diablos]

nm i got it fixed, turned out after upgrading my x packages my mga-made mga_drv.o and mga_dri.so files were overwritten and returned back to the included X 4.1.0 ones. Just reinstalled the mga made ones and all is good again