Bug 116153 - Will Not Boot
Will Not Boot
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: acl (Show other bugs)
rawhide
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Stephen Tweedie
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-02-18 12:17 EST by Wallace Judd
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-02-18 12:36:11 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Wallace Judd 2004-02-18 12:17:16 EST
Description of problem: 
When I try to boot using the cdroms I made for FC2 test 1 the boot
disk will not boot on my machine. I am using a machine that has a via
chipset, but I am not sure if that is the problem. The first fedora
core boots just fine. Also I have burned the boot.iso image and the
problem is the same. It will try to boot, but at the point where it
says ready to load the image, it will just go back to the original
screen where you are trying to install using graphical or text or
whatever.


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

How reproducible:
Just try to install on the walmart 200 dollar special computer with
the via  chipset. (Yeah I know I am cheap).

Steps to Reproduce:
1. Insert first disk made from fc2 test1 burned cds.
2. Wait till it boots to install with graphics hit return. 
3. It will not boot into installation program, but takes you back to 2
  
Actual results: No boot.


Expected results: Boot into installation screen.


Additional info: Burning the boot.iso image results in the same problem.
Comment 1 Bill Nottingham 2004-02-18 12:36:11 EST
Not supported in the FC2 test1 boot disks; this issue is in the
release notes and the release announcement.

This will be fixed in the next test release.

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