Bug#783990: efivarfs is a separate fs and needs moutning

Ian Jackson ijackson at chiark.greenend.org.uk
Fri Jul 16 12:35:56 BST 2021

Control: tags -1 - moreinfo
Control: tags -1 + confirmed patch
Control: found -1 2.93-8
Control: found -1 2.96-7

I just encountered the lack of evivars when using fwupd to update my
laptop firmware from lvfs.

My workaround was to put this in /etc/fstab
 efivarfs        /sys/firmware/efi/efivars       efivarfs   defaults

but the suggestion by Greg Pearson is correct and IMO should be
applied to mountkernfs.  (I felt that Greg's descriptiohn was
sufficientlty clear to be worth calling a "patch".)

Dmitry wrote:

> Hi. As I see on my system, /sys/firmware/efi is now part of /sys:
>  $ ls /sys/firmware/efi/
>  config_table
>  $ mount | grep efi
>  /dev/sda1 on /boot/efi type vfat (

But, the relevant directory is /sys/firmware/efi/efivars. not
/sys/firmware/efi.  The fact that efivars exists in /sys/firmware/efi
doesn't tell us that the contents is available.

Empirically on this buster system, I needed to manually arrange for
the mounting of /sys/firmware/efi/efivars to get fwupd to work.

Steve McIntyre confirmed to me on irc that this is a separate
filesystem on bullseye too.  I looked at the source for sid's sysvinit
and its mountkernfs still lacks this.

I think it would be worth considering this fix for a stable update,
after bullseye is released.


Ian Jackson <ijackson at chiark.greenend.org.uk>   These opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

More information about the Debian-init-diversity mailing list