hi,
On Di, 2009-02-10 at 16:34 -0800, Marc Singer wrote:
as soon as i switch to 16 blocks (2097152 bytes which is needed for the
above kernel size) apex gets stuck at copying the kernel, after a day of
digging top to bottom through slugimage and apex i still dont understand
why this
On Wed, Feb 11, 2009 at 02:36:20PM +0100, Loïc Minier wrote:
On Tue, Feb 10, 2009, Marc Singer wrote:
I responded to L. Minier with the suggestion that you move the load
address for the kernel to something after APEX. Try 0x0100. You
could also change the VMA address for APEX to be
On Wed, Feb 11, 2009 at 05:04:20PM +0100, Oliver Grawert wrote:
hi,
On Di, 2009-02-10 at 16:34 -0800, Marc Singer wrote:
as soon as i switch to 16 blocks (2097152 bytes which is needed for the
above kernel size) apex gets stuck at copying the kernel, after a day of
digging top to bottom
On Wed, Feb 11, 2009 at 12:10:43AM +0100, Oliver Grawert wrote:
hi,
i have a weird problem trying to build a d-i-nslu2.bin image with
slugimage that is supposed to carry a kernel binary of a size of 1978300
bytes ...
as i understand by looking at the d-i code that generates di-nslu2.bin
4 matches
Mail list logo
