Hi Julian,
I have tested grub 2.06-2ubuntu3 in both BIOS and EFI mode on VMs, and I
can confirm that your patches have fixed both of the issues I was
seeing.
Thanks for the quick turnaround! I will keep testing these packages, but
it all seems good under secureboot.
Thanks,
Matthew
--
You
Marking as fix released then, as this was only a problem in proposed
** Changed in: grub2-signed (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
grub-efi-am64-signed/bin 2.06-2ubuntu3 update works as expected .. thank
you for fixing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954566
Title:
jammy-proposed grub-efi-amd64-signed 1.175+2.06
One of the debug calls accidentally resets grub_errno I guess. I have
not investigated much where that happens.
** Changed in: grub2-signed (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I had same EFI error: out of memory error: you need to load the kernel
first.
as I am using a "real pc" not a VM
my question now is why would "set debug=all" fix this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
note: booting windows partition is not affected .. only linux partitions
fail to boot when debug is off .. i.e. normal state ..
if another grub menu item is selected to boot linux w/o debug turned on
it fails as described earlier .. lack of kernel memory etc.
--
You received this bug
I found the cause for "Out of Memory" that Matthew reported, but not
sure this is the same issue you are seeing, it seems you did not include
the error, but both disappear with debugging enabled in a lot of
scenarios.
We had code to allocate the kernel at a preferred address and if it
failed,
ok tried that .. to reduce the data spew I added: set pager=1 and set
debug=all lines to the first grub menu selection .. this turns debugging on
only if this menu is selected .. and although we got lots of output .. boot was
normal ..
if these lines were removed boot failed again .. this
Thanks for your bug report. To further evaluate this, we will need a
complete dump of the grub log with set debug=all. Unfortunately, I
cannot offer any advise on how to capture this, maybe recording the
screen with a camera works?
** Tags added: regression-proposed
** Changed in: grub2-signed
Hi Julian, Derk,
I have been testing grub2-2.06-2ubuntu2 in -proposed in KVM, on both
BIOS and EFI VMs, and both appear to be broken.
On BIOS, grub2 doesn't get installed automatically, so I have to
manually run "grub-install /dev/vda". When I do, I reboot into grub
2.06, and upon selecting a
10 matches
Mail list logo
