From: Adam Nielsen <a.nielsen@shikadi.net>
To: buildroot@busybox.net
Subject: [Buildroot] initramfs doesn't get linked into kernel
Date: Sat, 27 Apr 2013 19:53:20 +1000 [thread overview]
Message-ID: <klg76d$b42$1@ger.gmane.org> (raw)
In-Reply-To: <20130427031758.363b222f@skate>
Hi Thomas,
> If you let Buildroot build your kernel, it does that automatically (see
> the code in linux/linux.mk). If you build your kernel outside of
> Buildroot, you have to set CONFIG_INITRAMFS_SOURCE correctly.
>
> If you build your kernel outside of Buildroot, pointing
> CONFIG_INITRAMFS_SOURCE to the .cpio image works just fine. I'm doing
> that all the time here.
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.
I'll keep looking into the problem until I'm able to boot with root on NFS,
then I'll try initramfs again to see if that works, and report back.
Thanks again,
Adam.
next prev parent reply other threads:[~2013-04-27 9:53 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 [this message]
2013-04-27 17:34 ` Thomas Petazzoni
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='klg76d$b42$1@ger.gmane.org' \
--to=a.nielsen@shikadi.net \
--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