Red Hat Bugzilla – Bug 446129
can't do graphical install on box with Matrox G200e
Last modified: 2009-06-19 23:56:20 EDT
Description of problem:
With the re20080507.0 rel-eng build, can't do a graphical install. After trying
to start anaconda, it brings up the blue screen w/ RH logo but then crashes and
says "install exited abnormally" after "Starting graphical installation...".
I see anaconda with a segfault in another virtual console:
<6>anaconda: segfault at 000000000000008 rip 0000002a9b49cf6b rsp
0000007fbfeeee00 error 4
But other behaviors could mean something other than anaconda is at fault:
A text mode install works, but if you boot to runlevel 5, X comes to a black
screen with the X cursor moveable and seems to go no farther.
If you boot to runlevel 3 and then do init 5, the login screen comes up, but if
you login, there is a cycle of gnome-panel crashes and you can't do anything. If
you run system-config-display, a blue background image comes up, and a dialog
background briefly flashes up, then disappears and you're stuck with the blue
background and moveable arrow cursor. If I run startx from runlevel 3, it goes
right to a cycle of gnome-panel and nautilus crash messages, clicking through
them after a bit, it stops painting with the cursor moveable.
Gary Case tried the previous rel-eng compose 0505.0 and graphical install worked
Version-Release number of selected component (if applicable):
Since 0505.0, which apparently worked, only anaconda changed (of those three):
Reproduced on two Tylersburg EP developement systems, by gcase and myself.
We have one system in Westford with Geoff and John V, and another with Gary Case.
Geoff, do we have similar issues with the Tylersburg HEDT desktop unit? (IIRC,
they have a different graphics device installed.)
Right, the desktop version has no integrated graphics, and comes with a fancy
nVidia card. It works fine on 5.2, but hangs on 4.6, seems to be related to
graphics. Should be unrelated to this.
It appears that this problem is not restricted to the matrox cards. It looks
like a generic problem with this build of RHEL4U7. A completely different system
with an ATI ES1000 chip also fails, as does one with an Intel 82Q35 integrated
Could this be a dup of 446045?
Seems likely, yes.
From Kevin Martin in bug 446045 ...........
> I cannot tell if 446129 is related or not because it does not have any
> PCI IDs listed for the G200 there.
Setting this bug as a pre-req to bug 446129 until the situation is clarified.
(In reply to comment #6)
> From Kevin Martin in bug 446045 ...........
> > I cannot tell if 446129 is related or not because it does not have any
> > PCI IDs listed for the G200 there.
> Setting this bug as a pre-req to bug 446129 until the situation is clarified.
I think this is a dup of 446045
(In reply to comment #8)
> (In reply to comment #6)
> > From Kevin Martin in bug 446045 ...........
> > > I cannot tell if 446129 is related or not because it does not have any
> > > PCI IDs listed for the G200 there.
> > Setting this bug as a pre-req to bug 446129 until the situation is clarified.
> I think this is a dup of 446045
In order to verify if the problem is anaconda itself or the gtk2 bug please try
one of the 0514.0 or 0515.0 trees.
Please test this against a newer tree and report if you're still seeing the bug?
We think this is a dupe of #446045, but there's no way to be sure without testing.
John has this box and is taking over for me, so setting NEEDINFO to him.
I just tried to install RHEL 4.7 snapshot 4 and the anaconda graphical installer
came up fine. I think this bug is fixed.
duping to 446045 and removing from 4.8 list
*** This bug has been marked as a duplicate of 446045 ***