[gPXE] Booting from a local disk fails..

Pasi Kärkkäinen pasik at iki.fi
Mon Jul 11 15:18:39 EDT 2011


On Wed, May 18, 2011 at 05:59:10PM -0400, Gene Cumm wrote:
> On Wed, May 18, 2011 at 15:28, Pasi Kärkkäinen <pasik at iki.fi> wrote:
> > On Wed, May 18, 2011 at 10:09:18PM +0300, Pasi Kärkkäinen wrote:
> >> Hello,
> >>
> >> I'm using the following "default" cfgfile for gpxelinux.0:
> >>
> >>       default menu.c32
> >>       prompt 1
> >>       menu title Default PXE boot menu
> >>       timeout 100
> >>
> >>       label Boot from local disk
> >>       localboot 0x80
> >>
> >> I get the PXE menu, and I choose "Boot from local disk".
> >> After that I see the following on the server console:
> >>
> >>       Booting from local disk...
> >>       PXE-M0F: Exiting Intel Boot Agent.
> >>
> >> .. and nothing happens. Any ideas what could cause that?
> >> I'm currently using gpxelinux v1.0.0.
> >>
> >
> > .. from syslinux v4.04.
> >
> > And I just figured out "localboot -1" seems to work..
> 
> 1) It's really a Syslinux question.
> 
> 2) In the official archive, doc/syslinux.txt explains the option.
> 0x80 is wrong for PXELINUX; use -1 or 0.
> 
> 3) It's a common issue documented in the Syslinux Wiki.
> 
> 4) Could you collect either the output of dmidecode or sysdump.c32 and
> email it to hpa at zytor.com ?
> 
> -- 
> -Gene

Hello again,

Ok, so I finally had some more time to play with this stuff.

Using gpxelinux.0 from syslinux 4.04 and "localboot 0" hangs my server,
it says on the console:

Booting from local disk...
PXE-M0F: Exiting Intel Boot Agent.

<hangs here, no further output>

Using "localboot -1" instead works OK.

Here's the output from dmidecode from RHEL 5.6 running on that problematic server:
- http://pasik.reaktio.net/gpxelinux/dell-c6100/dmidecode.txt
- http://pasik.reaktio.net/gpxelinux/dell-c6100/lspci.txt
- http://pasik.reaktio.net/gpxelinux/dell-c6100/lspci-vvv.txt

Hardware info:
	- Dell PowerEdge C6100 server, (latest) BIOS version 1.56.
	- I'm PXE booting from Intel 82576 GE NIC, firmware version 1.3.64.


Anything else needed to troubleshoot the problem?

Thanks,

-- Pasi



More information about the gPXE mailing list