Bug 123975 – Installer doesn't boot

Bug 123975 - Installer doesn't boot

Summary:	Installer doesn't boot

Status:	CLOSED DUPLICATE of bug 121819

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	kernel (Show other bugs)
Sub Component:
Version:	2
Hardware:	i686 Linux

Priority	medium Severity high
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-05-22 04:16 EDT by Dick Knol
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:03:31 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 Dick Knol 2004-05-22 04:16:01 EDT

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6)
Gecko/20040206 Firefox/0.8

Description of problem:
I tried FC2-test3 and FC2-final, test3 just hangs after loading
initrd, while displaying "Now booting the kernel...".

FC2-final just reboots after loading initrd.

I have a ASUS P4P800-E DeLuxe motherboard with 2 IDE-drives attached.
I tweaked with different BIOS-settings, but that didn't help.

Fedora Core 1 does boot (and install).

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


How reproducible:
Always

Steps to Reproduce:
1. Put the Installation disk #1 in the drive
2. Boot
3. Hang / reboot (depends on version)
    

Actual Results:  I was not able to install FC2

Expected Results:  It should have booted

Additional info:

Comment 1 Arjan van de Ven 2004-05-22 04:18:46 EDT


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

Comment 2 Red Hat Bugzilla 2006-02-21 14:03:31 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.