Bug 508039
| Summary: | Use 24bpp framebuffer on g200se to avoid bandwidth limit | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Olivier Fourdan <ofourdan> | ||||||
| Component: | xorg-x11-drv-mga | Assignee: | Adam Jackson <ajax> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | desktop-bugs <desktop-bugs> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 5.4 | CC: | akarlsso, cmeadors, cward, herrold, kem, ltroan, martin.wilck, syeghiay, takeshi.suzuki, tao, tatsu-ab1 | ||||||
| Target Milestone: | rc | Keywords: | OtherQA, Patch | ||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 607093 (view as bug list) | Environment: | |||||||
| Last Closed: | 2009-09-02 11:55:03 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 509914 | ||||||||
| Attachments: |
|
||||||||
|
Description
Olivier Fourdan
2009-06-25 10:15:45 UTC
Created attachment 349369 [details]
Proposed Patch
This patch prefers a 24bpp packed framebuffer by default for the G200e SE chipset to reduce the impact of the limited bandwidth on this hardware.
The default of 32bpp remains unchanged for other chipsets.
This patch is 100% correct for this chip set, and has almost no risk of introducing regressions. You can be certain that Fujitsu and FTS will retest thoroughly with the G200SE, which is the only chip set affected by that patch. In fact, this patch is more appropriate for our problem (wrong resolutions with G200SE at depth 24) than the one proposed in bug #507536, which is more complex and has more potential for regressions with other chip sets. Applying the patch from 508039 will make the patch from 507536 unnecessary from our point of view. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. Built 1.4.10-4.el5 MODIFIED Event posted on 07-29-2009 11:12am JST by mfuruta Hi Tatsukawa-san, I'd like to inform test package at below, would you please verify it? http://people.redhat.com/mfuruta/309052/ Also ,this is blocker for Snapshot 5. Regards, Masaki Furuta Internal Status set to 'Waiting on Customer' Status set to: Waiting on Client This event sent from IssueTracker by mfuruta issue 309052 Per private comment #25, the UK TAM installed and tested package xorg-x11-drv-mga-1.4.10-4.el5.jx2.x86_64.rpm on a RHEL5.4snap3 machine using the Kronos1 1.7MB chipset and X came up fine on reboot at 1024x768 16bpp. Additionally, he installed xorg-x11-drv-mga-1.4.10-4.el5.jx2.x86_64.rpm on a RHEL5.4snap3 machine using the Kronos2 8MB chipset. The original resolution post-install didn't fit the screen properly but was readable, but using this test package it came up correctly at 1280x1024 24bpp on restarting X. He attached logs for engineering review. Kevin M. reviewed the *.after logs and they are correctly shrinking the virtual fb size to allow 1024x768 @ 16bpp. He will have Adam double check his findings tomorrow (Monday), and assuming they both agree, they will provide a recommendation to PM about how best to include the updated patch. Setting to NEEDINFO ajax. Do we have this driver on a people.page so partners may test it as well? > Do we have this driver on a people.page so partners may test it as well? http://people.redhat.com/ltroan/fixes/.mga/ ~~ Attention Partners - RHEL 5.4 Snapshot 5 Released! ~~ RHEL 5.4 Snapshot 5 is the FINAL snapshot to be release before RC. It has been released on partners.redhat.com. If you have already reported your test results, you can safely ignore this request. Otherwise, please notice that there should be a fix available now that addresses this particular issue. Please test and report back your results here, at your earliest convenience. If you encounter any issues while testing Beta, please describe the issues you have encountered and set the bug into NEED_INFO. If you encounter new issues, please clone this bug to open a new issue and request it be reviewed for inclusion in RHEL 5.4 or a later update, if it is not of urgent severity. If it is urgent, escalate the issue to your partner manager as soon as possible. There is /very/ little time left to get additional code into 5.4 before GA. Partners, after you have verified, do not flip the bug status to VERIFIED. Instead, please set your Partner ID in the Verified field above if you have successfully verified the resolution of this issue. Further questions can be directed to your Red Hat Partner Manager or other appropriate customer representative. 1916307 build (dist-5E-qu-candidate, RHEL-5:xorg-x11-drv-mga-1_4_10-5_el5): open (x86-004.build.bos.redhat.com) -> closed MODIFIED Fujitsu, please test using the latest RC1 test build for this package. This is the candidate build for RC1. http://people.redhat.com/~cward/5.4.0/xorg-x11-drv-mga/ Chris, xorg-x11-drv-mga-1.4.10-5.el5 has been verified for both Kronos1 1.7MB chipset and Kronos2 8MB chipset. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-1390.html Requested information was provided in IssueTracker. This is just to clear the needinfo flag. |