Displaying 20 results from an estimated 2000 matches similar to: "Could not find kernel image:"
2002 Jul 07
2
isolinux bug?
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
2002 Apr 07
3
Failure with 1st isolinux attempt
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
2005 Sep 20
4
standalone bootable usb-stick
hi ya syslinuxerz
- i've been slowly working on a making a custom bootable
standalone usb-stick with X11 and kde
- it's basically builds itself off of a slackware-10.1 server
- create a custom initrd.gz ( /dev/ram0 )
http://linux-boot.net/Bootable/InitRD/
- create a custom rootfs.gz ( /dev/loop0 )
http://linux-boot.net/Bootable/RootFS/
- create X11 and kde loopfiles
2005 Nov 03
2
simple menu limitations
I am using the following simple menu and have noticed that items at the
bottom are dropping off. I seem to be limited to 12 items. Is there a
limit to how many items can be on the simple menu?
default pxelinux.cfg/menu.c32
prompt 0
MENU TITLE UWSP PXE Boot Menu
# TIMEOUT 200
LABEL bartpe
MENU LABEL Build 12
KERNEL /STARTROM.0
APPEND keeppxe
LABEL 11dnet
MENU LABEL Build 11DNET beta
2005 Jan 11
17
[Fwd: Installing from distribution CDs]
Sorry, hit send instead of attach again. Rest of patches included.
--
Anthony Liguori
Samba, Linux/Windows Interoperability
Linux Technology Center (LTC) - IBM Austin
E-mail: aliguori@us.ibm.com
Phone: (512) 838-1208
Tie Line: 678-1208
2003 Jul 23
3
isolinux problem report
I have tried to use isolinux 2.05, and I am running into a problem where it
will not boot. I have previously used version 1.66, and the older version
works just fine. Changing nothing except dropping the new version in does
not work.
Below is all of the relevant info, I believe. This occurs on multiple
machines with different BIOS. I am currently in process of doing a binary
search to find the
2003 Jan 19
1
isolinux/gentoo
Hello,
Im a Gentoo kernel maintainer thats trying to fix some bugs on are upcoming
1.4 livecd release that uses IsoLinux.
Our isolinux.cfg is pretty standard :
#########################################
default gentoo
append initrd=initrd acpi=off root=/dev/ram0 init=/linuxrc
timeout 300
prompt 1
display boot.msg
F1 boot.msg
F2 help.msg
label livecd
kernel gentoo
append
2007 Jul 26
5
ISOLINUX boot problem: request for help
Hi,
I am trying to track down a ISOLINUX boot problem on my workhorse computer.
Booting slax-6.0.0-rc5.iso from www.slax.org (a live distro) from CD gives the
following messages:
Loading /boot/vmlinuz ...........
Loading /boot/initrd.gz ............
Ready.
_
Silence. The next message should be, but does not appear:
Uncompressing Linux ...........
This message appears with the same CD on an old
2005 Jul 07
2
bug(?) in 2.11
Hi!
I write this config line:
kernel /boot/i386/vmlinuz ro ramdisk=32768 root=/dev/ram0 init=/linuxrc
but when I try to boot I got this mesasge:
Could not find kernel image: /boot/i.386/
Same symptomes are with slash and backslash too. I think, the parses
don't understand the directory separator characters and count as the
part of filename.
ps
Sorry for my english
--
Gabor HALASZ
2005 Aug 12
5
PXE/Memdisk/bootimage having a fight
I have tried to get this working SO many times, everywhere I look on
the web tells me i have this correct.
I have the following stanza in my /tftboot/lts/pxelinux.cfg/default
label Ghost
kernel memdisk
append initrd=netboot.img
For some reason, it doesn't work - I get the error messages
Missing parameter in config file
Could not find kernel image: linux
boot:
The netboot.img is in the
2004 Nov 18
2
use of APPEND in default
Having fought my PXE config and eventually getting it to work (had to
comment out the group { } statments ?
I now come across another issue I cannot resolve and would appreciate some
help.
in my /tftpboot/pxelinux.cfg/default file I have cause to use the APPEND
statement to pass options
to the kernel being used.
Unfortunately this line has now become longer than 255 characters and
appears to be
2004 Jun 30
1
initramfs and kernel 2.6.7
Hi,
I 'am trying to launch linux kernel 2.6.7 with initramfs.
My pxelinux.cfg/default file looks as follows:
default a1
prompt 1
timeout 600
label a1
kernel vmlinuz-2.6.7-1
append initrd=initramfs_data.cpio.gz root=/dev/ram0 init=/linuxrc
Kernel image vmlinuz-2.6.7-1 and initramfs_data.cpio.gz was loaded
succesfully by pxelinux.
Kernel says:
checking if image is initramfs... it is
but
2012 Sep 04
1
ifcpu64.c32 not working properly when used in a menu include file
The following is a pxelinux problem, specifically to do with
including config files with the menu include directive and the
ifcpu64.c32 com module.
I have a working ifcpu64.c32 setup that jumps to the label rescue64
in the case of a 64-bit CPU. The label "rescue64" defines a 64-bit
kernel and a 64-bit initrd.img. The setup jumps to a label named
"rescue32" in the case of a
2003 Mar 24
5
Bootable Kernel
Hello,
Sorry to sound like a bad record, but I'm trying to figure out why I'm
getting "Bad gzip magic numbers" errors when ISOlinux is trying to
inflate the kernel. Right now I'm clueless as to what's wrong. I've tried
various kernels compiled on a few different platforms. Has anyone ever
seen this before? ANyone know where a better forum to ask this question
2006 Apr 03
2
probs running stuff from initrd
Hello all
Now I may be way of whack here, so please forgive me.
I''m trying to merge xen with redhat''s config-netboot. The idea being a
kinda stateless domU. For those that haven''t seen you share a rootfs and
then bind mount all the individual files over then top, and the redhat
gui builds all the pxeboot config and stuff for you if you want a
diskless client. I
2003 Jan 04
1
pxelinux and ram images
Looking at the FAQ for SysLinux there is an option for an initrd file
(initrd=filename), this does not seem to work with pxelinux (or it is
just that I am doing something wrong...).
here is my config file:
prompt 1
#serial 0 115200
label linux
kernel vmlinuz-2.4.18-ssi
#read-write
#root=/dev/ram0
append init=/linuxrc console=tty0 console=ttyS0,115200
initrd initrd-2.4.18-ssi.img
label local
2005 Feb 22
1
PXELinux
Greetings:
I'm hoping PXE linux can help me with my problem...
I'm trying to setup a PXE based install server under Linux that can
host Linux (SLES9, Slackware) and Windows (NT4, 2000, XP, 2K3) Install
images. I would ideally like to be able to have a PXE compliant host
boot, and prompt me to pick an image to boot. Has anyone ever done this
before?.. I have ISO images stored on the
2005 Jan 07
1
Version 3.02 floppy boot hangs.
Hello,
When I upgrade syslinux from 2.13 to 3.02. my linux floppy doesn't
boot anymore.
steps:
dd if=/dev/zero of=fdimg bs=18k count=160
mkdosfs fdimg
syslinux fdimg
mount -o loop fdimg /mnt
cp files/* /mnt/
umount /mnt
then use memdisk load fdimg
the files includes: vmlinuz initrd syslinux.cfg message.txt f1.txt ...
it only prompts 1 line:
SYSLINUX 3.02
2005 Nov 04
3
pxelinux menu questions
Hello all,
I have a few questions about the menuing system that I haven't been able
to find in the archives (it would be nice if they were available in a
searchable form other than having to click on a month-by month basis and
read through them - if they are searchable I would love to find a way to
do this but it hasn't jumped out at me).
My first question is : What is menu.c32? I
2006 Jun 10
1
PXELINUX with Kernel 2.6.15.4: VFS: Cannot open root device "hde1" or unknown-block(0, 0)
Hello again,
I'm always not able to boot-up my CF-FileSystem. (It works with a
2.4.x Kernel!)
See: http://syslinux.zytor.com/archives/2006-June/006942.html
I dont't understand, why the kernel can't mount the root-fs on exit
of "linuxrc".
Before finising "linuxrc" I can work on it, start a "bash"-shell, do
all sorts of linux-cmds on the root-fs...