https://git.launchpad.net/ubuntu/+source/grub2/tag/?h=import/2.12-5ubuntu5.1
It's great! It has completely solved the problems I encountered before!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20783
@resonic thank you for reporting this, I think you have found a real
issue with the new NX enablement stack in Oracular.
I have created
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2084104, as I am
pretty confident in my theory, and I'll also try to verify the above
theory tomorrow.
Thank
Hmm that looks extremely weird. It seems like GRUB is deciding to
enforce NX policy on your machine despite it clearly booting from the
shim that is requesting it not to...
One hunch I have is that maybe shim doesn't export MokPolicy with UEFI
Secure Boot disabled, and we accidentally always enfor
Here you go:
update-alternatives --query shimx64.efi.signed
Also can you check dpkg -l | grep shim?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078307
Title:
Grub 2.12 in Oracular is unable to boot Windows using chainloader
To manage notifications about
It looks like it is not the asus bug, as it is pointing to the correct
shim entry.
It still is an NX bug, but a different one then what I've expected.
It seems like your machine somehow ended up with the NX enforcing shim
instead of the non-NX one it should have received.
To confirm this theory
There is a NX problem indeed. You were right from the start :)
efibootmgr -v output from shell:
BootCurrent:
Timeout: 1 seconds
BootOrder: ,0003
Boot* Ubuntu
HD(1,GPT,64038958-7a20-4179-88a7-e67f851bfaa4,0x800,0x10)/File(\EFI\UBUNTU\SHIMX64.EFI)
dp: 04 01 2a 00 01 0
Hi,
I have done this, see attachments. Its an Asrock board running the X570
chipset. Dont know if they had the same bug in their AGESA implementation as
ASUS did.
Thanks a lot by the way for taking your time. You guys just really rock!
Love your effort and still happy having switched to linux fu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078307
Title:
Grub 2.12 in Oracular is unable to boot Windows using chainloader
To manage notifications about this bug go to:
https://bugs.launchpad.ne
And p.s. /boot/efi/EFI/BOOT/grubx64.efi is likely left over and not
needed if bootx64 and fbx64 are present in that directory and shimx64
and grubx64 are present in EFI\ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
I suspect Windows fails to boot because the NX compatibility check, and
Ubuntu only fails to boot when you've once unsuccessfully tried booting
Windows without restarting GRUB.
Please get the set debug=peimage output from GRUB as explained above.
And also can you get the output of efibootmgr -v f
GRUB console which you can access with c from the grub screen, then go
back the menu with escape
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078307
Title:
Grub 2.12 in Oracular is unable to boot
** Attachment added: "Message when trying to boot Ubuntu:"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2078307/+attachment/5826426/+files/PXL_20241009_143550967.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
The message when trying to boot windows:
** Attachment added: "PXL_20241009_143542790.jpg"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2078307/+attachment/5826425/+files/PXL_20241009_143542790.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
> Please run `set debug=peimage`
Where? Linux shell, UEFI shell?
Hardware:
Ryzen 5950X
X570 board
RTX 3090
64GB
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078307
Title:
Grub 2.12 in Oracular is
Sorry to hear that you are having difficulties with Ubuntu 24.10's
bootloader. Given the testing we are doing, I have strong doubts Ubuntu
24.10 doesn't boot "2 out of 3" on the vast majority of machines, so I
suspect there is something going on with your firmware.
Please run `set debug=peimage` p
Ubuntu 24.10 user here. It is still broken.
2 out of 3 times GRUB wont boot Ubuntu with the message "load kernel
first", Windows 10 never works with the error message: "cannot load
image". Despite being the version 2.12-5ubuntu5, it is still broken for
Ubuntu AND Windows.
--
You received this bu
This bug was fixed in the package cd-boot-images-ppc64el - 20
---
cd-boot-images-ppc64el (20) oracular; urgency=medium
* Rebuild against grub2 2.12-5ubuntu5 (LP: #2078307)
-- Mate Kukri Tue, 24 Sep 2024 15:25:15
+0100
** Changed in: cd-boot-images-ppc64el (Ubuntu)
Status
This bug was fixed in the package cd-boot-images-riscv64 - 15
---
cd-boot-images-riscv64 (15) oracular; urgency=medium
* Rebuild against grub2 2.12-5ubuntu5 (LP: #2078307)
-- Mate Kukri Tue, 24 Sep 2024 15:24:18
+0100
--
You received this bug notification because you are a mem
This bug was fixed in the package cd-boot-images-arm64 - 26
---
cd-boot-images-arm64 (26) oracular; urgency=medium
* Rebuild against grub-efi-arm64-signed 1.209+2.12-5ubuntu5 (LP:
#2078307)
-- Mate Kukri Tue, 24 Sep 2024 15:21:29
+0100
** Changed in: cd-boot-images-riscv64 (Ubu
This bug was fixed in the package cd-boot-images-amd64 - 30
---
cd-boot-images-amd64 (30) oracular; urgency=medium
* Rebuild against grub-efi-amd64-signed 1.209+2.12-5ubuntu5 (LP:
#2078307)
-- Mate Kukri Tue, 24 Sep 2024 15:17:53
+0100
** Changed in: cd-boot-images-amd64 (Ubunt
** Changed in: cd-boot-images-amd64 (Ubuntu)
Importance: Undecided => High
** Changed in: cd-boot-images-arm64 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
** Changed in: cd-boot-images-amd64 (Ubuntu)
Assignee: (unassigned) => Ubuntu Sponsors (ubuntu-sponsors)
** Changed in: cd-boot-images-arm64 (Ubuntu)
Assignee: (unassigned) => Ubuntu Sponsors (ubuntu-sponsors)
** Changed in: cd-boot-images-ppc64el (Ubuntu)
Assignee: (unassigned) =>
This bug was fixed in the package grub2 - 2.12-5ubuntu5
---
grub2 (2.12-5ubuntu5) oracular; urgency=medium
* peimage: Fixup grub_error -> grub_dprintf
* peimage: Fixup section consistency checks (LP: #2078307)
-- Mate Kukri Fri, 30 Aug 2024 16:11:07
+0100
** Changed in: grub2
** Changed in: cd-boot-images-amd64 (Ubuntu)
Milestone: None => ubuntu-24.10
** Changed in: cd-boot-images-arm64 (Ubuntu)
Milestone: None => ubuntu-24.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
cd-boot-images-* MPs:
https://code.launchpad.net/~mkukri/ubuntu/+source/cd-boot-images-amd64/+git/cd-boot-images-amd64/+merge/473737
https://code.launchpad.net/~mkukri/ubuntu/+source/cd-boot-images-arm64/+git/cd-boot-images-arm64/+merge/473738
https://code.launchpad.net/~mkukri/ubuntu/+source/cd-b
OK, approving this from the queue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078307
Title:
Grub 2.12 in Oracular is unable to boot Windows using chainloader
To manage notifications about this
** Also affects: cd-boot-images-amd64 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cd-boot-images-arm64 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cd-boot-images-riscv64 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cd-b
** Changed in: grub2 (Ubuntu)
Milestone: ubuntu-24.10-beta => ubuntu-24.10
** Changed in: grub2 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078307
Tit
Subscribing ubuntu-release as this likely won't make 24.10 beta and will
need a release note.
The grub is signed now and should be ready for oracular release however.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
ok
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078307
Title:
Grub 2.12 in Oracular is unable to boot Windows using chainloader
To manage notifications about this bug go to:
https://bugs.launchpa
That is not an Ubuntu problem, we only care about applying the whole
patchstack. Those two patches will be squashed down and will go away on
the next Debian merge anyway.
Also please bare in mind that if you only partially use our sources, and
don't use our build system, please do not claim during
I suggest moving the patches "peimage-fixup-section-consistency-
checks.patch" and "peimage-fixup-grub_error-grub_dprintf.patch" to the
nx directory, as these two newly added patches are fixes for peimage.
Not moving them to the nx directory will cause errors when loading the
"peimage-fixup-sectio
Thank you for your patient answers. I don't think I have any more
questions. Thanks again!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078307
Title:
Grub 2.12 in Oracular is unable to boot Window
> Do you mean that if the shim does not enforce the NX flag, then Ubuntu
GRUB2 will not check the NX flag of Windows?
That is exactly correct you just need a shim that doesn't set NX flag
and doesn't enforce it.
> Or, when applying the Ubuntu patches to GRUB2, is it possible to avoid
using the pa
I remember that Shim 15.8 has the NX flag enabled by default. Does that
mean Ubuntu's Shim 15.8 does not have the NX flag enabled by default?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078307
Titl
I think the GRUB2 code should temporarily avoid checking the NX flag;
otherwise, users in situations like mine will be unable to boot into
Windows.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078307
Do you mean that if the shim does not enforce the NX flag, then Ubuntu
GRUB2 will not check the NX flag of Windows? Unless the shim enforces
the NX flag, GRUB2 will only check the Windows NX flag if the shim
enables the NX flag?
Or, when applying the Ubuntu patches to GRUB2, is it possible to avoi
I suspect that the inability to boot with mixed-mode UEFI might also be
related to NX settings.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078307
Title:
Grub 2.12 in Oracular is unable to boot W
No, but if your shim does not enforce NX, like the Ubuntu shim, that is
fine.
The need to use a non-NX shim will remain to be the case until Windows
bootloader sets NX_COMPAT.
You need to boot Ubuntu shim (or another non-NX shim) -> Ubuntu GRUB ->
Windows and that will work. No other path will, b
You previously mentioned that you tested booting the Windows system
using Grub2. Did your Windows system boot file enable the NX flag?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078307
Title:
Gr
The default Windows system boot file does not enable the NX (No Execute)
flag, and the latest Windows 11 has not enabled the NX flag either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078307
Title
You need to use a non-NX shim if you are chainloading a version of
Windows that doesn't have the NX_COMPAT flag set.
This is not a bug anymore but expected results I think. Try using the
current non-NX Ubuntu shim to load your grub in the first place.
--
You received this bug notification becaus
/efi/Microsoft/Boot/bootmgfwceshi.efi was copied from
/efi/Microsoft/Boot/bootmgfw.efi.
I replaced /efi/Microsoft/Boot/bootmgfw.efi with the shimx64.efi file.
The attached file contains the debug information.
** Attachment added: "20240911.jpg"
https://bugs.launchpad.net/ubuntu/+source/grub2/
As I said I've prepared a fix and it's waiting for upload to Oracular.
In the meantime I've done some test builds here:
- https://launchpad.net/~ubuntu-uefi-team/+archive/ubuntu/build/+build/28929792
- https://launchpad.net/~ubuntu-uefi-team/+archive/ubuntu/build/+build/28929800
After these are b
After testing Debian's GRUB 2: https://salsa.debian.org/grub-
team/grub/-/tree/debian/2.12-5?ref_type=tags, it also supports hybrid
boot modes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078307
Ti
I know that Ubuntu was developed from Debian, so I just tried testing Debian's
Grub 2.12 code. With Grub 2 compiled from Debian's code, using chainloader to
boot Windows worked successfully.
https://salsa.debian.org/grub-team/grub/-/tree/debian/2.12-5?ref_type=tags
Therefore, I still suspect that
I have tested again on my end, and it is clear that the issue persists.
Could you let me know when the grub2 with the debian/2.12-5ubuntu5 patch
will be applied to the ISO available at
https://cdimages.ubuntu.com/ubuntu/daily-live/current/?
--
You received this bug notification because you are a
I have tested Windows 11 22H2 and the 23H2 ISO, and Windows 10 LTSC 2021
and all those work fine. Please make sure you use the correct branch
and/or version tag and ensure the binary you built is really from it, as
I think the code I've pushed to ~ubuntu-uefi-team should be functional.
--
You rec
** Changed in: grub2 (Ubuntu)
Milestone: None => ubuntu-24.10-beta
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078307
Title:
Grub 2.12 in Oracular is unable to boot Windows using chainloader
Hello, I have provided the information you requested. Have you received
it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078307
Title:
Grub 2.12 in Oracular is unable to boot Windows using chainlo
grub.cfg
{
set timeout=30
loadfont unicode
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
menuentry "Try or Install Ubuntu" {
set gfxpayload=keep
linux /casper/vmlinuz --- quiet splash
initrd /casper/initrd
}
menuentry "Ubuntu (safe graphi
I compiled a 64-bit version of GRUB2, so I’m certain about that, and I’m
also sure it’s a 64-bit Windows system. I’ve attached the build code.
** Attachment added: "mk-Grub2.12.sh"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2078307/+attachment/5812118/+files/mk-Grub2.12.sh
--
You r
Are you using a 64-bit build of that code? Are you using 64-bit Windows?
How did you build and install it?
I am pretty sure it boots Windows 10 bootmgfw.efi, because I tested it
myself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am absolutely certain that it is the code fetched from the URL you
provided.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078307
Title:
Grub 2.12 in Oracular is unable to boot Windows using chai
You need to pull the code from https://code.launchpad.net/~ubuntu-uefi-
team/grub/+git/ubuntu/+ref/ubuntu?, and the version you want is
2.12-5ubuntu5...
That will boot Windows 10 and 11 just fine. Test that
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
I just tested the Windows 11 24H2 version again, and it still shows the
error in the image 20240901.png.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078307
Title:
Grub 2.12 in Oracular is unable
After testing, it still doesn't work. I can confirm that the latest patches
have been included.
Windows version: Windows 10 1809
The attachment contains screenshots.
** Attachment added: "20240901.png"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2078307/+attachment/5811833/+files/202
Thank you for your quick reply. What is the difference between
https://git.launchpad.net/ubuntu/+source/grub2 and
https://code.launchpad.net/~ubuntu-uefi-
team/grub/+git/ubuntu/+ref/ubuntu?
I have been pulling code from
https://git.launchpad.net/ubuntu/+source/grub2. When will the latest
patches b
You are using the wrong source for our GRUB, that's up there is a sync
of versions uploaded to the Ubuntu archive.
The primary development repository currently is at
https://code.launchpad.net/~ubuntu-uefi-team/grub/+git/ubuntu (the
"ubuntu" branch is what you want)
--
You received this bug noti
When will the patch for Windows chainloading be synced to
https://git.launchpad.net/ubuntu/+source/grub2? I'd like to test it as
well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078307
Title:
Gr
The patch for Windows chainloading is prepared and will be uploaded for
oracular beta, as this is a supported feature for Ubuntu installs and
unfortunately got broken by accident.
And yes the 32-bit EFI GRUB was clearly considered and discarded, no one
has cared about it for years. Most old device
I would like to make a suggestion regarding the "mixed mode" UEFI.
Although Ubuntu no longer provides 32-bit Ubuntu ISOs, there are still
some devices on the market with 32-bit UEFI BIOS, but the CPU supports
64-bit mode. In this case, Ubuntu only needs to provide a 32-bit GRUB2
to successfully boo
The modified code can be seen at
https://git.launchpad.net/ubuntu/+source/grub2, right? So I can continue
testing it later.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078307
Title:
Grub 2.12 in
I hope this error can be fixed, otherwise it will affect the ability to
boot the Windows system through GRUB2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078307
Title:
Grub 2.12 in Oracular is u
So it is hitting this check in peimage
if (section->raw_data_size > section->virtual_size)
{
grub_dprintf ("peimage", "section data larger than virtual
size\n");
return GRUB_EFI_LOAD_ERROR;
}
Turns out the PE spec actually allows for
The issue in Oracular's GRUB is not in shim, the peimage module got
broken either during the NX work, or a mismerge of the latest Debian
GRUB.
That warning is not optimal, but there is a regression here vs Noble.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
https://launchpadlibrarian.net/746565039/1.png
The issue is likely within the shim code, and it would be best to
resolve it as well. I discovered this problem a long time ago.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
68 matches
Mail list logo
