Re: bzImage patch ? for monolithic kernels
H. Peter Anvin (hpa@transmeta.com)
5 Aug 1999 23:41:54 GMT
Followup to: <Pine.LNX.4.10.9908052016210.13486-100000@ps.cus.umist.ac.uk>
By author: Riley Williams <rhw@MemAlpha.CX>
In newsgroup: linux.dev.kernel
>
> > I am using bzImage. I get the following errors that are all
> > related to the fact that the kernel size is > 1 Meg.
>
> > Root device is (8, 1)
> > Boot sector 512 bytes.
> > Setup is 3440 bytes.
> > System is 1036 kB
> > System is too big. Try using modules.
> > make[1]: *** [bzImage] Error 1
> > make[1]: Leaving directory
> > `/mnt/micropolis2/src/linux.2312/arch/i386/boot'
> > make: *** [bzImage] Error 2
>
> > Anyone know a fix? I know that some previous debate had raged
> > about bzImage should be able to handle up to 16M kernel sizes
> > but have found no data/patches/etc on what to do to get past 1M.
>
> Whilst the bzImage format itsef can handle kernels up to 16M in size,
> there is a problem with boot loaders once the kernel gets to be over
> 1M in size, and that is the current limit.
>
> There HAS to be a way round that limit, but I for one haven't the
> foggiest what it is...
>
That's completely bogus. Those boot loaders (which??) are broken. I
know for a fact that SYSLINUX has no such limit, lbcon definitely will
not have it, and hard-coding that limit into the kernel compile
sequence is a BUG.
If LILO, say, doesn't support loading a bzImage > 1 MB then LILO
should complain, but not prevent someone from compiling the image for
use with another boot loader.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/