Bug 152639 - installer gets stuck on low-mem system
Summary: installer gets stuck on low-mem system
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 4
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-03-30 22:14 UTC by Florin Andrei
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-09-21 21:06:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Florin Andrei 2005-03-30 22:14:35 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050323 Firefox/1.0.2 Fedora/1.0.2-1.3.1

Description of problem:
Dual-PIII system, one IDE drive, 128MB RAM. I'm doing a text-mode install, in several ways: Custom, Server, etc.
I typically de-select all package groups, then re-select Development and Legacy Devel.

The installer always gets stuck when starting to install the libgcc package (which is the 3rd or 4th IIRC).
If i switch to the default graphical install mode, everything is fine.

I replaced the 128MB memory chip with a 256MB chip, and now the text-mode install is fine.

Normally i wouldn't report this, but i need the text-mode install to work flawlessly because i'm doing a lot of kickstart installs in text-mode, so perhaps this issue is signaling a hidden text-mode bug.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.see above
2.
3.
  

Additional info:

Comment 1 Jeremy Katz 2005-04-05 15:56:33 UTC
Any errors on tty3 or tty4?  Can you look at alt-sysrq-m (output will be on
tty4) to see if the kernel looks low on memory?

Comment 2 Florin Andrei 2005-04-05 17:04:56 UTC
Damn, i upgraded the system to 256M, i don't think there's an easy way to go
back. Sorry.

Comment 3 Jeremy Katz 2005-04-27 22:58:31 UTC
You can boot with mem=128M

Comment 4 Jeremy Katz 2005-09-21 21:06:23 UTC
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received the feedback we
requested, we will assume the problem was not reproduceable or has been fixed in
a later update for this product.  If you have further details, feel free to
reopen the report with the additional details attached.


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