[syslinux] Network Loading of freeBSD

[Geert Stappers]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, Dec 21, 2005 at 10:09:50AM +0100, Karl Rothenhöfer wrote:
> > -----Ursprüngliche Nachricht-----
> > Auftrag von Geert Stappers
> > Gesendet: Dienstag, 20. Dezember 2005 11:37
   <snip/>
> > > # results of ethereal trace
> > >
> > > Ethereal trace shows reception of
> > >
> > > pxelinux.0: 24 packets 512 Bytes data each + 1 packet 176 Byte data
> > > everything well acknowledged
> > >
> > > pxelinux.cfg/01:00:10:DC:0E:3F:31: 2 packets containing proper data
> > > everything well acknowledged
> > 
> > My bet: the acknowledge is not seen by the ErgoPro
> ErgoPro is client and hence sends the acknowlegements for the load packets
> received. The trace really indicates that the client has well and completely
> received pxeboot.0. The Problem must happen after successful reception.

I think you are right.

> > > pxeboot.0: 420 packets 512 Bytes data each + 1 packet 0 Byte data
> > > everything well acknowledged

Previous I did missed that pxeboot.0 was recieved by pxelinux.0

> > > After this no further activities of client ErgoPro are traced anymore,
> > > especially no further load request for additional data
> > >
> > >
> > > I know, that my above story is very similar to [syslinux] run FreeBSD
> > > "pxeboot" from pxelinux.0? in the syslinux mailing list of 2003. But
> > there
> > > the problem disappeared by magic with a new release of pxelinux, which
> > > meanwhile became obsolete. So the results have not been helpful for me.
> > >
> > 
> > AFAIK does EtherBoot do polling for recieving packets
> > and does PXE depend on interrupts for recieving packets.
>
> Those are internals of eepro100, that regrettably I don't know.
> I can see the BIOS displays when ErgoPro starts up and those indicate,
> that the BIOS wants to serve the NIC using interrupt 11.

IRQ 11 is a "normal" interrupt line for a NIC,
so nothing strange there.

> > Find out which interrupt line the NIC in the ErgoPro uses
> > and which IRQ it is supposed to use.
> 
> Don' know how to find out what pxeboot really wants to use?

You just reported that IRQ 11 is used.

> > > Hope desparately, that somebody can help me.
> > 
> > Let us known how you are doing.
> > (even if the topic goes to the etherboot mailinglist)
>
> Yes I will do so. There must be people around, who have been
> successfully doing, what I intent to do and I still hope for
> additional helpful comments.

About that pxeboot.0, what is it? What should it do?
(in other words: I don't know what it exactly is,
I assumed it something to load the FreeBSD kernel)

But hey:
 Why loading pxelinux.0 to load pxeboot.0 to load FreeBSD?

Try loading pxeboot.0 to load FreeBSD  (omit pxelinux.0)


HtH
GSt


P.S.

Reporting your results, means adding value to the archives.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFDqa5POSINbgwa/7sRAs9aAJ0ShqnYdP+q8Nn3bhE3z9CMZOT2BQCghkY4
bAATR/13+zghs3GtdOmKDLI=
=uNtW
-----END PGP SIGNATURE-----