kumon at flab.fujitsu.co.jp
2004-May-28 13:14 UTC
[syslinux] pxelinux: 2.04 works but 2.09 doesn't
Hi, Recently I upgraded pxelinux.0 from 2.04 to 2.09, after that the pxelinux doesn't correctly obtain server's IP address. The true address is 172.20.0.101, but 2.09 understand it as 172.20.0.11. "0" is dropped. As a result, root nfs-mount is directed to the non existent server. Following is the full screen dump of pxeboot by pxelinux 2.09: -------------------------------------------------------------------------- Broadcom UNDI PXE-2.1 (build 082) v7.0.3 Copyright (C) 2003 Broadcom Corporation Copyright (C) 1997-2000 Intel Corporation All rights reserved. Intel Base-Code, PXE-2.1 (build 083) Copyright (C) 1997-2001, Intel Corporation CLIENT MAC ADDR: 00 E0 81 29 CF 63 GUID 00020003-0004-0005-0006-000700080009 CLIENT IP: 172.20.8.15 MASK: 255.255.0.0 DHCP IP: 172.20.0.101 PXELINUX 2.09 2004-04-26 Copyright (C) 1994-2004 H. Peter Arvin UNDI data segment at: 000964C0 UNDI data segment size: 4CB0 UNDI code segment at: 0009B170 UNDI code segment size: 49B8 PXE entry point found (we hope) at 9B17:00D6 My IP address seems to be AD14080F 172.20.8.15 ip=172.20.8.15:172.20.0.11:0.0.0.0:255.255.0.0 TFTP prefix: Trying to load: pxelinux.cfg/01-00-e0-81-29-cf-63 Trying to load: pxelinux.cfg/AC14080F -------------------------------------------------------------------------- # Some typo may be included. This screen shot was captured by a camera # and wrote-down by hand. '0' and '8' is difficult to # distinguish. When I use 172.20.0.4 as a server, it works fine with pxelinux 2.09. Some string manipulation may have trouble. What should I do next? -- Kouichi Kumon, Director of Grid Computing and Bioinformatics Laboratory, Fujitsu Labs. kumon atmark flab.fujitsu.co.jp
kumon at flab.fujitsu.co.jp wrote:> Hi, > > Recently I upgraded pxelinux.0 from 2.04 to 2.09, after that the > pxelinux doesn't correctly obtain server's IP address. > > The true address is 172.20.0.101, but 2.09 understand it as > 172.20.0.11. "0" is dropped. As a result, root nfs-mount is > directed to the non existent server. >Try 2.10-pre4 when it comes out. I'll try to have a fix in that version for this problem. In the meantime, you shouldn't really be using "ipappend" if you can avoid it. Typically "ip=dhcp" is a better choice (and an even better choice is to use an initrd.) -hpa