GNU GRUB - Bugs: bug #62920, Memory address error when booting...
You are not allowed to post comments on this tracker with your current authentication level.
bug #62920: Memory address error when booting from LUKS-encrypted /boot
Submitter: | - <_326750> | ||
Submitted: | Fri 19 Aug 2022 03:08:33 PM UTC | ||
Category: | Booting | Severity: | Major |
Priority: | 5 - Normal | Item Group: | Software Error |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | Jason Yip |
Open/Closed: | Open | Release: | Git master |
Release: | Reproducibility: | Every Time | |
Planned Release: | None |
Wed 31 Aug 2022 02:00:42 PM UTC, comment #3: |
Linux Ninja <linuxninja> |
Sat 27 Aug 2022 01:00:13 PM UTC, comment #2: My setup is VERY similar to ljyip
|
Linux Ninja <linuxninja> |
Thu 25 Aug 2022 03:08:50 PM UTC, comment #1: I'm new here and I have created an account just for this issue.
|
zonep |
Fri 19 Aug 2022 03:08:33 PM UTC, original submission:
I have a LUKS2-encrypted /boot using PBKDF2. Commit g2f4430cc0 has always worked for me. However, commit g0c6c1aff2 would do the following: boot into linux-zen then return an error about access memory address.
|
- <_326750> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Powered by Savane 3.13-d3ae.
Corresponding source code
I was able to resolve my issue.
It is not enough to run grub-mkimage to replace the file in the EFI System Partition after upgrading the Grub package.
grub-install also needed to be run to replace the files in /boot/grub, THEN also use grub-mkimage to replace the file in the EFI System Partition.
Here are my steps (as the root user):