similar to: mboot hangs at MPI

On Wed, May 17, 2006 at 12:01:43PM -0700, syslinux-request at zytor.com wrote: > From: "Lin Salisbury" <lin.salisbury at gmail.com> > Subject: [syslinux] mboot hangs at MPI > > Where initrd.img is my own custom initrd that I've built to do some > pre-setup before booting to the real root on sda1. The problem is that > everytime I try and boot I get to this

All, When attempting to pxeboot the latest Xen3.0 hypervisor/kernel it was failing with the following error: ------ \ \/ /___ _ __ |___ / / _ \ _ _ _ __ ___| |_ __ _| |__ | | ___ \ // _ \ '_ \ |_ \| | | |__| | | | '_ \/ __| __/ _` | '_ \| |/ _ \ / \ __/ | | | ___) | |_| |__| |_| | | | \__ \ || (_| | |_) | | __/ /_/\_\___|_| |_| |____(_)___/ \__,_|_|

From: Tim Deegan <Tim.Deegan at cl.cam.ac.uk> Fix register constraints of final jump to kernel entry. When compiled with some GCC versions, mboot.c32 would clobber the kernel load address and try to jump to 0x2badb002. Signed-off-by: Tim Deegan <Tim.Deegan at cl.cam.ac.uk> --- --- syslinux-3.20-pre8/com32/modules/mboot.c.orig 2006-05-22 11:06:17.000000000 +0100 +++

I'm seeing this on a HP Blade and i'm not sure why this is happning since the nature of the issue is so wierd. I compiled mboot.c with a DEBUG defined in the mboot.c file. In the funciton init_mmap(), it prints the e820 map and on the HP blade this map values come out to be totally random. Some weird numbers which dont make any sense at all. However, if i add a while(1); or a exit(1); at

Hey, Looks like read disk function which was launched in 3.35 isnt working. Did anyone test this on any hardware? I'm using it thru the com32 interface to read contents of the active partition of a USB boot key (syslinux). I did a sample test like: void scanAndPrint() { com32sys_t regs_in; char *sectorBuf = __com32.cs_bounce; int i; memset(sectorBuf, 0x0, 512); // XXX MARK 1

From: Ralf Ertzinger <ralf at skytale.net> If a loaded kernel is in ELF format and contains a multiboot header indicating valid relocation information, prefer the informations from the ELF header. This is in violation of the Multiboot spec, but it's the way GRUB does things and Solaris kernels rely on this behaviour. Signed-of-by: Ralf Ertzinger <ralf at skytale.net> --- diff

This is a resend since I didn't hear back from anyone. Hey guys, I noticed the appended ipappend options end up in the beginning of the cmdline argv[] when mboot is entered. mboot then tries to parse the first argument as the name of the kernel module and promptly fails cuz it can't find "ip=.." or "bootif=...". I'm attaching a patch which basically looks for any

Set the boot device based on the derivative information. Signed-off-by: Sebastian Herbszt <herbszt at gmx.de> diff --git a/com32/mboot/mboot.c b/com32/mboot/mboot.c index d008da0..526d10a 100644 --- a/com32/mboot/mboot.c +++ b/com32/mboot/mboot.c @@ -224,6 +224,14 @@ int main(int argc, char *argv[]) mboot_apm(); mboot_syslinux_info(); + /* Set boot device info */ + const

Set a pointer to syslinux_version()->version_string in mbinfo. Signed-off-by: Sebastian Herbszt <herbszt at gmx.de> diff --git a/com32/mboot/mboot.c b/com32/mboot/mboot.c index 8425e06..76ef7a0 100644 --- a/com32/mboot/mboot.c +++ b/com32/mboot/mboot.c @@ -222,6 +222,13 @@ int main(int argc, char *argv[]) /* Add auxilliary information */ mboot_make_memmap(); mboot_apm();

