Control: tag -1 + patch Hi,
On Fri, 31 Mar 2023 13:52:45 +0000 Isaac True <isaac@is.having.coffee> wrote: > As part of our CI/CD system, we are building images for target devices. The > images are set up in virtual machines which boot using EFI, but flash-kernel > installation always fails as it detects that the system is running in EFI by > checking for the existence of /sys/firmware/efi. we have the same problem when building bootable images for the MNT Reform laptop: https://source.mnt.re/reform/reform-system-image/ The CI system is a machine that boots with EFI but the final system uses uboot to boot and not EFI. > Being able to setup the image on these VMs is an important part of our > testing and validation workflow, so it would be very helpful to have an > option to skip this check and proceed regardless of whether the system is > currently running in EFI mode or not. This used to work in the past but was broken by this commit: https://salsa.debian.org/installer-team/flash-kernel/-/commit/8a81a537995a2b98386aea883729ce9960a825bf > I've added a debdiff for a proposal for a new parameter --force-efi which can > be set to skip this check. The problem with implementing this using a command line flag or an environment variable is, that then you will have to run flash-kernel again manually after initially installing it. What do you think about instead using an option in /etc/default/flash-kernel which allows ignoring /sys/firmware/efi if inside a chroot as I implemented here: https://salsa.debian.org/installer-team/flash-kernel/-/merge_requests/33 Thanks! cheers, josch
signature.asc
Description: signature
