[Freedombox-discuss] Trouble Building Raspberry Pi Image

Chris Troutner chris.troutner at gmail.com
Wed May 14 14:21:47 UTC 2014

Great sleuthing, Nick. I appreciate  you looking into this.

I'm going to try the hack you recommended in order to get V0.2 loaded. I
really want to play with that. I'll document it on my blog.

Now that I've played around with the Raspberry Pi and actually tried to
load FreedomBox onto it, I'm more convinced than ever that it's an
important piece of target hardware. These things are very easy to get into
other peoples hands.


Chris Troutner

On Tue, May 13, 2014 at 7:12 PM, Nick Daly <nick.m.daly at gmail.com> wrote:

> Nick Daly <Nick.M.Daly at gmail.com> writes:
> > The immediate cause of the issue has been discovered, but we don't yet
> > know why it's broken.  Using "kpartx -a $IMAGE.img", you can easily
> > mount each partition of the image file and verify that the first
> > (primary boot) partition of the Raspberry Pi image is empty other than a
> > zero-byte start.elf file.  Because the boot partition is empty, the
> > image has no data with which to boot.
> It works fine with a DreamPlug.  Looking through F-M's
> bin/mk_freedombox_image, the only difference I can find is that the
> Raspberry Pi is missing uboot.  I'm trying to build an image with that
> now.
> Nick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/freedombox-discuss/attachments/20140514/a4ce9f14/attachment.html>

More information about the Freedombox-discuss mailing list