Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 928916

Summary: Driver not working since added support of randr12 for G200se, G200wb and G200eR
Product: Red Hat Enterprise Linux 6 Reporter: Matrox <mgi_lnx>
Component: xorg-x11-drv-mgaAssignee: Adam Jackson <ajax>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.4CC: mgi_lnx, tpelka
Target Milestone: rcKeywords: OtherQA
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-06 12:55:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Picture of the corruption
none
Proposed patch none

Description Matrox 2013-03-28 17:51:59 UTC 
Description of problem:

The mga driver is not working for G200se, G200wb and G200eR. 

1- The resolution list is not good, it only shows a limited list of resolution compared of what was available in RHEL6.2. 

2- Corruption at the bottom of the screen is seen in resolution higher than 1024x768.

3- System hangs with my monitor (Dell 2408WFP).


Version-Release number of selected component (if applicable):


How reproducible:



Steps to Reproduce:
1. Start X normally
2. Look at the resolution with randr or Display manager
3.
  
Actual results:

- Limited resolution list

- Corruption in bottom of the screen.

- System hang with a Dell 2408WFP.

Expected results:


Additional info:

The bug was observed in RHEL6.3 too. I looked at the code and the main difference between 6.4 and 6.2 is Randr1.2 support. If I disable RANDR12 option in xorg.conf file, the driver works fine as it was in 6.2. I haven't tried on the other G200 parts ( G200eH and G200eV) but they probably have the bug too.
Comment 1 Tomas Pelka 2013-06-04 14:11:29 UTC 
Dear Matrox,

I'm not sure if we can cover the testing for all mentioned graphics. Can we get a commitment from you to retest once fixed packages are ready?

Thanks in advance
Tom
Comment 2 Matrox 2013-06-27 20:28:28 UTC 
(In reply to Tomas Pelka from comment #1)
> Dear Matrox,
> 
> I'm not sure if we can cover the testing for all mentioned graphics. Can we
> get a commitment from you to retest once fixed packages are ready?
> 
> Thanks in advance
> Tom

Yes we will be able to test on all the products if you send the patches.

Thank you

Mathieu
Comment 3 RHEL Program Management 2013-10-14 04:00:31 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 4 Matrox 2013-11-11 19:11:02 UTC 
Status of this request:

A patch file (mga-1.6.1-size-rage.patch) included in the most recent package partially fixes this bug :
The resolution list is good and the system doesn't hang anymore.


However corruption is still visible. Around 20 lines are corrupted in the bottom of the screen. I made some investigation but wasn't to put my finger on the problem:

- The driver uses shadowFB and the shadow has the corruption as well. 

- On one of my product, the corruption starts at 864 which is the number of lines of the initial resolution selected at the boot. (log in screen)

- The problem happens only when the driver decline the preferred mode of the monitor.

I've attached a picture of the bug. 


Let me know if I can help in any way to solve this issue.
Comment 5 Matrox 2013-11-11 19:11:47 UTC 
Created attachment 822586 [details]
Picture of the corruption
Comment 6 Matrox 2014-01-07 18:37:26 UTC 
I investigated the corruption and it's a problem with the ShadowFB option. It seems that the allocation of the buffer wasn't resized and sometimes the resolution could exceed the size of the buffer. The solution is to allocate a bigger buffer for the shadow. I took the biggest height that we support (1200).

In addition, I discovered a bug with 1360x768 monitor. Our hardware is limited in the granularity of the lines, so I needed to add code to support pitch different than width. I'm attaching a new patch file with my proposals.
Comment 7 Matrox 2014-01-07 18:38:23 UTC 
Created attachment 846814 [details]
Proposed patch
Comment 8 Jan Kurik 2017-12-06 12:55:20 UTC 
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/