On 13/07/2023 at 08:54, Arnaud Rebillout wrote:
Following up with that, it seems that the failure is due to a change in
the kernel.
I'm testing 2 Kali netinst ISOs, one from last week (no problem), and a
daily iso from today (which fails).
Last weekly iso had kernel 6.1.0-kali9-amd64. In this iso, `cat
/proc/filesystems | grep efi` gives nothing, hence the grub-installer
postinst doesn't try to mount the efivarfs.
Today's iso has kernel 6.3.0-kali1-amd64. In this iso, `cat
/proc/filesystems | grep efi` gives `nodev efivarfs`, hence the
grub-installer postinst tries to mount efivarfs, and fails.
FTR, this is due to the following change in linux 6.3:
commit 301de9a2055357375a4e1053d9df0f8f3467ff00
Author: Johan Hovold <johan+lin...@kernel.org>
Date: Thu Jan 19 17:42:53 2023 +0100
efivarfs: always register filesystem
The efivar ops are typically registered at subsys init time so that
they are available when efivarfs is registered at module init time.
Other efivars implementations, such as Google SMI, exist and can
currently be built as modules which means that efivar may not be
available when efivarfs is initialised.
Move the efivar availability check from module init to when the
filesystem is mounted to allow late registration of efivars.
