<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
<tt>Peter Scheie wrote:</tt>
<blockquote type="cite" cite="mid:4B737C33.40604@scheie.homedns.org">
<title>[gPXE] Dell T300 w/Broadcom chip: gpxe hangs during dhcp</title>
<!-- Converted from text/plain format -->
<p><tt><font size="2">...where there would normally be a series of
dots<br>
marking time while it gets an address from our dhcp server, there
appears just a<br>
single dot and then it just hangs.<br>
</font></tt></p>
</blockquote>
<tt><br>
This happens to me on out-of-memory conditions, sometimes. I find that
often gPXE will still respond to Control-C at this point. The fewer
opened interfaces at once, the better. 'ifstat' and 'ifclose' can help
to ensure only a single interface is in use.<br>
<br>
</tt>
<blockquote type="cite" cite="mid:4B737C33.40604@scheie.homedns.org">
<p><tt><font size="2">...but as it's<br>
downloading the kernel, it stalls.</font></tt></p>
</blockquote>
<tt><br>
Strange. Could it be a sign of an out-of-memory condition, also? I
would expect gPXE to handle these nicely, though.<br>
<br>
</tt>
<blockquote type="cite" cite="mid:4B737C33.40604@scheie.homedns.org">
<p><tt><font size="2">So, any ideas as to<br>
- why gpxe hangs during dhcp for eth0?<br>
</font></tt></p>
</blockquote>
<tt><br>
Well, it could be a bug with the InitRD+CmdLine patched version of gPXE
you are running... You might try a regular gPXE and see if you get the
same results.<br>
<br>
</tt>
<blockquote type="cite" cite="mid:4B737C33.40604@scheie.homedns.org">
<p><tt><font size="2">- why it would stop communicating with the
gateway after ~90 seconds & 23MB?<br>
</font></tt></p>
</blockquote>
<tt><br>
Possibly due to a bug.<br>
<br>
</tt>
<blockquote type="cite" cite="mid:4B737C33.40604@scheie.homedns.org">
<p><tt><font size="2">- what kind of behavior one would expect if a
network card/chip is not supported<br>
by gpxe?<br>
</font></tt></p>
</blockquote>
<tt><br>
Not supported could mean not reported by 'ifstat'. If it's in
'ifstat', it's supposedly supported.<br>
<br>
</tt>
<blockquote type="cite" cite="mid:4B737C33.40604@scheie.homedns.org">
<p><tt><font size="2">- how to figure out why machines booting gpxe
connected directly to our<br>
corporate network can't get addresses from our dhcp server,</font></tt></p>
</blockquote>
<tt><br>
'tcpdump' or WireShark might be able to help with this. You could
e-mail a packet capture. You could also enable DHCP debugging in gPXE
like this:<br>
<br>
# cd gpxe/src<br>
# make DEBUG=dhcp bin/gpxe.lkrn<br>
<br>
</tt>
<blockquote type="cite" cite="mid:4B737C33.40604@scheie.homedns.org">
<p><tt><font size="2"> and if the address<br>
is provided by hand, can't download gpxe scripts from an external
webserver?<br>
</font></tt></p>
</blockquote>
<tt><br>
Try to be sure that your DNS and router settings are set correctly.
You can check the output of 'route' after making your manual settings.<br>
<br>
</tt>
<blockquote type="cite" cite="mid:4B737C33.40604@scheie.homedns.org">
<p><tt><font size="2"><br>
...</font></tt></p>
</blockquote>
<tt><br>
Disclaimer: All claims and opinions are solely those of myself and do
not and should not be perceived as representing the Etherboot nor the
gPXE projects in any way. Thank you for your understanding.<br>
<br>
- Shao Miller<br>
</tt>
</body>
</html>