Display issues on Debian Buster

pompopom · 05-07-2020, 02:38 AM

Hi everyone,

First post here.
Not exactly a newbie in linux, but I'll never call myself a specialist or guru. I usually work on machines without GUI. So... ok let's go.

I'm installing a "new" PC in my electronics lab. In fact it's the previous PC of my better half, but should be more than sufficient to run the tools I want to run.

Hardware:

Code:

Asus Motherboard, Intel Core DUO. 6GB RAM
Matrox G550 dual DVI from which only one is connected to an Acer B193W monitor.
OS Debian - GNOME
I have 2 x 1TB disks partitioned in software RAID. Some partitions in RAID-0 others in RAID-1

History:
I originally always installed Debian Stretch and did an upgrade to Buster afterwards. Just because I had the DVD laying around and was to lazy to burn a new install CD. Stretch installation went smooth but after upgrade to Buster, screen resolution fell back to 640x800 with no way to increase resolution (xrandr only showed this as option also...)
I admit I didn't invest to much time, so after two attempts and some fiddling I burnt an install CD for Buster directly.
Again installation itself is smooth, no probs here, but then the issues began...

After first reboot, I get the GRUB menu in high resolution and booting continues. Soon after that screen turns black and shows me "input not supported" After some troubleshooting (rebooting, switching videocard from MB slot, using other cables, convert DVI to VGA to use other input on monitor, ...) I came to the conclusioin that after each reboot I get the issue.
Solution: unplug the DVI, wait a few sec, replug: Login window appears (in correct resolution). I can call this a work-around, but it's not really handy.

2nd problem: When the OS goes into suspend (both automatically as manual) I'm not able to have the monitor resurrect. Machine starts but in no way I'm getting video on the monitor (not even with the above workaround after boot) I've been Googling a lot and it seems this has happened in the past already, but despite all the "solutions" posted I had no luck.

I'm not sure if both are related. But I might as well mention it.

Hope that this rings a bell with someone somewhere...
Sorry for the long post.

regards.

frankbell · 05-07-2020, 07:48 PM

I start by looking at the log files. I don't have an install of Debian to check the nomenclature, but I'd look for something like /var/log/system or /var/log/messages.

Or you could use journalctl. At the link, scroll down to the section titled "Journal Filtering by Time."

mrmazda · 05-09-2020, 12:51 AM

Matrox 550 on Buster needs xserver-xorg-video-mga, and on kernel cmdline, iomem=relaxed:

Code:

# inxi -V | head -n1
inxi 3.1.00-00 (2020-04-22)
# inxi -GSMxxxza
System:    Kernel: 4.19.0-8-686 i686 bits: 32 compiler: gcc v: 8.3.0 
           parameters: ipv6.disable=1 net.ifnames=0 noresume mitigations=auto consoleblank=0 vga=791 iomem=relaxed 
           Desktop: Trinity R14.0.7 tk: Qt 3.5.0 info: kicker wm: Twin 3.0 dm: startx 
           Distro: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop Mobo: Abit model: AI7 (Intel i865-ICH5) v: 1.0 serial: N/A BIOS: Phoenix v: 6.00 PG 
           date: 11/03/2004 
Graphics:  Device-1: Matrox Systems Millennium G550 driver: N/A bus ID: 01:00.0 chip ID: 102b:2527 
           Display: server: X.Org 1.20.4 driver: mga unloaded: fbdev,modesetting,vesa display ID: :0 screens: 1 
           Screen-1: 0 s-res: 1280x1024 s-dpi: 108 s-size: 301x241mm (11.9x9.5") s-diag: 386mm (15.2") 
           Monitor-1: default res: 1280x1024 hz: 60 
           OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6 compat-v: 3.1 direct render: Yes

pompopom · 05-15-2020, 04:05 AM

Code:

root@labo:~# inxi -GSMxxxza
System:    Kernel: 5.5.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 9.3.0 
           parameters: BOOT_IMAGE=/vmlinuz-5.5.0-2-amd64 
           root=UUID=ce20b8c1-1361-4acd-a256-5e5a3d2643f2 ro quiet usbhid.mousepoll=4 
           Console: tty 0 dm: GDM3 3.34.1 Distro: Debian GNU/Linux bullseye/sid 
Machine:   Type: Desktop Mobo: ASUSTeK model: P5K v: Rev 1.xx serial: <filter> 
           BIOS: American Megatrends v: 0603 date: 07/03/2007 
Graphics:  Device-1: Matrox Systems Millennium G550 driver: N/A bus ID: 03:00.0 chip ID: 102b:2527 
           Display: server: X.org 1.20.8 compositor: gnome-shell driver: mga 
           unloaded: fbdev,modesetting,vesa tty: 105x24 
           Message: Advanced graphics data unavailable in console for root. 
root@labo:~# apt-get install xserver-xorg-video-mga
Reading package lists... Done
Building dependency tree       
Reading state information... Done
xserver-xorg-video-mga is already the newest version (1:2.0.0-1).
0 upgraded, 0 newly installed, 0 to remove and 204 not upgraded.
root@labo:~#

