search for: fdimag

...m_[...]_i386.img: DOS floppy 1440k, x86 hard disk boot sector (This is a BIOS update boot image for the IBM X Series servers). I'm booting with PXE on the IBM machine, with this pxelinux.cfg: $ cat pxelinux.cfg/default [...] LABEL update_bios_img MENU LABEL ^BIOS Update (img) FDIMAGE ibm_fw_bios_m9e144a_anyos_i386.img [...] PXE boots, I select this image, and I get the following error upon botting this .img file: boot: update_bios_img Invalid image type for this media type! boot: Any ideas would be appreciated, thanks! Daniel -- L?VAI D?niel PGP key ID = 0x4AC0A4B1 Ke...

On a boot drive on a PC, I would like to boot Linux by having it at the beginning of the disk, right after the MBR and SYSLINUX, _before_ the first partition, and _not_ in a filesystem. Essentially I want something like booting a floppy with a kernel built using "make fdimage", but with a hard disk instead of a floppy disk. The first partition would probably start at the second cylinder; for a drive with 255*63*512 bytes/cyl, that should be enough room for a kernel and a little initrd/initramfs. Can I do this easily using SYSLINUX, and if so, is it something fai...

...@Gene, > > > > Not being a developer myself, I don't understand this "other > > KERNEL-like directives" sentence. I do know what "kernel-like > > Those directives which acts like KERNEL, specifying a binary to > execute. BOOT BSS COM32 COMBOOT CONFIG FDIMAGE LINUX LOCALBOOT PXE. > > > directives" means, but I do not know which one is the one you are > > referring to here, and why "_other_ KERNEL-like directives" would be a > > I'm referring to all of the above collectively. > > > concern. I mean, oth...

> > kernel.c:new_linux_kernel() to load_linux.c:bios_boot_linux() because > > there is no convenient way in new_linux_kernel() to control the boot > > flags value. > > This is the part that has me questioning things and trying to recall > if any other KERNEL-like directives ever utilize keeppxe. > @Gene, Not being a developer myself, I don't understand this

...ariants/sections (pxelinux.txt, isolinux.txt, comboot.txt; perhaps add menu.txt due to popularity) - DOS boot (for SYSLINUX on a FAT* file system)(perhaps group with installer command line) - Novice protection - "NOTES ON BOOTABLE CD-ROMS" (perhaps move to isolinux.txt; for the deprecated FDIMAGE directive / .img floppy image format) - Hardware compatibility list reference - (not present) Common problems list reference - MBR install (bad cat) (perhaps group with installer command line) - Boot loader IDs - Bug reports/contact info I'd think keeping all of the information specific to th...

...ze keeppxe. >> > > @Gene, > > Not being a developer myself, I don't understand this "other > KERNEL-like directives" sentence. I do know what "kernel-like Those directives which acts like KERNEL, specifying a binary to execute. BOOT BSS COM32 COMBOOT CONFIG FDIMAGE LINUX LOCALBOOT PXE. > directives" means, but I do not know which one is the one you are > referring to here, and why "_other_ KERNEL-like directives" would be a I'm referring to all of the above collectively. > concern. I mean, other than the behavior regarding file...

Anyone know the correct syntax for specifying a floppy image in the /tftpboot/pxelinux.cfg/default file? I am trying to use: label Dos Bootdisk MENU LABEL Dos bootdisk FDIMAGE discimage.img But when I select it the menu, I get a message saying "Automatic boot in 30 seconds" and nothing happens. I would use: label Dos Bootdisk 2 MENU LABEL Dos bootdisk 2 kernel memdisk append initrd=discimage.img but this is a 2.88meg floppy and memd...

...d include "GCC 4.7 fixes" (or 4.7.x ?). 2_ In "./NEWS", the changelog for version 4.05 includes "ISOLINUX: remove the .img file support". Since ".img" might have several possible interpretations, maybe it should be specified as "ISOLINUX: remove the FDIMAGE floppy.img file support" or alike. 3_ In Syslinux 4.04, a new "./diag/" directory was added, mostly related to MBR/VBR code. This directory and its subdirectories are the only ones containing instructions for the final user regarding the MBR. The wiki pages regarding the MBR hav...

...gt;> > Not being a developer myself, I don't understand this "other >> > KERNEL-like directives" sentence. I do know what "kernel-like >> >> Those directives which acts like KERNEL, specifying a binary to >> execute. BOOT BSS COM32 COMBOOT CONFIG FDIMAGE LINUX LOCALBOOT PXE. >> >> > directives" means, but I do not know which one is the one you are >> > referring to here, and why "_other_ KERNEL-like directives" would be a >> >> I'm referring to all of the above collectively. >> >>...

