Bug 124084 - Gateway fails to boot after installation
Summary: Gateway fails to boot after installation
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda   
(Show other bugs)
Version: 2
Hardware: i386 Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-05-23 21:28 UTC by Jon Wohlberg
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-07 18:28:05 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 Jon Wohlberg 2004-05-23 21:28:21 UTC
Description of problem:
Same as ID 120366.
Using a Gateway E-6100 with 30. Ghz, 1 Gig of Ram, 80 gig HD
After installing FC2 (also same problem with FC1) I reboot the 
computer and it just freezes at the Gateway splash screen. I am 
unable to boot of a floppy, cd, or enter the bios. I can not do 
anything but unplug the HD, boot to a disk a wipe the drive. 
I tried the suggestions in article ID 120366 but had no luck

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

How reproducible:

Steps to Reproduce:
1. Install FC1 or FC2
2. Reboot computer
3. Become frustratred
Actual results:
Computer freezes at splash screen

Expected results:
Boot to FC1 or FC2

Additional info:
Tried following suggestion in article ID 120366 but it did not solve 
the problem

Comment 1 Ed Bailey 2004-05-24 18:36:43 UTC
Changing component to something more appropriate...

Comment 2 Jeremy Katz 2004-05-26 03:15:51 UTC
Are there any BIOS upgrades available for that machine?

Comment 3 Jon Wohlberg 2004-05-26 14:55:10 UTC
I tried to install with the bios that came with machine. When that 
didn't work I upgraded the bios to the latest version with the same 
results. As it stands the bios is at the latest version.

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