From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] efivarfs vs sysfs-efivars
Date: Sun, 21 Nov 2021 16:00:32 +0100 [thread overview]
Message-ID: <20211121150032.LtKisg8iFRMyfelqtjkgyA1IHUD0L2z8ByH_LWk6ANA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34117@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
Closed issue by dkwo on void-packages repository
https://github.com/void-linux/void-packages/issues/34117
Description:
I was trying to understand better how efi variables works.
I realised our kernel has both the old and new version, which leads to displaying two sets of efi variables:
```
$ ls /sys/firmware/efi/vars/
Display all 141 possibilities? (y or n)
$ ls /sys/firmware/efi/efivars/
Display all 139 possibilities? (y or n)
```
This is due to having both options:
```
CONFIG_EFI_VARS=y
CONFIG_EFIVAR_FS=y
```
According to Arch wiki, the first one should be avoided.
> UEFI Runtime Variables Support (old efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled to prevent any potential issues with both efivarfs and sysfs-efivars enabled.
Can anyone clarify what the correct thing to do is here, and whether we should set `CONFIG_EFI_VARS=n`?
Thanks.
prev parent reply other threads:[~2021-11-21 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 17:53 [ISSUE] " dkwo
2021-11-18 10:45 ` dkwo
2021-11-19 12:48 ` dkwo
2021-11-19 13:46 ` leahneukirchen
2021-11-21 15:00 ` leahneukirchen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211121150032.LtKisg8iFRMyfelqtjkgyA1IHUD0L2z8ByH_LWk6ANA@z \
--to=leahneukirchen@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).