I have occasional problems booting kernel boot floppies made with syslinux-2.04/2.05. The symptom is that syslinux loads an initial part of the kernel image and then halts with Boot failed: please change disks and press a key to continue. Observations: 1. It's not a media problem. I've switched floppies and reformatted them, but the failure persists. 2. It's not a BIOS problem.

...ng a developer myself, I don't understand this "other > >> > KERNEL-like directives" sentence. I do know what "kernel-like > >> > >> Those directives which acts like KERNEL, specifying a binary to > >> execute. BOOT BSS COM32 COMBOOT CONFIG FDIMAGE LINUX LOCALBOOT PXE. > >> > >> > directives" means, but I do not know which one is the one you are > >> > referring to here, and why "_other_ KERNEL-like directives" would be a > >> > >> I'm referring to all of the above collect...

Hi. We've been using PXELINUX for years, to kick off OS installations (floppy images) and booting assorted tools. The addition of ISO support in memdisk opened up some new alternatives that we also use, e.g. booting WinPE ISO images over PXE. Today I downloaded a BIOS for a HP EliteBook 8440p and discovered that the BIOS file is 3 MB. I could probably squeeze it onto a 2.88 MB floppy image

...ink/ldlinux/execute.c b/com32/elflink/ldlinux/execute.c > --- a/com32/elflink/ldlinux/execute.c 2014-10-06 10:27:44.000000000 -0600 > +++ b/com32/elflink/ldlinux/execute.c 2015-02-18 18:46:02.193886584 -0700 > @@ -41,6 +41,7 @@ const struct image_types image_boot_type > { "fdimage", IMAGE_TYPE_FDIMAGE }, > { "com32", IMAGE_TYPE_COM32 }, > { "config", IMAGE_TYPE_CONFIG }, > + { "efi", IMAGE_TYPE_EFI }, > { NULL, 0 }, > }; > > @@ -89,6 +90,13 @@ __export void execute(const char *cmdlin >...

This series: 1. Updates the boot protocol to version 2.07 2. Clean up the existing build process, to get rid of tools/build and make the linker do more heavy lifting 3. Make the bzImage payload an ELF file. The bootloader can extract this as a naked ELF file by skipping over boot_params.setup_sects worth of 16-bit setup code. 4. Update the boot_params to 2.07, and update the

This series: 1. Updates the boot protocol to version 2.07 2. Clean up the existing build process, to get rid of tools/build and make the linker do more heavy lifting 3. Make the bzImage payload an ELF file. The bootloader can extract this as a naked ELF file by skipping over boot_params.setup_sects worth of 16-bit setup code. 4. Update the boot_params to 2.07, and update the

...diff -uprN a/com32/elflink/ldlinux/execute.c b/com32/elflink/ldlinux/execute.c --- a/com32/elflink/ldlinux/execute.c 2014-10-06 10:27:44.000000000 -0600 +++ b/com32/elflink/ldlinux/execute.c 2015-02-18 18:46:02.193886584 -0700 @@ -41,6 +41,7 @@ const struct image_types image_boot_type { "fdimage", IMAGE_TYPE_FDIMAGE }, { "com32", IMAGE_TYPE_COM32 }, { "config", IMAGE_TYPE_CONFIG }, + { "efi", IMAGE_TYPE_EFI }, { NULL, 0 }, }; @@ -89,6 +90,13 @@ __export void execute(const char *cmdlin do_sysappend(q); } +#ifdef __FIRMWARE_BIOS...

From: Matt Fleming <matt.fleming at intel.com> Since we can't use __intcall() for EFI, and since we can now have the ELF module code resolve all our symbols at runtime, we should delete as many references to __intcall() as possible and just access the symbols directly. The most interesting patch is the support for weak symbols. We need to be able to reference derivative-specific

...bits.h> #include <syslinux/config.h> - -/* Must match enum kernel_type */ -const char *const kernel_types[] = { - "none", - "localboot", - "kernel", - "linux", - "boot", - "bss", - "pxe", - "fdimage", - "comboot", - "com32", - "config", - NULL +#include <syslinux/boot.h> + +const struct image_types image_boot_types[] = { + { "localboot", IMAGE_TYPE_LOCALBOOT }, + { "kernel", IMAGE_TYPE_KERNEL }, + { "linux&...

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some