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 20976 - bzImage created does not boot
bzImage created does not boot
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2000-11-16 14:42 EST by Need Real Name
Modified: 2007-04-18 12:29 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-12-14 22:44:02 EST
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 Need Real Name 2000-11-16 14:42:58 EST
Installed RH7.0 and all the Updates.

I do a make mrproper; make xconfig; make dep; make bzImage;

in xconfig i load the "configs/kernel-2.2.16-i686", save and exit.

The kernel compiles and the bzImage is made.

do a cp bzImage /dev/fd0 and boot. I see the following :


Uncompressing Linux...

invalid compressed format (err=2)

 -- System halted --


I have tried all the iX86 config files all with the same result.
The kernel is also to large (611k) for zImage.

This worked with kernel-2.2.14-XX
Comment 1 Arjan van de Ven 2000-11-20 10:45:05 EST
you should probably not use "cp" with this.
Could you try:

dd if=bzImage of=/dev/fd0

(and then use rdev to set your root filesystem)
Comment 2 Need Real Name 2000-11-20 13:21:49 EST
I tried using the dd if=..... and the same thing.

I also grabbed the 2.4.0 kernel and that builds/boots just fine.

I also symlink'd /usr/include/[asm,linux] to /usr/src/linux-2.2.16/include/
[asm,linux] so that the includes are from the 2.2.16 kernel rather than the 
2.4.0. But that still does not produce a bootable kernel.

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