| 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
| ||
|
Message-ID: <m37iztv6y1.fsf@lugabout.jhcloos.org> Date: Sun, 24 Sep 2006 07:29:03 -0400 From: James Cloos <cloos@...loos.com> To: linux-kernel@...r.kernel.org Subject: bzImage too big to boot??? 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 <cloos@...loos.com> OpenPGP: 0xED7DAEA6 - 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/
Powered by blists - more mailing lists