similar to: Disk-On-Chip problem/question

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,

I have syslinux booting slax off of a usb stick but in the process I think I may have found a bug in syslinux im using version syslinux-3.31 my syslinux.cfg use to look as follows <== beginning display boot/splash.cfg default slax autoexec=startx prompt 1 timeout 40 F1 boot/splash.txt F2 boot/splash2.txt F3 boot/splash.cfg label slax kernel boot/vmlinuz append vga=769 changes=slaxsave.dat

isoconfig.sys file below - Only change from past is adding stuff after the bz28.7 kernel. DEFAULT vesamenu.c32 Prompt 0 menu color screen 37;40 #80ffffff #00000000 menu color border 30;44 #40000000 #00000000 menu color title 1;33;44 #c0fdd017 #00000000 menu color unsel 37;44 #90ffffff #00000000 menu color hotkey 1;37;44 #ffffffff #00000000 menu color sel 7;37;40

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have done some additional testing, and gotten it a bit close to what I was looking for. I had to modify the cat.c to eliminate the printing of the arguments and file name, and added a Press Enter to return menu line. With the below isolinux.cfg the options do display the files, and pressing enter than returns to the vesamenu. DEFAULT

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

Hi. I need some help from the experts please. I am experiencing a syslinux error message and I cannot find much in the way of help or reference from the documentation or the archives. Using a USB hard drive (as detailed below), I have three primary partitions and one extended partition. Disk /dev/sdb: 60.0 GB, 60011642880 bytes 255 heads, 63 sectors/track, 7296 cylinders Units = cylinders of

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, Maybe I am just not looking in the right spot but I can't figure out how to set a default menu in my isolinux.cfg. This is what it looks like: PROMPT 0 TIMEOUT 40 DEFAULT /boot/vesamenu.c32 LABEL cubez MENU LABEL Graphics mode (Compiz) - Experimental KERNEL /boot/vmlinuz APPEND vga=0x317 initrd=/boot/initrd.gz ramdisk_size=9999 root=/dev/ram0 rw chexpand=256 load=cubez

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 Team I need to run vfio driver using qemu and I'm using below xml file for this.. <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>instance</name> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <vcpu

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

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

I am running isolinux 4.02 and ramdisk_size does not seem to have an effect on the ramdisk size. No matter what I set it to in the isolinux.cfg file it seems the limit is 32768. I get the error: ram0: rw=0, want=360456, limit=32768 EXT2-fs error (device ram0): My isolinux.cfg file: LABEL EB KERNEL vmlinuxE APPEND initrd=bos.img root=/dev/ram0 rw ramdisk_size=545000 I am running the 2.6.38.2

When CONFIG_KLIBC_ZLIB is not set, related functions shall not be called otherwise build failure is encountered: KLIBCLD usr/kinit/static/kinit usr/kinit/ramdisk_load.o: In function `load_ramdisk_compressed': /root/ldb_base/ofl/packages/klibc/usr/kinit/ramdisk_load.c:68: undefined reference to `inflateInit2_' /root/ldb_base/ofl/packages/klibc/usr/kinit/ramdisk_load.c:116: undefined

As the subject says, I wanted to boot a domU from a CD to run a linux distribution installer (specifically, the 0.9.5-test2 installer ISO from http://www.sourcemage.org/). I looked for info on the web and in IRC on doing this, and most things that discuss it seem to suggest doing the install in a real system or using something line qemu first, then switching it to xen. I did get it to work using

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

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

Hello, I have a couple of questions, But first.... Thankyou for creating such an easy to use awesome piece of software. I am wanting to use ISO linux to select two different kernels/configurations and have set up the isolinux.cfg file as follows.... DISPLAY start.msg TIMEOUT 10000 DEFAULT linux LABEL linux KERNEL vmlinuz APPEND root=/dev/ram0 initrd=txtimage.gz LABEL linux-fb KERNEL

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