[syslinux] Size limit for initrd in PXELINUX?

[Duetsch Thomas]

Hi,

sorry for taking so long, but I needed to come up with a workaround and
haven't had much time.
I tried 2.0-pre11 and still have the same behaviour as before.
I was able to get some more differentiated information for the different
image sizes.
The first time it doesn't work is at an image size somewhere between
12288000 and 12582912 bytes. In this case, I get the "Couldn't find valid
RAM disk image starting at 0."-message after the kernel started.
Then, somewhere between 13312000 and 13824000 bytes, the image is downloaded
and the next thing I get is:

Ready
Uncompressing Linux..

ran out of input data

--System halt

At 14848000 bytes, the screen just goes crazy. Strange colors and special
characters start blinking all over the place.

Well, and after that, the system just reboots.
I hope that helps in some way.
Bye,

_tom


-----Original Message-----
From: H. Peter Anvin [mailto:hpa at zytor.com]
Sent: Dienstag, 22. Oktober 2002 16:38
To: Duetsch Thomas
Cc: Josef Siemes; syslinux at zytor.com
Subject: Re: [syslinux] Size limit for initrd in PXELINUX?


Duetsch Thomas wrote:
> Hi,
> 
> well the system starts up just fine, the Intel Boot Agent (Version 4.0.17)
> gets its IP address from the DHCP and then it continues as follows:
> 
> PXELINUX 1.76 2002-08-27 Copyright (C) 1994-2002 H. Peter Anvin
> UNDI data segment at:   000862F0
> UNDI data segment size: 94B0
> UNDI code segment at:   0008F7A0
> UNDI code segment size: 2020
> PXE entry point found (we hope) at 8F7A:0106
> My IP address seems to be C0A80004 192.168.0.4
> ip=192.168.0.4:192.168.0.1:192.168.0.1:255.255.255.0
> TFTP prefix:
> Trying to load: pxelinux.cfg/C0A80004
> ...
> Trying to load: pxelinux.cfg/C
> Trying to load: pxelinux.cfg/default
> boot: linux
> Loading vmlinuz-2.4.9-31................
> Loading initrd.gz..........................
> 
> Depending on how big the initrd.gz-file is, the system then behaves as
> described earlier.
> 

This looks normal.  I don't think this has anything to do with the 512K
memory issue.  This might be an issue with the memory overwrite bug just
described; please try 2.00-pre9.
	
	-hpa