Description of problem: The installer can't start in graphical mode on PS3, maybe because of memory shortage. The text mode can start. Version-Release number of selected component (if applicable): anaconda-11.4.1.36-1.ppc boot.iso 2008.09.16 (UTC) How reproducible: Every time. Steps to Reproduce: 1. Insert the installer DVD into PS3. 2. Boot PS3. 3. Start installer in graphical mode. 4. Select 'Skip' in the 'Disc Found' page in the 1st stage. Actual results: The installer stalls after the 'Disc Found' page. Expected results: There's any progress in the installation process. Additional info: I waited 1 hour+, but no progress. I selected 'OK' in the 'Disc Found' page so check the disc. But no error was detected.
Are there any messages on tty3, tty4, or tty5 that could indicate a problem?
I couldn't switch to the tty3 etc. I got a black screen after the 'Disc Found' page and the PS3 didn't respond to any input from keyboard or mouse. However it looks like the installer continued to access the DVD-ROM, because I could hear seek noise from the optical drive.
The graphical installer can start if I use a special hardware with 512MB memory. A retail PS3 console has 256MB memory, and only about 210MB is available for Linux. So I guessed the cause of this problem was memory shortage, but I'm not sure about that.
I tried similar situation on x86 PC by passing kernel option "mem=220M" to the installer, then the installer complained: You do not have enough RAM to use graphical installer. Starting text mode. and entered text mode. So the PowerPC installer should also behave the same?
When you say "available for Linux", what do you mean?
(In reply to comment #5) > When you say "available for Linux", what do you mean? Part of the memory is used by the hypervisor.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This should be fixed in notting's latest patch to anaconda.
I'm assuming this fixed since its so old. Feel free to reopen if you continue to see the bad behavior.