Sowmya.Krishnaswamy at nokia.com
2002-Oct-25 17:19 UTC
[syslinux] Having problems with PXELINUX parsing contents of pxelinux.cfg/AC134D6D
Hello, We are trying to use 'PXELINUX' for network boot with root file system on ramdisk, the kernel image vmlinuz and compressed root file system rootfs.img.gz are both present in /tftpboot directory PXELINUX client (pxelinux.0) requests and gets the config file AC134D6D from the TFTP server (which supports tsize option) contents are as follows timeout 10 prompt 1 label linux-new kernel vmlinuz append ramdisk_size=40000 initrd=rootfs.img.gz root=/dev/ram After this point we see tftp requests coming in for linux, linux.0, linux.cbt instead of vmlinz or rootfs.img.gz! Any idea why this happens? Is there some 'error' in the format of config file we are using? Are tabs allowed? Thanks, Sowmya
Duetsch Thomas
2002-Oct-25 17:32 UTC
[syslinux] Having problems with PXELINUX parsing contents of pxelinux.cfg/AC134D6D
Hi, you should probably increase the timeout (10 = 1 second, is ap retty short time to react) Another thing you might want to do is add a default boot by adding DEFAULT linux-new in your config file. So try: PROMPT 1 DEFAULT linux-new TIMEOUT 50 label linux-new kernel vmlinuz append ramdisk_size=40000 initrd=rootfs.img.gz root=/dev/ram I hope that works, _tom -----Original Message----- From: Sowmya.Krishnaswamy at nokia.com [mailto:Sowmya.Krishnaswamy at nokia.com] Sent: Freitag, 25. Oktober 2002 13:19 To: syslinux at zytor.com Subject: [syslinux] Having problems with PXELINUX parsing contents of pxelinux.cfg/AC134D6D Hello, We are trying to use 'PXELINUX' for network boot with root file system on ramdisk, the kernel image vmlinuz and compressed root file system rootfs.img.gz are both present in /tftpboot directory PXELINUX client (pxelinux.0) requests and gets the config file AC134D6D from the TFTP server (which supports tsize option) contents are as follows timeout 10 prompt 1 label linux-new kernel vmlinuz append ramdisk_size=40000 initrd=rootfs.img.gz root=/dev/ram After this point we see tftp requests coming in for linux, linux.0, linux.cbt instead of vmlinz or rootfs.img.gz! Any idea why this happens? Is there some 'error' in the format of config file we are using? Are tabs allowed? Thanks, Sowmya _______________________________________________ SYSLINUX mailing list Submissions to SYSLINUX at zytor.com Unsubscribe or set options at: http://www.zytor.com/mailman/listinfo/syslinux
Sowmya.Krishnaswamy at nokia.com
2002-Oct-25 18:41 UTC
[syslinux] Having problems with PXELINUX parsing contents of pxelinux.cfg/AC134D6D
Hi, Adding the DEFAULT helps! Thanks PXELINUX is downloading vmlinuz now. However the tftp server complains saying that its expecting ack for block [n] when its getting back ack for block [n-1]! Finally gets an ack for block [n] and moves on but this is going to take a lot longer to download vmlinuz than it would if the sequence numbers in ACK was synchronised. Would you have any suggestions on parameters to finetune at the server end or is there a hidden bug in PXELINUX-TFTP! Thanks, Sowmya -----Original Message----- From: ext H. Peter Anvin [mailto:hpa at zytor.com] Sent: Friday, October 25, 2002 10:52 AM To: Duetsch Thomas Cc: Krishnaswamy Sowmya (NET/MtView); syslinux at zytor.com Subject: Re: [syslinux] Having problems with PXELINUX parsing contents of pxelinux.cfg/AC134D6D Duetsch Thomas wrote:> Hi, > > you should probably increase the timeout (10 = 1 second, is ap retty short > time to react) > Another thing you might want to do is add a default boot by adding > DEFAULT linux-new > in your config file. > So try: > > PROMPT 1 > DEFAULT linux-new > TIMEOUT 50 > > label linux-new > kernel vmlinuz > append ramdisk_size=40000 initrd=rootfs.img.gz root=/dev/ram > > I hope that works, >Yes, without the DEFAULT option it will not pick a label unless it's called "linux". -hpa