similar to: Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32

Displaying 20 results from an estimated 11000 matches similar to: "Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32"

2015 Sep 22
3
Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
On 9/21/2015 5:44 PM, Gene Cumm wrote: > On Mon, Sep 21, 2015 at 6:23 PM, Alan Sparks via Syslinux >> With pxelinux 3.8.6 (or, < 5.x), I was able to chain boot pxelinux.0 >> from ipxe, having set appropriate values for DHCP options 210 and 209 >> for the remote file path and the config file. This doesn't work with 6.0.3. > > I thought I recall a newer commit
2015 Sep 22
7
Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
On 9/22/2015 4:33 AM, Gene Cumm wrote: > > https://sites.google.com/site/genecsyslinux/sl604p0g15-bios.tgz?attredirects=0&d=1 > https://sites.google.com/site/genecsyslinux/sl604p0g15-x64.tgz?attredirects=0&d=1 > Tried these new binaries this morning. No change, still will not attempt to load ldlinux.c32. As a context, what I'm really trying to do is get a newer
2015 Sep 28
2
Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
On Thu, Sep 24, 2015 at 07:57:47AM -0600, Alan Sparks via Syslinux wrote: > On 9/24/2015 4:59 AM, Gene Cumm wrote: > > On Thu, Sep 24, 2015 at 6:33 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > > > >> Now I have something I can reproduce. Booting my same ipxe.iso to > >> perform an initial TFTP load shows what I saw already. Attempting to > >>
2015 Sep 23
4
Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
On 9/23/2015 3:32 PM, Ady via Syslinux wrote: > >> On 9/23/2015 2:08 PM, Ady via Syslinux wrote: >> >>> Even if it still hangs with this test, does it hang exactly as before >>> (i.e. shows only one character and hangs immediately)? >> >> It happens with one entry, or two entries, or three. >> The configuration works otherwise perfectly on any
2015 Sep 22
0
Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
On Mon, Sep 21, 2015 at 8:02 PM, Alan Sparks <asparks at doublesparks.net> wrote: > On 9/21/2015 5:44 PM, Gene Cumm wrote: >> On Mon, Sep 21, 2015 at 6:23 PM, Alan Sparks via Syslinux >>> With pxelinux 3.8.6 (or, < 5.x), I was able to chain boot pxelinux.0 >>> from ipxe, having set appropriate values for DHCP options 210 and 209 >>> for the remote file
2015 Sep 21
0
Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
On Mon, Sep 21, 2015 at 6:23 PM, Alan Sparks via Syslinux <syslinux at zytor.com> wrote: > If this is asked before, please point me at the answer, can't find it... I seem to recall seeing this before. > With pxelinux 3.8.6 (or, < 5.x), I was able to chain boot pxelinux.0 > from ipxe, having set appropriate values for DHCP options 210 and 209 > for the remote file path
2015 Sep 24
1
Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
On 9/24/2015 4:33 AM, Gene Cumm wrote: > On Wed, Sep 23, 2015 at 5:43 PM, Alan Sparks via Syslinux > <syslinux at zytor.com> wrote: > Although it means another round of testing, you could also consider > lpxelinux.0 which can support HTTP URLs on its own and probably > interacts differently with iPXE. I am curious about a quantifiable > description of "an odd
2015 Sep 23
2
Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
On 9/23/2015 2:08 PM, Ady via Syslinux wrote: > Even if it still hangs with this test, does it hang exactly as before > (i.e. shows only one character and hangs immediately)? It happens with one entry, or two entries, or three. The configuration works otherwise perfectly on any other environment. If I simplify to the the following, it still hangs after outputting the one visible
2015 Sep 22
0
Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
On Tue, Sep 22, 2015 at 1:42 PM, Alan Sparks <asparks at doublesparks.net> wrote: > On 9/22/2015 4:33 AM, Gene Cumm wrote: >> >> https://sites.google.com/site/genecsyslinux/sl604p0g15-bios.tgz?attredirects=0&d=1 >> https://sites.google.com/site/genecsyslinux/sl604p0g15-x64.tgz?attredirects=0&d=1 >> > > Tried these new binaries this morning. No
2015 Sep 23
3
Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
On 9/23/2015 12:14 AM, Ady via Syslinux wrote: > About your customers' setup... > Are they using official binaries downloaded from kernel.org? Yes. Stock versions, no local modifications. > Which exact version of Syslinux are they using? I've tried versions 3.86, 4.07, 6.01, 6.03. We can only generally use 4.07 or less because of the described ipxe compatibility issues, 6.0x
2015 Sep 24
4
Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
On Thu, Sep 24, 2015 at 6:33 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > Now I have something I can reproduce. Booting my same ipxe.iso to > perform an initial TFTP load shows what I saw already. Attempting to > load a file via http results in an immediate error message with no > resulting traffic as far as I can see. OK. Found it. core/fs/pxe/pxe.h disabled all of the
2015 Sep 24
0
Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
On Wed, Sep 23, 2015 at 5:43 PM, Alan Sparks via Syslinux <syslinux at zytor.com> wrote: > On 9/23/2015 3:32 PM, Ady via Syslinux wrote: >> >>> On 9/23/2015 2:08 PM, Ady via Syslinux wrote: >>> All this works OK on the menu.c32 in 6.x. I'm just stuck, since I can't >>> upgrade because ipxe chainloading won't work in 6.x. If I could resolve
2015 Sep 27
1
Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
On Sat, Sep 26, 2015 at 1:59 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Thu, Sep 24, 2015 at 6:59 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Thu, Sep 24, 2015 at 6:33 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >>> Now I have something I can reproduce. Booting my same ipxe.iso to >>> perform an initial TFTP load shows what I
2015 Sep 23
0
Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
> As a context, what I'm really trying to do is get a newer version of > menu.c32 that doesn't hang in some of my customers' contexts - they're > creating KVM/QEMU instances with no graphics, just text console, and for > them menu.c32 is printing exactly the first character of the text menu, > then hanging. The menu.c32 in 6.0.3 doesn't seem to cause that...
2015 Sep 28
0
Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
On 9/27/2015 10:11 PM, Geert Stappers wrote: > On Thu, Sep 24, 2015 at 07:57:47AM -0600, Alan Sparks via Syslinux wrote: >> On 9/24/2015 4:59 AM, Gene Cumm wrote: >>> OK. Found it. core/fs/pxe/pxe.h disabled all of the gPXE/iPXE >>> callbacks in the core, disabling HTTP and other functionality. It >>> appears someone disabled it intentionally in commit ID
2015 Sep 23
0
Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
> On 9/23/2015 2:08 PM, Ady via Syslinux wrote: > > > Even if it still hangs with this test, does it hang exactly as before > > (i.e. shows only one character and hangs immediately)? > > It happens with one entry, or two entries, or three. > The configuration works otherwise perfectly on any other environment. > > If I simplify to the the following, it still
2015 Sep 26
0
Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
On Thu, Sep 24, 2015 at 6:59 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Thu, Sep 24, 2015 at 6:33 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > >> Now I have something I can reproduce. Booting my same ipxe.iso to >> perform an initial TFTP load shows what I saw already. Attempting to >> load a file via http results in an immediate error message with
2015 Sep 24
0
Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
On 9/24/2015 4:59 AM, Gene Cumm wrote: > On Thu, Sep 24, 2015 at 6:33 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > >> Now I have something I can reproduce. Booting my same ipxe.iso to >> perform an initial TFTP load shows what I saw already. Attempting to >> load a file via http results in an immediate error message with no >> resulting traffic as far as I
2015 Sep 23
0
Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
> On 9/23/2015 12:14 AM, Ady via Syslinux wrote: > > > About your customers' setup... > > Are they using official binaries downloaded from kernel.org? > > Yes. Stock versions, no local modifications. > > > Which exact version of Syslinux are they using? > > I've tried versions 3.86, 4.07, 6.01, 6.03. > We can only generally use 4.07 or less
2015 Sep 23
0
Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
Alan Sparks via Syslinux <syslinux at zytor.com> writes: > As a context, what I'm really trying to do is get a newer version of > menu.c32 that doesn't hang in some of my customers' contexts - they're > creating KVM/QEMU instances with no graphics, just text console, and for > them menu.c32 is printing exactly the first character of the text menu, > then