Bug 1902519 - Matrox MGA G200e Pilot ServerEngines - no kernel video in kernel 5.9
Summary: Matrox MGA G200e Pilot ServerEngines - no kernel video in kernel 5.9
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 32
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-29 22:25 UTC by Trevor Cordes
Modified: 2021-05-25 17:51 UTC (History)
21 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-05-25 17:51:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Trevor Cordes 2020-11-29 22:25:32 UTC
1. Please describe the problem:
After upgrade from F31 to F32 (kernel 5.8 to 5.9) on a Intel motherboard server (S1200) with onboard Matrox M200e video, there is no video after grub starts booting linux.

Note, I'm not talking about X: we are not running X, this is a command-line only server.

05:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200e [Pilot] ServerEngines (SEP1) (rev 07)


2. What is the Version-Release number of the kernel:
5.9.10-100.fc32.x86_64


3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

good: 5.8.18-100.fc31
bad : 5.9.10-100.fc32

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Yes, just reboot into 5.9 kernel


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

I tried to install rawhide kernel but bug prevents me from doing so, see bottom of:
https://bugzilla.redhat.com/show_bug.cgi?id=1489628
I have the same problem as that last comment


6. Are you running any modules that not shipped with directly Fedora's kernel?:

no


7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

This subset should be adequate:
Nov 29 14:40:40  kernel: [    0.106652] random: crng done (trusting CPU's manufacturer)
Nov 29 14:40:40  kernel: [    0.115161] Console: colour VGA+ 80x25
Nov 29 14:40:40  kernel: [    0.137805] printk: console [tty0] enabled
--
Nov 29 14:40:40  kernel: [    0.367072] iommu: Default domain type: Translated 
Nov 29 14:40:40  kernel: [    0.367564] pci 0000:05:00.0: vgaarb: setting as boot VGA device
Nov 29 14:40:40  kernel: [    0.367697] pci 0000:05:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
Nov 29 14:40:40  kernel: [    0.367868] pci 0000:05:00.0: vgaarb: bridge control possible
Nov 29 14:40:40  kernel: [    0.367868] vgaarb: loaded
Nov 29 14:40:40  kernel: [    0.367899] SCSI subsystem initialized
--
Nov 29 14:40:40  kernel: [   10.395539] e1000e 0000:04:00.0 0000:04:00.0 (uninitialized): registered PHC clock
Nov 29 14:40:40  kernel: [   10.439284] mgag200 0000:05:00.0: vgaarb: deactivate vga console
Nov 29 14:40:40  kernel: [   10.441500] e1000e 0000:04:00.0 eth3: (PCI Express:2.5GT/s:Width x1) 00:1e:67:64:81:88
--
Nov 29 15:19:00  kernel: [    0.106060] random: crng done (trusting CPU's manufacturer)
Nov 29 15:19:00  kernel: [    0.114755] Console: colour VGA+ 80x25
Nov 29 15:19:00  kernel: [    0.137281] printk: console [tty0] enabled
--
Nov 29 15:19:00  kernel: [    0.366552] iommu: Default domain type: Translated 
Nov 29 15:19:00  kernel: [    0.366552] pci 0000:05:00.0: vgaarb: setting as boot VGA device
Nov 29 15:19:00  kernel: [    0.366552] pci 0000:05:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
Nov 29 15:19:00  kernel: [    0.367035] pci 0000:05:00.0: vgaarb: bridge control possible
Nov 29 15:19:00  kernel: [    0.367171] vgaarb: loaded
Nov 29 15:19:00  kernel: [    0.367379] SCSI subsystem initialized
--
Nov 29 15:19:00  kernel: [    8.809725] RAPL PMU: hw unit of domain package 2^-16 Joules
Nov 29 15:19:00  kernel: [    8.810288] mgag200 0000:05:00.0: vgaarb: deactivate vga console
Nov 29 15:19:00  kernel: [    8.821635] Console: switching to colour dummy device 80x25
--
Nov 29 15:23:46  kernel: [    0.106271] random: crng done (trusting CPU's manufacturer)
Nov 29 15:23:46  kernel: [    0.114981] Console: colour VGA+ 80x25
Nov 29 15:23:46  kernel: [    0.137527] printk: console [tty0] enabled
--
Nov 29 15:23:46  kernel: [    0.367287] iommu: Default domain type: Translated 
Nov 29 15:23:46  kernel: [    0.367422] pci 0000:05:00.0: vgaarb: setting as boot VGA device
Nov 29 15:23:46  kernel: [    0.367424] pci 0000:05:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
Nov 29 15:23:46  kernel: [    0.367595] pci 0000:05:00.0: vgaarb: bridge control possible
Nov 29 15:23:46  kernel: [    0.367595] vgaarb: loaded
Nov 29 15:23:46  kernel: [    0.367620] SCSI subsystem initialized
--
Nov 29 15:23:46  kernel: [    8.884886] RAPL PMU: hw unit of domain package 2^-16 Joules
Nov 29 15:23:46  kernel: [    9.074671] mgag200 0000:05:00.0: vgaarb: deactivate vga console
Nov 29 15:23:46  kernel: [    9.086240] Console: switching to colour dummy device 80x25

Comment 1 Alberto Abrao 2020-12-10 14:27:51 UTC
I know Trevor and he mentioned this bug to me. Coincidentally, I have a server with the exact same video interface that I can use for testing.

After updates, same issue happened here. No video.


The fix:

1) Obviously, we need to boot first. So edit the GRUB boot entry and pass the parameter "vga=793" right after "quiet".

2) Then, edit /etc/default/grub and, on GRUB_CMDLINE after quiet, add

(...) quiet -- vga=793"

Then, reinstall GRUB.


The issue:

card sees a monitor that supports a higher resolution than it can display, tries to use it, fails miserably, as we're talking about an old video interface. That parameter will force the 1280x1024 resolution, which is working fine on my 1080p display, and should work on most as far as I know.

* To see all modes, pass "vga=ask" after quiet. Press ENTER to see available modes.

* To use another one, convert the Mode for the desired Resolution to decimal. To do so, I used:

printf "%d\n" 0x319  (for 1280x1024)

Equals 793. vga=793.

Comment 2 Fedora Program Management 2021-04-29 17:07:40 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2021-05-25 17:51:25 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.