similar to: How to use --once? Does it work?

On Jun 05 2014, Ady wrote: > > I'm working on a system derived from ARCH linux, running what they > > call version 6.02-4 of the syslinux package (which would be your > > version 6.02 plus their/our patches). I've got a syslinux.cfg > > ArchLinux currently is already using 6.03-pre12 or newer, so I would > suggest for you to update. I want to keep the

> Hi Folks, > > I've got what I hope is a clueless newbie question for you. I couldn't > find much about it in the last 8 or so months or achives, or anywhere > else, so I'm asking before settling down to read the fine source code > ;-) > > I'm working on a system derived from ARCH linux, running what they > call version 6.02-4 of the syslinux package

> On Jun 05 2014, Ady wrote: > > > > I'm working on a system derived from ARCH linux, running what they > > > call version 6.02-4 of the syslinux package (which would be your > > > version 6.02 plus their/our patches). I've got a syslinux.cfg > > > > ArchLinux currently is already using 6.03-pre12 or newer, so I would > > suggest for

Hi all, wasnt sure whether this was the best place to put this information; but something seems to have gone 'backwards' in the later pre-releases of 6.03 regarding network booting. below are results of me testing - i did each a few times to make sure they are valid results. hope it helps identify something that's gone awry ? so far, 6.03 pre11 and pre13 (excluding efi32) seem most

> Message: 3 > Date: Fri, 06 Jun 2014 08:13:36 -0700 > From: "H. Peter Anvin" <hpa at zytor.com> > To: Andrew Rae <A.M.Rae at leeds.ac.uk>, "'syslinux at zytor.com'" > <syslinux at zytor.com> > Subject: Re: [syslinux] EFI booting over network - can't then load > anything > Message-ID: <5391DAA0.2050207 at

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

Testing Syslinux 6.03-pre13 in a BIOS 32-bit VM, boot: vesa.c32 Undef symbol FAIL: luaL_checklstring Failed to load COM32 file vesa.c32 boot: Is there a Lua-related issue? Is vesa.c32 expecting some kind of argument? TIA, Ady.

>> Hi, >> >> We have some problems while network booting thin clients. The type is T5540. >> >> At this moment we are using pxe linux 6.03. >> >> The systems are booting correctly with pxe linux version 6.03-pre14. >> We have seen the same error with version 6.03-pre9. >> >> The error message: >> >> Failed to load ldlinux.c32

On Thu, Jun 5, 2014 at 8:50 AM, Wissam Shoukair <wissams at mellanox.com> wrote: > Hi Gene, > > More information about this? > > I have found in the syslinux git that this commit id is the last good > commit: > > commit 41c29c26d70fde563d7c255872bbadad87a39dfa (tag: > refs/tags/syslinux-5.02-pre3) > Author: Matt Fleming <matt.fleming at intel.com> >

Hi guys, I'm have a pure 64-bit system (Intel based). Due to that I can't use 32-bit ELF extlinux binary provided in the syslinux-6.03 package. Unfortunately building extlinux installer failed... See error below after these command: make bios clean make bios (failed) ... ar cq liblpxelinux.a rawcon.o pxeboot.o pxelinux-c.o fs/pxe/dhcp_option.o fs/pxe/pxe.o fs/pxe/tftp.o

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

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

On May 13, 2014 4:04 PM, "Ady" <ady-sf at hotmail.com> wrote: > > On Tue, May 13, 2014 at 7:51 PM, Ady <ady-sf at hotmail.com> wrote: > > > I wonder why the already built-in binaries are not enough / adequate. > > I don't believe it can be used as is: > > bash# file syslinux > > syslinux: ELF 32-bit LSB executable, Intel 80386, version

On Sun, Feb 8, 2015 at 7:49 PM, Alexey Orishko via Syslinux <syslinux at zytor.com> wrote: > Hi guys, > > I'm have a pure 64-bit system (Intel based). Due to that I can't use 32-bit ELF > extlinux binary provided in the syslinux-6.03 package. > > Unfortunately building extlinux installer failed... > > See error below after these command: > make bios clean

On Sun, 8 Feb 2015 20:21:58 -0500 Gene Cumm via Syslinux <syslinux at zytor.com> wrote: > On Sun, Feb 8, 2015 at 7:49 PM, Alexey Orishko via Syslinux > <syslinux at zytor.com> wrote: > > Hi guys, > > > > I'm have a pure 64-bit system (Intel based). Due to that I can't > > use 32-bit ELF extlinux binary provided in the syslinux-6.03 > >

Hello, I noticed the following behavior of extlinux 4.05: I created an ext3 filesystem on the first (primary and active) partition of a usb stick. I mounted it at /mnt/. Then I copied to /mnt/ldlinux.sys the ldlinux.sys found in the syslinux 4.05 archive and I created a basic /mnt/extlinux.cfg. Then I ran "extlinux -i /mnt/" and rebooted on the usb stick. I got "ERROR: No

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

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,

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

On Fri, 6 Feb 2015, Ady wrote: > ... > But if we are talking about Chromebooks with SeaBIOS, are we talking > about booting kernels in CSM mode? Or in UEFI mode? > > Other than Chromebooks with (stock) SeaBIOS, is this new reported > behavior also seen under other cases / hardware / firmware / kernels > (versions)? Hi Ady, With a clone of the git repo on kernel.org I run