<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
<tt>Randy McAnally wrote:</tt>
<blockquote type="cite" cite="mid:20100303184056.M11784@fast-serv.com">
<title>Re: [gPXE] localboot 0 hang on some machines</title>
<!-- Converted from text/plain format -->
<p><tt><font size="2">Thank you so much, this is the kind of news I
needed!<br>
<br>
---------- Original Message -----------<br>
From: "Arends, R.R." <a href="mailto:r.r.arends@hro.nl" class="moz-txt-link-rfc2396E"><r.r.arends@hro.nl></a><br>
To: "Randy McAnally" <a href="mailto:rsm@fast-serv.com" class="moz-txt-link-rfc2396E"><rsm@fast-serv.com></a><br>
Cc: <a href="mailto:gpxe@etherboot.org" class="moz-txt-link-rfc2396E"><gpxe@etherboot.org></a><br>
Sent: Wed, 03 Mar 2010 10:10:56 +0100<br>
Subject: Re: [gPXE] localboot 0 hang on some machines<br>
<br>
> I had troubles with localboot 0 from a gpxelinux.0 menu on some<br>
> machines aswel. Chain.c32 does work for me to boot from harddisk
tho...</font></tt></p>
</blockquote>
<tt><br>
The news does not include version information, though.<br>
<br>
gpxelinux.0 is:<br>
gPXE's undionly.kkpxe build with:<br>
embedded script to boot embedded PXELINUX<br>
embedded PXELINUX (pxelinux.0)<br>
<br>
The Syslinux Project delivers gpxelinux.0 and thus includes a stable
gPXE state that H. Peter Anvin deems acceptable for this use case.
Historically, he's noted some issues and features required for best
results. Some of these were incorporated into gPXE 1.0.0 and Syslinux
3.85.<br>
<br>
Unfortunately, some news of LOCALBOOT versus CHAIN.C32 results came a
little late for the Syslinux 3.85 release, so it would be good to
figure out the solution(s), if possible, for the computer types
involved, I think. To be absolutely sure that there is actually a
challenge to be overcome, the version(s) involved could benefit.<br>
<br>
I am not sure that failing on, let's say, gpxelinux.0 from Syslinux
3.83, then failing on the gpxelinux.0 from Syslinux 4.00-preX can give
confidence that Syslinux 3.85 is broken. My impression is that 3.85
and 4.XX are separate development branches, though they can and do
share some code. This impression could be mistaken.<br>
<br>
- Shao Miller<br>
</tt>
</body>
</html>