Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Calfee <nospamcalfee@yahoo.com>
To: buildroot@busybox.net
Subject: [Buildroot] diskimage HOWTO
Date: Mon, 24 Aug 2009 11:13:46 -0700 (PDT)	[thread overview]
Message-ID: <263477.7826.qm@web58202.mail.re3.yahoo.com> (raw)
In-Reply-To: <f3566d60908232239l268a7233necd10a6dd342f58f@mail.gmail.com>

--- On Sun, 8/23/09, Bai Shuwei <baishuwei@gmail.com> wrote:

> From: Bai Shuwei <baishuwei@gmail.com>
> Subject: [Buildroot] diskimage HOWTO
> To: buildroot at busybox.net, qemu-devel at nongnu.org
> Date: Sunday, August 23, 2009, 10:39 PM
> Hi, All:
>   I want to build a test enviroment with QEMU and
> buildroot. But I don't know how to build the diskimage
> which same as linux-0.2.img offered by BUILD-ROOT. I build
> the diskimage following the  
>    buildroot-2009.05/docs/README.diskimage,
> but failure. 
>  
Hi Bai,

I tried following those instructions and failed too. It is very complicated. There are 4 things that must be correct and in sync, the kernel, busybox, uclibc (compiler and filesystem), and bootstrap. 

Yesterday I did get things to run with qemu. I intend to update the docs when I can systematically get everything to work. For one thing on Ubuntu Jaunty I have not figured out how to get kqemu to install or work.... I have not mastered emulated ethernet either.

Anyway I built buildroot from a fairly recent git version - I suspect any older release will work. I took the defaults in all the configurations, the built-in configs are missing lots of the new options. This is curious, you do a make, it starts menuconfig, it thinks awhile and then another of the 4 main things wants to be menuconfiged. Anyway, I selected plain old 386 as my cpu and built with all the built in minimal options. It built the first time (way to go Peter!).

Originally, either by default or I mistakenly selected it, I built a rootfs.i386.jffs2 file system (from the buildroot make menuconfig). This did not work because the kernel did not know how to boot from anything but an ext2 or cramfs file system. There must be a kernel parameter to fix this, but I don't know what it is. So to get things going select an ext2 file system.

I discovered a gui interface for qemu, called "qemu launcher". Use that it simplifies things. You no longer have to build another disk image with your bootstrap and kernel inside with your root filesystem. No partitioning required etc. 

IN the GUI:

I pointed hard disk 0 to "/home/calfee/buildroot/buildroot/binaries/uclibc/rootfs.i386.ext2" boot disk: "Hard disk 0".

Then on the linux boot tab I checked "boot linux kernel directly", removing the need to fiddle with grub.

I put in kernel image "/home/calfee/buildroot/buildroot/binaries/uclibc/bzImage"

Then on the kernel command line I put root=/dev/hda

At this point press the launch button, and linux will boot and ask for your login. By default your username is root, with no password. Now you are running your built system!

I would like to get the diskimage instructions to work, people like me want to test on a known platform (their development PC) before jumping directly to test hardware, it reduces the unknowns.

If you get qemu ethernet working, please post an email with instructions.

Regards, Steve


      

  parent reply	other threads:[~2009-08-24 18:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-24  5:39 [Buildroot] diskimage HOWTO Bai Shuwei
     [not found] ` <4A9245EA.9030108@redhat.com>
2009-08-24  8:30   ` [Buildroot] [Qemu-devel] " Bai Shuwei
     [not found]   ` <f284c33d0908241004g3eb4608dga6acc979d0547c6a@mail.gmail.com>
2009-08-25  3:55     ` Bai Shuwei
2009-08-24 18:13 ` Steve Calfee [this message]
     [not found] ` <20090911093217.GA2342@amd.home.annexia.org>
2009-09-11 11:27   ` 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=263477.7826.qm@web58202.mail.re3.yahoo.com \
    --to=nospamcalfee@yahoo.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