similar to: syslinux and btrfs-formatted dos/MBR partition

Hello Gene, thanks for your reply. Yes BIOS mode. The config wants a menu, which loads fine under ext4 and not under btrfs. Under btrfs I have also tried to remove the syslinux.cfg file altogether (which should trigger the boot: prompt if I am not mistaken) and the result is the same: only the copyright line appears and no prompt. The three letter sequence is EDD. The disk is 160GB, here is the

On Tue, Jan 21, 2014 at 2:53 AM, David de Marneffe <daviddemarneffe at gmail.com> wrote: > Hello syslinux list, > > I have installed Arch over a btrfs-formatted dos/MBR primary > partition* (no btrfs subvolumes, just installing everything including > /boot in the root of the btrfs). > > I have been unsuccessful for several days trying to get it to boot > with syslinux

On Tue, Jan 21, 2014 at 7:42 AM, David de Marneffe <daviddemarneffe at gmail.com> wrote: > Hello Gene, thanks for your reply. > > Yes BIOS mode. The config wants a menu, which loads fine under ext4 > and not under btrfs. Under btrfs I have also tried to remove the > syslinux.cfg file altogether (which should trigger the boot: prompt if > I am not mistaken) and the result is

For the MBR: I usually don't touch the Microsoft MBR and chainload Linux from the Microsoft bootloader. However while trying to get my btrfs setup to work, I backed up the Microsoft MBR (dd if=/dev/sda bs=440 count=1 of=MBRbackup.bin) and I installed the syslinux MBR. I tried several ways: - with the script provided by Arch: syslinux-install_update -i -a -m - manual method with mbr.bin (first

I have some concerns about the Syslinux boot process, which I'm now investigating in connection with my work on booting Live-CD images from USB flashdrives. Some of these are related to what seems to be inadequate documentation, but I think that there are also aspects of Syslinux operation which could be fairly easily improved. quoting from the official documentation: Since version 5.00,

On Fri, Nov 13, 2015 at 06:14:36AM +0100, Geert Stappers via Syslinux wrote: > On Fri, Nov 13, 2015 at 05:05:26AM +0200, Ady via Syslinux wrote: > > diff U3 syslinux-6.03/extlinux/main.c syslinux-6.03_typo/extlinux/main.c > > --- syslinux-6.03/extlinux/main.c Mon Oct 06 16:27:44 2014 > > +++ syslinux-6.03_typo/extlinux/main.c Fri Nov 13 02:29:56 2015 > > patch seen >

On Tue, May 20, 2014 1:52 pm, Anatol Pomozov wrote: > Ok, we've figured out potential cause of the problem. The next > question how to minimize the size of ldlinux.sys? > > BTW looking at official (?) binary > https://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/6.03/syslinux-6.03-pre11.tar.xz > I see that their size is also more than 64K Actually, there is *no*

> On May 25, 2014 3:39 AM, "Geert Stappers" <stappers at stappers.nl> wrote: > > > > > > While going throug old posts found: > > > > Op 2013-08-31 om 17:01 schreef Raphael S.Carvalho: > > > Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds > the limit. > > > ldlinux.sys must fit between the bootsector and

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

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 (limit) can be at most: 65536 - 2 * ADV_SIZE - 512. Certain file systems (such as BTRFS and UFS2) will rely on ldlinux.sys being installed on the 0-64k range, thus it can't exceed the limit,

On Tue, May 20, 2014 at 12:20 PM, Anatol Pomozov <anatol.pomozov at gmail.com> wrote: > Hi > > On Tue, May 20, 2014 at 9:18 AM, Anatol Pomozov > <anatol.pomozov at gmail.com> wrote: >> Hi >> >> On Tue, May 20, 2014 at 3:12 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >>> On May 20, 2014 12:33 AM, "Anatol Pomozov"

Signed-off-by: Nicolas Cornu <nicolac76 at yahoo.fr> --- extlinux/main.c | 44 ++++++++++++++++++++++---------------------- 1 file changed, 22 insertions(+), 22 deletions(-) diff --git a/extlinux/main.c b/extlinux/main.c index 6871fb1..385b364 100644 --- a/extlinux/main.c +++ b/extlinux/main.c @@ -1415,21 +1415,12 @@ static int open_device(const char *path, struct stat *st, char

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

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

Hi On Tue, May 20, 2014 at 3:12 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On May 20, 2014 12:33 AM, "Anatol Pomozov" <anatol.pomozov at gmail.com> wrote: >> >> Hi >> >> On Mon, May 19, 2014 at 6:58 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> > On May 19, 2014 5:17 PM, "Anatol Pomozov" <anatol.pomozov at

On Sun, Nov 15, 2015 at 12:30:35PM +0100, Ady SF via Syslinux wrote: > [PATCH] extlinux/main.c: typo fixes > > Some typo fixes in extlinux/main.c. > None of them effects code execution. > --- > extlinux/main.c | 10 +++++----- > 1 file changed, 5 insertions(+), 5 deletions(-) > FWIW working on a new version that is `git am` ready, it will have a "sign-off".

On May 25, 2014 3:39 AM, "Geert Stappers" <stappers at stappers.nl> wrote: > > > While going throug old posts found: > > Op 2013-08-31 om 17:01 schreef Raphael S.Carvalho: > > 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. >

It's needed to enumerate both UFS1/2 since they have different magic numbers and super block offsets. Besides, UFS2 can be installed in the 0-64k range like BTRFS, whereas UFS1 can't. Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> --- extlinux/main.c | 71 +++++++++--- extlinux/ufs.h | 26 ++++ extlinux/ufs_fs.h | 307

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 *

Hi Syslinuxers, I am trying to understand the basic load chain in fat32 and ext4. I dug into the assembly for MBR, which is pretty straightforward: 1. Find boot partition (or use the pre-defined one at byte 440 for altmbr.bin) 2. Load the first 512-byte sector of the partition (VBR for fat32, Block Group 0 padding for ext). 3. Execute that code The code that is loaded, however, has to be too