Here's a script to set that up:
https://gist.github.com/satmandu/4266de009e54146ef55833e7cae8de25
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811984
Title:
flash-kernel 3.90ubuntu3.18.10.1 fails
Whoops! Need an "exit 0" at the end of that last file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811984
Title:
flash-kernel 3.90ubuntu3.18.10.1 fails with mkimage: not found if no
uboot is
If this is still relevant, the easiest workaround for using the
raspberry pi bootloader directly and bypassing u-boot is to do the
following. (This is actually useful if you use a custom kernel, since
the needed dtb file for u-boot may not be the one you want to use for
your custom kernel.)
Do
The thing is: In the previous version, flash-kernel ignored if mkimage
was missing and just continued normally without throwing any error or
even showing any warning. Which is the behaviour I'd prefer.
The new version aborts and throws an error although there's no need to
run mkimage on my system
NB: If you're using an official image and it's missing mkimage, could
you point at the specific image you used? :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811984
Title:
flash-kernel
This is by design, flash-kernel has different dependencies depending on
the target hardware; the piece of software making the system bootable
(e.g. the flash-kernel udeb in d-i/ubiquity) will install flash-kernel
and the hardware-specific deps (such as u-boot-tools).
** Changed in: flash-kernel