So I guess I should be good regarding the drivers?
Regarding the logs: What should I be looking for?
The only odd thing I have found atm in the /var/log/messages is the following:

Code:

May 15 11:36:22 labo /usr/libexec/gdm-x-session[953]: (II) MGA(0): Monitor name: Acer B193W

Which is in fact correct, however when I go into Settings => Displays menu I get "unknown display" message, which might declare the fact that Buster sends a totally "random" display size resulting in the "input not supported". On the other hand: have no idea whatsoever how unplugging/re-plugging the display then solves the issue...

So I manually put the system in suspend, and have it wake up with the keyboard. Same result regarding the display. Since the system actually wakes up, I SSH'd from another PC into the box and found the following:

Code:

*snip*
May 15 11:07:27 labo kernel: [ 5447.470942] atl1 0000:01:00.0: enp1s0 link is up 1000 Mbps full duplex
May 15 11:07:27 labo kernel: [ 5447.476414] IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0: link becomes ready
May 15 11:07:27 labo gnome-shell[1507]: JS ERROR: Error getting systemd inhibitor: Gio.IOErrorEnum: GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation inhibition has been requested for is already running#012inhibit/<@resource:///org/gnome/shell/misc/loginManager.js:187:55
May 15 11:07:27 labo gsd-color[1564]: unable to get EDID for xrandr-default: unable to get EDID for output
May 15 11:07:27 labo /usr/libexec/gdm-x-session[1254]: (II) event3  - Logitech USB-PS/2 Optical Mouse: is tagged by udev as: Mouse
May 15 11:07:27 labo /usr/libexec/gdm-x-session[1254]: (II) event3  - Logitech USB-PS/2 Optical Mouse: device set to 400 DPI
May 15 11:07:27 labo /usr/libexec/gdm-x-session[1254]: (II) event3  - Logitech USB-PS/2 Optical Mouse: device is a pointer
May 15 11:07:27 labo /usr/libexec/gdm-x-session[1254]: (II) systemd-logind: got resume for 13:64
May 15 11:07:27 labo /usr/libexec/gdm-x-session[1254]: (II) event0  - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
May 15 11:07:27 labo /usr/libexec/gdm-x-session[1254]: (II) event0  - AT Translated Set 2 keyboard: device is a keyboard
May 15 11:07:27 labo /usr/libexec/gdm-x-session[1254]: (II) systemd-logind: got resume for 13:65
May 15 11:07:27 labo /usr/libexec/gdm-x-session[1254]: (II) event1  - Power Button: is tagged by udev as: Keyboard
May 15 11:07:27 labo /usr/libexec/gdm-x-session[1254]: (II) event1  - Power Button: device is a keyboard
May 15 11:07:27 labo /usr/libexec/gdm-x-session[1254]: (II) systemd-logind: got resume for 13:66
May 15 11:07:27 labo /usr/libexec/gdm-x-session[1254]: (II) event2  - Power Button: is tagged by udev as: Keyboard
May 15 11:07:27 labo /usr/libexec/gdm-x-session[1254]: (II) event2  - Power Button: device is a keyboard
May 15 11:07:27 labo kernel: [ 5447.916385] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
May 15 11:07:27 labo kernel: [ 5447.940547] ata2.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
May 15 11:07:27 labo kernel: [ 5447.940550] ata2.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
May 15 11:07:27 labo kernel: [ 5447.940841] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
May 15 11:07:27 labo kernel: [ 5447.946352] ata2.00: configured for UDMA/100
May 15 11:07:27 labo kernel: [ 5447.976388] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
May 15 11:07:27 labo kernel: [ 5447.978666] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
May 15 11:07:27 labo kernel: [ 5447.978668] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
May 15 11:07:27 labo kernel: [ 5447.978917] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
May 15 11:07:27 labo kernel: [ 5447.985901] ata1.00: configured for UDMA/100
May 15 11:07:28 labo gsd-sharing[1599]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded.
May 15 11:07:32 labo colord[695]: failed to get session [pid 671]: No data available
May 15 11:07:33 labo /usr/libexec/gdm-x-session[3921]: The XKEYBOARD keymap compiler (xkbcomp) reports:
May 15 11:07:33 labo /usr/libexec/gdm-x-session[3921]: > Internal error:   Could not resolve keysym XF86FullScreen
May 15 11:07:33 labo /usr/libexec/gdm-x-session[3921]: Errors from xkbcomp are not fatal to the X server
May 15 11:07:33 labo /usr/libexec/gdm-x-session[3923]: The XKEYBOARD keymap compiler (xkbcomp) reports:
May 15 11:07:33 labo /usr/libexec/gdm-x-session[3923]: > Internal error:   Could not resolve keysym XF86FullScreen
May 15 11:07:33 labo /usr/libexec/gdm-x-session[3923]: Errors from xkbcomp are not fatal to the X server
May 15 11:07:33 labo /usr/libexec/gdm-x-session[3925]: The XKEYBOARD keymap compiler (xkbcomp) reports:
May 15 11:07:33 labo /usr/libexec/gdm-x-session[3925]: > Internal error:   Could not resolve keysym XF86FullScreen
May 15 11:07:33 labo /usr/libexec/gdm-x-session[3925]: Errors from xkbcomp are not fatal to the X server

