Bug 132496 - xorg is missing driver modules that prevent it from being configured properly on the x86_64
xorg is missing driver modules that prevent it from being configured properly...
Product: Fedora
Classification: Fedora
Component: xorg-x11 (Show other bugs)
x86_64 Linux
medium Severity high
: ---
: ---
Assigned To: X/OpenGL Maintenance List
Depends On:
  Show dependency treegraph
Reported: 2004-09-14 00:13 EDT by Sam Williams
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-14 11:41:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Sam Williams 2004-09-14 00:13:39 EDT
Description of problem:
When trying to configure xorg 6.7.0 on Fedora Core 2 running on a dual
opteron machine I find that there is only the mga driver. I need to
get a 4 head matrox video card and a single head DV output matrox card
working. Sadly, the cards get confused because the only driver thats
available is the "mga". Missing is "mgag200 pci" and mgag400". These
are really critical for serious use and application. Also missing is
the "mga_hal" driver that should allow better resolution on the large
37" digital display.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:
System confusion when trying to drive the single head montitor.
Essentially, monitor0 on the quad card displays the content. This is
wrong and I believe it is correctable if the proper drivers were

Expected results:
The ability to have 4 21" lcd monitors driven with one card and a 37"
 Sharp LCD monitor joined through the use of xinerama. The behavior is
critical for an aircraft simulation systems.

Additional info:
Comment 1 Mike A. Harris 2004-09-14 03:07:38 EDT
Quad head Matrox hardware is not supported by the open source "mga"
driver.  The MGA "hallib" driver, is a proprietary driver which
is only available from Matrox's website.  The source code is not
available for hallib, and it is not shipped or supported by Red Hat.

You may wish to contact your hardware vendor directly, to see if they
have support for this hardware in Linux.

Setting status to "NOTABUG"
Comment 2 Sam Williams 2004-09-14 10:06:53 EDT
according to the man pages there should be other drivers associated
with Matrox. Specifically, "mga2064w", "mga1064sg",  "mga2164w", 
"mga2164w  agp",  "mgag100", "mgag200", "mgag200 pci", "mgag400",
"mgag550". These drivers aren't there!!!! I don't know why the people
responding to bugzilla reports latch onto something like mga_hal and
then close the ticket. If you had read the original ticket I was
complaining about the other drivers listed in the mga manpage. Now if
these were proprietary and available only from Matrox why would they
be listed at all????? Further, on the x86_64, they aren't available 
from Matrox either. The information should be explained somewhere.
I've tried to make this work for many days and now I'm hearing that
the documentation is misleading and has in fact  my time!!! That is
not a community minded attitude...

Further, if these drivers were not available with Fedora Core then why
would they be mentioned in the MANPAGES????? I know mga_hal is
proprietary, but according to the manpages the others are not, so
there is still a problem.... Its either with the manpages or the
missing drivers. I don't know why you would want to be evasive on this
problem. If its the manpage then change it and make a note to the
effect. If its the driver then please provide them. The bottom line is
that the problem should not be closed with a little brush off

If you use the aforementioned device names, you will get an error when
you fire up xorg on x86_64! So either change the manpages to reflect
the reality or supply drivers that support the hardware. User
implementation time is important. My project  is  a multi-million
dollar implementation which could really showcase Fedora to our
customers, however if these drivers aren't there then I'm not the only
one that gets a black-eye. Like I indicated, because of the bogus
manpage information for "mga" I have waste may days and will end  up
with a professional black-eye because I believed the documentation....
Please fix one documentation or drivers before this call is reclosed......
Comment 3 Kristian Høgsberg 2004-09-14 11:41:06 EDT
You need to read the man page again. "mga" is the driver name and is
the only valid value for the "Driver" field.  As for the names you
mention, they are *chipset* names that you may override by using the
"ChipSet" field in the "Device" section.  The driver should be able to
figure out the right chipset itself, though.

Finally, the man page explicitly states that to use dualhead output
for the G400, the mga_hal binary module is required.  You didn't
mention what kind of 4-head card you are trying to get working, but I
doubt that it is supported without the mga_hal module.

I'm closing the bug again.
Comment 4 Mike A. Harris 2004-09-14 12:45:39 EDT
Kristian is correct.  There is only one single driver for Matrox
video hardware included in X.Org X11 (or XFree86 also), which is
the "mga" driver.  The mga driver does not support all Matrox
hardware, and also does not support all variants of a particular
chipset.  It supports dualhead on Matrox G450 and G550, but not
on G400, and it does not support quad head on any Matrox hardware.

The proprietary Matrox driver comes with "hallib", which does
support dualhead on G400, and TVout and various other things
which should be documented somewhere on Matrox' website.

You've misunderstood what the "mga" manpage is stating.  While
the manpage indicates what chipsets are supported, the driver
does not support quad head hardware, and does not support
all variants of hardware Matrox has produced.

If you require additional assistance, you may perhaps find the
"xorg" mailing list useful.

Note You need to log in before you can comment on or make changes to this bug.