similar to: Bootloader chaining

I'm trying to move off of bpbatch and on to pxelinux (bpbatch doesn't boot the installation kernels for SuSE 8.1 and SLES 8--they appear to be too big). This has been a pretty easy transition, except for the fact that I'm using bpbatch to install Windows 2000 over the network as well as Linux. For Windows 2000 I use a DOS boot diskette with network drivers and run the 16-bit WINNT.EXE

What is the difference between PXELINUX and bpbatch ? AFAICT, bpbatch doe not require a TFTP server which supports the 'tsize' option. So in the absence of such a server, I may need to explore bpbatch... It seems that bpbatch can be used to remotely boot DOS. Can PXELINUX also do this? -- John

I've been working with Matt Burgess here on this problem, and have found the following: syslinux 3.08-pre10 ? broken >>> config.inc:max_cmd_len=255 syslinux 3.08-pre11 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.08 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre1 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre2 ? broken

Hi there, I have some troubles to boot a node with gpxelinux, chain.c32 and a freebsd (version 7) bootloader installed on the /dev/sda3 part of my node. For information, it works fine with pxelinux. In both cases, the version 3.73 of gpxelinux/pxelinux is used. My PXE profile : DEFAULT bootlabel label bootlabel KERNEL images_emmanuel/chain.c32 APPEND hd0 3 The message I

> 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

Hi as described on the syslinux pxe webpage: A multi-hardware boot floppy is included with Windows Server 2000 and 2003. A company called Argon Technology used to offer a free-as-in-beer updated version, but is seems to have gone fully commercial. This floppy (which can also be burned to a CD using El Torito in floppy-emulation mode), is known to work with PXELINUX 2.03 or later only I'm

After the PXE PROM code downloads and runs the pxelinux.0 image and it tries to download config information the client stops acknowledging the server OACK packets from the server. pxelinux from syslinux 3.11 from Fedora RPM, accessing Solaris 10 in.tftpd The tftp client in pxelinux.0 sends a tftp file read request with extended options tsize \00 0 \00 blksize \00 1440 \00 and then the server

I just wanted to chime in and mention that I'm running into the problem with getting a "Non-system disk..." error on a system using a USB floppy when the floppy is not attached when I try to boot the system over the network using memdisk to boot a floppy image. Its actually fairly important to be able to do this, as the architecture of the hardware that I'm working with utilizes

I wrote a new module "whichsys.c32" which detemines which command to execute, based on the Syslinux bootloader variant. In the near future it should/can be replaced by a lua script. But for people who want small binaries: whichsys.c32 is +/- eighty times smaller than lua.c32, atm. Usage: whichsys.c32 [-iso- command] [-pxe- command] [-sys- command] Examples: whichsys.c32 -iso-

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

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

Hi, I'm trying to install Fedora Core 3 on an AMD 64-based machine using PXE (via DHCP and TFTP). I've managed to get the machine to load the kernel over the network and start booting, but instead of loading the root fs from initrd.img (that I appended as a config via pxelinux.cfg), it loads the pre-existing rootfs on my harddisk. At the top of dmesg is the message: "so old

Hi, I'd just want to express my gratitude for the recent versions of pxelinux and memdisk. They allowed me not only to install Linux, but also to boot those darn rescue Floppys on my IBM ThinkPad X22, which comes without Floppy or CDDROM drive, but a built-in Ethernet card which supports PXE. I also had a look at other projects, like bpbatch, but none were so easy to use and functional as

If you have a multiboot kernel which is booted by syslinux/pxelinux/isolinux, etc., is there a way to determine who actually is the bootloader among the three? I'm wondering if the multiboot header or any part of memory has a consistent identifier somewhere. thanks, Ram

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

I tracked down the source of the "invalid kernel image" in 1.73 -- it turns out that in two different places I was accessing word-sized variables as dwords :( Consequently, SYSLINUX would reject valid kernels. PXELINUX/ISOLINUX are unaffected. Thus, SYSLINUX 1.74 is out. Expect a 1.75-pre1 quite soon. I'm working on a rewrite using 32-bit code from the very beginning, which

hello, i noticed in a past message: Arco wrote: >> I want to chain multiple servers with pxelinux initiated from a ris server. >> (Correct me if i'm wrong) >> The Ris server sends a tftp-path-prefix location where the pxelinux.cfg is searched. >> On the ris server I have entries like: >> label server2 >> kernel 192.168.1.2::pxelinux.0 >>

I've just been playing with PXELINUX 1.74, and I can't get NBP chaining to work. First problem is that the code doesn't appear to recognize .0 files. I could be completely mistaken (x86 assembler isn't my forte) but I think the problem in pxelinux.asm is here: ------------------------------------------------------------------------ .one_step: mov ecx,[di-4]

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

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