Bug 809431 - Input signal out of range on G550 DVI
Summary: Input signal out of range on G550 DVI
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: xorg-x11-drv-mga
Version: 6.3
Hardware: All
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Adam Jackson
QA Contact: Desktop QE
URL:
Whiteboard:
: 879200 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-03 11:12 UTC by Jiri Koten
Modified: 2017-12-06 10:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 10:17:21 UTC
Target Upstream Version:

Attachments (Terms of Use)
dmesg output (50.93 KB, text/plain)
2012-04-03 11:12 UTC, Jiri Koten 		no flags Details
Xorg log (39.28 KB, text/plain)
2012-04-03 11:13 UTC, Jiri Koten 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Jiri Koten 2012-04-03 11:12:15 UTC 
Description of problem:
When I start X, there is no output displayed on my monitor. Monitor complains about "Input signal out of range". Monitor is connect through DVI.
No xorg.conf is used.

I get display output with "vesa" driver.
VGA analog output also works, though the card has two dvi ports, therefore I have to use reduction.
 

hw:VGA compatible controller [0300]: Matrox Graphics, Inc. MGA G550 AGP [102b:2527] (rev 01)


Version-Release number of selected component (if applicable):
xorg-x11-drv-mga-1.4.13-4.el6.x86_64
kernel-2.6.32-251.el6.x86_64
xorg-x11-server-Xorg-1.10.4-15.el6

How reproducible:
100%

Steps to Reproduce:
1. start X session
  
Actual results:
Monitor stays blank

Expected results:
X session starts

Additional info:
Comment 1 Jiri Koten 2012-04-03 11:12:48 UTC 
Created attachment 574827 [details]
dmesg output
Comment 2 Jiri Koten 2012-04-03 11:13:20 UTC 
Created attachment 574828 [details]
Xorg log
Comment 3 RHEL Program Management 2012-05-03 05:43:19 UTC 
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 4 Adam Jackson 2013-01-04 18:11:56 UTC 
*** Bug 879200 has been marked as a duplicate of this bug. ***
Comment 5 RHEL Program Management 2013-10-14 05:03:41 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 6 Jan Kurik 2017-12-06 10:17:21 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/
Note You need to log in before you can comment on or make changes to this bug.