similar to: success story with EXTLINUX 6.04 --> why not release it?

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

Le 23/07/2020 ? 09:05, Pierre-Philipp Braun via Syslinux a ?crit?: > I do not succeed building 6.03 nor 6.04-pre1 on slackware current with GCC 9 anyway.? This is why I was using the development branch. > > v6.04-pre1 make install and installers were complaining so I used its binaries right away as such (I tried both / and /boot/syslinux/) > > ??????? dd if=./bios/mbr/mbr.bin

Ady Ady via Syslinux wrote: > > As usual, builds/versions should not be mixed, at least within the same > platform (bios/ia32/x64). > > Currently, the Syslinux-related binary packages in Debian are: > > _ extlinux > _ isolinux > _ pxelinux > _ syslinux > _ syslinux-common > _ syslinux-efi > _ syslinux-utils > > The list of packages and their

On 05.03.2016 14:43, Gene Cumm via Syslinux wrote: > 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

> 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

hello everybody, apologies if I'm missing something here Just tried to build 6.04-pre1 test version with: make bios installer and found some problems all (seemingly) related to inaccurate paths in various Makefiles. I enclose a complete patch at the end of this email, which details the problems I found and how they got fixed for me. As an example, this is the first error I got:

On 06.03.2016 16:47, poma wrote: > ... >> nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \ >> -DHEXDATE="0x56dc3c62" \ >> -Di386 \ >> -I/tmp/syslinux-6.04-pre1/core/ \ >> -l ldlinux.lsr -o ldlinux.o -MP -MD ./.ldlinux.o.d /tmp/syslinux-6.04-pre1/core/ldlinux.asm >> nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \

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

... > nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \ > -DHEXDATE="0x56dc3c62" \ > -Di386 \ > -I/tmp/syslinux-6.04-pre1/core/ \ > -l ldlinux.lsr -o ldlinux.o -MP -MD ./.ldlinux.o.d /tmp/syslinux-6.04-pre1/core/ldlinux.asm > nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \ > -DHEXDATE="0x56dc3c62" \ > -Di386 \ >

I am excited to try this on my system that hangs with 6.03. Is this the best place to report if it continues not to work? Thanks for all of this work! Sent from my iPhone > On Mar 5, 2016, at 08:43, Gene Cumm via Syslinux <syslinux at zytor.com> wrote: > > After so much time and improvements, I'm glad to see and publicize a > pre-release, 6.04-pre1 in >

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

On 07.03.2016 06:45, poma wrote: > On 06.03.2016 18:23, poma wrote: >> On 06.03.2016 16:47, poma wrote: >>> ... >>>> nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \ >>>> -DHEXDATE="0x56dc3c62" \ >>>> -Di386 \ >>>> -I/tmp/syslinux-6.04-pre1/core/ \ >>>> -l ldlinux.lsr -o ldlinux.o -MP -MD

On 06.03.2016 18:23, poma wrote: > On 06.03.2016 16:47, poma wrote: >> ... >>> nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \ >>> -DHEXDATE="0x56dc3c62" \ >>> -Di386 \ >>> -I/tmp/syslinux-6.04-pre1/core/ \ >>> -l ldlinux.lsr -o ldlinux.o -MP -MD ./.ldlinux.o.d /tmp/syslinux-6.04-pre1/core/ldlinux.asm >>>

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 root".

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

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

hi i'm about to upgrade systems. yesterday i got https://www.zytor.com/pub/syslinux/Testing/6.04/syslinux-6.04-pre3.tar.xz in order to upgrade 6.04-pre1 version. i first was upgrading a usb-disk which was booting smootly with a simple configuration. i changed the EFI installation in /EFI/BOOT: efi64/efi/syslinux.efi (UEFI bootloader for EFI X64 (x86_64) firmware) ?

As the subject says, building syslinux fails when built against 2.6.8.1 kernel headers. Anybody out there have a patch? The compile errors are below. set -e ; for i in memdisk dos win32 mtools unix extlinux sample com32 ; do make DATE=0x41e470ae HEXDATE=0x41e470ae -C $i all ; done make[1]: Entering directory `/usr/src/syslinux-3.07-pre1/memdisk' make[1]: Nothing to be done for `all'.