The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Wakko Warner <wakko@animx.eu.org>
To: linux-kernel@vger.kernel.org, airlied@redhat.com
Subject: Re: MGA G200 issue in 6.12 and up
Date: Mon, 14 Apr 2025 20:35:24 -0400	[thread overview]
Message-ID: <Z/2pzDAplsZz8AVd@animx.eu.org> (raw)
In-Reply-To: <Z/anHRAx3SQWr+h8@animx.eu.org>

I found the fix that works for me.  See below.

Wakko Warner wrote:
> I decided to upgrade to 6.14 on a system with a Matrox G200 onboard vga
> (supermicro X9SCL).
> 
> I use this system via the BMC.  When the mgag200 driver loads, the bmc
> screen flashes between no signal and the screen.  The rate seems to be about
> 1 second no signal and 1 second with signal.
> 
> 6.12 and 6.13 both have this problem.
> 
> 6.11 does not have this problem.
> 
> I have a monitor plugged into the vga port and it doesn't have this problem
> on any of the kernels I've tried.  Only the remote connection through the bmc
> has this problem.  I have booted the system with and with out the monitor
> plugged in, it does not appear to make a difference.

I found a thread on arch linux forums
(https://bbs.archlinux.org/viewtopic.php?id=303819) where the op has the
same issue.  He bisected and came up with the bad commit.
That commit is 
d6460bd52c27fde97d6a73e3d9c7a8d747fbaa3e drm/mgag200: Add dedicated variables
for blanking fields

I searched this commit and manually reverted it from my vanilla 6.14 and it
works fine.  No blinking in the BMC remote console and the external VGA
works fine as well.

-- 
 Microsoft has beaten Volkswagen's world record.  Volkswagen only created 22
 million bugs.

  reply	other threads:[~2025-04-15  0:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-09 16:58 MGA G200 issue in 6.12 and up Wakko Warner
2025-04-15  0:35 ` Wakko Warner [this message]
2025-04-16  1:46   ` David Airlie
2025-04-16  8:47     ` Thomas Zimmermann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Z/2pzDAplsZz8AVd@animx.eu.org \
    --to=wakko@animx.eu.org \
    --cc=airlied@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox