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?
File(1) shows the same output for the larger files as for the smaller
ones, so if it is a bug in the vmlinux -> bzImage build process it is
corrupting the files only beyond the point that file(1) checks.
The laptop's optical drive failed?, so I cannot test whether syslinux
can boot it. (Unless there is a way to have grub boot a vfat file-
system image with syslinux and the kernel?)
Any thoughts on where I should look? Or should I just bug-grub?
-JimC
? The old adage that software cannot kill hardware doesn't apply
when the hardware expects the software to moderate the thermally
inefficient laser and lacks safeguards for software which doesn't
know how to keep the laser from overheating and letting all of the
magic smoke out..... ;-/
--
James Cloos <[email protected]> OpenPGP: 0xED7DAEA6
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