similar to: PATCH: Handle virtual entry point in mboot.c32

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

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

This patch is just a (shameless) copy from bug #28 [1]. The original patch has been sitting there for a couple of years now, and it was based on Syslinux v 4.05. The patch I am posting here is just a re-base on v.6.03. Whichever inadequate formatting (tabs, trailing spaces...), or any kind of correction that was required for the original patch to be accepted, is probably still required now.

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

This patch moves lguest.c one level bellow, and enhances it with the ability to kick off 64 binaries. It would be much easier to just ifdef functions, but I have x86_64 machines loading 32-bit kernels as a longer goal, and that's why the patch features the load_elf_header() function. Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com> -- Glauber de Oliveira Costa Red Hat Inc.

This patch moves lguest.c one level bellow, and enhances it with the ability to kick off 64 binaries. It would be much easier to just ifdef functions, but I have x86_64 machines loading 32-bit kernels as a longer goal, and that's why the patch features the load_elf_header() function. Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com> -- Glauber de Oliveira Costa Red Hat Inc.

I started with Vivek's ELF bzImage patch from Oct last year, mashed it to apply to hpa's new setup/boot code. This patch does a couple of things, which would probably be better split into multiple patches: 1. Glue an ELF header onto the front of bzImage. This is a real ELF header at the front of the file. Breaks akpm's laptop, apparently, but it works for me. 2.

I started with Vivek's ELF bzImage patch from Oct last year, mashed it to apply to hpa's new setup/boot code. This patch does a couple of things, which would probably be better split into multiple patches: 1. Glue an ELF header onto the front of bzImage. This is a real ELF header at the front of the file. Breaks akpm's laptop, apparently, but it works for me. 2.

plain text document attachment (lguest64-loader.patch) I noticed that the lguest loader code for i386 was in Documentation/lguest. Well, that's fine (I guess) but it can't just be for i386. So I made a separate directory to put the loader code in. So now we have: Documentation/lguest/i386/... for the lguest i386 loader. and Documentation/lguest/x86_64/... for the lguest x86_64

plain text document attachment (lguest64-loader.patch) I noticed that the lguest loader code for i386 was in Documentation/lguest. Well, that's fine (I guess) but it can't just be for i386. So I made a separate directory to put the loader code in. So now we have: Documentation/lguest/i386/... for the lguest i386 loader. and Documentation/lguest/x86_64/... for the lguest x86_64

The program segments loaded presently in mboot.c only consists of a subset of sections described by the ELF Section Header Table (SHT) in the ELF kernel binary. Segments with useful information often needed for debugging purposes (symbol tables, string tables, etc.) aren't usually present in the program segments and hence not loaded above. Some kernels use this debugging information to

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

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

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)

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 arguments in the argv[] array and appends them to the

I'm currently trying to integrate ReactOS's bootloader into my concept bootdisk with standard layout. It uses Syslinux 4.10pre15. This is failing on two parts: 1) bootsector method only works if specifying huge cluster size (16KB) 2) Multiboot method fails due to opening bootloader's configuration file from harddisk instead of bootdisk.

Hi all, I have merged Tim's patches to the mboot loader, and have pushed it out as 3.20-pre7. I guess I'm going to actually have to make a 3.20 here soon... -hpa

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

The commit "linux.c32: move handling of mem= and vga= into the library function" also sets DEBUG to 1 in mboot.h. Is this intended? - Sebastian

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