<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE>Re: [gPXE] gpxe & keeping pxe stack loaded & DOS NDIS??</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE="2">Add "startpxe" to the gPXE script before the chain. - Shao<BR>
<BR>
----- Original Message -----<BR>
From: gpxe-bounces@etherboot.org <gpxe-bounces@etherboot.org><BR>
To: gpxe@etherboot.org <gpxe@etherboot.org><BR>
Sent: Thu Mar 11 11:30:08 2010<BR>
Subject: [gPXE] gpxe & keeping pxe stack loaded & DOS NDIS??<BR>
<BR>
<BR>
I have gpxe loading through our ISC dhcp server to any PXE client that<BR>
requests an IP address. All of our clients have either the Broadcom PXE<BR>
stack or the Intel PXE stack loaded into their NIC's (all Dell Optiplex<BR>
GX280, GX620, 745, 755, 760, 780's). <BR>
<BR>
I'm using gpxe v1.0.0 with the "undionly" options and both keep stack<BR>
methods (grabbed from rom-o-matic using the "undionly" driver selection:<BR>
<BR>
gpxe-1.0.0-undionly.kpxe<BR>
gpxe-1.0.0-undionly.kkpxe<BR>
<BR>
gpxe then chainloads vesamenu.c32 and my initial menu config file<BR>
through DHCP using the following file passed to gpxe from the DHCP<BR>
server:<BR>
<BR>
#!gpxe<BR>
chain vesamenu.c32 menu.cfg<BR>
<BR>
<BR>
My menu.cfg file looks like this:<BR>
<BR>
default vesamenu.c32<BR>
PROMPT 0<BR>
ALLOWOPTIONS 0<BR>
MENU ROWS 9<BR>
<BR>
MENU TITLE PLEASE CHOSE A SYSTEM TO BOOT<BR>
<BR>
LABEL localboot<BR>
MENU LABEL Local Boot<BR>
MENU INDENT 1<BR>
<BR>
LABEL ldms-dos<BR>
MENU LABEL Managed DOS<BR>
MENU INDENT 1<BR>
KERNEL memdisk<BR>
APPEND floppy keeppxe initrd=ldms/x86pc/undi/dosundi/dosundi.1<BR>
<BR>
<BR>
When I select "Managed DOS" to boot from the boot menu, the dosundi.1<BR>
file is downloaded and DOS is started properly. The problem is when it<BR>
gets the loading the network driver for dos (it uses the universal Intel<BR>
DOS UNDI NDIS driver along with the Microsoft tcp/ip stack for DOS) the<BR>
following message is displayed:<BR>
<BR>
Error: UNDI API Not available.<BR>
Failure: Driver did not load, load NDIS environment invalid.<BR>
Error loading device driver NDIS.SYS<BR>
Error 7306: The driver failed to initialize.<BR>
NDIS.DOS was not loaded.<BR>
Error 7321: Network-card drivers failed to load.<BR>
<BR>
<BR>
If I understand everything correctly this sounds like the PXE UNDI stack<BR>
is not loaded. <BR>
<BR>
If I go back and change my gpxe config file to add pxelinux.0 chained<BR>
like this:<BR>
<BR>
#!gpxe<BR>
chain pxelinux.0 vesamenu.c32 menu.cfg<BR>
<BR>
The "Managed DOS" boot option loads and the DOS UNDI driver loads<BR>
without any problems. <BR>
<BR>
Can't I do all of this "natively" within gpxe without having to chain<BR>
pxelinux.0 to get it to work properly? Thanks for any help you can<BR>
provide! <BR>
<BR>
--greg<BR>
<BR>
<BR>
Gregory A. Fuller - CCNA<BR>
Network Manager<BR>
State University of New York at Oswego<BR>
<A HREF="http://www.oswego.edu/~gfuller">http://www.oswego.edu/~gfuller</A><BR>
<BR>
_______________________________________________<BR>
gPXE mailing list<BR>
gPXE@etherboot.org<BR>
<A HREF="http://etherboot.org/mailman/listinfo/gpxe">http://etherboot.org/mailman/listinfo/gpxe</A><BR>
</FONT>
</P>
</BODY>
</HTML>