Re: further issues with MGA G200 graphics chipset

[Jacob Keller <jacob.e.keller@intel.com>]

On 4/27/2026 3:53 PM, Jacob Keller wrote:
> On 4/27/2026 5:14 AM, Thomas Zimmermann wrote:
>> Hi
>>> 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.
>>
>> For now, I've modified the two places that have BMC support in the
>> driver. Could you please also tell me your system's exact Matrox chipset
>> or its PCI id?
>>
> 
> Here's the lspci output:
> 
>>
>> b5:00.0 VGA compatible controller [0300]: Matrox Electronics Systems Ltd. Integrated Matrox G200eW3 Graphics Controller [102b:0536] (rev 08) (prog-if 00 [VGA controller])
>>         DeviceName: Embedded Video
>>         Subsystem: Dell Integrated Matrox G200eW3 Graphics Controller [1028:0d38]
>>         Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
>>         Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
>>         Interrupt: pin A routed to IRQ 16
>>         NUMA node: 0
>>         IOMMU group: 16
>>         Region 0: Memory at e5000000 (32-bit, prefetchable) [size=16M]
>>         Region 1: Memory at e6810000 (32-bit, non-prefetchable) [size=16K]
>>         Region 2: Memory at e6000000 (32-bit, non-prefetchable) [size=8M]
>>         Capabilities: [dc] Power Management version 3
>>                 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
>>                 Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
>>         Kernel driver in use: mgag200
>>         Kernel modules: mgag200
> 
> The device ID looks to be 0x0536, and the subdevice ID is Dell 0x0D38. I
> don't see anything specifically related to mini display port. It is
> plausible there is an encoder between that output and the G200eW3.
> 
>> The patch is attached for your testing. It would work against drm-tip or
>> v7.1-rc1.
>>
> 
> I'll give it a shot.
> 
The systems that were having trouble are currently being used by other
folks on my team to check other issues. It might take a day or two
before I can get access again to test this. I'll update you once I've
gotten access and had a chance to test the changes.

Thanks,
Jake