similar to: bootloader installation improvements

On Fri, Aug 4, 2017 at 12:06 PM, ian_bruce--- via Syslinux <syslinux at zytor.com> wrote: > 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 >

Thanks for the response, Gene. Much appreciated. I didn't get all of it; mind if I follow on below? ldlinux.sys is ldlinux.bin without the VBR (Volume Boot Record) code. > Makes sense. > > 1. Where is the code that goes in the VBR or Block Group 0 padding? > > diskboot.inc. > which appears to be included in diskstart.inc. I will have to dig in and see how this all gets

Gene, thanks for doing "Reply-All". I only get digest, so this keeps me in the loop. Appreciated. > which appears to be included in diskstart.inc. I will have to dig in and > see > > how this all gets compiled (pointers always appreciated :-) ). > > Yes. > Is the build process documented? Or am I just going to have to plod through the makefiles? > As Ady said,

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

On Thu, Jul 7, 2016 at 8:00 AM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > >> > We would need at least: > > A_ the partitions and directory structure in which the following items > are _located_ : /dev/sda1: # tree . . ??? extlinux ? ??? ldlinux.c32 ? ??? ldlinux.sys ? ??? libcom32.c32 ? ??? libmenu.c32 ? ??? libutil.c32 ? ??? menu.c32 ? ???

> > > Is the build process documented? Or am I just going to have to plod > through > > the makefiles? > > I don't think so. > Oh well... > > 1. Run installer > > 2. Installer loads ldlinux.sys onto the filesystem (and copies > ldlinux.c32, > > but irrelevant for now). > > 3. Installer calculates which blocks in the filesystem contain

I'm trying to add boot support to https://github.com/libguestfs/nbdkit/tree/master/plugins/floppy This NBD server plugin generates a completely virtual FAT filesystem and partition table. Nothing is ever written to a file, and it must run without anything needing to be root, loop mounting etc. Running "syslinux --install <something>" is a non-starter. So I've looked at

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

From: Matt Fleming <matt.fleming at intel.com> The first two patches in this series are fixes for bugs reported by someone in #syslinux. The third makes dmitest.c32 actually wait for user input. If no one has any objections/concerns, I'll pull this into the official elflink branch. Matt Fleming (3): core: Print error message if we don't load ldlinux.c32 Clean up $(GPLLIB) leak

On Mon, Dec 3, 2018 at 10:02 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > Now it is just dd, mkfs and copy in the files we need. > > One less thing to worry about keeping versions consistent. > > > > > > I just noticed those 2 files that were added by > > > > syslinux -i boot.img > > > > (right?) > > > >

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

> I have used syslinux 4.0x and earlier for many years, with Puppy Linux > and more recently Quirky Linux. Though, my knowledge of all the > capabilities of syslinux remains rudimentary. > > I am new to UEFI. I recently got my hands on a win8.1 laptop, 64-bit > system, and decided to tackle booting Quirky on it, from a USB stick. > > I turned off Secure Boot. > > I

On Wed, Dec 5, 2018 at 2:21 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > After some discussion/debugging behind the scenes, we are back on > track, with updated Debian packages. > > > 0_ Starting from an _original_ (so-called "hd-media") boot.img mounted > in "target" (or "$target", or some similar notation), and the version

Ady, Thanks for taking the time to respond to my lengthy post. Here are my answers: On 11/5/14, Ady <ady-sf at hotmail.com> wrote: > >> I have used syslinux 4.0x and earlier for many years, with Puppy Linux >> and more recently Quirky Linux. Though, my knowledge of all the >> capabilities of syslinux remains rudimentary. >> >> I am new to UEFI. I recently

I have used syslinux 4.0x and earlier for many years, with Puppy Linux and more recently Quirky Linux. Though, my knowledge of all the capabilities of syslinux remains rudimentary. I am new to UEFI. I recently got my hands on a win8.1 laptop, 64-bit system, and decided to tackle booting Quirky on it, from a USB stick. I turned off Secure Boot. I wrote /usr/share/syslinux/gptmbr.bin to the flash

Hi, I've spent few long hours on weekend trying to get syslinux as boot loader for my alpine linux. Long story short: Failing to load ldlinux.c32 on ext4, but after changing file system from ext4 to ext3, everything worked (all other things being the same). Details below, my setup is fairly complicated so this is might be a partial reason, ALTHOUGH final and the only change which makes

works with legacy, hangs with efi. where works is: No DEFAULT or UI configuration directive found! but enter and ^v make things happen hangs is: nothing happens, no response from keyboard, have to reboot. note: config prompt.cfg prompt.cfg does not exist, but I would expect similar behaviour between efi and legacy. test is: starting with blank image, mkfs, mount it... + cp

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

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