linux-kernel - Re: bzImage too big to boot???

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200609241633.14250.vda.linux@googlemail.com>
Date:	Sun, 24 Sep 2006 16:33:14 +0200
From:	Denis Vlasenko <vda.linux@...glemail.com>
To:	James Cloos <cloos@...loos.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: bzImage too big to boot???

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/