Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot with SquashFS root file system
Date: Tue, 6 Dec 2011 09:56:05 -0600	[thread overview]
Message-ID: <201112060956.07523.minimod@morethan.org> (raw)
In-Reply-To: <4EDE32C3.7020400@neotion.com>

On Tue December 6 2011, Emmanuel BOUAZIZ wrote:
> 
> Hi,
> 
> I'm trying to run buildroot 2011.11 on an atom based board, booting via PXE.
> 
> I've selected the SquashFS 4.x root filesystem (xz compressed), bzImage as the Kernel binary format, and
> syslinux/pxelinux as the  bootloader.
> In the system configuration, I checked "remount root filesystem read-write during boot"
> 
> In the kernel configuration, I checked Initial RAM filesystem and RAM disk support+XZ, and SquashFS/XZ filesystem support.
> 
> On the PXE server, I put these kernel parameters: append vga=0x305 fbcon=scrollback:4096k initrd=rootfs.squashfs
> 
> Here is what I get during the boot sequence:
> 
> (...)
> RAMDISK: squashfs filesystem found at block 0
> RAMDISK: Loading 14133KiB [1 disk] into ram disk.../
> usb 1-7: new high speed USB device number 3 using ehci_hcd
> VFS: Mounted root (squashfs filesystem) readonly on device 1:0
> usb 2-2: new full speed USB device number 2 using uhci_hcd
> can't open /dev/null: No such file or directory
> can't open /dev/null: No such file or directory
> can't open /dev/null: No such file or directory
> can't open /dev/null: No such file or directory
> can't open /dev/null: No such file or directory
> can't open /dev/null: No such file or directory
> Starting logging: OK
> Starting mdev...
> mdev: /sys/class: No such file or directory
> Starting network...
> hub 2-2:1.0: USB found
> hub 2-2:1.0: 3 ports detected
> ifup: can't open '/var/run/ifstate': Read-only file system
> (...)
> 
> I get the exact same result if I try to use a cramfs instead of a SquashFS.
> 
> Oddly enough, it works perfectly with a cpio root filesystem, or when I integrate the root filesystem as an initramfs in
> the kernel image.
> 
> I probably missed an important item, but can't figure which. 
> Any help appreciated. 
> 

SquashFS is a read-only file system.

So which of the "device support" options did you choose?
You'll need one that puts devices in something writable, like tmpfs.

Mike
> Thanks,
> 

  reply	other threads:[~2011-12-06 15:56 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 [this message]
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
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=201112060956.07523.minimod@morethan.org \
    --to=minimod@morethan.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox