similar to: Manually copy over ldlinux.sys

Due to delayed allocation feature on XFS filesystems, a write is not guaranteed to flushed out to the underlying file system after crash or something else - so we need to make sure that ldlinux.sys is installed correctly in the mounted filesystem. Signed-off-by: Paulo Alcantara <pcacjr at zytor.com> --- extlinux/main.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/extlinux/main.c

Hello fellow syslinux/extlinux users! Please forgive the long post, but I believe my problem warrants the background info to understand the issue. I've developed a specialized spin of Fedora that runs off CompactFlash. The spin is actually produced by the livecd-tools package and is then transferred to the CF card -- which has been formatted with ext3 -- using livecd-tools'

I need to debug some issue in second stage of syslinux boot, i.e. ldlinux.sys. I have put a few debug instructions in core/diskstart.inc and recompiled everything. The newly obtained ldlinux.sys confirms to the size restriction for the boot sector. Now how do o replace the current /boot/ldlinux.sys file with mine. I tried removing the immutable flag and then doing a copy. Nothing changes. It

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

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

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

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

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

I have LVM volumes: /dev/disk1/main /dev/disk1/mainboot /dev/disk1/other /dev/disk1/otherboot I can boot main by using syslinux with syslinux.cfg including: LABEL main MENU LABEL Main LINUX ../vmlinuz-linux APPEND root=UUID={UUID} {kernel parameters} INITRD ../initramfs-linux.img (1) I see a lot of places saying syslinux can't boot a kernel on another partition, and that you have

Hi, I merged ldlinux.asm and extlinux.asm on the fsc branch, observing that there were very little difference between them left. So far, so good. I found, however, a test which fails on the fsc branch (with or without the merge.) I have tracked it down to vfat_mangle_name() overwriting a bunch of random .bss16 memory, eventually including the CallbackSP variable.

Hi, The examples for making a bootable usb key using extlinux just transfer a live cd to usb. To me, this misses the advantage of usb keys (other than size), that they are writable. I would like to have a full linux install on a usb key and be able to boot it using extlinux. This way I can install new packages and make other changes without jumping through squashfs hoops. Is there reason why

On 07/26/2013 08:10 AM, Matt Fleming wrote: > On Wed, 24 Jul, at 08:05:16AM, Raphael S.Carvalho wrote: >> Check if ldlinux.sys is larger than 64k at build time. >> >> Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> >> --- >> core/Makefile | 5 +++-- >> core/ldlinux_limit.pl | 31 +++++++++++++++++++++++++++++++ >> 2

On 07/26/2013 01:36 PM, Raphael S Carvalho wrote: > > Bootsector is installed into the 0-512 range, whereas 2 copies of ADV > into (65536 - 2 * ADV_SIZE). > Then basically ldlinux.sys must fit between the bootsector and two > copies of ADV whose size may vary. > > The range 0-64k is laid out something like this, right?! > [0](bootsector)[512](ldlinux.sys)[65536 - 2 *

Check if ldlinux.sys is larger than 64k at build time. Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> --- core/Makefile | 5 +++-- core/ldlinux_limit.pl | 31 +++++++++++++++++++++++++++++++ 2 files changed, 34 insertions(+), 2 deletions(-) create mode 100644 core/ldlinux_limit.pl diff --git a/core/Makefile b/core/Makefile index f795a5c..00de331 100644 ---

Hello, I noticed the following behavior of extlinux 4.05: I created an ext3 filesystem on the first (primary and active) partition of a usb stick. I mounted it at /mnt/. Then I copied to /mnt/ldlinux.sys the ldlinux.sys found in the syslinux 4.05 archive and I created a basic /mnt/extlinux.cfg. Then I ran "extlinux -i /mnt/" and rebooted on the usb stick. I got "ERROR: No

A proposal for changing the LDLINUX.SYS layout and flow: The current situation ("old style"): ldlinux.bin's physical layout: - VBR - 512 bytes of padding (never lands in memory) - ldlinux.sys, which is: - Sect1 code (494 bytes, leaving enough room for at least one extent, as planned) - Extent pointer patch space (1920 bytes) - The rest of the code

My question is the following: I need to "syslinux" a harddisk(partition-type is FAT16, size is about 100mb). I created a Dos-Bootdisk with WindowsXP and removed everything except command.com, io.sys and msdos.sys. Then I copied syslinux.com (and even ldlinux.sys) to the disk but nothing seems to help, I always get the "SYSLINUX: Cannot read ldlinux.sys"-error. Should I use

Merge btrfs_read_adv and xfs_read_adv into a single generic function ext_read_adv and split ext_write_adv_offset out of ext_write_adv. Use those new functions in rewrite_boot_image and btrfs_install_file where it is actually hardcoded. Signed-off-by: Nicolas Cornu <nicolac76 at yahoo.fr> --- extlinux/main.c | 113 +++++++++++++++++++++++++++----------------------------- 1 file changed, 55

From: Raphael S. Carvalho <raphael.scarv at gmail.com> v2: Extract ADV_SIZE automatically from libinstaller/setadv.h. Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds the limit. ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary. Thus, the size of ldlinux.sys can be at most: 65536 - 2 * ADV_SIZE - 512 (limit). Certain file systems

Hi, i think i found the reason for the boot failure in the definition of Extended Boot Records. https://en.wikipedia.org/wiki/Extended_boot_record#Values "Starting sector = relative offset between this EBR sector and the first sector of the logical partition. Note: This is often the same value for each EBR on the same hard disk; usually 63 for Windows XP or older." So if