similar to: Syslinux/Extlinux chain : Unexpected change of Extlinux configuration folder after reboot

On Tue, Oct 20, 2015 at 1:08 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > >> Hello, >> >> We are experiencing a strange behaviour on an embedded system (i386 PC board). >> >> The structure of our disk is the following one : >> - A 2GB fat16 partition with DOS and syslinux >> - A 100GB Ext4 partition with Extlinux an several linux images

> Hello, > > We are experiencing a strange behaviour on an embedded system (i386 PC board). > > The structure of our disk is the following one : > - A 2GB fat16 partition with DOS and syslinux > - A 100GB Ext4 partition with Extlinux an several linux images to boot on ram > - A swap partition > > The system boot on syslinux to choose among Dos and Linux boot using

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

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,

I'm trying to install extlinux on my dual-booting computer, but when i try cat mbr.bin > /dev/sda the computer boots windows (it doesn't even come up with the extlinux menu). My partition setup is as follows: /dev/sda1 -> NTFS (Windows) /dev/sda5 -> Linux Swap /dev/sda6 -> Linux Root (/) /dev/sda7 -> Linux Home (/home) Now I presume that mbr.bin calls the bootsector of

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

On Wed, Jan 3, 2018 at 2:38 AM, Avi Deitcher <avi at deitcher.net> wrote: > 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 :-) ). >>

Richard W.M. Jones via Syslinux wrote: > 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

Hello syslinux, I'm a newbie to extlinux, and I'm a developer from yocto project (an embedded linux project). The device or filesystem must be mounted before we can install the bootsector to the device if I understand correctly, for example: $ mount /dev/sdcX /tmp/mnt $ extlinux -i /tmp/mnt Usually, the mount command requires the root privilage, we may not have the root privilage when

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 >

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 @@ -14,7 +14,7 @@ /* * extlinux.c * - * Install the syslinux boot block on an fat, ntfs, ext2/3/4, btrfs, xfs, + * Install the syslinux boot block on a fat, ntfs, ext2/3/4, btrfs, xfs, * and ufs1/2

On Sat, Jan 6, 2018 at 12:34 PM, Avi Deitcher <avi at deitcher.net> wrote: >> > 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 >> >

Hello list, I'm having problems with newest BIOS updates from Gigabyte to my Mother Boards, they don't want to boot syslinux, extlinux y usb-hdd mode. Then I need to know if someone else are having same problem, and can send me the Mother Board versions and bios versions to report as a bios bug. this is from the support, I'm awaiting for answer.

git://git.zytor.com/users/genec/syslinux.git Branch core-diskstart-boot-for-hpa. I found that INT 13h AH 08h in BOCHS used ES, DI, at least when using a partitionless HDD, causing "Boot error" from the magic check as it was loaded to the wrong location. HPA suggested wrapping INT 13h with the push/pop for ES's safety. This then lead to checking over for all int 13h calls in

Spaces, ASCII 0x20, have been * moved * inserted * deleted Signed-off-by: Geert Stappers <stappers at stappers.nl> --- extlinux/main.c | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/extlinux/main.c b/extlinux/main.c index 26eb43c..ed359f1 100644 --- a/extlinux/main.c +++ b/extlinux/main.c @@ -393,11 +393,11 @@ int install_bootblock(int fd,

Mr Anvin, is there a specific loading address used with the Syslinux bootsector (to load ldlinux.sys)? like msdos 0x70, freedos 0x60 we're trying to have a SYS program that can create bootsector for other OS's than FreeDOS only. not much luck though :( this way I'm trying to avoid the use of syslinux.exe/com (need the diskspace that it would save by not including this program) I

On Fri, 5 Dec 2014, Ady wrote: > > > If so: http://www.syslinux.org/wiki/index.php/Mboot.c32 > > > > I?m not permitted to edit either that page or its talk page. > > Do I submit the content addition here, then? > > Please do. Okay, MediaWiki syntax docs follow. Note I have tested those only a bit, and not within the vesamenu context, but if mboot.c32 resets to

(I *really* need to learn this list is configured for replying to sender instead of the list itself..) Dinesh P. schreef: > Hi there, > I am using memdisk with pxelinux, i have created ms-dos boot disk from windows xp, but when i boot from it stops on starting.... > what is the problem can anybody tell me.. > please read Syslinux and Memdisk

Hi! Facing a strange problem about not being able to access the floppy drive after booting from a rescue-floppy with 2.2.x kernel on an asus p4te mainboard, i searched the net and found a bug in the bootsector of the 2.2.x kernels. Before control is redirected to the kernel, the floppy drive is shut down in a way, that freezes the FD-Controller on recent mainboards (like the ASUS P4T-E). The

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 *