This bug was fixed in the package linux-raspi - 6.11.0-1012.12
---------------
linux-raspi (6.11.0-1012.12) oracular; urgency=medium
* oracular/linux-raspi: 6.11.0-1012.12 -proposed tracker (LP:
#2107088)
* CONFIG_EFI_STUB support disabled since 6.5.0-1002.2 (LP: #2053147)
- [Config] raspi: Set EFI=y
[ Ubuntu: 6.11.0-25.25 ]
* oracular/linux: 6.11.0-25.25 -proposed tracker (LP: #2107099)
* Packaging resync (LP: #1786013)
- [Packaging] update annotations scripts
* log_check/kernel_tainted failed with kernel warnings at
kernel/time/timer_migration.c:543 on Oracular (LP: #2106022)
- timers/migration: Fix off-by-one root mis-connection
-- Hui Wang <[email protected]> Wed, 16 Apr 2025 21:20:02 +0800
** Changed in: linux-raspi (Ubuntu Oracular)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/2053147
Title:
CONFIG_EFI_STUB support disabled since 6.5.0-1002.2
Status in linux-raspi package in Ubuntu:
Fix Released
Status in linux-raspi source package in Noble:
Fix Committed
Status in linux-raspi source package in Oracular:
Fix Released
Status in linux-raspi source package in Plucky:
Fix Released
Bug description:
[Impact]
Looks like since commmit 0d02ca7853f4e487ff8b912b0d1d43ceb31a528b
(https://git.launchpad.net/ubuntu/+source/linux-
raspi/commit/?h=applied/ubuntu/devel&id=0d02ca7853f4e487ff8b912b0d1d43ceb31a528b)
The support for EFI in the kernel config was disabled with no mention
of why:
"""
- [Config] raspi: Set EFI=n
"""
This disables support for CONFIG_EFI_STUB which means that the kernel
cannot be loaded via EFI directly.
Any reasons for this? We are booting RPI by setting u-boot to launch
in EFI mode, which runs grub.efi and then we load our entries from
there, but this totally breaks support for that.
This worked until the previous kernel version with no issues that we
could find. Is there anything we can do to revert this and re-enable
this option int he kernel?
[Fix]
Re-enable CONFIG_EFI.
[Test Case]
Check that EFI configs are enabled:
$ modprobe configs
$ zgrep ^CONFIG_EFI /proc/configs.gz
CONFIG_EFI_STUB=y
CONFIG_EFI=y
CONFIG_EFI_PARTITION=y
CONFIG_EFI_ESRT=y
CONFIG_EFI_VARS_PSTORE=m
CONFIG_EFI_PARAMS_FROM_FDT=y
CONFIG_EFI_RUNTIME_WRAPPERS=y
CONFIG_EFI_GENERIC_STUB=y
CONFIG_EFI_BOOTLOADER_CONTROL=m
CONFIG_EFI_CAPSULE_LOADER=m
CONFIG_EFI_TEST=m
CONFIG_EFI_EARLYCON=y
CONFIG_EFIVAR_FS=m
[Where Problems Could Occur]
Boot issues with the official non-EFI Raspberry Pi
firmware/bootloader. Additional interference due to new and/or changed
config options.
[Notes]
Booting via EFI is not officially supported by Canonical. We're re-
enabling this option as a courtesy to our users. We will turn it back
off if it introduces problems.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2053147/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
