Red Hat Bugzilla – Bug 446571
X hangs on white iBook when running Fedora 9 installer
Last modified: 2009-07-14 13:29:56 EDT
Description of problem:
When booting from the Fedora 9 boot.iso in order to run the installer, and it
gets to the point of starting X to run the graphical installer, the X server
hangs, with the whole screen going, in sequence, black, white, red, green, blue,
then various black/white stippled patterns, then back to black. It spends about
2 seconds showing each color/pattern.
While it is in this state it is possible to switch away to another console with
Version-Release number of selected component (if applicable):
Whatever is in the Fedora 9 boot.iso for ppc.
Boot F9 boot.iso on a white 1.4GHz iBook G4 (PowerBook6,7), which has an ATI M11
NV video chip.
Steps to Reproduce:
1. Get F9 boot.iso, burn cdrom, boot iBook from CD
2. Answer questions from text-mode first stage installer
3. Admire the pretty patterns on the screen :)
Screen shows solid colors and stipple patterns
Graphical installer window visible
I have attached the ps output showing the X command line, the X log, the X
config file used, and the anaconda.log, in case it is useful.
Created attachment 305439 [details]
X config file
Created attachment 305440 [details]
X log file
Created attachment 305441 [details]
Anaconda log file
Created attachment 305442 [details]
ps output for X server
If you have enough willpower, could you try installation again, please? When the
anaconda crashes, please, switch to the console (Ctrl+Alt+F2)and cp /tmp/X* to
some other place -- USB stick, some other computervia network, some on the
Internet, and please attach it to the bug report as individual uncompressed file
attachments using the bugzilla file attachment link below.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
I already did that. The only files in /tmp starting with "X" were X.log and
XConfig.test. See the "X config file" and "X log file" attachments in the list
of attachments below, or comments #1 and #2 above.
I did some further experimentation. The problem seems to be caused by the X
config file specifying a 800x600 resolution, when the native panel resolution is
1024x768. If I stop anaconda (with kill -STOP) and kill the non-working X
server, take out the Anaconda screen section, and run Xorg, it starts up
correctly and displays the root weave and X cursor.
So there are in fact two problems here:
1. Whatever anaconda is using to generate the X config file is incorrectly
assuming that the screen can do 800x600;
2. The radeon driver is blowing up when asked to do 800x600 on a 1024x768 LCD panel.
Created attachment 308325 [details]
X log file for the working case
This is the log file from Xorg when I ran it without the -screen Anaconda
option. I stopped anaconda and killed the X server, then ran it with the same
command (as in attachment 305442 [details]) but without -screen Anaconda. It started
fine and displayed the X cursor. I switched back to VT2 and pressed ^C, at
which point the X server crashed with a segfault. This is the log file from
<airlied> abartlet: probably overwriting the palette.
<airlied> or a test pattern trigger..
<abartlet> it seems a bit extreme for getting the resolution wrong :-)
<airlied> abartlet: it might be an LCD built-in thing either.
<airlied> abartlet: when we don't power it up correct it goes into some wierdass
<airlied> abartlet: but if its running F9 with all updates installed, I'd be
interested in an xorg log file.
Created attachment 312530 [details]
Log file from X server
Yes, it still misbehaves with the updated X server. Here is the log file as
I can confirm comment #7 from Paul Mackerras: When I installed Fedora (8) on my iBook I had the same problem.
Is it possible that the OpenFirmware-based ATI Radeon Mobility is unable to generate any other display size than 1024x768 on the internal LCD? Perhaps it is the LCD which does not like other sizes.
Setting various display sizes on the external port (VGA-0) works fine btw.
> 1. Whatever anaconda is using to generate the X config file is incorrectly
> assuming that the screen can do 800x600;
Yes, this indeed a problem and caused me to install in text mode. Btw: How one activates text mode installation via yaboot is badly documented.
Long time ago I wrote about the installation procedure:
> 2. The radeon driver is blowing up when asked to do 800x600 on a 1024x768 LCD
See above. I think it is possible that the hardware only support one display size since it is meant to be run with that proprietary OS from Apple solely...
Some workaround for the iBook G4 hardware that would make anaconda aware of that situation would be cool.
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '9'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 9's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.