I have found a workarround to use the `mga' driver again: I activated the kernel framebuffer interface in the device section of the X.org configuration file /etc/X11/xorg.conf (Option "UseFBDev" "true").
Section "Device"
Identifier "Matrox Graphics, Inc. MGA G200"
Driver "mga"
BusID "PCI:1:6:0"
Option "UseFBDev" "true"
Option "OldDmaInit" "True"
EndSection
I haven't tested it with the default ubuntu kernel, but with my self-compiled 2.6.18-rc6, I had to load the `matroxfb_base' before starting the X-Server. If you compile the matrox framebuffer into the kernel, you shouldn't notice any problems. If you have compiled it as a module, you should add `matroxfb_base' to your /etc/modules file.
I have found a workarround to use the `mga' driver again: I activated the kernel framebuffer interface in the device section of the X.org configuration file /etc/X11/xorg.conf (Option "UseFBDev" "true").
Section "Device"
Identifier "Matrox Graphics, Inc. MGA G200"
Driver "mga"
BusID "PCI:1:6:0"
Option "UseFBDev" "true"
Option "OldDmaInit" "True"
EndSection
I haven't tested it with the default ubuntu kernel, but with my self-compiled 2.6.18-rc6, I had to load the `matroxfb_base' before starting the X-Server. If you compile the matrox framebuffer into the kernel, you shouldn't notice any problems. If you have compiled it as a module, you should add `matroxfb_base' to your /etc/modules file.