Dell machines normally come the boot ROM
integrated with the BIOS. The boot ROM code was developed by 3Com/Lanworks
and its known as the Managed PC Boot Agent or (MBA). MBAs
support many network boot protocols; however, Etherboot is not supported.
However, you can remoteboot LTSP clients using the PXE protocol - the default
protocol of the MBA. You can find out more about the MBA and
PXE at http://www.argontechnology.com.
I have also posted an MBA HOW-TO doc on the ltsp website that may be of value to
you. Anyway, below is a correspondence I wrote
regarding Etherboot and PXE.
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 a
network bootstrap program (nbp) also known as the 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. Furthermore, PXE boot ROMs are
unable to execute tagged kernels.
Have a look at the PXE-LTSP How-To or the PXELINUX doc for details. These files have links on the LTSP
website.
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.
The PXE-Etherboot method is quite ingenuious. In a nutshell, the nbp code forces your PXE
boot ROM to function like a normal Etherboot boot ROM or floppy. In this approach, you can
use any of LTSP kernel as-is. Normally, PXE boot ROM can't handle a kernel that has been
tagged using mknbi - which is usually the case with ltsp pre-built kernels.
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 a
network bootstrap program (nbp) also known as the 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. Furthermore, PXE boot ROMs are
unable to execute tagged kernels.
Have a look at the PXE-LTSP How-To or the PXELINUX doc for details. These files have links on the LTSP
website.
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.
The PXE-Etherboot method is quite ingenuious. In a nutshell, the nbp code forces your PXE
boot ROM to function like a normal Etherboot boot ROM or floppy. In this approach, you can
use any of LTSP kernel as-is. Normally, PXE boot ROM can't handle a kernel that has been
tagged using mknbi - which is usually the case with ltsp pre-built kernels.
Many corporate desktops sold by Dell, Compaq, IBM and others usually come with a PXE boot ROM built-in.
Some participants might recommend that you should reflash (reprogram) these boot ROMs with Etherboot
code. However, I find this endeavour pointless, if not impossible, since the PXE-Etherboot method
mentioned earlier offers the same end result. Furthermore, retaining the PXE code offers you the
flexibility to work with many PXE-aware desktop management tools such as IBM's LCCM, Novell's
Zenworks, Symantec Ghost, Altiris Express, and even - heyhem - Windows 2000 Remote Installation Services.
With PXE you can keep your options open and enjoy the best of all worlds.
Regards,
Conrad
----- Original Message -----
From: "Dimitri Yioulos" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, August 17, 2002 2:50
PM
Subject: [Ltsp-discuss] 3Com 3C920 NIC
issue
> particular LTSP. I have created a server, and have successfully connected
> machines having Intel Pro 100 and 3COM 3C905C-TX NICs, using Etherboot
> disks. My problem comes with machines which have integrated 3COM 3C920
> cards in them. These cards are supposedly 3C905C-TX compatible, but they
> don't seem to find the LTSP server so as to get an IP address via DHCP.
> Obtaining other machines is out of the question; all of our machines are
> purchased from Dell. Adding a card that works is also out of the question;
> it adds cost.
>
> Can anyone shed light on this problem? It would be so greatly appreciated.
>
> Diggy
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone? Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _____________________________________________________________________
> 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
>
