Syslinux - Feb 2009 - Problems with PXELINUX falling through to localboot on a HP Proliant DL385

I'm having problems with PXELINUX passing through to a "localboot"
on a
HP Proliant DL385.   I'm working with 3.73.

 

If I configure PXELINUX to directly "localboot", everything works.  
If
I configure PXELINUX to use menu.c32 or anything like that, a subsequent
localboot fails.   I see the expected "PXE ROM exiting" message but
the
next device doesn't kick in.

 

GPXE seems to have the same problem.

 

I tested the latest HP firmware, with no luck.

 

This appears to have been hit before - there was a patch posted about a
year ago that seems to work for me (you can see it at
http://www.gossamer-threads.com/lists/syslinux/users/9475?do=post_view_t
hreaded#9475 ).

 

Is there a preferred workaround, or is the referenced patch the best way
to go?   Does it have a chance of making the cut for 3.74?

 

Thanks in advance

 

-          Daniel Padwa, daniel.padwa at gs.com

Padwa, Daniel wrote:
> I'm having problems with PXELINUX passing through to a
"localboot" on a
> HP Proliant DL385.   I'm working with 3.73.
> 
> Is there a preferred workaround, or is the referenced patch the best way
> to go?   Does it have a chance of making the cut for 3.74?
> 
The problem is that that patch isn't "constructive" - all it tells
me is
that the Proliant ROM touches memory it shouldn't, and shuffling things
around at random seems to make it work.

It still means random memory is corrupted, but I don't know what memory
it is.  As such I can't really fix it.

Since your problem is with localbooting, I would suggest using chain.c32
as a workaround:

label localboot
	com32 chain.c32
	append hd0

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.