Xorg fails to load correct video driver for Matrox G550 & G450 video cards.

[Luke Yelavich]

 affects ubuntu/xserver-xorg-video-mga

When attempting to load GDM on latest jaunty, xorg either fails to make use of the Matrox video driver, or the Matrox video driver is for some reason unable to identify the card in use. The
motherboard is an Abit BP6 with a Matrox G550 AGP video card (see lspci output)

Attached are the dmesg log, Xorg logs, and lspci output.

[lspci]
01:00.0 VGA compatible controller [0300]: Matrox Graphics, Inc. MGA G550 AGP [102b:2527] (rev 01)
     Subsystem: Matrox Graphics, Inc. Device [102b:0f84]

[Antti Ruonakoski (anttimr)]

Yes. I got the same result and Xorg.0.log with Jaunty Alpha live daily-build 2009-02-17. The video card is MGA 450 AGP. I get kicked into the low resolution mode / vesa driver.
lspci attached.

[Antti Ruonakoski (anttimr)]

WORKAROUND:

Enable textured xv option in /etc/X11/xorg.conf

Section "Device"
....
Option "TexturedVideo" "True"

Now Xserver doesn't fail to start. Video acceleration performance is, as far as I can see, not hurt. Maybe driver should be patched to enable TexturedVideo by default?

[Mr. Captcha (mr-captcha)]

Binary package hint: xserver-xorg-video-mga

I have updated my ubuntu for testing to nearly full jaunty (kernel is still 2.6.27-12 but this is an other bug)

In my computer runs a MGA 400 Card . If I do not install the nvidia-glx-96 driver, the X-Server will not boot into gnome but reports an error and only vesa driver works. But if I install the nvidia-glx-96 and nvidia-common (not testet if it still runs without) then the full gnome desktop will appear. But glxinfo reports:

:~$ glxinfo
name of display: :0.0
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't find RGB GLX visual or fbconfig

Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
3 GLXFBConfigs:
   visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav
 id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat
----------------------------------------------------------------------
Segmentation fault (core dumped)

all OpenGL-using programs will not work.

mga-vid-sourec and mga-vid-common are not installed (will also not run with)

If you need more files please contact me.

[Luke Yelavich (themuso)]

Antti, this workaround doesn't appear to work for me, I still get several flickers with several attempts, and then dropped at failsafe, this is with a G550 card.

[Bryce Harrington (bryce)]

[This is an automatic notification.]

Hi Luke,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 322184

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 322184 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/322184

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.