Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 274831

Summary: add OPMA server support
Product: Red Hat Enterprise Linux 5 Reporter: LisaWu <liswu>
Component: xorg-x11-drv-atiAssignee: Dave Airlie <airlied>
Status: CLOSED ERRATA QA Contact: desktop-bugs <desktop-bugs>
Severity: low Docs Contact:
Priority: medium    
Version: 5.0CC: jvuong, liswu, woliu, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: RHEA-2008-0474 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-05-21 17:31:17 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:
Attachments:
Description Flags
when OPMA server is detected, we validate modes according to local monitor DDC info by default.
none
patch against xorg-x11-drv-ati-6.6.3-3.2.el5
none
patch against xorg-x11-drv-ati-6.6.3-3.2.el5
none
proposed fix - just cleaned up the ATI patch. none

Description LisaWu 2007-09-03 03:30:00 UTC
Description of problem:
On OPMA servers (use ES1000 as video chip), when connect local monitor that 
supports low resolution, say, max 1024x768, radeon driver will display 
1600x1200 resolution in the OPMA remote console, while local CRT monitor 
simply goes out of range.

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


How reproducible:
Always

Steps to Reproduce:
1. connect a CRT monitor that support low resolution to OPMA server
2. when graphic installation begin, CRT monitor goes out of range.
  
Additional info:
RN50 has only one CRTC to generate timings. With current implementation, 
radeon driver is programmed for driving only one display on one CRTC. only one 
monitor EDID will be collected by radeon driver, which in our case, server KVM 
EDID is got, while radeon driver is not aware the existance of local monitor. 
Output modes are validated according to OPMA EDID. thus local monitor will go 
out of range.

Comment 1 LisaWu 2007-09-03 03:30:00 UTC
Created attachment 184971 [details]
when OPMA server is detected, we validate modes according to local monitor DDC info by default.

Comment 2 Adam Jackson 2007-12-19 00:07:12 UTC
Yet another RN50 bug.  Reassigning.

Comment 3 RHEL Program Management 2007-12-19 00:14:56 UTC
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.

Comment 4 Dave Airlie 2007-12-20 00:04:46 UTC
From what I can see this will possibly limit the resolution on a lot more than
just OPMA cards as they have re-used the pci vendor/device id as the subsystem
vendor device ID..

This leads me to think that other RN50s will exist in the field where the test 
if ((info->PciInfo->subsysVendor == 0x1002) &&
+                (info->PciInfo->subsysCard  == 0x515e) && info->Chipset==
PCI_CHIP_RN50_515E){

is also true...

so I don't think we can just apply this patch as-is.

Comment 5 LisaWu 2007-12-21 08:57:36 UTC
(In reply to comment #4)
> if ((info->PciInfo->subsysVendor == 0x1002) &&
> +                (info->PciInfo->subsysCard  == 0x515e) && info->Chipset==
> PCI_CHIP_RN50_515E){
> is also true...
> 
en,this may expand the restriction to other cards have the same subsysVendorID,
what about we use the monitor Name read from EDID to distinguish it from other 
cards?
the unique monitor name is "AQUARIUS" 

Comment 6 Dave Airlie 2007-12-21 09:29:22 UTC
That sounds like a better idea? can you supply a patch for review?

Comment 7 LisaWu 2007-12-25 04:22:53 UTC
Created attachment 290371 [details]
patch against xorg-x11-drv-ati-6.6.3-3.2.el5

Comment 8 LisaWu 2007-12-25 04:28:44 UTC
Created attachment 290372 [details]
patch against xorg-x11-drv-ati-6.6.3-3.2.el5

sorry, uploaded a wrong patch, please ignore the former one.

Comment 9 Dave Airlie 2008-01-14 08:01:52 UTC
okay this looks better, I might clean it up a bit before release...

Comment 10 Dave Airlie 2008-01-14 08:28:09 UTC
Created attachment 291574 [details]
proposed fix - just cleaned up the ATI patch.

this is the final patch I'm going to apply, please check it can work, it may
need a bit of munging to apply cleanly to 6.6.3-3.2 as there are other patches
in the same area that I've applied.

Comment 11 LisaWu 2008-01-15 02:01:51 UTC
Thanks,the patch is OK.

Comment 13 LisaWu 2008-04-14 01:46:04 UTC
Hi, would you please inform which version will this patch be included? Thanks 
a lot 

Comment 15 errata-xmlrpc 2008-05-21 17:31:17 UTC
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 the 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/RHEA-2008-0474.html