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.
Have a look at the PXE-LTSP How-To or the PXELINUX doc for details. 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. [EMAIL PROTECTED] wrote: >HI, I have this problem, > >I have 3com 3c905c-TX NIC , I couldn't find the module for that NIC in the >kernel. >So I tried all other(including 3c9xx) 3com modules, but i keep getting this >eror message on the client-workstation : > >PXE-E34 : TFTP too many package > >Can anybody help me? >Thankyou > >_____________________________________________________________________ >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
