[Bug 1811984] Re: flash-kernel 3.90ubuntu3.18.10.1 fails with mkimage: not found if no uboot is used
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 with mkimage: not found if no uboot is used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1811984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811984] Re: flash-kernel 3.90ubuntu3.18.10.1 fails with mkimage: not found if no uboot is used
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 used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1811984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811984] Re: flash-kernel 3.90ubuntu3.18.10.1 fails with mkimage: not found if no uboot is used
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 NOT uninstall u-boot.
edit /boot/firmware/config.txt so that all kernel lines are commented
out and make sure the [all] section has these two lines:
kernel=vmlinuz
initramfs initrd.img followkernel
Then create put the following text in
/etc/kernel/postinst.d/_rpi_kernel:
#!/bin/sh -eu
#
# This uncompresses the arm64 kernel so the rpi bootloader can load it.
#
# First exit if we aren't running an ARM64 kernel.
#
[ $(uname -m) != aarch64 ] && exit 0
#
KERNEL_VERSION="$1"
KERNEL_INSTALLED_PATH="$2"
gunzip -c -f ${KERNEL_INSTALLED_PATH} > ${KERNEL_INSTALLED_PATH}.nogz &&
mv -f ${KERNEL_INSTALLED_PATH}.nogz ${KERNEL_INSTALLED_PATH}
--
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 used
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1811984/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811984] Re: flash-kernel 3.90ubuntu3.18.10.1 fails with mkimage: not found if no uboot is used
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 (a Raspberry Pi with somewhat recent firmware can boot the Linux kernel directly without the need for uboot). In my eyes this is a newly introduced bug. Especially if flash-kernel doesn't run properly with a "recommended" package missing. The image I'm using is the Ubuntu arm64 one - but I got rid of u-boot. -- 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 used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1811984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811984] Re: flash-kernel 3.90ubuntu3.18.10.1 fails with mkimage: not found if no uboot is used
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 3.90ubuntu3.18.10.1 fails with mkimage: not found if no uboot is used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1811984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811984] Re: flash-kernel 3.90ubuntu3.18.10.1 fails with mkimage: not found if no uboot is used
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 (Ubuntu) Status: New => Invalid -- 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 used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1811984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
