On Tue, Nov 8, 2011 at 15:16, Octavio Schroeder <oschroeder at peer1.com>
wrote:> I have been using PXELINUX for a while and appreciate all you guys are
doing!
>
> I have a couple of questions re PXELINUX:
>
> 1. I am experiencing problems with the LOCALBOOT statement on an IBM x3650.
IBM mentions the following:
> http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5084755
>
> I am using PXELINUX 4.04. Is this problem still attributed to some bug in
PXELINUX? Right now I am using the work-around of using chain.c32 with the
append hd0 parameter. But this solution skips the BIOS boot sequence.
The problem is determining who is actually at fault, PXELINUX or BIOS
vendors. Is there an incompatibility? Yes. Who is at fault? I'm
not sure. Are there other NBPs that can perform similar callbacks and
have issues? I'm uncertain.
> 2. Is there a plan to make an EFI version of PXELINUX?
>
> Regards,
>
> Octavio
On Nov 8, 2011 4:28 PM, <paul.szabo at sydney.edu.au>
wrote:>
> Dear Octavio,
>
> I am not a syslinux developer or even a guru, however I encountered a
> problem similar to yours on Dell Optiplex 990 machines.
Iirc, I had personally documented at least 3 more Dell business
systems with the same issue in the wiki (prior to recent events),
Latitude E6400, Latitude E6410 and I think the OptiPlex 980.
> My workaround was:
> Workaround seems to be as per
>
http://sourceforge.net/projects/freeghost/forums/forum/730844/topic/4560984
> using:
> kernel chain.c32
> append hd0
> instead of LOCALBOOT 0 in the config file.
> Of course I needed to have chain.c32 accessible via TFTP, copied to the
> same directory where pxelinux.0 was.
> This was sent to this list already:
> http://www.syslinux.org/archives/2011-October/016982.html
>
> Cheers, Paul
>
> Paul Szabo psz at maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/
> School of Mathematics and Statistics University of Sydney Australia
--
-Gene