suddenly, i can't boot barebox on my beagle xM anymore [ISOLATED]

Robert P. J. Day rpjday at
Mon Dec 3 03:48:40 EST 2012

On Mon, 3 Dec 2012, Jan Lübbe wrote:

> On Mon, 2012-12-03 at 03:31 -0500, Robert P. J. Day wrote:
> > *sigh* ... i *think* i figured out what's happening.  in order to
> > play with barebox on my xM, until recently, i'd done nothing more than
> > create a single FAT partition on a micro SD card, put MLO and
> > barebox.bin on it, put it in my xM, and let it boot.  until that OMAP
> > merge, it worked fine.
> >
> >   as i read it, the new default environment for the xM *requires* a
> > second (ext3) partition or the boot process simply hangs, am i reading
> > that right?  if that's true, how can i adjust that so i can once again
> > just boot to barebox without having a kernel and root fs created yet?
> Only the kernel uses the second partition for its rootfs, barebox
> should get to the prompt where you can interrupt autoboot anyway.
> So figuring out the exact commit would be useful. The bisection
> should take only a few steps. Sascha build-checks every revision, so
> all the bisection steps should build fine.

  actually, i *did* use bisection to isolate it -- here's the commit
that introduces the issue:

commit 5f2074bdd13ea69af5a10c3bcccb648720d6937a
Author: Sascha Hauer <s.hauer at>
Date:   Wed Oct 31 10:16:48 2012 +0100

    ARM OMAP3 beagle: switch to new environment

    Signed-off-by: Sascha Hauer <s.hauer at>

  did i forget to post that?  oops ...



Robert P. J. Day                                 Ottawa, Ontario, CANADA


More information about the barebox mailing list