similar to: Missing parameter in syslinux.cfg

Howdy to all, We've been using isolinux quite successfully for quite some time now, and I have come across a couple of laptops where isolinux balks at my config file.. Upon booting on this systems, the image background appears corrupted, and at the boot prompt, the following happens automatically. Unknown keyword in config file. Could not find kernel image: 1 boot: Any label input here

folks, Im finding that using a config like this: SERIAL 0 19200 #IPAPPEND 2 PROMPT 1 TIMEOUT 100 IMPLICIT 0 APPEND console=ttyS0,19200n81 root=/dev/nfs nfsaddrs=10.10.10.100:10.10.10.2:10.10.10.2:255.255.255.0:soekris:eth0 nfsroot=10.10.10.2:/nfshost/truck panic=15 LABEL deb268 KERNEL vmlinuz-2.6.8-1-386 initrd=initrd.img-2.6.8-1-386 panic=10 LABEL deb268-ram KERNEL vmlinuz-2.6.8-1-386

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

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

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

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

Hi, I am trying to load kernel 2.6.6 on a Soekris net4521 from the network using PXE. I built my initrd with mkinitrd. RedHat nash (while running linuxrc) hangs after mounting /proc and says "Creating block devices". I am using the pxelinux.0 from the syslinux-2.10 distribution and the kernel and initrd were built on redhat 9.0. I built my kernel with BLK_DEV_RAM, RAMFS, TMPFS,

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

the following config-file triggers a couple of odd corner-cases in 3.08-pre5 ; SERIAL 0 19200 CONSOLE 0 APPEND console=ttyS0,19200n81 root=/dev/hda1 IMPLICIT 0 #DEFAULT sk1 #DEFAULT menu.c32 DEFAULT sk1 PROMPT 0 MENU TITLE Simple Boot Menu LABEL sk1 KERNEL vmlinuz-2.6.10-sk1 APPEND console=ttyS0,19200n81 root=/dev/nfs

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

I am attempting to install Gentoo on my cdless machine using the thumbdrive as a boot device. The motherboard is an Intel D815EEA, and is the latest firmware revision (at least on the BIOS). I believe I have done everything right, but it tells me I have unknown keywords in my syslinux.cfg and corrupt kernel images. The steps I have followed are thus: 1) Starting with a 4GB flash device,

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

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

Hi Gabor. Don't know if that helps, but I discovered a difference between the two lines: > kernel /boot/i386/vmlinuz ro ramdisk=32768 root=/dev/ram0 init=/linuxrc > Could not find kernel image: /boot/i.386/ i386 =?= i.386 You're sure that there's no typo in your configuration? Bernhard

Hi, in short: - EPIA MII6000E motherboard with CF-Card - Booting from network works with Linux Kernel 2.4.25 - Change to 2.6.15.4 doesn't work -- kernel panics: VFS: Cannot open root device "hde1" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncinc: VFS: Unable to mount root fs on unknown-block(0,0) in Detail: -

This is most exceedingly weird boot/shutdown sequence that I used once, and can't find a way to adapt to initramfs. Since you guys are trying to adapt all mechanisms that use initrd to using initramfs, this should interest you. initrd has (all binaries static): /bin: init halt mount poweroff pivot_root reboot sh umount /etc: fstab haltrc /dev: null zero tty tty0 tty1 console->tty0 hda1

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

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

Hello, I am experiencing a strange problem. I have a CF-based linux that boots with syslinux. (I tried 3.07 thru 3.11). Booting works fine if I put the CF into an embedded PC that detects the CF card as an IDE device (Secondary Master). - Some other system detects the CF as an USB device. - I can boot from the CF card as a SCSI-Device through VMware. In both of those cases, syslinux shows its

Hi I am trying to have a built in initramfs along with the traditional initrd. So I mount the initrd from the initramfs, but am facing problems in trying to run the 'linuxrc'. Following are the issues: 1. I mount the initrd from the initramfs and exceve 'linuxrc'. It starts executing linuxrc, but gives the following errors and panics: Red hat nash version 3.4.42 starting