similar to: Issue with ldlinux.c32 when symlinked on Windows

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

> As shown above, the file ldlinux.c32 can not be downloaded because it is > a symlink, if I do remove the symlink and copy the file in the tftp root > directory it works. Are you creating a symlink on NTFS? One possible reason, perhaps, IIRC... PXELINUX does not understand symlinks on NTFS volumes. Having said that, I might be misremembering and/or confused about this.

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

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

Sebastian, On 01/15/2015 12:49 AM, Sebastian Herbszt wrote: > which version of pxelinux were you trying? Looks like < 5.x. the one from Fedora 20, syslinux-4.05. It turns out that pxelinux.0 from Fedora 21, syslinux-6.03, reports "Failed to load ldlinux.c32" when ldlinux.c32 can't be read, and "Loading <FILE>... failed: No such file or directory" when the

Hello there I built development version of syslinux from git 6.04-pre3-3-(sometag) and I am trying to boot a slackware-current system with it. I do not use a separated partition for `/boot`. It's just `/dev/sda1` here for `/` and `/boot` is just a folder. I simply use `mbr.bin` against a DOS partition table and the first partition having the bootable flag. With this layout, the only

If this is asked before, please point me at the answer, can't find it... 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. With 6.0.3, this throws the "failed to load ldconfig.c32" error now. The files are in

Hello, today I upgraded from Syslinux 4.06 to to Syslinux 5.00. But now the system won't boot anymore and I get the message Failed to load ldlinux.c32 Boot failed: please change disks and press a key to continue What I have done: 1) Installed Syslinux 5.00 2) Reinstalled "mbr.bin" to /dev/sda and /dev/sdb using dd bs=440 count=1 conv=notrunc

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

Hello Geert Thanks for replying.. But i think i can?t use it, as i don?t reach the point where the debug module will be available.. it just pulls the lpxelinux.0 and tries to get the next download-- the ldlinux.c32 and it fails...and freezes. And the next step would be other modules i think.. if i?m wrong.. excuse me 8-).. yesterday i managed to get ipxelinux working from ipxe.org.. so the nic

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

Am 04.09.2019 um 22:18 schrieb Ady Ady via Syslinux: >> I am trying to setup a PXE server for two Debian releases (stretch and >> buster) using their respective network boot images (netboot.tar.gz), >> which I extracted into subdirectories of the TFTP server's root directory: >> >> ??? ??? debian >> ??? ??? ??? buster >> ??? ??? ??? ???

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 > >>

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

> 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

Hello list, We have a scenario where our TFTP server is not the same IP as our DHCP server. While testing with 6.03, our setup works just fine. However with the master branch, for some reason pxelinux.0 is fetched from the TFTP servers IP, but then it tries to load ldlinux.c32 from the DHCP servers IP. I've tracked down this problem to the following commit:

Hi there, first, thanks a lot for syslinux! I'm aware that one can't mix syslinux 4's MBR + ldlinux.sys with syslinux 6's COM32R modules. Fair enough. Now, I need to know how strong this "versions *must* match" requirement is when dealing with different versions of syslinux 6.x. E.g. * MBR and ldlinux.sys installed by syslinux 6.03-pre1 * all *.c32 modules

Thank you for your answer. I need to correct some information from my previous post: booting from `/` did not work either. I just assumed it did based on previous experience. But with that successful build on development branch, it did not either. > I would suggest trying first the official binaries that are already > included in the official distribution archive (6.03-pre1). Let me

Hello, I am trying to setup a PXE server for two Debian releases (stretch and buster) using their respective network boot images (netboot.tar.gz), which I extracted into subdirectories of the TFTP server's root directory: ??? ??? debian ??? ??? ??? buster ??? ??? ??? ??? debian-installer ??? ??? ??? ??? ldlinux.c32 -> debian-installer/i386/boot-screens/ldlinux.c32 ??? ??? ??? ???

I am new to syslinux/extlinux. Can I boot from a linux btrfs subvolume? I am getting "Failed to load ldlinux.c32" when I attempt to boot from a btrfs subvolume. Setup: 1) I have a USB disk with one partition. The partition is marked "active". 2) I make a btrfs filesystem with "mkfs.btrfs /dev/sdd1". I mount the partiton and execute "btrfs su create