[Bug 307074] New: add OPMA server support

https://bugzilla.novell.com/show_bug.cgi?id=307074 Summary: add OPMA server support Product: SUSE Linux 10.1 Version: Final Platform: Other OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: sndirsch@novell.com ReportedBy: liswu@ati.com QAContact: sndirsch@novell.com Found By: --- This bug is originally found on RHEL5. 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=307074#c1 --- Comment #1 from Lisa Wu <liswu@ati.com> 2007-09-02 23:30:29 MST --- Created an attachment (id=161406) --> (https://bugzilla.novell.com/attachment.cgi?id=161406) this patch is against xf86-video-ati 6.6.19x. we use this patch to get monitor DDC from VGA_DDC line first and validate mode according to it -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=307074#c2 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Priority|P5 - None |P2 - High --- Comment #2 from Stefan Dirsch <sndirsch@novell.com> 2007-09-03 03:25:45 MST --- Lisa, thanks for the patch. Since it is limited to to exactly one Vendor/Device/Subvendor/Subdevice combination applying it to our driver is no problem at all. It is reported against SUSE 10.1. I don't think that we'll still fix for 10.1, but SLES10/SLES10-SP1 (which is based on SUSE 10.1) would be an option. I'll add it for openSUSE 10.3 in any case. Let me know, what you think about SLES10/SLES10-SP1. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=307074#c3 --- Comment #3 from Lisa Wu <liswu@ati.com> 2007-09-03 03:42:24 MST --- Stefan, thanks a lot for your quick response. I am sorry I choose a too old OS version to report this bug. It would be nice if this patch will be added to SLES10/SLES10-SP1 and openSUSE10.3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com