[syslinux] SYSLINUX 3.85 released

[H. Peter Anvin]

On 02/22/2010 04:58 AM, Thomas Mieslinger wrote:
> Hi,
> 
> I did some testing

Thanks.  Of course, it would have been nice to get some testing before
the release :(  I realize that's not always possible, but it does make
it harder to address problems.

> (all tests with gpxelinux.0)
> (G6 BIOS 01/13/2010)
> 
>                      HP DL360G3/G5/G6    Dell PE1950
> 3.85 localboot 0     fail        OK
> 3.85 localboot 0x80  fail        fail
> 3.85 chain.c32 hd0 0 fail (1)        fail (1)
> 
> (1) message: "Chainboot failed!"
> 
>         HP DL360 G3/G5    G6    Dell PE1950
> 3.84 localboot 0    fail    OK    OK
> 3.84 localboot 0x80    fail(1)    fail(1)    OK(2)
> 3.84 chain.c32 hd0 0    OK    fail    OK
> 
> (1) Message: Could not execute pxelinux.0: Error 0x00000080
> (2) Same Error as in (1) but BIOS continues.
> 

"localboot 0x80" for (g)pxelinux is nonsense, so it's not at all
surprising that that fails.

What happens with plain pxelinux.0?

> How can I get more information about that chain.c32 Problems on DL360G6
> in 3.84 or chain.c32 3.85 Problems at all?

The first thing to do is to use the "sysdump" tool included in Syslinux
3.85 to generate a machine dump and send it to me.  It can either send
it to a TFTP server or use ymodem over a serial port to generate a lot
of system information.

One thing you can do is to add the following line to com32/lib/MCONFIG
right before the line marked .SUFFIXES: and recompile:

CFLAGS += -DDEBUG=2

This will cause chain.c32 to output *lots* of information, but in
particular it is likely to explain the "Chainboot failed" error --
assuming it doesn't scroll off the screen (capturing it over a serial
console might be necessary.)

	-hpa

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