Bug 43744 - System will not boot
Summary: System will not boot
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: bootpc   
(Show other bugs)
Version: 7.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Elliot Lee
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2001-06-07 00:04 UTC by Steven
Modified: 2008-05-01 15:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-07-16 13:41:10 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Steven 2001-06-07 00:04:55 UTC
Description of Problem:  During installation system would hang after the 
detection of the CD-ROM.  Some how was able to get past it on one occasion 
and performed install.  Upon rebooting system after install it continues 
to hang every time at this location.  Would like to know how or why system 
hangs or a way to correct.  Are there any known BIOS settings that could 

How Reproducible:
Every time

Steps to Reproduce:
1. Boot system
2. Try to install OS

Actual Results:
System hangs with no error messages

Expected Results:
Boot to OS

Additional Information:
All hardware is new and was burned in for 2 weeks excecpt for hard drives 
which were factory new and did not contain any OS prior.

Asus mother board latest BIOS
Twin Intel P800mhz
Twin golden orb coolers
1/2gig ECC RAM (Micron)
Acer 50x CD
(2)IBM 7200 75gig ATA100 drives
Promise Technologies TX2 controller running RAID1
Intel Pro 10/100
Rage128 AGP video

Comment 1 Elliot Lee 2001-08-26 20:53:56 UTC
This might be an issue for Red Hat tech support instead of bugzilla - there
doesn't appear to be a specific problem here that you can provide details or a
solution for.

I would start by trying RHL 7.1 instead of 7.0 - newer usually means less bugs. :)

Sorry for the delay. (bootpc has nothing to do with the boot process,
incidentally. Most likely this was a 2.2.x kernel issue.)

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