Description of Problem: The .spec file contains a line "UseMatroxHal NO", which disables ability to use Matrox's mga_hal_drv.o module. Unfortunately, HAL module is *required* if one needs to use more than one G450 (e.g. G450AGP+G450PCI) or 2nd head of G400. (See http://www.xfree86.org/pipermail/xpert/2001-September/011381.html for details of testing on Red Hat's 4.0.3, and 4.1 gives the same results.) What's so bad in the HAL module? Sure, it slows down X startup, but since Red Hat doesn't ship mga_hal_drv.o itself, "UseMatroxHal YES" is harmless. Otherwise those who know what they are doing have to replace the driver itself (mga_drv.o). I see no reason for it. Version-Release number of selected component (if applicable): 4.1.0-3 How Reproducible: 100%
Deferring for future consideration.
It is just as easy for a user to install a replacement mga_drv.o along with hallib as it is to just install hallib. Matrox's hallib really should be used with their latest driver source anyway. Red Hat doesn't support systems using hallib, and since there's no major benefit to having the default driver allow hallib - when it is just as easy to install both files simultaneously, I don't see the benefit here to enabling hallib support on our side - neither to Red Hat, nor to our users. Matrox can package up an RPM or tarball of the necessary bits quite easily. Their mga driver can even co-reside with the one that we ship, simply by using ModulePath directives in the config file. I believe this gives a lot more flexibility, as it allows one to use both drivers, and switch between them. If a user has a problem with the Matrox driver and hallib, they can disable it, and use our driver to try and reproduce the problem. Closing WONTFIX