From: Adam Nielsen <a.nielsen@shikadi.net>
To: buildroot@busybox.net
Subject: [Buildroot] initramfs doesn't get linked into kernel
Date: Sun, 28 Apr 2013 08:50:58 +1000 [thread overview]
Message-ID: <klhkoe$dak$1@ger.gmane.org> (raw)
In-Reply-To: <20130427193407.0e7423c6@skate>
>> 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.
>
> 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.
Sorry, I didn't post them because I didn't think it would be easy to solve -
here they are:
http://www.shikadi.net/files/buildroot/2013-04-28.br.cannot_run_init.config
http://www.shikadi.net/files/buildroot/2013-04-28.k.cannot_run_init.config
I don't think it's an issue with /dev as I don't think the kernel gets that
far in the boot process. I am building the kernel outside of buildroot while
I'm testing (and I can only do OABI here) but I also copied my changes across
and built it through buildroot (so I could enable EABI in the kernel config)
but there was no change.
I'll keep investigating, but let me know if you have any insight!
Many thanks,
Adam.
next prev parent reply other threads:[~2013-04-27 22:50 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
2013-04-27 22:50 ` Adam Nielsen [this message]
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='klhkoe$dak$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