tim.gardner at canonical.com
Sun Nov 22 23:18:58 UTC 2015
Your flash-kernel fu is spot on. I had actually been attempting to use
FLASH_KERNEL_SKIP=1, but wasn't smart enough to get it right. Paolo
pointed out how to correct my errors.
On 11/19/2015 02:23 AM, Alexander Sack wrote:
> my flash-kernel fu is a bit rusty, but iirc setting env
> FLASH_KERNEL_SKIP=1 might be what you want...
> Otherwise, ogra and lool would know most tricks and details on this topic :)...
> - Alexander
> On Thu, Nov 19, 2015 at 1:43 AM, Tim Gardner <tim.gardner at canonical.com> wrote:
>> I've got branches for amd64/i386 that seem to be working OK, though I've not
>> been able to test them yet. I'm waiting on code to land for Snappy 2.0 (I
>> I've been running into issues generating an initrd for armhf (which will
>> eventually be tailored for Beagle Bone Black). The flash-kernel hooks
>> complain there is no root device, a condition that I've had no luck solving.
>> In the bbb-from-deb-16.04 branch of the repo you can see that I've hacked
>> out some flash-kernel hooks that allow update-initramfs to succeed. See
>> rootstock:build_chroot(). Surely there is a more elegant way to do this ?
>> sudo rm $CHROOT/usr/sbin/flash-kernel
>> sudo rm
>> sudo rm $CHROOT/etc/initramfs/post-update.d/flash-kernel
>> I feel like I'm using a sledge hammer where a lighter touch might be just as
>> Tim Gardner tim.gardner at canonical.com
>> snappy-devel mailing list
>> snappy-devel at lists.ubuntu.com
>> Modify settings or unsubscribe at:
Tim Gardner tim.gardner at canonical.com
More information about the snappy-devel