Bug 250671 - Graphical installer has problem with Matrox G400
Summary: Graphical installer has problem with Matrox G400
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: xorg-x11-drv-mga (Show other bugs)
(Show other bugs)
Version: 5.0
Hardware: All Linux
Target Milestone: ---
: ---
Assignee: Adam Jackson
QA Contact: desktop-bugs@redhat.com
Keywords: Triaged
Depends On:
TreeView+ depends on / blocked
Reported: 2007-08-02 20:12 UTC by Peter Bieringer
Modified: 2012-04-17 20:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-04-17 20:05:10 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
/var/log/anaconda.xlog as requested (53.91 KB, text/plain)
2007-09-12 17:58 UTC, Peter Bieringer
no flags Details

Description Peter Bieringer 2007-08-02 20:12:11 UTC
Description of problem:
Graphical installer would be unusable on a system with a Matrox G400 on a
1280x1024 TFT display unless "resolution=1280x1024" is given on boot prompt.

Actual results:
Without boot parameter, only the upper left part of the graphical installer is

Using the "resolution", the full graphical installer (800x600??) is shown on the
left upper corner.

Comment 1 Matěj Cepl 2007-09-10 16:41:11 UTC
Thanks for the bug report.  We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue.

Please attach your X server config file (/etc/X11/xorg.conf) and X server log
file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file
attachments using the bugzilla file attachment link below.

Could you please also try to run without any /etc/X11/xorg.conf whatsoever and
let X11 autodetect your display and video card? Attach to this bug
/var/log/Xorg.0.log from this attempt as well, please.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 2 Peter Bieringer 2007-09-10 19:56:45 UTC
How to catch the X11 config during anaconda runs?

Comment 3 Matěj Cepl 2007-09-12 00:11:58 UTC
During the anaconda runs there should be files *log* in /tmp. After anaconda
finishes the file we are interested in is /var/log/anaconda.xlog

Comment 4 Peter Bieringer 2007-09-12 17:58:08 UTC
Created attachment 193711 [details]
/var/log/anaconda.xlog as requested

Comment 5 Peter Bieringer 2007-09-12 17:58:52 UTC
File as requested

Comment 6 Adam Jackson 2012-04-17 20:05:10 UTC
No further hardware enablement updates are planned for RHEL5's X stack.  If this issue remains in RHEL6, please update the affected product version and reopen this bug.

Note You need to log in before you can comment on or make changes to this bug.