Created attachment 363588 [details] Unreadable green output with mgag200 driver Hi, I am not sure how to phrase the problem. I hope the attached screenshot will show you my problem: The output is green (which makes the output nearly unreadable). Also, sometimes the output will crash (resolution changes from 1024x768 to something like 90x100 and the output is garbage). I tried sys-kernel/gentoo-sources-3.11.8 and sys-kernel/vanilla-sources-3.12.0. They seems to work. Not sure if we can identify the fix and backport it to the longterm kernel. The system is a HP DL120 G7 server: 01:00.1 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200EH (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device 330e Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin B routed to IRQ 16 Region 0: Memory at f9000000 (32-bit, prefetchable) [size=16M] Region 1: Memory at fbae0000 (32-bit, non-prefetchable) [size=16K] Region 2: Memory at fb000000 (32-bit, non-prefetchable) [size=8M] Expansion ROM at <unassigned> [disabled] Capabilities: [a8] 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- Capabilities: [b0] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [c0] Express (v1) Legacy Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal+ Fatal+ Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s, Latency L0 <4us, L1 <4us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt- Kernel driver in use: mgag200 Kernel modules: mgag200 I am booting with the "video=1024x768-16" parameter.
Created attachment 363590 [details] .config My kernel configuration.
Created attachment 366112 [details] mpag200.commits.txt Attached a list of commits which messages contain mpag200; there aren't much of them, but I don't have a direct idea what could be the commit. There are some you could exclude based on their commit message; and there are also some that are particularly interesting like "drm/mgag200: Don't do full cleanup if mgag200_device_init fails", "drm/mgag200: Fix framebuffer pitch calculation" and those touching the BO. I'd suggest you try to undo the changes by some of these to identify which commit it could be. Given an example commit ID da55839870263563cc70e700a7f58090a860576d, you can see the changes using an URL like http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=da55839870263563cc70e700a7f58090a860576d
OK, I was wrong. Well, not at all: I am still able to reproduce the "green output" when booting with video=1024x768-16 But when I remove the depth information (-16) I am unable to reproduce the "green output" with 3.10.x, e.g. booting with video=1024x768 video=1024x768-32 works. Well, booting kernel >=3.11 with "video=1024x768-16" works, too: I never got the "green output" with kernels >=3.11... so there's still a commit which should be backported, but I don't know which one :) But there is another problem: When the screen goes blank, the resolution will randomly change multiple times. I saw resolutions like: 560x768 872x768 1456x768 1968x768 1504x768 752x768 1264x768 1904x768 1280x768 1808x768 496x768 1168x768 944x768 16x768 880x768 528x768 1952x768 2000x768 1744x768 1936x768 788x768 352x768 1888x768 This isn't usable. Because of this problem (which still exists in 3.12.6) I have to boot with "nomodeset vga=791". But now I don't have KMS so I don't have the problem with the "green screen". Feel free to close this bug report. Until the randomly changing resolution problem is solved, I won't care about this bug report anymore. Maybe I'll report the problem to upstream... but no need for the gentoo-sources team to watch this. Thanks!
Ok, so I will close this. Thanks for reporting. Glad things are better in later kernels. I'll call it obsolete as it's not fixed in 3.10, but works in >=3.11.
