Hi Pascal, Am 5. Januar 2025 14:40:32 MEZ schrieb Pascal Hambourg <pas...@plouf.fr.eu.org>: >Hi, > >On Sat, 13 Jul 2019 09:24:06 +0200 Cyril Brulebois <k...@debian.org> wrote: >> Control: tag -1 patch >> >> Cyril Brulebois <k...@debian.org> (2019-07-12): >> > 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.
Could you turn this into a merge request, please? Thanks Holger -- Sent from /e/ OS on Fairphone3
