For aarch64 liveinstall images we want to replace the kernel-core package
with kernel-uki-dtbloader for:
https://fedoraproject.org/wiki/Changes/Automatic_DTB_selection_for_aarch64_EFI_systems
This is implemented by:
1. Adding a new BootCoreLive profile which is the same as the BootCore
profile and re-uses most of the description. Rreplacing the kernel-core
package with kernel-uki-dtbloader on aarch64.
2. Switch the LiveInstall from the BootCore profile to the BootCoreLive
profile.
Signed-off-by: Hans de Goede <johannes.goede@oss.qualcomm.com>
This ensures that there's empty space for arm-image-installer to
inject firmware blobs into images as part of preparing to install
for various single board computers.
shim-ia32 no longer exists at present. We can talk with pjones
about bringing it back, but for now, this is preventing Rawhide
composes from working.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This became necessary with 10.0.13 / after merging
https://github.com/OSInside/kiwi/pull/2535 but doesn't seem to
noticeable effects besides miisin "GRUB_ENABLE_BLSCFG=true" in
/etc/default/grub.
menu_auto_hide=1 is required for the boot_success provided by Fedora's
grub2 package. This will fall back to the previous kernel and show the
usually hidden grub menu when booting fails.
This makes it unnecessary to override the timeout_style and using a
reduced timeout of 1 second for disk images.
The Raspberry Pi 3 does not recognize a FAT filesystem marked with
the 0xef type, so until we drop support for this device, hack the
partition manually to use a legacy FAT filesystem partition type.
It is hard to ensure that hardware support packages are pulled in
universally when it's splintered across different variant profiles.
To fix this and ensure Server benefits from this, unify everything
into a common profile and make everything require it.
Most of the changes are self-explanatory and just follow what's
already happening for existing architectures.
Two things are worth pointing out:
* we need to use shim-unsigned instead of shim-signed because
riscv64 is not fully integrated into Fedora yet and so we
can't do Secure Boot signing for the time being;
* we use ext4 as bootfilesystem since in most cases the
underlying firmware is going to be U-Boot, which needs to be
able to load the board's DTB from /boot and doesn't support
XFS.
Signed-off-by: David Abdurachmanov <davidlt@rivosinc.com>
Many of the older supported AArch64 systems (particularly single
board computers) require a legacy MBR (Master Boot Record) type
partitioning to successfully boot.
The boot environment for non-cloud disk images was incomplete,
leading to images not bootable on real hardware. This change
adds the missing packages to fix that.
4096 blocksize is required for Macs, and some newer machines can see it,
but many other machines are not able to use the 4096 blocksize.
Signed-off-by: Troy Dawson <tdawson@redhat.com>
Adam Williamson