<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><DIV>We have seen the same thing at my company where the system freezes in the init scripts at ipconfig.</DIV>
<DIV> </DIV>
<DIV>What was actually happening we found was that ipconfig was waiting for a dhcp response on an ethernet interface that was not actually plugged in. The live scripts in the initrd are flawed in that they do not use ipconfig properly within do_netmount() function, as they do not pass the timeout argument, so ipconfig likely tries the first network interface and waits regaurdless of a timeout.</DIV>
<DIV> </DIV>
<DIV>Thomas<BR><BR>--- On <B>Mon, 1/26/09, Dirk Geschke <I><dirk@lug-erding.de></I></B> wrote:<BR></DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(16,16,255) 2px solid">From: Dirk Geschke <dirk@lug-erding.de><BR>Subject: FAI-3.2.16 and Broadcom-Ethernet/PXE/DHCP-problem with ipconfig<BR>To: linux-fai@uni-koeln.de<BR>Date: Monday, January 26, 2009, 11:43 AM<BR><BR><PRE>Hi all,
probably this is a known bug but I can't find an easy solution
so far...
I started to setup FAI on amd64 but the "normal" Debian version
from stable aka etch was too buggy but at least it worked with
a lot of adjusting of scripts...
Now I started with lenny and FAI-3.2.16 but the client installation
stops during boot via PXE/TFTP/DHCP where ipconfig is called. The
last line is something with IP-Config followed from two status
lines of eth0/tg3.
I think the call of ipconfig within the initrd causes the trouble.
Is there already a solution for this problem available?
Best regards
Dirk
--
+----------------------------------------------------------------------+
| Dr. Dirk Geschke / Plankensteinweg 61 / 85435 Erding |
| Telefon: 08122-559448 / Mobil: 0176-96906350 / Fax: 08122-9818106 |
| dirk@geschke-online.de / dirk@lug-erding.de / kontakt@lug-erding.de |
+----------------------------------------------------------------------+
</PRE></BLOCKQUOTE></td></tr></table><br>