I wrote:
> So yes, something is wrong. It could of course be that the kernel dies an
> early death because of some internal conflicts which aren't related to
> size. Investigating ...
Well, found it. It was size, indeed, just not exactly in the most
obvious way ...
With the attached patch (for 2.3.48), kernels using up to 7 MB should
be okay. This should correspond roughly to a compressed size of 2.5 MB.
Tried with bootimg (vmlinux) and LILO (bzImage). Both get the kernel
running (*). Kernel statistics:
# size vmlinux
text data bss dec hex filename
4235019 752417 560816 5548252 54a8dc vmlinux
# objcopy -O binary vmlinux bin; ls -l bin
-rwxr-xr-x 1 root root 4994368 Mar 3 18:59 bin*
# ls -l arch/i386/boot/bzImage
-rw-r--r-- 1 root root 2221497 Mar 3 18:59 arch/i386/boot/bzImage
(* In order to reach this size, I had to include tons of drivers for
which I don't have hardware anyway, so at one point it hangs in a
detection loop (probably TCIC-2), from which it only proceeds if I
quickly "power-cycle" the machine (this is a Sony-Vaio-ism, don't
try this at home ;-), and then it eventually dies because I forgot
devfs=nomount, oh well :-)
- Werner
-- _________________________________________________________________________ / Werner Almesberger, ICA, EPFL, CH werner.almesberger@ica.epfl.ch / /_IN_N_032__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/
- 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/
This archive was generated by hypermail 2b29 : Tue Mar 07 2000 - 21:00:15 EST