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 124068

Summary: Fedora Core 2: Installer reboot the system when loading initrd.img
Product: [Fedora] Fedora Reporter: Kostadin Chikov <kostadin.chikov>
Component: distributionAssignee: Bill Nottingham <notting>
Status: CLOSED DUPLICATE QA Contact: Bill Nottingham <notting>
Severity: high Docs Contact:
Priority: medium    
Version: 2CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:03:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kostadin Chikov 2004-05-23 19:19:15 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007

Description of problem:
I am not able to start the installation of Fedora Core 2 (not a test
release). When I boot from the CD I get that far:

loading vmlinuz......
loading initrd.img.............

and then the computer reboots. This happens every time I start the
installation of FC2.
I am able to start the installation of RH9 and FC1. This problem comes
only by FC2. I checked the downloaded images with md5sum, they are OK.

Here is what I have on my system:
Asus P4P800 Motherboard with Intel 865PE Chipset
Intel Pentium IV 2.8GHz 800MHz
Asus R9600SE/TD ATI Radeon 9600SE
1GB RAM



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


How reproducible:
Always

Steps to Reproduce:
1.Start the installation of FC2
2.
3.
    

Additional info:

Comment 1 Bill Nottingham 2004-05-25 16:38:29 UTC

*** This bug has been marked as a duplicate of 121819 ***

Comment 2 Red Hat Bugzilla 2006-02-21 19:03:37 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.