[Touch-packages] [Bug 2104316] Re: 25.04 beta TPMFDE: first boot failure

2025-04-07 Thread Utkarsh Gupta
** Changed in: edk2 (Ubuntu) Milestone: None => ubuntu-25.04 ** Changed in: ubuntu Milestone: ubuntu-25.04 => None ** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https

[Touch-packages] [Bug 2104316] Re: 25.04 beta TPMFDE: first boot failure

2025-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package edk2 - 2025.02-3ubuntu2 --- edk2 (2025.02-3ubuntu2) plucky; urgency=medium * Uninstall memory attribute protocol in all images, workaround for (LP: #2104316) -- Mate Kukri Fri, 04 Apr 2025 18:44:53 +0100 ** Changed in: edk2 (Ubuntu) Stat

[Touch-packages] [Bug 2104316] Re: 25.04 beta TPMFDE: first boot failure

2025-04-04 Thread Dan Bungert
I retested based on edk2_2025.02-3ubuntu2.dsc in unapproved, and indeed it installs and boots the TPMFDE vm fine. Thanks for the upload. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpa

[Touch-packages] [Bug 2104316] Re: 25.04 beta TPMFDE: first boot failure

2025-04-04 Thread Mate Kukri
GRUB issue is that peimage tries to write relocations addends to read- only sections after setting them read only But i suspect fixing that will make the GRUB problem be the same as the firmware direct boot problem, so we nicely caught two bugs here. ** Changed in: edk2 (Ubuntu) Status

[Touch-packages] [Bug 2104316] Re: 25.04 beta TPMFDE: first boot failure

2025-04-04 Thread Mate Kukri
> This makes sense because other systems boot after all. Is this "borked hooking" only in newer systemds? (because Noble TPM FDE installs apparently work with plucky ovmf) Hmm I am not sure, I'll look into this in more detail as part of fixing this bug properly after edk2 workaround is done. > Yo

[Touch-packages] [Bug 2104316] Re: 25.04 beta TPMFDE: first boot failure

2025-04-03 Thread Michael Hudson-Doyle
> - UKIs don't work with mem attribute protocol + secure boot enabled, this is likely due to systemd's borked hooking of the SEC ARCH 2 protocol pointer, which i assume is in protected memory... This makes sense because other systems boot after all. Is this "borked hooking" only in newer systemds?

[Touch-packages] [Bug 2104316] Re: 25.04 beta TPMFDE: first boot failure

2025-04-03 Thread Mate Kukri
Two possible causes: - UKIs don't work with mem attribute protocol + secure boot enabled, this is likely due to systemd's borked hooking of the SEC ARCH 2 protocol pointer, which i assume is in protected memory... - grub page faults when running chainloader on kernel.efi , or linux + boot on ker