similar to: Weird early-boot sequence, can't find a way to adapt to ramfs

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

I converted my lvm root initrd to an initramfs by putting glibc, lvm, pivot_root, my linuxrc, etc. in my initramfs source file. I use ash compiled against klibc to run my linuxrc Unfortunately - pivot_root . initrd - complains - pivot_root: Invalid argument I suspect this may be because you can't pivot_root using a cpio initramfs root? If so, what should I do instead? Should I

Hi, I hope this is the right list for initramfs questions. First I noticed: with initrd I can use real-root-device and pivot_root mechanisms. with initramfs only pivot_root works. My init (or linuxrc) scripts end like this: mount -t xfs -n -o ro /dev/mapper/root /new-root umount -n /sys || true umount -n /dev || true umount -n /proc || true cd /new-root pivot_root . initrd exec chroot .

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

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''ve installed xen-2.0.5 from source on gentoo, but the xen dom0 kernel doesn''t find the root device: ############################# snip ###################################### Kernel panic: VFS: Unable to mount root fs on unknown-block (3,3) ############################# snap ###################################### grub.conf: ############################# snip

I've created a bootable cd with isolinux but it can't load the kernel. It detects everything fine, decompresses the initrd, loads and decompresses the kernel and then tries to boot the kernel. But after that the computer hangs. Here's the screen dump: ISOLINUX 1.73 2002-05-26 Copyright (C) 1994-2002 H. Peter Anvin isolinux: Starting up, DL = 9F isolinux: Loaded spec packet OK,

I'm not sure when exactly this started, but currently when I specify a ramfs image via the initrd line in grub, kinit picks it up as an initrd and tries (and fails) to unpack it and run linuxrc from it. I'm assuming this is not the intended behavior. Can anyone point me into the proper direction for unpacking an initramfs image ontop of the in-kernel image? Currently, I am using kernel

Hi, All I am currently learning on the early userspace(EUS) code. And my goal is accessing initrd while in the EUS. For example: mount an initrd with the EUS mount command, Fsck it, chroot to it, run linuxrc in it and so on... But depend on the code, One can not preserve a initrd image when loading into EUS. So I must modify the EUS code to reach the goal. Can you give me some advices about

Hello, I was using a bunch of cpios in initramfs as a working system, and wondering why the unused files weren't being paged out to swap. So I reread ramfs-rootfs-initramfs.txt and now I know. So I wrote the attached utility. It creates a tmpfs, moves all files on the initramfs, moves / and executes the real init. It works, even with hardlinks, but it isn't the correct approach. Have

[Who wants to be on CC here? I took several names from the posters to the last lkml and klibc list threads: Olaf Hering, H. Peter Anvin, Roman Zippel, Jeff Bailey, Aaron Griffin, Gerd Hoffmann, Milton Miller, Andi Kleen, Jeff Garzik. Since I'm not subscribed I only see the From unless I am Cc'd]. On Mon Jul 10 21:48:34 PDT 2006, Olaf Hering wrote: > On Tue, Jun 27, 2006 at

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

After supermin has finished running, the initramfs files sit around occupying swappable memory but serving no further purpose. This saves a little memory, at the cost of about 1ms of extra boot time. --- init/init.c | 50 ++++++++++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 48 insertions(+), 2 deletions(-) diff --git a/init/init.c b/init/init.c index 733d66e..5ac53e9 100644 ---

Hi All, I am trying to start a lxc container using libvirt and I am facing an issue due to pivot_root. The return code from the system call ?pivot_root? is EINVAL (Invalid arguments). I isolated the issue to this specific condition check within the system call. This is an code snippet from fs/namespace.c::pivot_root * error = -EINVAL; if (root.mnt->mnt_root != root.dentry)

Hi I had some doubts regarding what all the init application should do: >> so, that should that application do? >> - mount /dev/hda1 /new-root >> - cd /new-root >> - run-init 1. Of what I understand, before exitting, init should mount the realroot and execute the init process. Is realroot the '/' or the empty directory created (in the cpio archive) ?

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

dear friend. i have mips board with BCM sibyte 1125CPU(use board sibyte 1250 swarm.) i use linux-kernel 2.6.12-rc1 download from linux-mips.com i use kernel 2.4.26 before this time, it's work ok at 2.4.26 with Ramdisk-busybox when i try to use ramdisk in 2.6.1x version, i found that ramdisk i not exist, i don't known how to use it again(i had try a patch for get ramdisk init to

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, Here's a try at writing an initramfs HOWTO. This is basically a write-up of a number of interesting emails I collected over time. It could probably use an editor, more fact-checking and a bunch of other good things, but it should be better than nothing ;-) Daniel -------------- next part -------------- INITRAMFS HOWTO 0) What are klibc and initramfs? Initramfs is a ramfs into which