Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 155565 - kernel 2.6.11 doesn't recognize initramfs (wrong cpio-format)
Summary: kernel 2.6.11 doesn't recognize initramfs (wrong cpio-format)
Alias: None
Product: Fedora
Classification: Fedora
Component: mkinitrd
Version: 3
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Peter Jones
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2005-04-21 14:07 UTC by Chris Heitkamp
Modified: 2008-02-08 03:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-02-08 03:24:00 UTC

Attachments (Terms of Use)

Description Chris Heitkamp 2005-04-21 14:07:54 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.7) Gecko/20050418 Firefox/1.0.3

Description of problem:
Linux 2.6.11 doesn't recognize an initramfs when produced with mkinitrd-4.2.8 and cpio-2.6

Version-Release number of selected component (if applicable):
cpio-2.6 kernel-2.6.11

How reproducible:

Steps to Reproduce:
1. Build a kernel-2.6.11 with initramfs support
2. Build initramfs using mkinitrd
3. Boot kernel

Actual Results:  Kernel fails to load the initramfs and claims to have no root VFS.

Expected Results:  Kernel should decrompess the initramfs and start /init on the initramfs, with mounts the real root...

Additional info:

"cpio -c" generates the odc format, but the kernel needs the newc format.

Changing "cpio --quiet -c -o"
to "cpio --quiet -H newc -o"
or "cpio --quiet --format=newc -o" fixes this problem.

Comment 1 Matthew Miller 2006-07-10 20:13:39 UTC
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!

Comment 2 petrosyan 2008-02-08 03:24:00 UTC
Fedora Core 3 is not maintained anymore.

Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.

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