Hi Sergio, Have you got time to look at the problem?
Further more, the ubuntu-core-generic-initrd can't detect U-Boot on x86 thus doesn't generate the correct fstab entry accordingly. I can workaround the two issues with manually partitioning the SD image and patch scripts/ubuntu-core-rootfs in my kernel snap. It would be great however if Ubuntu core supports it officially. Cheers, Jian On Mar 22, 2016 12:08, "Jian LUO" <jian.luo...@gmail.com> wrote: > Sorry, forgot to cc the list. > On Mar 22, 2016 12:00 PM, "Jian LUO" <jian.luo...@gmail.com> wrote: > >> Yes, of cause. paste.ubuntu.com/15471214 >> >> Jian >> On Mar 22, 2016 10:59 AM, "Sergio Schvezov" < >> sergio.schve...@canonical.com> wrote: >> >> >> >> El 22/03/16 a las 05:50, Jian LUO escribió: >> > Hi, >> > >> > I'm trying to port Ubuntu Core to a custom x86 board with U-Boot as >> > bootloader. So far with manuel partitioning everything works. However >> > when i tried with ubuntu-device-flash to create a flash image, it >> > stopped with error message: >> > >> > <snip> >> > Unmounting... >> > boot/ubuntu bind mount failed with: exit status 32 mount: mount point >> > /tmp/ diskimage295316242/system/boot/uboot does not exist >> > >> > Either ubuntu-device-flash should create this folder when absent, or it >> > should be included in the os snap. What's do your think? >> >> IIRC, it only creates it if your gadget snap says the bootloader is >> u-boot. Can you confirm that or maybe just pastebin you gadget snap's >> meta/snap.yaml. >> >> Cheers >> Sergio >> >> >> -- >> snappy-devel mailing list >> snappy-devel@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/snappy-devel >> >>
-- snappy-devel mailing list snappy-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snappy-devel
