Matrox G550/AGP on AMD64 debian/etch, Xorg 7.1.1

[Jörg]

Hi,

thank you all for continuing the good work. I came over here after discovering that the relevatn Matrox Support Forum has been shut down.

A fresh reboot yesterday uncovered that opengl stopped working (again). Same old story - but this time I am out of luck - the "howtos" are gone 8-(

Hardware:
Matrox MGA 550 AGP (rev 01)
AMD64

Software:
Debian etch (testing)
xserver-xorg 7.1.0-8

After reading this post I removed all previous workaround from my xorg.conf and updated the matrox driver from 4.4.0 to 4.4.1 using the installer from this site:

The relevant sections of my xorg.conf are now:

Section "Module"
Load "dbe"
Load "ddc"
Load "drm"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
# Load "i2c"
# Load "bitmap"
# Load "int10"
# Load "type1"
# Load "vbe"
EndSection

#Section "Extensions"
# Option "Composite" "Enable"
#EndSection

Section "Device"
Identifier "Standardgrafikkarte"
Driver "mga"
BusID "PCI:1:0:0"
# VideoRam 32768
# Option "NoHal" "False"
# Option "AGPSize" "128"
# Option "AGPMode" "4"
# Option "OverclockMem" "true"
# Option "XAANoOffscreenPixmaps" "true"
# Option "mtrr" "on"
# Option "AGPFastWrite" "on"
# Option "OldDmaInit" "true"
EndSection

A new ServerFlags section has been added:
Section "ServerFlags"
Option "IgnoreABI" "True"
EndSection

Xserver Flags were changed using gdmsetup:
/usr/bin/X -dpi 96 -audit 0 -ignoreABI

glxinfo returns:
direct rendering: No
OpenGL vendor string: Mesa project: http://www.mesa3d.org

The relevant Xorg.0.log entry is:
(EE) MGA(0): [drm] Could not boot-strap DMA (-12)

Now, I would like to re-enable opengl. I tried uncommenting my old settings above and didn't succeed (also other combinations).

Any hint would be highly appreciated.

Jörg


Logs:

dmesg reports:
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: reserved bits set (8) in mode 0x1f00021c. Fixed.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
[drm:mga_do_agp_dma_bootstrap] *ERROR* Unable to allocate 0MB AGP memory
[drm:mga_do_pci_dma_bootstrap] *ERROR* Unable to allocate primary DMA region: -22
[drm:drm_unlock] *ERROR* Process 6270 using kernel context 0


Xorg.0.log (partial):
(**) Option "IgnoreABI" "True"
(**) Ignoring ABI Version
[..]
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.3
X.Org Video Driver: 1.0
X.Org XInput driver : 0.6
X.Org Server Extension : 0.3
X.Org Font Renderer : 0.5
[..]
(--) PCI:*(1:0:0) Matrox Graphics, Inc. MGA G550 AGP rev 1, Mem @ 0xfa000000/25, 0xfe9fc000/14, 0xfe0
00000/23, BIOS @ 0xfe9c0000/17
[..]
(II) LoadModule: "drm"
(II) Loading /usr/lib/xorg/modules/linux/libdrm.so
(II) Module drm: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) Loading sub module "drm"
(II) LoadModule: "drm"
(II) Reloading /usr/lib/xorg/modules/linux/libdrm.so
[..]
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "mga"
(II) Loading /usr/lib/xorg/modules/drivers/mga_drv.so
(II) Module mga: vendor="Matrox Graphics Inc. - x86_64 - Release v4.4.0"
compiled for 7.0.0, module version = 1.2.1
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 0.8
(WW) module ABI major version (0) doesn't match the server's version (1)
[..]
(II) MGA: driver for Matrox chipsets: mga2064w, mga1064sg, mga2164w,
mga2164w AGP, mgag100, mgag100 PCI, mgag200, mgag200 PCI,
mgag200 SE A PCI, mgag200 SE B PCI, mgag400, mgag550
(II) Primary Device is: PCI 01:00:0
(--) Chipset mgag550 found
[..]
(--) MGA(0): Chipset: "mgag550"
(II) Loading sub module "mga_hal"
(II) LoadModule: "mga_hal"
(II) Loading /usr/lib/xorg/modules/drivers/mga_hal_drv.so
(II) Module mga_hal: vendor="Matrox Graphics Inc. - x86_64 - Release v4.4.0"
compiled for 7.0.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.8
(WW) module ABI major version (0) doesn't match the server's version (1)
(==) MGA(0): Matrox HAL module used
(**) MGA(0): Depth 24, (--) framebuffer bpp 32
(==) MGA(0): RGB weight 888
(==) MGA(0): Using AGP 1x mode
(--) MGA(0): Linear framebuffer at 0xFA000000
(--) MGA(0): MMIO registers at 0xFE9FC000
(--) MGA(0): Pseudo-DMA transfer window at 0xFE000000
(--) MGA(0): BIOS at 0xFE9C0000
(II) Attempted to read BIOS 64KB from /sys/bus/pci/devices/0000:01:00.0/rom: got 36KB
(--) MGA(0): Video BIOS info block at offset 0x07D20
(--) MGA(0): VideoRAM: 32768 kByte
[..]
(II) MGA(0): VESA VBE DDC supported
(II) MGA(0): VESA VBE DDC Level 2
(II) MGA(0): VESA VBE DDC transfer in appr. 1 sec.
(II) MGA(0): VESA VBE DDC read successfully
(II) MGA(0): VBE DDC Monitor info: 0x7e00b0
(II) MGA(0): Manufacturer: IVM Model: 385c Serial#: 1
(II) MGA(0): Year: 2002 Week: 45
(II) MGA(0): EDID Version: 1.3
(II) MGA(0): Analog Display Input, Input Voltage Level: 0.714/0.286 V
[..]
(==) MGA(0): Default visual is TrueColor
(II) MGA(0): [drm] bpp: 32 depth: 24
(II) MGA(0): [drm] Sarea 2200+664: 2864
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: Searching for BusID pci:0000:01:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: drmOpenMinor returns 8
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
(II) MGA(0): [drm] DRM interface version 1.2
(II) MGA(0): [drm] created "mga" driver at busid "pci:0000:01:00.0"
(II) MGA(0): [drm] added 8192 byte SAREA at 0x10010000
(II) MGA(0): [drm] mapped SAREA 0x10010000 to 0x2aaaaade7000
(II) MGA(0): [drm] framebuffer handle = 0xfa000000
(II) MGA(0): [drm] added 1 reserved context for kernel
(EE) MGA(0): [drm] Could not boot-strap DMA (-12)
(II) MGA(0): [drm] removed 1 reserved context for kernel
(II) MGA(0): [drm] unmapping 8192 bytes of SAREA 0x10010000 at 0x2aaaaade7000
(II) MGA(0): Using 3328 lines for offscreen memory.
(II) MGA(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
Solid filled trapezoids
8x8 mono pattern filled rectangles
8x8 mono pattern filled trapezoids
Indirect CPU to Screen color expansion
Screen to Screen color expansion
Solid Lines
Dashed Lines
Scanline Image Writes
Offscreen Pixmaps
Setting up tile and stipple cache:
32 128x128 slots
20 256x256 slots
6 512x512 slots
(==) MGA(0): Backing store disabled
(==) MGA(0): Silken mouse enabled
(**) Option "dpms"
(**) MGA(0): DPMS enabled
(II) MGA(0): Using overlay video
(WW) MGA(0): Direct rendering disabled
(==) RandR enabled
(EE) AIGLX: Screen 0 is not DRI capable
(II) Loading local sub module "GLcore"
(II) LoadModule: "GLcore"
(II) Loading /usr/lib/xorg/modules/extensions/libGLcore.so
(II) Module GLcore: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) GLX: Initialized MESA-PROXY GL provider for screen 0

