Bug 160472 - Fedora Core 4 installation fails on MPC Clientpro system
Fedora Core 4 installation fails on MPC Clientpro system
Status: CLOSED DUPLICATE of bug 159026
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2005-06-15 07:47 EDT by Kevin Taylor
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-06-15 14:41:47 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kevin Taylor 2005-06-15 07:47:16 EDT
Description of problem:

I'm trying to install FC4 on a MPC clientpro system (with a SATA root disk) and
receive the following messages during the initrd stage:

RAMDISK: Couldn't find valid ramdisk image starting at 0
VFS: cannot open root device "<NULL>" or unknown-block (8,3)

Then kernel panic. I've seen similar issues with FC2 when upgrading a kernel and
not recreating the initrd with these options:

--preload=sd_mod --preload=scsi_mod --with=ata_piix 

However, I'm not sure how to rebuild the install cd with an updated initrd to
try this.

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

How reproducible:

You may not be able to reproduce this where you are depending on the type of
systems you have. The FC4 install cd works fine on a gateway system we have also
with a SATA root disk. It may be BIOS/motherboard rev dependant.
Comment 1 Warren Togami 2005-06-15 14:41:47 EDT
Indeed.   Most likely the strange workaround in Bug 159026 will allow you to
boot your system.  An announcement explaining what happened is forthcoming.

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

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