similar to: reinstalling syslinux

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

Hi, I encounter a problem with Syslinux 5.00 I cannot really describe. So I created two small videos: Booting with Syslinux 5.00 (1.3 MB): <https://www.dropbox.com/s/b6g8cdf2t9v48c6/boot-syslinux5-fail.mp4> How I fixed the problem by downgrading to Syslinux 4.06 and how booting should look like (6.5 MB): <https://www.dropbox.com/s/lt7cpgfm0qvqtba/boot-syslinux5-how-i-fixed-it.mp4>

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

Hello! I'm posting some experiences with GRUB0/1 + sys/extlinux + MBR/GPT in a pendrive with 15 partitions. This could be helpful improving sys/extlinux. I did make a bootable pendrive with 14 distros using a GPT partition table and a tricky solution to let sys/extlinux boot from every partition chainloaded from GRUB (GRUB0 or GRUB1). Having a MBR schema, sys/extlinux can't be

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

Hi, I installed syslinux 6.0.3 on a UEFI/GPT system with Arch Linux. My /boot/EFI/syslinux/syslinux.cfg contains MENU SAVE but selected entries aren't saved. Just after I hit the Enter key in the syslinux menu, I see efi_adv_write: Unable to open file \ldlinux.sys, this message isn't displayed when the boot starts after the timeout (default entry). My installation didn't have this

I have syslinux 5.10 on a 32bit gentoo system. It boots fine. Now I installed another linux system in other partitions of the same drive (a 64 bit system), updated syslinux.cfg, setup the new system as default, and the new entry appears in the menu. Problem is: it doesn't boot. On timeout, it starts counting down again, and that's it. No error message whatsoever. Selecting the old system

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,

> 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

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

After so much time and improvements, I'm glad to see and publicize a pre-release, 6.04-pre1 in https://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/6.04/ Personally, I've already been working testing the pre-release as-is and my tests have been positive so far. I appreciate feedback like that from Gabriele Balducci and testing "make bios installer". Yes, there are a

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

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 chain. When Linux is chosen, syslinux chains to

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

> > As opposed to "label", > "dlabel" ... > https://github.com/ErwanAliasr1/syslinux/commit/ebf8cbf > > SeaBIOS / GRUB2 > > ... > ... > <target dev='vdc' bus='virtio'/> > <boot order='3'/> > ... > ... > <target dev='vdd' bus='virtio'/>

Hi all, I was using grub2 for booting Archlinux x86_64 in my GPT Internal HDD (/dev/sda) then I switched to syslinux/extlinux. It was working fine but suddenly it staring showing "Boot Error" message on screen. I googled for a solution and tried all syslinux versions from 4.04-pre4 down to 4.03-stable but non of them worked. I don't know what suddenly changed caused this

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

That is perfectly true. I had a beautiful bug in the code .... Switching from python to C have some weird side-effect. Indenting is not enough, brackets are required.... So I pushed https://github.com/ErwanAliasr1/syslinux/commit/5a122d218553a6d4019273653ba9fad66d6ae79e with the fix. I tested it on my multi-disk system with success. I also changed the name of the function. 2016-07-17 8:21

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

I recently tried to install several distros on a usb stick, with the peculiarity of creating in it a GPT label rather than the usual dos label. Installed Grub2 using the parted bios_grub flag on a partition, I proceeded to copy several distros on the remaining partitions. Grub2 worked fine, chainloading syslinux on each of the partitions. Or rather it worked all fine until I reached the fifth