similar to: extlinux from syslinux 4.04 failed hard after choosing bzImage.

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 am trying to get a UEFI bootable USB. And I am unable to make it working. I have two x86_64 systems and both of them 'hangs' when I choose to boot UEFI from USB. I've created fat32 formated partition with ef00 type. I placed EFI/BOOT there with content of efi64/ distribution, I've created syslinux.cfg and renamed syslinux.efi to BOOTX64.EFI. However, it does just

Hi, Is syslinux still under active development? I do not see any new commit in git repo for about a year. -- Piotr.

Jeremy Fitzhardinge <jeremy@goop.org> writes: > Eric W. Biederman wrote: >> All it does is set a flag that tells a bootloader. >> "Hey. I can run when loaded a non-default address, and this is what >> you have to align me to." >> >> All relocation processing happens in the kernel itself. >> > > Is it possible to decompress and

Jeremy Fitzhardinge <jeremy@goop.org> writes: > Eric W. Biederman wrote: >> All it does is set a flag that tells a bootloader. >> "Hey. I can run when loaded a non-default address, and this is what >> you have to align me to." >> >> All relocation processing happens in the kernel itself. >> > > Is it possible to decompress and

> > > On 09/05/2013 01:55 AM, Gene Cumm wrote: > > > On Wed, Sep 4, 2013 at 2:34 PM, Piotr Karbowski > > > <piotr.karbowski at gmail.com> wrote: > > > > > >> With syslinux (extlinux) it will jump to last INCLUDE'ed menu always, with > > >> 5.01 it will display list of elements, then allow me to choose which one I > >

Hi, What the the size limit of booting bzImage file with syslinux ? I have tested different sized bzImage files, and when the files are small <800K, they work with syslinuz, but at some size larger they fail to work. This was the same problem loadlin1.6 had, but loadlin1.6c fixes the issue, and I can boot bzImage sizes up to 1.5Meg with loadlin, but syslinux fails. Can you confirm this

Hello list, Since a few months I get the following error after I have recompiled Xen from hg, xen-4.1-stable or xen-unstable: ERROR Invalid kernel: xc_dom_probe_bzimage_kernel: kernel is not a bzImage This comes from domU''s that are configured to use pv-grub. As a workaround I do have a working pvgrub-x86_64.gz from an earlier compile so I''m using that without problems.

Package: src:xen Version: 4.1.3-4 Severity: serious The bzimage loader used in both libxc and the hypervisor lacks XZ support. Debian kernels since 3.6 are compressed with XZ and can't be loaded. Support for XZ compression was added in changeset 23002:eb64b8f8eebb somewhere last year. Bastian -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990,

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: serious After noting that this version supposedly loads bzImage kernels: | xen-3 (3.2.1-2) unstable; urgency=low | | * Use e2fslibs based ext2 support for pygrub. (closes: #476366) | * Fix missing checks in pvfb code. | See CVE-2008-1952. (closes: #487095) | * Add support for loading bzImage files. (closes: #474509) | *

Hi I'm having problems PXE-booting a Sun-Blade 100x. As the subject line says, booting stops during "Loading /bzimage...." Broadcom UNDI PXE-2.1 (build 082) v6.2.11 Copyright (C) 2000-2003 Broadcom Corporation Copyright (C) 1997-2000 Intel Corporation All rights reserved. CLIENT MAC ADDR: 00 03 BA 44 4F F4 GUID: 00000000 0000 0000 0000 000000000000 CLIENT IP: 10.148.11.21 MASK:

Thanks all, It should be quick, so it will be implemented in C. Maybe I should have stated that I am not an expert in syslinux (intelligent but no expert). I think that I understand the "custom COM32 module" option : I simply have to change the code (and begin by looking into the files that were suggested). As for Peter's suggestion, I am not sure if I understood. Is this an

On Wed, Mar 19, 2014 at 4:16 PM, Mau Z <zmau1962 at gmail.com> wrote: > Hi, > > I am wondering how to implement the following customer's requirement : > The system is a stand alone embedded system with no operator (with Linux). > There is one SSD for the system's usage (and that is where the system loads > from). > > The requirement is to have a duplication of

On 03/19/2014 01:30 PM, Gene Cumm wrote: > On Wed, Mar 19, 2014 at 4:16 PM, Mau Z <zmau1962 at gmail.com> wrote: >> Hi, >> >> I am wondering how to implement the following customer's requirement : >> The system is a stand alone embedded system with no operator (with Linux). >> There is one SSD for the system's usage (and that is where the system loads

On Mar 19, 2014 5:22 PM, "H. Peter Anvin" <hpa at zytor.com> wrote: > Or we could make the Linux loader (load_linux.c) throw an error on a bad > CRC, which is probably a good idea anyway. Then the ONERROR option can > be used for the fallback. > > -hpa Sounds like an excellent idea. Should linux.c32 get an override option (in case of a non-compliant

Mau Z <zmau1962 at gmail.com> writes: > I am wondering how to implement the following customer's requirement : > The system is a stand alone embedded system with no operator (with Linux). > There is one SSD for the system's usage (and that is where the system loads > from). > > The requirement is to have a duplication of the Linux Image, and that > syslinux

Hello, I am trying to figure out where to change mmc rate to maximum speed. All images are loaded from emmc. I see in syslinux.c that it calls loadfile(), but I don't see how the filesystem fread() is actually done from emmc, and where to change its speed to maximum. Thank you for any comment, ranran

Well, it seems to be about time to have this conversation again. A rough overview of the previous thread and requirements is: 1. bzImage would not be a bare ELF file, but it would contain an ELF header+file within it 2. We need some way to add extra ELF notes into that ELF file 3. We use a "paravirtualized" bootloader type, with some other field to determine which

Well, it seems to be about time to have this conversation again. A rough overview of the previous thread and requirements is: 1. bzImage would not be a bare ELF file, but it would contain an ELF header+file within it 2. We need some way to add extra ELF notes into that ELF file 3. We use a "paravirtualized" bootloader type, with some other field to determine which

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: important Hi, I set the severity to important as it seems that current xen tools does not allow to load amd64 Debian kernel in DomU. I also put the debian-kernel ML in CC as I'm not sure the problem comes from xen tools or the kernel itself. Here is my configuration: Hypervisor: xen-hypervisor-3.2-1-amd64 3.2.1-2