ubuntu-device-flash creates an rpi2 image that won't boot

[Rick Spencer]

I did this:

$ sudo ubuntu-device-flash core 15.04 --channel edge --developer-mode --enable-ssh --install webdm -o myimage.img --oem pi2.canonical

$ ls
myimage.img

$ sudo umount /media/your-user-name/*
$ sudo dd if=./myimage.img of=/dev/sdb bs=32M
$ sync

When I plug the sd card into my laptop, it has the four expected partitions. However, when I try to boot my rpi2 with it, the green light flashes briefly, then it appears there is no activity.

[Oliver Grawert (ogra)]

i'm not really sure how that built at all ... since there is no device tarball anywhere for this image (ubuntu-device-flash should have failed) ... as you can see in the RPi2 section on https://developer.ubuntu.com/en/snappy/start/ you need the "device-pi2-*.tar.xz: device tarball" from http://people.canonical.com/~platform/snappy/raspberrypi2/ to get the RPi2 kernel into the image, i assume your image has the -generic kernel from the archive now.

[Oliver Grawert (ogra)]

after talking to sergio it turns out that there is currently no way to bind the pi2 snap to a certain device tarball, especially when --developer-mode is set.
this will change once the device tarballs become snaps themselves and will carry a package name for the respective device (kernel) snap in package.yaml

[Oliver Grawert (ogra)]

we have actual raspi2 device tarballs on the system-image server now (requires to use the --device raspi2_armhf option in ubuntu-device-flash). following the instructions at https://developer.ubuntu.com/en/snappy/start/ should now always produce a proper image.