Re: Matrox G550 mga driver hangs system
Felix Miata wrote on Fri, 31 Mar 2017 18:17:09 -0400 >...So, a bug filing is apparently needed. I'd like you to file it OK, with great trepidation I've sent a report to the Debian Bug Tracking System, and received automatic acknowledgement of it as Bug#859423. Those interested should follow progress via www.debian.org/Bugs Tony
Re: Matrox G550 mga driver hangs system
Felix Miata wrote on Fri, 31 Mar 2017 02:22:10 -0400 >Your goal is to boot without Plymouth and without framebuffer, in >80x25 mode, to give Xorg the best possible chance to work as expect. >If Plymouth is installed, purge it. > >To proceed, hit the e key when the Grub menu appears, then remove any >line that says "load_video", and from any line that includes "video=" >or "vesa" or "vga=" or "quiet" or "splash", remove each whole such >string. Optionally, if the string "text" appears, remove it too. > >If all the above doesn't help, repeat it, but append "iomem=relaxed" to the >line >that included video and/or vesa and/or vga. OK, I did all that. More strictly I edited grub.cfg (I do have a rescue CD, so not a disaster if I broke grub.cfg) to comment out two calls of load_video, one in the menu entry for the boot and one in the preamble. The grub dialogue duly came up in 80x25 mode, encouragingly, but even with "iomem=relaxed" on the "linux" line I still had no joy when it came to starting X, alas. >Are you using a greeter, or logging in on a vtty and using startx or >equivalent? For this investigation I am using the latter, but normally I use lightdm and its greeter. I dispensed with lightdm here to simplify while trying to sort out what was going on. >What are the permissions on your /usr/bin/Xorg? -rwxr-xr-x >Doing something like 'journalctl -b -1 | grep -i failed' might be >useful. There is an awful lot of stuff making particular points of >interest hard to identify in the journal. It certainly is hard to find the needle in the haystack, even when as in my case much of it is gobbledegook. I've tried the suggestion but it didn't throw up anything very startling. One thing I have found is that although ctrl-alt-Fn has no observable effect when the xserver has jammed, ctrl-alt-del does provoke reboot, and the shutdown is reasonably orderly, as seen later in journalctl, so the underlying system is still flying. Thanks for all the other helpful instruction, even if it hasn't solved the problem. >It may be time for you to ask for help from the devs, using the >debian-devel mailing list or one of the freedesktop.org Xorg mailing >lists, or by filing a Debian bug. Yes, perhaps, if I can pluck up enough courage... Tony
Re: Matrox G550 mga driver hangs system
Felix Miata wrote on Wed, 29 Mar 2017 16:44:01 -0400 >> https://lists.debian.org/debian-user/2017/03/msg00895.html >Did you try other things suggested in that thread or the openSUSE bug >referenced there >https://bugzilla.opensuse.org/show_bug.cgi?id=1004453 ? To be honest, I'm way out of my depth in all that. I would be happy to try a particular experiment, given instructions... >e.g. disabling framebuffer? Er, how? xserver-xorg-video-fbdev isn't installed, nor for that matter xserver-xorg-video-modesetting. As I said, I'm out of my depth. >Which is yours PCIe, or AGP? Ah! One I can answer: AGP >Which WM/DE(s) is/are you trying to use? xfce4 and all that goes with it, but I don't think it's getting that far. As previously remarked, that stuff does all work with the vesa driver (achieved by tweaking xorg.conf). >Can you see any other clues than Xorg.0.log shows by running >'journalctl -b -1'? Nope, though I might possibly not recognise a clue... Apologies for uselessness (and also btw for wrecking the thread structure with a completely inadvertent small subject change, the genesis of which is a complete mystery to me). -- Tony Stoneley
Re: Matrox G550 + mga driver hangs system
to...@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
Re: Matrox G550 mga driver hangs system
Felix Miata suggested https://lists.debian.org/debian-user/2017/03/msg00895.html Thanks, Felix, but I had already seen that and tried it, to no great effect. I should have said so. Except that I see the log I filed doesn't say so. Here is (part of) one that does, and fails similarly- [ 6651.505] X Protocol Version 11, Revision 0 [ 6651.505] Build Operating System: Linux 3.16.0-4-amd64 i686 Debian [ 6651.505] Current Operating System: Linux tresco 4.9.0-2-686-pae #1 SMP Debian 4.9.13-1 (2017-02-27) i686 [ 6651.505] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-2-686-pae root=UUID=920046b5-b826-4c18-85a7-c986f9c15dfd ro quiet iomem=relaxed [ 6651.505] Build Date: 03 March 2017 03:15:35PM [ 6651.506] xorg-server 2:1.19.2-1 (https://www.debian.org/support) ... [ 6659.399] (EE) [ 6659.399] (EE) Backtrace: Apologies. Problem remains, however. -- Tony Stoneley, a...@ajms.ukfsn.org
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 @ 0xe400/33554432, 0xe600/16384, 0xe700/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
