similar to: AW: 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

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,

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

I am having a problem with setting up diskless clients under CentOS 5.2. I have everything working under CentOS 4.7. This is an adaptation of the (somewhat old) Diskless Linux with PXE HOWTO by Gerd v. Egidy, originally at the URL http://www.intra2net.com/opensource/diskless-howto/, which is now defunt (there is a mirror of it at http://blog.chinaunix.net/u/2389/showart_82438.html). What I am

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

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

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

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

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

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

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

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

Hi Xen developers, We are hitting a DomU Linux kernel panic and we''d like to find a solution for it. We are porting our virtual appliance to Amazon''s AWS. Our kernel is 2.6.27.57. We know it is old but we have to stay with it for now. The problem is when the kernel (64-bit) boots up in EC2 ( a large instance with 7.5 GB memory), the kernel crashes when hitting the BUG in

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

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

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?ve got a 512M machine and a 330M ( uncompressed ) initrd image. How can I mount the ramdisk? Normal booting seems to want to copy the entire initrd image into a Ramdisk, thus requiring 2X the memory. So what happens is the kernel boots correctly and I get, RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 330000 blocks [ 1 disk ] into ram disk And then I never see the light of day after