similar to: Cannot chainload a formerly working Linux system

I am trying to create a bootable cd from a working LFS 6.1 partition. Thank you in advance for any thoughts on this. This is the error I get: ISOLINUX 3.10 2008-08-24 Copyright (C) 1994-2005 H. Peter Anvin Could not find kernel image: lfskernel-2.6.11.12 boot : _ under /isolinux/ I have these files: isolinux.bin I've tried 3.10 and 3.09 isolinux.cfg: default livecd label livecd

Folks I've just tried booting the 1st Linux CD I've made using Isolinux and it fails. At boot time I see: Boot from ATAPI CD-ROM: No Emulation ISOLINUX 1.67 2002-02-03 Copyright (C) 1994-2001 H. Peter Anvin boot: Could not find kernel image: /isolinux The cdimage was made using the command: mkisofs -v -o austin.iso -b isolinux/isolinux.bin -c isolinux/boot.cat

Please forgive me if this is a known issue or "feature". I didn't notice anything in the list archives or the docs, so I'm assuming this is a bug. I was attempting to create a bootable LFS cd using the instructions found at http://hints.linuxfromscratch.org/hints/boot-cd_easy.txt. I wasn't following the steps exactly as I had some personal changes I wanted to make. One

Hi > From syslinux-admin at zytor.com Mon Apr 8 02:11:05 2002 >From: Dermot Bradley <bradley at oldcolo.com> >To: syslinux at zytor.com >cc: erich.titl at think.ch >Subject: [syslinux] Re: Failure with 1st isolinux attempt >Sender: syslinux-admin at zytor.com >X-BeenThere: syslinux at zytor.com >X-Mailman-Version: 2.0.6 >List-Help: <mailto:syslinux-request

Hello everyone! So, I am working on creating a live CD that contains various different tools and iso images. I have been working under the assumption that I cannot boot iso images directly from syslinux, so I have been trying to chainload to Grub with custom config files, but it has not been working. The way I have the liveCD image setup gives each iso it's own grub lst file. When I try to

Hi, I have two disks in my computer with each one, a bootloader. The first disk (a usb key) boot with syslinux bootloader that launches a tiny kernel. The second disk has grub 2. I need to boot the disk 2 with grub, from the tiny kernel of the disk 1. So i use the bios interruption 0x19 to load the second bootloader, but this solution doesn't works. If i use a my own bootloader, the

Hello, I'm investigating ways to boot a DOS floppy image stored on the FAT32 EFI System Partition using Syslinux and Memdisk. The system will be running Win8 using UEFI mode (GPT disks) and secure boot off. Change the Windows efi boot loader is the easy part... With the current syslinux's alpha version (6.0), is it possible to boot the syslinux's efi module from the FAT32 EFI

Hi, I'm trying to use pxelinux to start Linux and optionally other things, maintained by windows folks. They use the Intel pxe boot loader, bstrap.0, and when I load it with a "kernel bstrap.0" statement, it fails. The reason it fails is because it can't find the !PXE data area. I guess it doesn't get the correct pointer or something along those lines. Do you think it

Inspired from a similar patch posted on grub-devel for Grub2 I immersed myself into the code of Grub Legacy and came up with this absurdedly simple patch to allow syslinux or other bootloaders residing in logical partition to be chainloaded from GRUB Legacy (0.9x). Hoping it to be of help, regards Fulvio Scapin -------------- next part -------------- A non-text attachment was scrubbed... Name:

Hi, I'm trying to boot Debian-Installer image from extlinux with chain.c32; i.e.: - I'm doing this from a loopback device (loop0) which later will be dumped to an USB stick. - GPT disklabel. - Partition 15 (loop0p15) contains extlinux info, and partition 12 contains Debian multi-arch installer image *dumped*[1], and its corresponding menu entry for extlinux is something like: LABEL

Hello, I'm investigating ways to boot a DOS floppy image stored on the FAT32 EFI System Partition using Syslinux and Memdisk. The system will be running Win8 using UEFI mode (GPT disks) and secure boot off. Change the Windows efi boot loader is the easy part... With the current syslinux's alpha version (6.0), is it possible to boot the syslinux's efi module from the FAT32 EFI System

> I have a USB disk with syslinux files installed in /boot/syslinux, and the > bootloader is installed into MBR or VBR > > I then extracted a *.iso file which uses syslinux as the bootloader, into > root dir of the disk. The iso file contains a rescue OS or an OS installer. > Now I got the directory /isolinux with files isolinux.bin and isolinux.cfg > in this folder >

On 06/16/2014 02:57 PM, Alexander Perlis wrote: > > > On 06/16/2014 10:41 AM, Gene Cumm wrote: >> [...] Initially I wrote pxechn.c32 to allow further >> modifications of the DHCP data [...] > > Awesome! In fact, this might allow us to install an automatic 'http' > prefix on all subsequent requests, to avoid slow tftp --- or is that a > bad idea, and/or

On Mon, Jun 16, 2014 at 5:57 PM, Alexander Perlis <aperlis at math.lsu.edu> wrote: > On 06/16/2014 10:41 AM, Gene Cumm wrote: >> >> [...] Initially I wrote pxechn.c32 to allow further >> modifications of the DHCP data [...] > > > Awesome! In fact, this might allow us to install an automatic 'http' prefix > on all subsequent requests, to avoid slow

> On 06/16/2014 07:12 PM, H. Peter Anvin wrote: > > On 06/16/2014 02:57 PM, Alexander Perlis wrote: > >> Here's what I mean by 'chainloading to install an automatic http prefix': > > > > The other option is to use a very small default configuration file > > containing only: > > > > default reload > > label reload > >

Hi, I would like to chainload syslinux 3.86 after booting from pxelinux of syslinux 6.04 is it possible? I was checking chain.c32, but i was not very successful so far. on my tftproot? dir i has this: pxelinux.0 boot/isolinux/ pxelinux.cfg/ isolinux_3.86/pxelinux.0 isolinux_3.86/boot/isolinux/ isolinux_3.86/pxelinux.cfg/ Does anyone know how i can, after booting from the tftproot pxelinux.0

> I would like to chainload syslinux 3.86 after booting from pxelinux of > syslinux 6.04 is it possible? > Does anyone know how i can, after booting from the tftproot pxelinux.0 > (syslinux 6.04), chainload isolinux_3.86/pxelinux.0 and make > isolinux_3.86/ the working dir? Try using pxechn.c32 from the same version that you are booting with (6.04..., + libutil.c32 +

Hello, I have the following scenario: - GPT Partitioned USB disk with syslinux (or extlinux) on the first partition and a menu to boot each partition; all of them are iso9660 images of different linux distros, - Before dumping every iso image into its partition space on the USB disk I need to remaster it changing something on its initrd to be able to coexist with other linux distros on the

perhaps the boot-from-cdrom code in Smart Boot Manager? Bernd >>> No, since booting from CD-ROM requires that the El Torito part of the BIOS is activated, which it won't be if it didn't boot from CD-ROM in the first place. ---------------------------------------------------------------- Op deze e-mail zijn de volgende voorwaarden van toepassing:

On Mon, Jun 16, 2014 at 10:23 AM, Alexander Perlis <aperlis at math.lsu.edu> wrote: > When chainloading one pxelinux from another (e.g., chainloading from say > pxelinux 4.07 to pxelinux 6.02), can one pass parameters or somehow control > the root directory and/or server IP address? > > Here's the need: we have a loaded-up PXE server working great under 4.07, > and