Bug 51021 - Matrox g200 driver mgag200 doesn't work with FS PRIMERGY RX200 S4
Summary: Matrox g200 driver mgag200 doesn't work with FS PRIMERGY RX200 S4
Status: RESOLVED INVALID
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-26 16:01 UTC by Igor Sverkos
Modified: 2012-11-26 21:03 UTC (History)
0 users

See Also:
Kernel Version: 3.6.7
Subsystem:
Regression: No
Bisected commit-id:

Attachments
This is how the display looks when the mgag200 is loaded (197.34 KB, image/jpeg)
2012-11-26 16:01 UTC, Igor Sverkos 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Igor Sverkos 2012-11-26 16:01:01 UTC 
Created attachment 87311 [details]
This is how the display looks when  the mgag200 is loaded

Hi,

sorry - don't know how to better phrase "doesn't work". With doesn't work I mean, that my screen will look like the attached screenshot.

Relevant lspci output:

rx200s4 ~ # lspci -s 1b: -nn
1b:00.0 VGA compatible controller [0300]: Matrox Electronics Systems Ltd. MGA G200e [Pilot] ServerEngines (SEP1) [102b:0522] (rev 02)
rx200s4 ~ # lspci -s 1b: -xxvv
1b:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200e [Pilot] ServerEngines (SEP1) (rev 02) (prog-if 00 [VGA controller])
	Subsystem: Fujitsu Technology Solutions Device 108e
	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 A routed to IRQ 18
	Region 0: Memory at f6000000 (32-bit, prefetchable) [size=16M]
	Region 1: Memory at fc000000 (32-bit, non-prefetchable) [size=16K]
	Region 2: Memory at fc800000 (32-bit, non-prefetchable) [size=8M]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [dc] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [e4] Express (v1) Legacy Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
			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 <64ns, L1 <1us
			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-
	Capabilities: [54] MSI: Enable- Count=1/1 Maskable- 64bit-
		Address: 00000000  Data: 0000
	Kernel driver in use: mgag200
00: 2b 10 22 05 47 01 10 10 02 00 00 03 10 00 00 00
10: 08 00 00 f6 00 00 00 fc 00 00 80 fc 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 34 17 8e 10
30: 00 00 00 00 dc 00 00 00 00 00 00 00 0b 01 00 00
Comment 1 Igor Sverkos 2012-11-26 21:03:47 UTC 
Sorry - mgag200 seems to be working fine. Because the system does not have EFI, I disabled CONFIG_EFI, which disabled CONFIG_FB_EFI, which is required for passing gfxpayload from bootloader to kernel, which failed.

See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567245#17
Note You need to log in before you can comment on or make changes to this bug.