[Soekris] Can get pxelinux to boot but no kernel?

Huub Reuver h_reuver at mantell.xs4all.nl
Sat Nov 30 12:00:58 UTC 2002


On Fri, Nov 29, 2002 at 10:22:30PM -0600, Dion Rowney wrote:
> I figured it out so please ignore... It was looking to tftp a file called 
> "linux" so I renamed the vmlinuz file to linux and put it in the /tftpboot 
> directory.
> 
> It then loaded this kernel and started booting.

If you're using the same pxe-configuration as I am, you will find the
configuration in pxelinux.cfg/default. For multiple configurations the 
configuration can be adjusted (see documentation pxelinux/syslinux).

If you are using a different configuration, the same options should be 
present.

> It has been booting for about 20 minutes so far.  is this time normal or do 
> I have a network problem?

Does the net4521 know where it should start looking for a nfsroot? Does it
know its IP-address?

../pxelinux.cfg/default:
DEFAULT net4501-2.4.9 root=/dev/nfs nfsroot=192.168.3.5:/tftpboot/net4501/
IPAPPEND 1 

In the above example the kernel should be able to use nfs as its root 
filesystem. The "net4501-2.4.9" is were you point the kernel to be used.
"vmlinux" in your first try or "linux" in your second. Note that the IPAPPEND
is required. After linux has booted it has to be told its IP-address (again).

I'm not quite sure if linux can work with hostnames in the nfsroot statement
already. Normally nameservers are available after init has started.

> >I have gotten close but I am missing something and am hoping someone can 
> >help.  I have the Soekris 4521 and and trying to boot debian over the 
> >network.  I can get it to connect via tftp and retrieve the pxelinux.0 and 
> >the config file but it stops as it appears to try looing for a file called 
> >linux then linux.cbt then linux.com.
> >
> >Here is the output and the logs if they help:
> >
> >comBIOS Monitor.   Press ? for help.
> >
> >>boot f0
> >
> >BootManage UNDI, PXE-2.0 (build 082)
> >BootManage PXE-2.0 PROM 1.0, NATSEC 1.0, SDK 3.0/082 (OEM52)
> >Copyright (C) 1989,2000 bootix Technology GmbH, D-41466 Neuss.
> >PXE Software Copyright (C) 1997, 1998, 1999, 2000 Intel Corporation.
> >Licensed to National Semiconductor
> >
> >CLIENT MAC ADDR: 00 00 24 C0 76 88
> >CLIENT IP: 192.168.1.5  MASK: 255.255.255.0  DHCP IP: 192.168.1.2
> >GATEWAY IP: 192.168.1.1
> >3;01H3;97HP3;01HX3;01HE3;01HL3;01HI3;01HN3;01HU3;01HX3;01H 
> >3;01H13;01H.3;01H63;H
> >PXELINUX 1.67 2002-02-03  Copyright (C) 1994-2001 H. Peter Anvin
> >
> >^^^this is as far as it appears to get.
> >
> >Nov 28 11:00:54 linux dhcpd: DHCPREQUEST for 192.168.1.5 (192.168.1.2) 
> >from 00:00:24:c0:76:88 via et
> >h0
> >Nov 28 11:00:54 linux dhcpd: DHCPACK on 192.168.1.5 to 00:00:24:c0:76:88 
> >via eth0
> >Nov 28 19:00:55 linux in.tftpd[32295]: RRQ from 192.168.1.5 filename 
> >/pxelinux.0

You use the logfiles for finding the error. I suggest you learn to use
tcpdump and tethereal. You will find it easier to work with raw data to
find a problem. A good start is:
tcpdump -ni eth0 host 192.168.0.1
tethereal -ni eth0
(For more information see the man-pages.)

Tcpdump shows the connections that are to be build. Tethereal can provide 
more information such as readable output of traffic like ARP and such.

Hope above information will help you a little.

With regards,
Huub



More information about the Soekris-tech mailing list