Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 125874 - Error in Anaconda with AMD64
Summary: Error in Anaconda with AMD64
Keywords:
Status: CLOSED DUPLICATE of bug 119447
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-06-13 02:26 UTC by Ben
Modified: 2007-11-30 22:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:04:03 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Text of Error (deleted)
2004-06-13 02:29 UTC, Ben 		no flags Details
View All

Description Ben 2004-06-13 02:26:56 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET 
CLR 1.1.4322)

Description of problem:

During the "Performing Post Install Configuration" part of 
installation an exception occurs.  It will occur in graphical or text 
install modes.  


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


How reproducible:
Always

Steps to Reproduce:
1.Install with all options except Server components
2.
3.
    

Actual Results:  Install caused error and was unable to complete 
install.  OS was unusable.

Expected Results:  A working system.

Additional info:
Comment 1 Ben 2004-06-13 02:29:24 UTC 
Created attachment 101090 [details]
Text of Error
Comment 2 Pete Stieber 2004-07-09 18:08:35 UTC 
See bug number 124029. The work around for me was to use

linux mem=256M

when installing. My HW

MB: Tyan Tomcat K8S(S2850G2N)
Processor: AMD Opteron 146 (2GHz)
RAM: 1 GB
HD: Maxtor 80GB 7200 RPM IDE ULTRA ATA 133

Maybe it's a problem with x86_64 systems with more that X MB of 
memory where X > 256M.
Comment 3 Jeremy Katz 2004-10-07 18:49:20 UTC 

*** This bug has been marked as a duplicate of 119447 ***
Comment 4 Red Hat Bugzilla 2006-02-21 19:04:03 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.