From: Jacob Keller <jacob.e.keller@intel.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
Jocelyn Falempe <jfalempe@redhat.com>,
"airlied@redhat.com" <airlied@redhat.com>
Cc: <dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Pasi Vaananen <pvaanane@redhat.com>
Subject: Re: further issues with MGA G200 graphics chipset
Date: Fri, 24 Apr 2026 16:29:37 -0700 [thread overview]
Message-ID: <df849883-f61d-484a-bd4c-32da52473ad3@intel.com> (raw)
In-Reply-To: <0be82b55-0f78-4ef9-8b50-f068ec36ec4f@suse.de>
On 4/24/2026 12:47 AM, Thomas Zimmermann wrote:
> Hi Jocelyn
>
> Am 24.04.26 um 09:36 schrieb Jocelyn Falempe:
>> On 24/04/2026 08:20, Thomas Zimmermann wrote:
>>> Hi
>>>
>>> Am 23.04.26 um 21:42 schrieb Jacob Keller:
>>> [...]
>>>> Unfortunately, I also have no better idea than a DMI quirk table to
>>>> record known platforms that include the controller but don't have a
>>>> physical VGA connection exposed.
>>>
>>> I'm in favor of this. If you send a meaningful DMI identifier for
>>> your system, I'd make you a patch for testing.
>>
>> I didn't find something related to VGA connector in dmidecode.
>> My suggestion would be to use the chassis-type [1], and disable
>> polling on Blade (0x1C and 0x1D) and Rack Mount (0x17) as they are
>> less likely to have a real VGA monitor connected.
>> My Dell T310, which is kind of a Tower, has a chassis-type of 0x11
>> "Main server chassis" so it might not be very reliable.
>
> This is the first time, I hear about this problem. I don't think it's
> very common. And it appears only to be related due to cheap hardware
> manufacturing.
>
> So I suggest to pick Manufacturer, Product, Version as key. I'd be
> surprised if we find more than a hand full of systems with the issue. If
> we see a trend or common pattern, we can generalize later on.
>
I think this is the best solution. Keep it focused for now. I believe
Intel has two major platforms that we care about with respect to this
issue. I'll see if I can dig up the data. The systems install the MGA
G200 for BMC use but don't seem to expose the VGA connection.
For the specific system I have that was faulty, we have the following:
$ for t in system-manufacturer system-product-name system-version ; \
do dmidecode -s ${t}; \
done
Dell Inc.
PowerEdge XR8720t
Not Specified
I believe there was also some concern about HP systems which similarly
use this chipset, but I don't have the DMI data for that one off hand.
I've asked some colleagues to confirm the situation and obtain that
data. I'll get back early next week if we think there are any other
systems possibly affected.
In the mean time, I'm happy to have our team test any patch to confirm
that it behaves as expected and resolves the service interruptions.
Appreciate all the feedback on this thread.
Thanks,
Jake
next prev parent reply other threads:[~2026-04-24 23:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 23:55 further issues with MGA G200 graphics chipset Jacob Keller
2026-04-23 0:05 ` David Airlie
2026-04-23 21:39 ` Jacob Keller
2026-04-23 7:44 ` Thomas Zimmermann
2026-04-23 16:35 ` Jacob Keller
2026-04-23 19:22 ` Jocelyn Falempe
2026-04-23 19:42 ` Jacob Keller
2026-04-23 21:02 ` David Airlie
2026-04-23 21:18 ` Jacob Keller
2026-04-24 6:16 ` Thomas Zimmermann
2026-04-24 6:20 ` Thomas Zimmermann
2026-04-24 7:36 ` Jocelyn Falempe
2026-04-24 7:47 ` Thomas Zimmermann
2026-04-24 23:29 ` Jacob Keller [this message]
2026-04-27 12:14 ` Thomas Zimmermann
2026-04-27 22:53 ` Jacob Keller
2026-04-27 23:32 ` Jacob Keller
2026-04-28 19:12 ` stuart hayes
2026-04-28 21:07 ` Jacob Keller
2026-04-29 6:40 ` 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=df849883-f61d-484a-bd4c-32da52473ad3@intel.com \
--to=jacob.e.keller@intel.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jfalempe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pvaanane@redhat.com \
--cc=tzimmermann@suse.de \
/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