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.

So, copy correct boot partition data from an old image to a new image's
boot partition and you'll have a hacky workaround.  I assume we missed
something that changed in vmdebootstrap.

Nick

Attachment: pgpje0PC85Lbs.pgp
Description: PGP signature

_______________________________________________
Freedombox-discuss mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

Reply via email to