Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #179574 > unrolled thread

Matrox G550 + mga driver hangs system

Back to article view | Back to linux.debian.user

Contents

  Matrox G550 + mga driver hangs system "Tony Stoneley" <ajms@ajms.ukfsn.org> - 2017-03-29 16:10 +0200
    Re: Matrox G550 + mga driver hangs system <tomas@tuxteam.de> - 2017-03-29 16:40 +0200
      Re: Matrox G550 + mga driver hangs system "Tony Stoneley" <ajms@ajms.ukfsn.org> - 2017-03-29 22:00 +0200
    Re: Matrox G550 + mga driver hangs system Felix Miata <mrmazda@earthlink.net> - 2017-03-29 17:30 +0200
    Re: Matrox G550 + mga driver hangs system Felix Miata <mrmazda@earthlink.net> - 2017-03-30 11:30 +0200
    Re: Matrox G550 + mga driver hangs system kamaraju kusumanchi <raju.mailinglists@gmail.com> - 2017-04-02 17:20 +0200

#179574 — Matrox G550 + mga driver hangs system

I'm trying an experimental upgrade from stable to testing on an
elderly system with a Matrox Millenium G550 graphics adaptor plugged
directly into the motherboard, using the mga driver, and have run into
a brick wall with the xserver. When started, eg with startx, the
system immediately freezes and the only escape seems to be reboot. In
particular ctrl-alt-Fn has no effect in this state, which makes
diagnosis tricky. Any help or suggestions would be appreciated.

[Mandatory declaration, having read the rubrics: I am not subscribed
to this list (for fear of drowning). I just read the web archive. I
post this with some trepidation...]

I feel reasonably confident that the problem lies in the mga driver,
not least because the vesa driver works ok, to my great relief, but
conceivably a bug elsewhere is being triggered by mga. I am using
xserver-xorg-legacy. I note the earlier thread "Matrox G550 - MGA X
server fails", but whether this is part of the same story I am unsure.

Backtracking to relic versions of xserver-xorg-video-mga, which just
happen to be lying around in the apt cache, suggests that the trouble
started somewhere around version 1.4-1 or 1.4-2, but the dependencies
on other bits of xorg make such backtracking a clumsy and difficult
process and I can't be more precise about it, though I've tried. I
have a partition reserved for such adventures so that when "testing"
graduates to "stable" it's not too much of a shock, but mostly I fly
with stable and I'm no expert in this area.

A severely trimmed version of /var/log/Xorg.0.log follows. The whole
affair is 616 lines, which seems excessive for an initial posting.
This is with the fully up-to-date testing distribution, in particular
with xserver-xorg-video-mga version 1:1.6.5-1.

X.Org X Server 1.19.2
Release Date: 2017-03-02
 ...
[  3311.142] Current Operating System: Linux tresco 4.9.0-2-686-pae #1 SMP Debian 4.9.13-1 (2017-02-27) i686
[  3311.142] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-2-686-pae root=UUID=920046b5-b826-4c18-85a7-c986f9c15dfd ro quiet
 ...
[  3311.146] (**) |   |-->Device "Matrox Graphics, Inc. MGA G550 AGP"
 ...
[  3311.149] (++) using VT number 2

[  3311.157] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_36
[  3311.159] (--) PCI:*(0:1:0:0) 102b:2527:102b:0f84 rev 1, Mem @ 0xe4000000/33554432, 0xe6000000/16384, 0xe7000000/8388608, BIOS @ 0x????????/131072
[  3311.159] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[  3311.159] (II) LoadModule: "ddc"
[  3311.159] (II) Module "ddc" already built-in
[  3311.159] (II) LoadModule: "dri"
[  3311.159] (II) Module "dri" already built-in
[  3311.159] (II) LoadModule: "extmod"
[  3311.159] (II) Module "extmod" already built-in
[  3311.159] (II) LoadModule: "glx"
[  3311.160] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  3311.249] (II) Module glx: vendor="X.Org Foundation"
[  3311.249] 	compiled for 1.19.2, module version = 1.0.0
[  3311.249] 	ABI class: X.Org Server Extension, version 10.0
[  3311.249] (II) LoadModule: "int10"
[  3311.249] (II) Loading /usr/lib/xorg/modules/libint10.so
[  3311.258] (II) Module int10: vendor="X.Org Foundation"
[  3311.258] 	compiled for 1.19.2, module version = 1.0.0
[  3311.258] 	ABI class: X.Org Video Driver, version 23.0
[  3311.258] (II) LoadModule: "vbe"
[  3311.258] (II) Loading /usr/lib/xorg/modules/libvbe.so
[  3311.272] (II) Module vbe: vendor="X.Org Foundation"
[  3311.272] 	compiled for 1.19.2, module version = 1.1.0
[  3311.272] 	ABI class: X.Org Video Driver, version 23.0
[  3311.272] (II) LoadModule: "mga"
[  3311.272] (II) Loading /usr/lib/xorg/modules/drivers/mga_drv.so
[  3311.302] (II) Module mga: vendor="X.Org Foundation"
[  3311.302] 	compiled for 1.19.1, module version = 1.6.5
[  3311.302] 	Module class: X.Org Video Driver
[  3311.302] 	ABI class: X.Org Video Driver, version 23.0
[  3311.302] 	ABI class: X.Org Video Driver, version 23.0
[  3311.315] (II) MGA: driver for Matrox chipsets: ... mgag550
 ...
  lots of stuff that looks perfectly normal until -