Hi, I'm trying to get FreeBSD 7.2 booting using mboot module from syslinux 3.82. Unfortunately it doesn't seem to work. Here is my pxelinux config: === 8< === label freebsd72-i386-mboot kernel mboot.c32 append /kernels/freebsd/7.2/i386/boot/kernel/kernel single --- /kernels/freebsd/7.2/i386/boot/mfsroot === 8< === Here is the error message I get on boot: === 8< ===

Hi. VMWare has an own/modified mboot.c32, which is capable of using Configfiles. This mboot.c32 is on every Installsystem for their ESXi hypervisor install-iso. Until syslinux 4.07 this works with pxelinux out of the box. Since 5.x this mboot.c32 will not work anymore. There seem to be more modifications than only a parameter "-c". Does anyone has an idea what has changed so this

Hi all, I've started writing a new mboot.c32 using the Syslinux native APIs; it is currently on the new-mboot branch of the Syslinux git repository. However, I don't have a huge number of things which use Multiboot set up to test, so I'd really appreciate it if you're a user of mboot.c32 to help me try this and report back positive or negative. I don't have the Solaris DHCP

Hello all, I'm new on the list and hope this question isn't out of order. I'm booting Xen with mboot.c32 but with 100mb/s cards. I want to upgrade to 1000mb/s. I haven't got the biggest budget to trial and error new network cards so I'd like to buy the right card first time. I think this can be a bit tricky from 100mb/s card experience. A 3c905CX-TXM (03-0247-000 E)

Hello. I want to make ESXi on LUKS encrypted partition. ESXi uses Mboot.c32. Can the Mboot.c32 work with luks-encrypted? If it is possible, where i can see an example? Thank you!

Hello, The pxeconfig part: label sapcl03-xen kernel mboot.c32 append sles10/xen.gz dom0_mem=258048 --- sles10/linux-xen netdevice=eth0 insmod=aic79xx console=ttyS0,57600 --- sles10/initrd-xen.sapcl03 The thing sort of boots: COM32 Multiboot loader v0.2. Copyright (C) 2005-2006 Tim Deegan. Kernel: sles10/xen.gz dom0_mem=258048 Loading sles10/xen.gz..... Module:

From: Geert Stappers <stappers at nero.gpm.stappers.nl> They were introduced by the patch for ELF64 support. --- com32/mboot/map.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/com32/mboot/map.c b/com32/mboot/map.c index 2e8641f..1992f14 100644 --- a/com32/mboot/map.c +++ b/com32/mboot/map.c @@ -281,7 +281,7 @@ struct multiboot_header *map_image(void *ptr, size_t

Hi, I am trying to get xen booted on a new mainboard I bought using efi-syslinux/mboot. No success so far. When I choose the xen menu entry except from some characters being wiped from the bottom of the screen nothing is happening. I have made a typo in the xen kernel filename. Nothing changed, no errors about wrong a filename were displayed Initially I compiled syslinux 6.03 (slackware64,

Hi, I have had a VMware ESXi network boot setup for quite some time now. After upgrading from 4.06 to 5.01 (or 5.10-pre3) the network boot fails with the following error: --- snip --- Failed to load COM32 file esxi/5.1.0/mboot.c32 boot: --- snip --- This error is seen for the ESXi bootup only. The default mboot.c32 from syslinux itself doesn't work and this setup has been working with

Hi all, I'm attempting to PXE boot ESXi, which uses the syslinux mboot.c32 module. The mboot.c32 included with ESXi seems to be an older version that runs into an "out of memory loading.." problem halfway through, even though the box has 8GB memory. This may be related to NUMA, since it works fine on an older box but not the newer blade. I saw that some non-contiguous memory issues

Hello, I use Tim's mboot.c32 to load multiboot kernels over pxelinux. However, some kernels require the symbol table and other information in the ELF section header table to be able to load properly. This functionality is not present in mboot.c now, so I added support for it. The patch is attached. It would be great if you can push this into the next release of syslinux so ELF multiboot