All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot with SquashFS root file system
Date: Tue, 06 Dec 2011 21:29:36 +0100	[thread overview]
Message-ID: <878vmpqw9b.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4EDE32C3.7020400@neotion.com> (Emmanuel BOUAZIZ's message of "Tue, 06 Dec 2011 16:20:35 +0100")

>>>>> "Emmanuel" == Emmanuel BOUAZIZ <ebouaziz@neotion.com> writes:

 Emmanuel> Hi,

 Emmanuel> I'm trying to run buildroot 2011.11 on an atom based board,
 Emmanuel> booting via PXE.

 Emmanuel> I've selected the SquashFS 4.x root filesystem (xz
 Emmanuel> compressed), bzImage as the Kernel binary format, and
 Emmanuel> syslinux/pxelinux as the bootloader.

 Emmanuel> In the system configuration, I checked "remount root
 Emmanuel> filesystem read-write during boot"

That doesn't make much sense for a readonly file system like squashfs.

 Emmanuel> In the kernel configuration, I checked Initial RAM filesystem
 Emmanuel> and RAM disk support+XZ, and SquashFS/XZ filesystem support.

 Emmanuel> On the PXE server, I put these kernel parameters: append
 Emmanuel> vga=0x305 fbcon=scrollback:4096k initrd=rootfs.squashfs

An initramfs would be a better option than initrd, but OK. Did you build
the kernel with buildroot or manually?


 Emmanuel> Here is what I get during the boot sequence:

 Emmanuel> (...)
 Emmanuel> RAMDISK: squashfs filesystem found at block 0
 Emmanuel> RAMDISK: Loading 14133KiB [1 disk] into ram disk.../
 Emmanuel> usb 1-7: new high speed USB device number 3 using ehci_hcd
 Emmanuel> VFS: Mounted root (squashfs filesystem) readonly on device 1:0
 Emmanuel> usb 2-2: new full speed USB device number 2 using uhci_hcd
 Emmanuel> can't open /dev/null: No such file or directory
 Emmanuel> can't open /dev/null: No such file or directory
 Emmanuel> can't open /dev/null: No such file or directory
 Emmanuel> can't open /dev/null: No such file or directory
 Emmanuel> can't open /dev/null: No such file or directory
 Emmanuel> can't open /dev/null: No such file or directory

Do you have CONFIG_DEVTMPFS enabled in your kernel? From a quick look at
the kernel sources (init/do_mounts_initrd.c) I see that the kernel
doesn't mount devtmpfs automatically when an initrd is used, so you'll
need to add a wrapper script as /linuxrc which mounts it and execs
/sbin/init, similar to how we do it for initramfs (fs/cpio/init):

# devtmpfs does not get automounted for initramfs
/bin/mount -t devtmpfs devtmpfs /dev
exec 0</dev/console
exec 1>/dev/console
exec 2>/dev/console
exec /sbin/init $*

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2011-12-06 20:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06 15:20 [Buildroot] buildroot with SquashFS root file system Emmanuel BOUAZIZ
2011-12-06 15:56 ` Michael S. Zick
2011-12-06 17:59   ` Emmanuel BOUAZIZ
2011-12-06 18:16     ` Michael S. Zick
2011-12-08 10:31       ` Emmanuel BOUAZIZ
2011-12-08 10:48         ` Peter Korsgaard
2011-12-08 11:26           ` Emmanuel BOUAZIZ
2011-12-08 14:27             ` Michael S. Zick
2011-12-08 17:34               ` Emmanuel BOUAZIZ
2011-12-06 20:29 ` Peter Korsgaard [this message]
2011-12-13 17:18 ` Arnout Vandecappelle
2011-12-14  8:40   ` Thomas Petazzoni
2011-12-14  9:01   ` Peter Korsgaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878vmpqw9b.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.