[Bug 2028891] Re: HTTP boot grub issue
Loïc Minier
2028891 at bugs.launchpad.net
Fri Nov 22 11:43:17 UTC 2024
We've got a report of a similar issue with NVIDIA IGX systems and we're
investigating. Since the problem is in the GRUB binaries from jammy
series, I'm reassigning that to grub2-unsigned, not sure yet if we're
also going to update grub2-signed but I believe we don't sign
grubnetaa64.bin.
** Also affects: grub2-unsigned (Ubuntu)
Importance: Undecided
Status: New
** Changed in: grub2-unsigned (Ubuntu)
Status: New => Confirmed
** Changed in: grub2-unsigned (Ubuntu)
Importance: Undecided => Medium
** Changed in: grub2-unsigned (Ubuntu)
Assignee: (unassigned) => Sebastian Weyer (sebwey)
** No longer affects: linux-bluefield (Ubuntu)
** Changed in: grub2-unsigned (Ubuntu)
Status: Confirmed => In Progress
** Also affects: grub2-unsigned (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: grub2-unsigned (Ubuntu Jammy)
Status: New => In Progress
** Changed in: grub2-unsigned (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: grub2-unsigned (Ubuntu Jammy)
Assignee: (unassigned) => Sebastian Weyer (sebwey)
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2-unsigned in Ubuntu.
https://bugs.launchpad.net/bugs/2028891
Title:
HTTP boot grub issue
Status in grub2-unsigned package in Ubuntu:
In Progress
Status in grub2-unsigned source package in Jammy:
In Progress
Bug description:
SRU Justification:
[Impact]
We have tested PXE boot successfully on the BlueField using grubaa64.efi and grub.cfg but HTTP boot does not work.
During HTTP boot, UEFI is able to load the grubaa64.efi but doesn’t load grub.cfg and goes instead into the grub rescue shell.
From the grub shell, I try to load the grub.cfg file manually, but I get the error shown below.
grub> set
?=0
cmdpath=(http,192.168.200.1)
color_highlight=black/light-gray
color_normal=light-gray/black
feature_200_final=y
feature_all_video_module=y
feature_chainloader_bpb=y
feature_default_font_path=y
feature_menuentry_id=y
feature_menuentry_options=y
feature_nativedisk_cmd=y
feature_ntldr=y
feature_platform_search_hint=y
feature_timeout_style=y
grub_cpu=arm64
grub_netfs_type=efi
grub_platform=efi
lang=
locale_dir=
net_default_interface=efinet2
net_default_ip=192.168.200.2
net_default_mac=<oob mac>
net_default_server=192.168.200.1
net_efinet2_ip=192.168.200.2
net_efinet2_mac=<oob mac>
package_version=2.06-2ubuntu14.1
pager=
prefix=(http,192.168.200.1)/grub
pxe_default_server=192.168.200.1
root=http,192.168.200.1
secondary_locale_dir=
configfile (http,192.168.200.1)/grub/grub.cfg
this doesn't works: error: Fail to send a request! status=0x8000000000000002.
However it works if I run:
configfile (tftp,192.168.200.1)/grub/grub.cfg
This forum discusses a similar issue which points to a grub issue:
https://groups.google.com/g/linux.debian.bugs.dist/c/CqfwbhAd-Xg
Could you please help investigate this? Or point me to the right
person?
[Fix]
* Unknown yet. Investigate grub.
[Test Case]
* HTTP boot via OOB
* HTTP boot via Connect X
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2028891/+subscriptions
More information about the foundations-bugs
mailing list