Bug#931917: grub-installer: call efibootmgr (if available) to keep track of boot order/options

[Cyril Brulebois]

Package: grub-installer
Version: 1.165
Severity: important

With stretch, we were getting efibootmgr's output in the installer's
syslog, which could help track down issues related to the boot sequence.

With buster, due to grub2's switch to using libefi* (since both the
2.02+dfsg1-14 and 2.02+dfsg1-15 uploads), efibootmgr is no longer used;
it's kept in Recommends (since 2.02+dfsg1-17) though.

It would be great to check whether efibootmgr is present and to call it
to get its output back into the installer's syslog.

This would have been helpful for the #931910 installation report, for
example.


Once it's implemented and tested in unstable/testing, I'll consider
backporting this for a buster point release.


Cheers,

[Cyril Brulebois]

Control: tag -1 patch

Post by Cyril Brulebois
With stretch, we were getting efibootmgr's output in the installer's
syslog, which could help track down issues related to the boot sequence.
With buster, due to grub2's switch to using libefi* (since both the
2.02+dfsg1-14 and 2.02+dfsg1-15 uploads), efibootmgr is no longer used;
it's kept in Recommends (since 2.02+dfsg1-17) though.
It would be great to check whether efibootmgr is present and to call it
to get its output back into the installer's syslog.
This would have been helpful for the #931910 installation report, for
example.
Once it's implemented and tested in unstable/testing, I'll consider
backporting this for a buster point release.

Untested commit pushed in the pu/efibootmgr-for-debugging-931917 branch.

Review/tests welcome!


Cheers,

[Pascal Hambourg]

Hi,

Post by Cyril Brulebois
Control: tag -1 patch

Post by Cyril Brulebois
With stretch, we were getting efibootmgr's output in the installer's
syslog, which could help track down issues related to the boot sequence.
With buster, due to grub2's switch to using libefi* (since both the
2.02+dfsg1-14 and 2.02+dfsg1-15 uploads), efibootmgr is no longer used;
it's kept in Recommends (since 2.02+dfsg1-17) though.
It would be great to check whether efibootmgr is present and to call it
to get its output back into the installer's syslog.
This would have been helpful for the #931910 installation report, for
example.
Once it's implemented and tested in unstable/testing, I'll consider
backporting this for a buster point release.

Untested commit pushed in the pu/efibootmgr-for-debugging-931917 branch.
Review/tests welcome!

I found this bug report and thought it was a good idea so I rebased your
commit on current master and tested it on amd64/efi with and without
efivars and on amd64/generic -> ok.

[Holger Wansing]

Hi Pascal,

Hi,

Post by Cyril Brulebois
Control: tag -1 patch

Post by Cyril Brulebois
With stretch, we were getting efibootmgr's output in the installer's
syslog, which could help track down issues related to the boot sequence.

Post by Cyril Brulebois
With buster, due to grub2's switch to using libefi* (since both the

2.02+dfsg1-14 and 2.02+dfsg1-15 uploads), efibootmgr is no longer used;
it's kept in Recommends (since 2.02+dfsg1-17) though.

Post by Cyril Brulebois
It would be great to check whether efibootmgr is present and to call it

to get its output back into the installer's syslog.

Post by Cyril Brulebois
This would have been helpful for the #931910 installation report, for

example.

Post by Cyril Brulebois

Post by Cyril Brulebois
Once it's implemented and tested in unstable/testing, I'll consider

backporting this for a buster point release.

Untested commit pushed in the pu/efibootmgr-for-debugging-931917 branch.
Review/tests welcome!

I found this bug report and thought it was a good idea so I rebased your commit on current master and tested it on amd64/efi with and without efivars and on amd64/generic -> ok.

Could you turn this into a merge request, please?
Thanks


Holger

[Pascal Hambourg]

Post by Holger Wansing

I found this bug report and thought it was a good idea so I rebased your commit on current master and tested it on amd64/efi with and without efivars and on amd64/generic -> ok.

Could you turn this into a merge request, please?

<https://salsa.debian.org/installer-team/grub-installer/-/merge_requests/25>

[Debian Bug Tracking System]

Post by Cyril Brulebois
tag -1 patch

Bug #931917 [grub-installer] grub-installer: call efibootmgr (if available) to keep track of boot order/options
Added tag(s) patch.

[Debian Bug Tracking System]

tag -1 pending

Bug #931917 [grub-installer] grub-installer: call efibootmgr (if available) to keep track of boot order/options
Ignoring request to alter tags of bug #931917 to the same tags previously set

[Debian Bug Tracking System]

tag -1 pending

Bug #931917 [grub-installer] grub-installer: call efibootmgr (if available) to keep track of boot order/options
Added tag(s) pending.

[Debian Bug Tracking System]

Your message dated Fri, 10 Jan 2025 09:49:22 +0000
with message-id <E1tWBdq-00GLh9-***@fasolo.debian.org>
and subject line Bug#931917: fixed in grub-installer 1.206
has caused the Debian Bug report #931917,
regarding grub-installer: call efibootmgr (if available) to keep track of boot order/options
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)