I am using memdisk to remotely flash the BIOS and other firmware. It works well for most flash programs. After the flash I need to initialize the NIC to send a signal to my management server that the flash is complete. I am curious as to how others have solved this problem. Thanks.
Egan Ford wrote:> I am using memdisk to remotely flash the BIOS and other firmware. It works well > for most flash programs. After the flash I need to initialize the NIC to send a > signal to my management server that the flash is complete. > > I am curious as to how others have solved this problem. >You probably want to reboot the machine at that point; could the TFTP load (PXELINUX) handle that? -hpa
H. Peter Anvin wrote:> Egan Ford wrote: > >> I am using memdisk to remotely flash the BIOS and other firmware. It >> works well >> for most flash programs. After the flash I need to initialize the >> NIC to send a >> signal to my management server that the flash is complete. >> >> I am curious as to how others have solved this problem. >> > > You probably want to reboot the machine at that point; could the TFTP > load (PXELINUX) handle that?I too am very curious about how to do something like this. I would like to boot dos boot images to configure hardware ( bios, raid, etc ) before the OS gets loaded. However, updating to the next stage of the process is the hard part. I can hack it from the tftp side, but it would be nicer to handle it in the client so you could add logic to only do the update if the bios flash, etc was successful and reboot. Is there a reasonable tcpip stack available for DOS ( and some basic utilities like a dhcp client, reboot, wget ) that could be used to manage this? Michael
Michael Blandford wrote:> > Is there a reasonable tcpip stack available for DOS ( and some basic > utilities like a dhcp client, reboot, wget ) that could be used to > manage this? >Look at http://www.wattcp.com/ -hpa
Why not just use the keeppxe flag? On Tue, 28 Oct 2003, H. Peter Anvin wrote:> Michael Blandford wrote: > > > > Is there a reasonable tcpip stack available for DOS ( and some basic > > utilities like a dhcp client, reboot, wget ) that could be used to > > manage this? > > > > Look at http://www.wattcp.com/ > > -hpa > > _______________________________________________ > SYSLINUX mailing list > Submissions to SYSLINUX at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux > Please do not send private replies to mailing list traffic. > >--
"Egan Ford" <egan at sense.net> writes:> Is there a UNDI packet driver that I can use with wattcp and > keeppxe?Not that I know of, but there are two "universal" DOS NDIS drivers which work with keeppxe. One is 3com's undis3c.dos available at: http://support.3com.com/infodeli/tools/nic/mba.htm The other is Intel's ndis.dos (or undis.dos, depending) and is a little harder to find... It ships with Intel's PXE PDK, which you can find by doing a search on Intel's site. So, you can use the MSCLIENT TCP/IP stack with one of these drivers. This is what I did for my boot disk (see <http://unattended.sourceforge.net/>), and it works great with PXELINUX (or ISOLINUX) and memdisk. Or you can use a generic "NDIS to packet driver" shim, which should let you use these NDIS drivers with wattcp. I believe such a shim exists, but I do not remember where to get it. - Pat
Peter.Leenders at computacenter.com
2003-Oct-29 07:47 UTC
[syslinux] Using memdisk to remotely flash BIOS
By the way, does anybody know a UNDI DOS/ODI driver for use with netware bootdisks. This will solve a problem with the broadcom B57 driver and a PXE-booted netware client and make live easy with all the other nics. - Peter "Egan Ford" <egan at sense.net> writes:> Is there a UNDI packet driver that I can use with wattcp and > keeppxe?Not that I know of, but there are two "universal" DOS NDIS drivers which work with keeppxe. One is 3com's undis3c.dos available at: http://support.3com.com/infodeli/tools/nic/mba.htm The other is Intel's ndis.dos (or undis.dos, depending) and is a little harder to find... It ships with Intel's PXE PDK, which you can find by doing a search on Intel's site. So, you can use the MSCLIENT TCP/IP stack with one of these drivers. This is what I did for my boot disk (see <http://unattended.sourceforge.net/>), and it works great with PXELINUX (or ISOLINUX) and memdisk. Or you can use a generic "NDIS to packet driver" shim, which should let you use these NDIS drivers with wattcp. I believe such a shim exists, but I do not remember where to get it. - Pat _______________________________________________ SYSLINUX mailing list Submissions to SYSLINUX at zytor.com Unsubscribe or set options at: http://www.zytor.com/mailman/listinfo/syslinux Please do not send private replies to mailing list traffic.
Peter.Leenders at computacenter.com wrote:> By the way, > > does anybody know a UNDI DOS/ODI driver for use with netware bootdisks. > This will solve a problem with the broadcom B57 driver and a PXE-booted > netware client and make live easy with all the other nics. >UNDI is basically NDIS2. Thus, there is a UNDI NDIS driver, and you can presumably use NDIS->pkt or NDIS->ODI shim drivers. -hpa
So, if UNDI is NDIS2, all I need is an NDIS packet driver if I want to use wattcp?> -----Original Message----- > From: syslinux-bounces at zytor.com > [mailto:syslinux-bounces at zytor.com] On Behalf Of H. Peter Anvin > Sent: Wednesday, October 29, 2003 1:03 AM > To: Peter.Leenders at computacenter.com > Cc: SYSLINUX at zytor.com > Subject: Re: [syslinux] Using memdisk to remotely flash BIOS > > > Peter.Leenders at computacenter.com wrote: > > By the way, > > > > does anybody know a UNDI DOS/ODI driver for use with > netware bootdisks. > > This will solve a problem with the broadcom B57 driver and > a PXE-booted > > netware client and make live easy with all the other nics. > > > > UNDI is basically NDIS2. Thus, there is a UNDI NDIS driver, > and you can > presumably use NDIS->pkt or NDIS->ODI shim drivers. > > -hpa > > _______________________________________________ > SYSLINUX mailing list > Submissions to SYSLINUX at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux > Please do not send private replies to mailing list traffic. >
"Egan Ford" <egan at sense.net> writes:> So, if UNDI is NDIS2, all I need is an NDIS packet driver if I want > to use wattcp?I believe hpa meant that the UNDI programmatic interface is very similar to the NDIS2 programmatic interface. The phrase "NDIS packet driver" is a contradiction. An NDIS driver is for use with the MSCLIENT network stack. A packet driver is for use with wattcp. There are at least two NDIS drivers which are written to invoke UNDI, thus making them "universal" drivers. There are no such packet drivers. There are "shims" which implement a packet driver using an NDIS driver and vice-versa. By combining such a shim with a universal NDIS driver and an functioning UNDI stack, you end up with something which should be useable by wattcp. In theory. I could be wrong about any of this, by the way. I have never looked at wattcp very carefully. - Pat