similar to: multiboot patch

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

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

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

If you have a multiboot kernel which is booted by syslinux/pxelinux/isolinux, etc., is there a way to determine who actually is the bootloader among the three? I'm wondering if the multiboot header or any part of memory has a consistent identifier somewhere. thanks, Ram

Hi all, A number of people have posted to the Xen lists recently wanting to network-boot Xen on machines whose NICs are not supported by GRUB. I''ve been writing a module for PXELINUX that will allow it to boot Xen directly over the network on PXE-enabled machines, without relying on any hacks (mbootpack, &c.), or needing to write/port any device drivers. I have a version of it

Hi All, Now that we have multiboot capable pxelinux, thanks to mboot.c32, I decided to try and remove pxegrub from my x86 jumpstart infrastructure since, in theory, pxelinux can now do it all. The problem I'm having is I'm not very sure I'm following Tim's documentation correctly... I'm not 100% what comes after the --- and whether the Sun kernel needs it's arguments

Hello, I noticed after upgrading from 3.20, I haven't been able to get syslinux to boot properly with menu.c32 or mboot.c32 from a USB key. I get an error saying invalid kernel when its trying to load menu.c32 or mboot.c32 (or any other kernel for that matter). I tried 3.35 and 3.36-pre5. Same exact behaviour. I'm using the following to compile: gcc version 3.2.3 20030502 (Red Hat Linux

I''ve now given up trying to get grub working with my particular e1000 adapter, I''ve tried all the patches and all I can get is something that works a little bit but never past the grub menu. I''m sure I read something somewhere about a tool which would combine a multiboot image + modules into a single bootable item which could be loaded by lilo, and am hoping that the

I''m trying to install xen-3.0.4 from source on a debian sarge (3.1r4) box with dual AMD-64 processors (with the new HVM support, although I don''t think that''s got anything to do with the problem). I installed only the packages necessary to compile xen and its kernel(gcc, make, bzip2, bridge-utils, etc). In the source directory, I ran ''make world &&

Hi All, I am not able to boot Xen . My "/boot/grub/menu.lst" has this entry title Xen 3.3.2-rc5 / Debian GNU/Linux, kernel 2.6.18.8-xen root (hd0,0) kernel /boot/xen-3.3.2-rc5.gz module /boot/vmlinuz-2.6.18.8-xen root=/dev/sda1 ro console=tty0 module /boot/initrd.img-2.6.18.8-xen savedefault I am getting following error : ERROR

Hi All, I am not able to boot Xen . My "/boot/grub/menu.lst" has this entry title Xen 3.3.2-rc5 / Debian GNU/Linux, kernel 2.6.18.8-xen root (hd0,0) kernel /boot/xen-3.3.2-rc5.gz module /boot/vmlinuz-2.6.18.8-xen root=/dev/sda1 ro console=tty0 module /boot/initrd.img-2.6.18.8-xen savedefault I am getting following error : ERROR

Hi All, I am not able to boot Xen . My "/boot/grub/menu.lst" has this entry title Xen 3.3.2-rc5 / Debian GNU/Linux, kernel 2.6.18.8-xen root (hd0,0) kernel /boot/xen-3.3.2-rc5.gz module /boot/vmlinuz-2.6.18.8-xen root=/dev/sda1 ro console=tty0 module /boot/initrd.img-2.6.18.8-xen savedefault I am getting following error : ERROR

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

folks, If you boot from syslinux based USB/harddisk, is there a way to know the partition or disk you booted from? I'm using the mboot module, so if the info is availble to thru the COM api, i can get it and append it to cmdline. thanks. -- Ram

Hello, I'm having trouble PXE booting the Xen hypervisor kernel as follows: PXELINUX 3.31 0x4518b206 Copyright (C) 1994-2005 H. Peter Anvin UNDI data segment at: 00094FC0 UNDI data segment size: 4A30 UNDI code segment at: 000999F0 UNDI code segment size: 44E4 PXE entry point found (we hope) at 999F:00D6 My IP address seems to be 0A000063 10.0.0.99

I'm attempting to PXE boot a XEN dom0 kernel version 2.6.16, xen version 3.0.2-2. I've built syslinux-3.20-pre8 from source and am using the following config: DEFAULT mboot.c32 xen-3.0.2-2.gz dom0_mem=258048 --- vmlinuz-2.6.16-xen0 ro console=ttyS0 root=/dev/sda1 --- initrd.img Where initrd.img is my own custom initrd that I've built to do some pre-setup before booting to the real

On Fri, 5 Dec 2014, Gene Cumm wrote: > >> mostly in C and be BIOS-only) or making the MirOS kernel act like > >> either an MBOOT kernel or a Linux kernel (for their boot protocols), The MirBSD _bootloader_ (not kernel) can act as a Multiboot kernel. It can then use disc access (not PXE), or you can pass it the ?real? kernel, but also e.g. configuration files, as Multiboot

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

> On Fri, 5 Dec 2014, Gene Cumm wrote: > > > >> mostly in C and be BIOS-only) or making the MirOS kernel act like > > >> either an MBOOT kernel or a Linux kernel (for their boot protocols), > > The MirBSD _bootloader_ (not kernel) can act as a Multiboot kernel. > It can then use disc access (not PXE), or you can pass it the "real" > kernel, but

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