From: Denis Vlasenko <vda.linux@googlemail.com>
To: James Cloos <cloos@jhcloos.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bzImage too big to boot???
Date: Sun, 24 Sep 2006 16:33:14 +0200 [thread overview]
Message-ID: <200609241633.14250.vda.linux@googlemail.com> (raw)
In-Reply-To: <m37iztv6y1.fsf@lugabout.jhcloos.org>
On Sunday 24 September 2006 13:29, James Cloos wrote:
> I don't know whether this is a build-time issue or a grub issue, but
> I've found that on my (pent-3m) laptop I cannot boot any kernel that
> is larger than about 2500 K. (2504K boots, 2552K fails.)
>
> Past that threshold grub complains: ERR_BAD_FILETYPE.
>
> A 2504 K bzImage translates to a 6128 K vmlinux, 2552 K to 6252 K.
>
> Should bzImages that large be bootable on x86?
Yes. I can boot 3MB bzImage with lilo and with linld,
although lilo seems to have some trouble with initrd
with kernel images that large.
--
vda
prev parent reply other threads:[~2006-09-24 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 11:29 bzImage too big to boot??? James Cloos
2006-09-24 14:33 ` Denis Vlasenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200609241633.14250.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=cloos@jhcloos.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox