Hi,<br><br>I am running v29cz of Scyld. Are you asking what version of beoboot? It is from an iso image created from beosetup.<br><br>I am running 32 bit on a Intel Pentium M (is that x86_64 or IA32?)<br><br>Where do I change the TKM delay? Is that on the master before I create the ISO image?
<br><br>Thanks! As you can tell, I am lost.<br><br>- Gardner<br><br><div><span class="gmail_quote">On 1/30/06, <b class="gmail_sendername">Donald Becker</b> <<a href="mailto:becker@scyld.com">becker@scyld.com</a>> wrote:
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Fri, 27 Jan 2006, Gardner Pomper wrote:<br><br>> I am trying to get my test Scyld cluster up. I have Scyld v29cz running on
<br>> my head node, and I am trying to get one slave node booting from a CD. The<br>> slave finds the master, and is assigned an IP address, but it fails with the<br>> following error:<br><br>What version are you using?
<br>Are you booting from the distribution CD, or an "iso image" created from<br>Beosetup?<br>Are you running on a x86_64 or IA32?<br><br>> Boot information received for interface eth0 from RARP:<br>> Assigned IP address:
<a href="http://192.168.1.10">192.168.1.10</a> / <a href="http://255.255.255.0">255.255.255.0</a><br>> Server: <a href="http://192.168.1.50">192.168.1.50</a> boot file '/var/beowulf/boot.img'<br>> BProc master
<a href="http://192.168.1.50">192.168.1.50</a> port 2223,<br>> VMA server <a href="http://192.168.1.50">192.168.1.50</a> port 1556, protocol tcp.<br>> boot: installing module "kmonte"<br>> connect: no route to host
<br>> Boot image download failure: numerical result ouf of range<br><br>Hmmm, this appears to be a routing problem.<br><br>We have seen a similar problem once before in the quick-remaster case,<br>where the old default route prevents a new route from being added, even
<br>though the interface was shut down. (This is a kernel routing bug that<br>can be worked around by explicitly deleting the old default route.)<br><br>> I hope I got all this right, because it automatically clears the screen and
<br>> reboots after 5 seconds and I haven't found a way to stop it.<br><br>The parameter 'fatal_delay' should set that timeout, and the default is<br>normally 120 seconds. The only five second delay is in Two Kernel Monte,
<br>and that shouldn't be called. (FYI: The TKM delay may changed with the<br>'bootmode' flags. The upper 8 bits specify the delay in seconds before<br>switching kernels. This is pretty much useful only for<br>debugging and developers, and isn't likely the delay here.)
<br><br><br><br>--<br>Donald Becker <a href="mailto:becker@scyld.com">becker@scyld.com</a><br>Scyld Software Scyld Beowulf cluster systems<br>914 Bay Ridge Road, Suite 220
<a href="http://www.scyld.com">www.scyld.com</a><br>Annapolis MD 21403 410-990-9993<br><br><br></blockquote></div><br>