Re: Kernel image size limitations silo?

[crn@netunix.com]

It is not that simple.
Basically ( the Oracle guys should know more ) the OBP only initialises
a small block of memory so your image must fit into that space until it
has initialised enough memory management to use more space.
The clue is to cut the image down to the absolute minimum to get the
install started. Its a long time ago so my memory is a tad vague, I
seem to recall needing to use pivot root when I was working on Sparc32.

Hope this helps.



On Mon, 28 Dec 2015, John Paul Adrian Glaubitz wrote:

> Hi Jose (and others @Oracle)!
>
> I am in the final process of creating a fresh set of debian-installer
> images for sparc64 and just stumbled over the following comment in
> the scripts which create the sparc install images [1]:
>
> # Sparc64 kernel is so big, that uncompressing it corrupts SILO memory,
> # uncompress it before hand.
>
> Does this apply to the 64-bit version of silo which I built from git
> plus your patches from [2]?
>
> I assume this no longer applies and I can replace the zcat in the final
> line with just a simple "cp".
>
> Cheers,
> Adrian
>
> > [1]
> https://alioth.debian.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=debian-cd/debian-cd.git;a=blob;f=tools/boot/stretch/boot-sparc;h=fa8715e4a62c781e0f13bff78ef9282b5ba221da;hb=HEAD
> > [2] https://lists.debian.org/debian-sparc/2015/12/msg00092.html
>
> --
> .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaubitz@debian.org
> `. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
>  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913