Bug 119465 – install cd boot fails

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 119465 - install cd boot fails

Summary:	install cd boot fails

Status:	CLOSED DUPLICATE of bug 119386

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	kernel (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Arjan van de Ven
QA Contact:	Brian Brock
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2004-03-30 14:21 EST by Dave Rogers
Modified:	2007-11-30 17:10 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-02-21 14:02:16 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)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Dave Rogers 2004-03-30 14:21:43 EST

Description of problem:
Cannot boot

Version-Release number of selected component (if applicable):
FC2 Test 2 CD 1

How reproducible:
Always

Steps to Reproduce:
1. insert CD 1
2. reset
3. 
  
Actual results:
Brief boot faiure message on CDROM

Expected results:

boot up into install script

Additional info:

This system (my test box) has FC1 installed and has no problems. It
boots the FC2 Test 1 CD fine. Tried the CD on another machine and it
boots correctly. So I suspect it may be architecture dependent. The
system in question is a 200MHz Intel P2 /w ASUS motherboard. Does FC2
Test 2 only have i686 kernels? If so that would explain it.

Comment 1 Bill Nottingham 2004-03-30 17:06:35 EST


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

Comment 2 Red Hat Bugzilla 2006-02-21 14:02:16 EST

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.