Re: zImage not supported for 2.2.20?

Matthias Andree (matthias.andree@stud.uni-dortmund.de)
Fri, 28 Dec 2001 14:35:08 +0100


On Fri, 28 Dec 2001, Roy Hills wrote:

> Note that I build the kernels on a separate machine, hence the "scp" to
> copy the kernel & sysmap to the target system.
>
> The old 2.2.17 zImage kernel that runs fine has a filesize of 462060 bytes
> and
> reports 784k kernel code, 412k reserved, 1168k data, 36k init.
>
> The new 2.2.20 zImage kernel that fails has a filesize of 482795 bytes.
> Actual sizes are not known as the system fails with "out of memory" just
> after the decompression of the kernel and before any kernel messages get
> printed.

Hum, I recall this struck another 2.2.x version already, and the
workaround was to hack some HASH size in one of the arch/i386/boot/
files. I don't recall the details, but you can find them in the
archives.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/