Guess that indicates an issue indeed.

martin2018 · 05-15-2020, 06:08 AM

Quote:

Originally Posted by pompopom

Hi everyone,

First post here.
Not exactly a newbie in linux, but I'll never call myself a specialist or guru. I usually work on machines without GUI. So... ok let's go.

I'm installing a "new" PC in my electronics lab. In fact it's the previous PC of my better half, but should be more than sufficient to run the tools I want to run.

Hardware:

Code:

Asus Motherboard, Intel Core DUO. 6GB RAM
Matrox G550 dual DVI from which only one is connected to an Acer B193W monitor.
OS Debian - GNOME
I have 2 x 1TB disks partitioned in software RAID. Some partitions in RAID-0 others in RAID-1

History:
I originally always installed Debian Stretch and did an upgrade to Buster afterwards. Just because I had the DVD laying around and was to lazy to burn a new install CD. Stretch installation went smooth but after upgrade to Buster, screen resolution fell back to 640x800 with no way to increase resolution (xrandr only showed this as option also...)
I admit I didn't invest to much time, so after two attempts and some fiddling I burnt an install CD for Buster directly.
Again installation itself is smooth, no probs here, but then the issues began...

After first reboot, I get the GRUB menu in high resolution and booting continues. Soon after that screen turns black and shows me "input not supported" After some troubleshooting (rebooting, switching videocard from MB slot, using other cables, convert DVI to VGA to use other input on monitor, ...) I came to the conclusioin that after each reboot I get the issue.
Solution: unplug the DVI, wait a few sec, replug: Login window appears (in correct resolution). I can call this a work-around, but it's not really handy.

2nd problem: When the OS goes into suspend (both automatically as manual) I'm not able to have the monitor resurrect. Machine starts but in no way I'm getting video on the monitor (not even with the above workaround after boot) I've been Googling a lot and it seems this has happened in the past already, but despite all the "solutions" posted I had no luck.

I'm not sure if both are related. But I might as well mention it.

Hope that this rings a bell with someone somewhere...
Sorry for the long post.

regards.

-------------------------
I have just done the latest updates on cinnamon on my HP computer and had similar to the above. Now the display only gives me two resolutions whereas before there were several. I have double boot with windows 7 on the other sector and that still has the normal display resolutions. Presume the problems is with the display drivers but don't know how to fix that. Any ideas?

ondoho · 05-16-2020, 02:30 AM

martin2018, please open a dedicated thread for a different problem.

mrmazda · 05-16-2020, 05:38 AM

Quote:

Originally Posted by pompopom

Code:

root@labo:~# inxi -GSMxxxza
...
           Console: tty 0 dm: GDM3 3.34.1 Distro: Debian GNU/Linux bullseye/sid 
...
Graphics:  Device-1: Matrox Systems Millennium G550 driver: N/A bus ID: 03:00.0 chip ID: 102b:2527 
           Display: server: X.org 1.20.8 compositor: gnome-shell driver: mga ...

So I guess I should be good regarding the drivers?

I believe this is probably true. However, for Matrox issues, I'm in no position to help with any problem specific to 64bit, Wayland, GDM, Gnome and/or Bullseye, which appears your problem is most likely to involve. I suspect X itself is OK, if it's in use, otherwise Wayland may be the root problem. Installation is via Xorg, but quite likely it's actually Wayland you are running.

Quote:

Regarding the logs: What should I be looking for?

The important log to share, via http://pastebin.com/ or http://paste.debian.net/, is Xorg.#.log, most likely Xorg.0.log but possibly Xorg.1.log, or something from the journal. The pastebinit command can make uploading it easy. Please do not paste it in here, and do include the whole file. This log is traditionally found in /var/log/, but with Gnome configurations it is likely to be in ~/.local/share/xorg/ instead or in addition, and it's the latest timestamped needed if found in both locations. With Wayland, I know nothing material about finding its logging, which might be accessed via journalctl only.

pompopom · 05-24-2020, 05:01 AM

Thx for your patience and help so far.

This morning I came to the conclusion the mga kernel module wasn’t loaded correctly. I found that message in /var/log/messages. Dunno how come I skipped that before, must have been due to the overwhelming amount of info and wrong “grep” filter while searching. Anyway few minutes later detected a kernel incompatibility with the mga module. Machine was in fact running 5.6.X (dunno how it got there, I suppose an apt-get update made this happen) but initially, pretty sure about this, I was on 5.4.X. So I rebooted and in the GRUB boot menu I chose to boot with kernel 5.4.X instead of default 5.6.X. This solved my issue with the screen turning black showing an “input not supported” upon boot.
Adapted GRUB default boot => Problem solved.

HOWEVER: The black screen when resuming after a suspend is still present.
I just read your latest replies, will try and fine some more info this afternoon.

Kind regards.