All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Kuntke <paul@42degreesoffreedom.com>
To: buildroot@busybox.net
Subject: [Buildroot] Unable to boot via initrd
Date: Wed, 11 Jan 2012 10:02:28 +0100	[thread overview]
Message-ID: <20120111090228.GA3269@krikkit> (raw)

Hi to all,
I'm very new to buildroot and building Initrds and I would like to set up a
minimalistic environment for booting PCs (i386) over PXE. 

For this I would like to set up a Kernel and an initrd as System-Filesystem.
After everything was build fine I wanted to test the environment. But every
tries ended in a Kernel-Panic moaning about no /init to find. I've also tried
to set the "init" kernel-parameter to /bin/busybox. But even then it is not
able to start /bin/busybox. 

As testing environment I tried qemu as well as some real PCs with syslinux
over PXE. 

Kernel-Parameters I've tried: "root=/dev/ram init=/init" 
As Initrd I tried to use the bzImage with the build in initrd-image as well as
the rootfs.cpio.bz2 or rootfs.cpio.

Do I have to set some special Kernel-Params or do I have to set some special
options in the buildroot config?

Thanks,
 Paul

-- 
Paul Kuntke <paul@42degreesoffreedom.com>

Jabber-ID: paul at 42degreesoffreedom.com

This Mail is signed via gpg. 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120111/d6931a46/attachment.asc>

             reply	other threads:[~2012-01-11  9:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11  9:02 Paul Kuntke [this message]
2012-01-11 14:04 ` [Buildroot] Unable to boot via initrd Michael S. Zick
  -- strict thread matches above, loose matches on Subject: below --
2012-07-10 21:24 Bart J. Smit
2012-07-10 22:30 ` Arnout Vandecappelle
2012-07-11 13:54   ` Bart J. Smit
2013-09-02 19:06 Matthieu
2013-09-03 16:11 ` Arnout Vandecappelle
2013-09-03 22:41   ` Matthieu
2013-09-04  7:50     ` Thomas Petazzoni
2013-09-04 11:38       ` Matthieu
2013-09-04 11:53         ` Matthieu

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=20120111090228.GA3269@krikkit \
    --to=paul@42degreesoffreedom.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 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.