From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] initramfs doesn't get linked into kernel
Date: Sat, 27 Apr 2013 19:34:07 +0200 [thread overview]
Message-ID: <20130427193407.0e7423c6@skate> (raw)
In-Reply-To: <klg76d$b42$1@ger.gmane.org>
Dear Adam Nielsen,
On Sat, 27 Apr 2013 19:53:20 +1000, Adam Nielsen wrote:
> Ahh ok, so what I did should have worked then. Since then I have added
> Ethernet support for my board and tried booting with a root filesystem on NFS.
> This worked (it mounted the filesystem) but it doesn't seem to be able to
> run the init binary (in this case Busybox built by buildroot.) Looking at
> tcpdump it correctly follows the symlinks and appears to download the busybox
> binary, but then fails saying it couldn't find init.
>
> I'm not quite sure what the problem is (I'm wondering whether it's a
> compatibility issue like OABI vs EABI or something) but it's possible this is
> what was causing the apparent initramfs failure, since it's the same
> filesystem (I just unzipped the .tar of the root filesystem that buildroot
> generated, into the NFS share.) I built the kernel with and without EABI
> support though and there was no difference, so I'm not really sure what it
> might be.
Again, please post your Buildroot .config and kernel .config. Another
issue you might be having if you're building your kernel outside of
Buildroot is that you may have enabled the usage of devtmpfs as
the /dev strategy, but forgot to enable CONFIG_DEVTMPFS and
CONFIG_DEVTMPFS_MOUNT in your kernel configuration. See
http://buildroot.org/downloads/manual/manual.html#_dev_management for
more details.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-04-27 17:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 23:37 [Buildroot] initramfs doesn't get linked into kernel Adam Nielsen
2013-04-27 1:17 ` Thomas Petazzoni
2013-04-27 9:53 ` Adam Nielsen
2013-04-27 17:34 ` Thomas Petazzoni [this message]
2013-04-27 22:50 ` Adam Nielsen
2013-05-04 0:29 ` Adam Nielsen
2013-05-04 8:25 ` Thomas Petazzoni
2013-05-04 11:35 ` Adam Nielsen
2013-05-04 17:36 ` Thomas Petazzoni
2013-05-05 1:47 ` Adam Nielsen
2013-05-05 2:11 ` Adam Nielsen
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=20130427193407.0e7423c6@skate \
--to=thomas.petazzoni@free-electrons.com \
--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