[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ltsp-discuss
Subject:    Re: [Ltsp-discuss] Newbie - PXE-E3A TFTP too many packages
From:       "Conrad Lawes" <conrad.lawes () rogers ! com>
Date:       2001-12-29 5:06:06
[Download RAW message or body]

When using an etherboot or BOOTP boot ROM network booting is quite straightforward:
The client PC contacts the DHCP or BOOTP server to get its IP address and the name of \
the boot image file (ltsp kernel) to transfer down and execute.  The client PC uses \
TFTP to download the ltsp kernel from the boot server; hence the reason for the TFTP \
daemon.  

In PXE booting, things are little different.  The PXE client must first download the \
network bootstrap program (nbp) or PXE loader.  The PXE loader will in turn transfer \
down the ltsp kernel.  Why is this so?  This is just the nature of PXE. The PXE \
loader or nbp must not be greater than 32K in size; otherwise, you'll get the \
unintuitive "PXE-E3A TFTP too many packages"  error.

In the case of PXELINUX, the PXE loader is the called pxelinux.bin.  Pxelinux.bin \
reads the default.cfg file to determine the ltsp kernel to download.  If you find the \
PXELINUX approach too complicated then try the  PXE-Etherboot approach.




----- Original Message ----- 
From: "Jim McQuillan" <jam@McQuil.Com>
To: "Russ Ferriday" <russ@focuslearning.com>
Cc: <ltsp-discuss@lists.sourceforge.net>
Sent: Friday, December 28, 2001 10:41 PM
Subject: Re: [Ltsp-discuss] Newbie - PXE-E3A TFTP too many packages


> Russ,
> 
> For PXE, you need the un-tagged kernel.  That is in the ltsp_initrd_kit
> package.  You'll also need to build the initrd image.
> 
> I really should  build a PXE kernel package, but I don't have any
> PXE nics to test it with.
> 
> Thanks for telling me about the gdm_init_default.tmpl file, i'll have
> to have a closer look at that.
> 
> The debian.sh script with my uid should be Ok.  I fixed that about
> a week ago.
> 
> When did you download the RPM's ?
> 
> Jim McQuillan
> jam@ltsp.org
> 
> 
> Russ Ferriday wrote:
> 
> > Plenty of references to this problem on the net, but I'm still short of 
> > an answer to my problem. I'll appreciate any pointers from this list.
> > 
> > Data
> > RedHat 7.2
> > ltsp_core-3.0.0-1.i386.rpm
> > ltsp_kernel-3.0.1-0.i386.rpm
> > 
> > Client loader firmware:
> > Intel UNDI, PXE-2.0 (build 071) for Realtek RTL8139 PCI v2.0
> > 
> > Workstation console shows that DHCP request is successful, with correct 
> > client IP, mask, and DHCP IP, but I get
> > "PXE-E3A TFTP too many packages" after about 700 packets of 1456 bytes 
> > are transferred to the client. (ethereal sniff)
> > 
> > Is there such thing as a PXE kernel that I should load, instead of 
> > what's in ltsp_kernel?
> > 
> > (Apart from that there was a missing file from the ltsp-core rpm, 
> > gdm_Init_Default.tmpl, and a little snafu with one of the rpm files 
> > having Jim's UID.)
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > _____________________________________________________________________
> > Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
> > https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> > For additional LTSP help,   try #ltsp channel on irc.openprojects.net
> 
> 
> 
> _____________________________________________________________________
> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
> https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help,   try #ltsp channel on irc.openprojects.net


[Attachment #3 (text/html)]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="MSHTML 5.00.2920.0" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT size=2>When using an etherboot or BOOTP boot ROM network booting is 
quite straightforward:</FONT></DIV>
<DIV><FONT size=2>The client PC contacts the DHCP or BOOTP server to get its IP 
address and the name of the boot image file (ltsp kernel) to transfer down and 
execute.&nbsp; The client PC uses TFTP to download the ltsp kernel from the boot 
server; hence the reason for the TFTP daemon.&nbsp; </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=2>In PXE booting, things are&nbsp;little different.&nbsp; The 
PXE client must first download the network bootstrap program (nbp) or PXE 
loader.&nbsp;&nbsp;The PXE loader will in turn&nbsp;transfer down the ltsp 
kernel.&nbsp; Why is this so?&nbsp; This is just the nature of PXE.</FONT></DIV>
<DIV><FONT size=2>The PXE loader or nbp must not be greater than 32K in size; 
otherwise, you'll get the unintuitive "PXE-E3A TFTP too many packages"&nbsp; 
error.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=2>In the case of PXELINUX, the PXE loader is the called 
pxelinux.bin.&nbsp; Pxelinux.bin&nbsp;reads the default.cfg file to determine 
the ltsp kernel to download.&nbsp; If you find the PXELINUX approach too 
complicated then try the  <A 
href="http://www.ltsp.org/documentation/pxe.howto.html">PXE-Etherboot 
</A>approach.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=2>----- Original Message ----- </FONT>
<DIV><FONT size=2>From: "Jim McQuillan" &lt;</FONT><A 
href="mailto:jam@McQuil.Com"><FONT size=2>jam@McQuil.Com</FONT></A><FONT 
size=2>&gt;</FONT></DIV>
<DIV><FONT size=2>To: "Russ Ferriday" &lt;</FONT><A 
href="mailto:russ@focuslearning.com"><FONT 
size=2>russ@focuslearning.com</FONT></A><FONT size=2>&gt;</FONT></DIV>
<DIV><FONT size=2>Cc: &lt;</FONT><A 
href="mailto:ltsp-discuss@lists.sourceforge.net"><FONT 
size=2>ltsp-discuss@lists.sourceforge.net</FONT></A><FONT 
size=2>&gt;</FONT></DIV>
<DIV><FONT size=2>Sent: Friday, December 28, 2001 10:41 PM</FONT></DIV>
<DIV><FONT size=2>Subject: Re: [Ltsp-discuss] Newbie - PXE-E3A TFTP too many 
packages</FONT></DIV></DIV>
<DIV><BR></DIV><FONT size=2>&gt; Russ,<BR>&gt; <BR>&gt; For PXE, you need the 
un-tagged kernel.&nbsp; That is in the ltsp_initrd_kit<BR>&gt; package.&nbsp; 
You'll also need to build the initrd image.<BR>&gt; <BR>&gt; I really 
should&nbsp; build a PXE kernel package, but I don't have any<BR>&gt; PXE nics 
to test it with.<BR>&gt; <BR>&gt; Thanks for telling me about the 
gdm_init_default.tmpl file, i'll have<BR>&gt; to have a closer look at 
that.<BR>&gt; <BR>&gt; The debian.sh script with my uid should be Ok.&nbsp; I 
fixed that about<BR>&gt; a week ago.<BR>&gt; <BR>&gt; When did you download the 
RPM's ?<BR>&gt; <BR>&gt; Jim McQuillan<BR>&gt; </FONT><A 
href="mailto:jam@ltsp.org"><FONT size=2>jam@ltsp.org</FONT></A><BR><FONT 
size=2>&gt; <BR>&gt; <BR>&gt; Russ Ferriday wrote:<BR>&gt; <BR>&gt; &gt; Plenty 
of references to this problem on the net, but I'm still short of <BR>&gt; &gt; 
an answer to my problem. I'll appreciate any pointers from this list.<BR>&gt; 
&gt; <BR>&gt; &gt; Data<BR>&gt; &gt;&nbsp;&nbsp; RedHat 7.2<BR>&gt; 
&gt;&nbsp;&nbsp; ltsp_core-3.0.0-1.i386.rpm<BR>&gt; &gt;&nbsp;&nbsp; 
ltsp_kernel-3.0.1-0.i386.rpm<BR>&gt; &gt; <BR>&gt; &gt; Client loader 
firmware:<BR>&gt; &gt;&nbsp;&nbsp; Intel UNDI, PXE-2.0 (build 071) for Realtek 
RTL8139 PCI v2.0<BR>&gt; &gt; <BR>&gt; &gt; Workstation console shows that DHCP 
request is successful, with correct <BR>&gt; &gt; client IP, mask, and DHCP IP, 
but I get<BR>&gt; &gt; "PXE-E3A TFTP too many packages" after about 700 packets 
of 1456 bytes <BR>&gt; &gt; are transferred to the client. (ethereal 
sniff)<BR>&gt; &gt; <BR>&gt; &gt; Is there such thing as a PXE kernel that I 
should load, instead of <BR>&gt; &gt; what's in ltsp_kernel?<BR>&gt; &gt; 
<BR>&gt; &gt; (Apart from that there was a missing file from the ltsp-core rpm, 
<BR>&gt; &gt; gdm_Init_Default.tmpl, and a little snafu with one of the rpm 
files <BR>&gt; &gt; having Jim's UID.)<BR>&gt; &gt; <BR>&gt; &gt; <BR>&gt; &gt; 
<BR>&gt; &gt; <BR>&gt; &gt; <BR>&gt; &gt; <BR>&gt; &gt; <BR>&gt; &gt; <BR>&gt; 
&gt; <BR>&gt; &gt; <BR>&gt; &gt; <BR>&gt; &gt; <BR>&gt; &gt; 
_____________________________________________________________________<BR>&gt; 
&gt; Ltsp-discuss mailing list.&nbsp;&nbsp; To un-subscribe, or change prefs, 
goto:<BR>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT><A 
href="https://lists.sourceforge.net/lists/listinfo/ltsp-discuss"><FONT 
size=2>https://lists.sourceforge.net/lists/listinfo/ltsp-discuss</FONT></A><BR><FONT 
size=2>&gt; &gt; For additional LTSP help,&nbsp;&nbsp; try #ltsp channel on 
irc.openprojects.net<BR>&gt; <BR>&gt; <BR>&gt; <BR>&gt; 
_____________________________________________________________________<BR>&gt; 
Ltsp-discuss mailing list.&nbsp;&nbsp; To un-subscribe, or change prefs, 
goto:<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT><A 
href="https://lists.sourceforge.net/lists/listinfo/ltsp-discuss"><FONT 
size=2>https://lists.sourceforge.net/lists/listinfo/ltsp-discuss</FONT></A><BR><FONT 
size=2>&gt; For additional LTSP help,&nbsp;&nbsp; try #ltsp channel on 
irc.openprojects.net</FONT></BODY></HTML>

_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.openprojects.net

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic