[syslinux] trying to chainload the normal ubuntu pxe installer

[Warren Turkal]

On Tue, Oct 26, 2010 at 13:27, Gene Cumm <gene.cumm at gmail.com> wrote:

> On Tue, Oct 26, 2010 at 15:29, Warren Turkal <wt at 8x8.com> wrote:
> > Hi syslinux experts,
>
> > In my menu.cfg, I tried the following to to chainload the ubuntu
> installer:
> > UI pxe_bin/menu.c32
> > PROMPT 0
> > MENU TITLE PXE Boot Menu
> >
> > LABEL ubuntu_10_10_amd64
> > MENU LABEL Ubuntu 10.10 (Meerkat) AMD64
> > KERNEL pxe_bin/pxechain.com
> > APPEND <tftp_server_ip>::linux/ubuntu/amd64/meerkat/pxelinux.0
>
> I believe there are some issues with pxechain.com at the moment (4.xx).
>

Does this problem exist in 4.0.1? Does pxechain just not work? Is there a
workaround?


> > However, it locks the machine up when I try the chainload. Is it actually
> > possible to chainload pxelinux.0 like this?
> >
> > I am using syslinux 4.0.1 file from Ubuntu 10.10 for my main pxelinux.0,
> and
> > I am using the file unchanged in the Ubuntu 10.10 netboot image. I would
> > think they'd be the same version, but I wanted to point it out in case it
> > presents a known problem.
> >
> > Also, I cannot seem to find a way to change the pathprefix or the
> > configfile. I suspect that may cause problems if I get past the lockup.
> Are
> > there ways to override those values for the chainloaded pxelinux.0?
>
> COM32 config.c32
> APPEND configfile directorypath
>

Am I able to chainload a new pxelinux.0 after I do that?


> By default, PXELINUX appends what you place as a directory path.
>

I actually did try putting the files in the regular pxelinux.cfg/default
location. That didn't seem to magically fix the issue. I encountered the
same symptoms.


> > BTW, I am willing to consider gPXE solutions. I just didn't want to
> > complicate the config for my question.
> >
> > I know that I can get it working by adding entries specifically in my
> menu,
> > but I am trying to boot an unchanged netboot image to make it easy to
> pull
> > in new distribution versions when they are released.
>
> You'll definitely want pxechain.com to help.
>

Can I work around the problem you mentioned above? Is building 4.0.3 a
viable solution?

Thanks,
wt