[  3316.209] (II) xfree86: Adding drm device (/dev/dri/card0)
[  3316.211] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 26 paused 1
[  3316.211] (EE) Error systemd-logind returned paused fd for drm node
[  3316.211] (II) systemd-logind: releasing fd for 226:0
[  3316.213] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
 ...  
  lots more stuff, file ending with -
[  3316.234] (EE) 
[  3316.234] (EE) Backtrace:

Perhaps there was more that never got flushed to disk, but who knows.
More of the elided material available on request of course, together
with any other info.

Tony

[toc] | [next] | [standalone]

#179576

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, Mar 29, 2017 at 02:36:55PM +0100, Tony Stoneley wrote:
> I'm trying an experimental upgrade from stable to testing on an
> elderly system with a Matrox Millenium G550 graphics adaptor plugged
> directly into the motherboard, using the mga driver, and have run into
> a brick wall with the xserver. When started, eg with startx, the
> system immediately freezes and the only escape seems to be reboot. In
> particular ctrl-alt-Fn has no effect in this state, which makes
> diagnosis tricky. Any help or suggestions would be appreciated.

Sorry I can't help you much with X, but perhaps one remark/question
which might be of interest to those who can:

is the system totally dead or just the display? Can you ping (or even
ssh) your box? In case you have no network, the effort of setting one
up (locally) might well pay off.

> [Mandatory declaration, having read the rubrics: I am not subscribed
> to this list (for fear of drowning). I just read the web archive. I
> post this with some trepidation...]

No worries :-)

> Perhaps there was more that never got flushed to disk, but who knows.
> More of the elided material available on request of course, together
> with any other info.

Another thing you could clear up if you can access your box through
the back door.

Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAljbxOAACgkQBcgs9XrR2kbSDQCdGuzy1LMJNZaiYjOERJqBwnR2
9HIAnRP5PvDpfH0FGoWV9wEPaV7yxzVx
=wMcd
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#179586

tomas@tuxteam.de wrote on Wed, 29 Mar 2017 16:29:52 +0200
>is the system totally dead or just the display? Can you ping (or even
>ssh) your box? In case you have no network, the effort of setting one
>up (locally) might well pay off.

I wish I could, but alas I only have one PC here, albeit on a small
LAN, connected to the world by a portmapping link. A new machine is on
my wish list. Maybe I will have to bring Christmas forward, or lean on
a kindly friend to loan a machine...

As to the underlying question, I think the system is still somewhat
alive, since the disc active light flickers now and then.

Tony

[toc] | [prev] | [next] | [standalone]

#179577

Tony Stoneley composed on 2017-03-29 14:36 (UTC+0100):

> I'm trying an experimental upgrade from stable to testing on an
> elderly system with a Matrox Millenium G550 graphics adaptor plugged
> directly into the motherboard, using the mga driver, and have run into
> a brick wall with the xserver. When started, eg with startx, the
> system immediately freezes and the only escape seems to be reboot. In
> particular ctrl-alt-Fn has no effect in this state, which makes
> diagnosis tricky. Any help or suggestions would be appreciated.

> [Mandatory declaration, having read the rubrics: I am not subscribed
> to this list (for fear of drowning). I just read the web archive....

Seriously?
Date: Thu, 23 Mar 2017 11:11:52 -0400
Subject: Re: Matrox G550 - MGA X server fails
https://lists.debian.org/debian-user/2017/03/msg00895.html
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#179596

I tried to net install Stretch to my MGA550 machine, but kept getting segfaults 
trying to configure network. So I restored a backup image of Jessie from another 
machine to my MGA550 machine. It worked normally, so I dist-upgraded it to 
Stretch on vtty 3. When done, I logged into :1 using startx with a good TDE 
session. Then I exited and logged in in the greeter. That worked too. I logged 
out, then tried to log back in, and got a black screen and no keyboard response.

I rebooted, and tried various cmdline options and switching back and forth 
between graphical and multi-user targets for over an hour. Sometimes I'd get 
black screen and no keyboard response. Sometimes X would start and immediately 
exit. Sometimes a segfault would show up in dmesg. Sometimes a segfault would 
show up in Xorg.0.log. I had a bug almost ready to file before figuring out 
using multi-user.target how to reliably get a working TDE session using this 
kernel cmdline:
root=LABEL=SS25deb9 ipv6.disable=1 net.ifnames=0 noresume vga=791 iomem=relaxed

I'm actually starting via a script, /usr/local/bin/tdestart:
#!/bin/sh
WINDOWMANAGER=/opt/trinity/bin/starttde startx

xserver-xorg-legacy is installed, and /usr/bin/Xorg perms are set to 4711.

Adding drm.debug=1 or drm.debug=0x0e to cmdline causes black screen, no KBD 
response, and the following in dmesg & the journal:
kernel: mtrr: no MTRR for f4000000,2000000 found
kernel: [drm] Initialized
kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
kernel: [drm] No driver support for vblank timestamp query.
kernel: [drm] Initialized mga 3.2.1 20051102 for 0000:01:00.0 on minor 0
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#179710

On Wed, Mar 29, 2017 at 9:36 AM, Tony Stoneley <ajms@ajms.ukfsn.org> wrote:
>
> A severely trimmed version of /var/log/Xorg.0.log follows. The whole
> affair is 616 lines, which seems excessive for an initial posting.
> This is with the fully up-to-date testing distribution, in particular
> with xserver-xorg-video-mga version 1:1.6.5-1.

In Xorg.0.log, the errors are logged with (EE) prefix, so the output of

grep EE /var/log/Xorg.0.log

would be useful in documenting the problem. In your case, you already
gave the relevant information but thought I would point it out in case
you are not aware of it.

raju
-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web