[Jörg]

I'll take that back... direct rendering _will_ be enabled if I revert to the following setup:

Section "Device"
Identifier "Standardgrafikkarte"
Driver "mga"
BusID "PCI:1:0:0"
VideoRam 32768
# Option "NoHal" "False"
Option "AGPSize" "128"
Option "AGPMode" "4"
# Option "OverclockMem" "true"
# Option "XAANoOffscreenPixmaps" "true"
Option "mtrr" "on"
# Option "AGPFastWrite" "on"
Option "OldDmaInit" "true"
EndSection

However, Opengl seems to be broken - all I get is a black screen...
doh 8-(

[tuxx-home.at]

I came over here after discovering that the relevatn Matrox Support Forum has
been shut down.

Great, welcome Jörg!
May I ask you how you found this forum?

[drm:mga_do_agp_dma_bootstrap] *ERROR* Unable to allocate 0MB AGP memory
[drm:mga_do_pci_dma_bootstrap] *ERROR* Unable to allocate primary DMA region: -22
[drm:drm_unlock] *ERROR* Process 6270 using kernel context 0

That looks strange... Have you also upgraded your kernel?
Is the mga kernel module loaded?

Could you please attach (yes, attach, attachments should now work ) your
complete xorg.conf and Xorg.0.log file here as well as the whole dmesg
output, please?

[Jörg]

Great, welcome Jörg!
May I ask you how you found this forum?

sure, driver failed -> seek for help at matrox forum -> find out that only the mga forum has been closed -> found credits for "David E. Anderson" in update-install.sh of old installation -> google -> find tuxx-home.at

That looks strange... Have you also upgraded your kernel?
Is the mga kernel module loaded?

nope, still with 2.6.16 due to some home-grown driver. Kernel driver is loaded. I believe the last apt-get upgrade between 29th of Dec and 2nd of January caused the problem.

Could you please attach (yes, attach, attachments should now work ) your
complete xorg.conf and Xorg.0.log file here as well as the whole dmesg
output, please?

here we go...

Jörg

[tuxx-home.at]

nope, still with 2.6.16 due to some home-grown driver.

May I ask which one this is?

OK, according to your logfiles, what you are experiencing is the known
DRI
unlock bug.

DRIUnlock called when not locked

This bug has been fixed by the Xorg version of the mga driver, but has not
been yet incorporated in the official mga driver, which is - as so many other
things - on my todo list.

Please give me some minutes, I'll try to do something about it....

BTW:

(WW) MGA(0): config file vrefresh range 43-60Hz not within DDC vrefresh ranges.

Please specify the correct timing values for your displays which are:

Code: Select all

VertRefresh 48-78
HorizSync 28-64


[Jörg]

nope, still with 2.6.16 due to some home-grown driver.

May I ask which one this is?

offtopic: actually two drivers

First one driver for some fancy usb MSP430 development tool (EZ430). Not loaded at the moment. 2.6.17 changed some internal structures for serial devices and I have no idea why debian choose to go with a newer kernel than 2.6.16 (which is in "stable" maintainance mode).

Second another serial driver for a time critical homebrew addon that I didn't bother to check wether it works using 2.6.17 as driver #1 failed using similar structures. Also unloaded most of the time.

OK, according to your logfiles, what you are experiencing is the known
DRI unlock bug.
[..]
DRIUnlock called when not locked

cannot remember having this before... please note the last lines of the current Xorg.0.log where I tried to launch glxgears (that failed).

Please specify the correct timing values for your displays which are:

Thanks - I never changed it because I sometimes use different displays. One old CRT freaks out with high refresh rates and I currently use a LCD. I changed it anyway, though...

Thank you in advance, Alexander

Jörg

[edit: fixed most miserable typos]

[tuxx-home.at]

cannot remember having this before... please note the last lines of the current
Xorg.0.log where I tried to launch glxgears (that failed).

This bug seems to be only present in newer Xorg versions. Maybe your Xorg
version has been upgraded during the last `apt-get upgrade`?

However, could you please give this one a try?
[temporary download link to 4.4.2 prerelease removed]

[Jörg]

However, could you please give this one a try?
[temporary download link to 4.4.2 prerelease removed]

won't cut it - I'm running x86-64

[tuxx-home.at]

OK
Then let me please compile the 64bit driver on your system, ok?

[Jörg]

OK
Then let me please compile the 64bit driver on your system, ok?

go for it... ssh/sftp is your friend


UPDATE: fixed - Thanks a lot!

[tuxx-home.at]

Great, check out the download section of this forum for the brandnew 4.4.2
version of the mga driver