* [bug#40662] [PATCH 0/2] Add efivarfs support.
@ 2020-04-16 15:04 Mathieu Othacehe
2020-04-30 12:46 ` pelzflorian (Florian Pelz)
2020-04-30 16:06 ` pelzflorian (Florian Pelz)
0 siblings, 2 replies; 7+ messages in thread
From: Mathieu Othacehe @ 2020-04-16 15:04 UTC (permalink / raw)
To: 40662; +Cc: Mathieu Othacehe
Hello,
Here's a small serie to add support for efivarfs and fix the issue reported
here: https://lists.gnu.org/archive/html/bug-guix/2020-04/msg00274.html.
The first patch is a bit hacky, so I didn't bother to write the documentation,
in case we find another solution.
Thanks,
Mathieu
Mathieu Othacehe (2):
file-system: Add mount-may-fail? option.
file-system: Add efivarfs support.
gnu/build/file-systems.scm | 49 +++++++++++++++++++++----------------
gnu/system/file-systems.scm | 23 ++++++++++++++---
gnu/system/install.scm | 1 +
3 files changed, 49 insertions(+), 24 deletions(-)
--
2.26.0
^ permalink raw reply [flat|nested] 7+ messages in thread
* [bug#40662] [PATCH 0/2] Add efivarfs support.
2020-04-16 15:04 [bug#40662] [PATCH 0/2] Add efivarfs support Mathieu Othacehe
@ 2020-04-30 12:46 ` pelzflorian (Florian Pelz)
2020-04-30 15:41 ` pelzflorian (Florian Pelz)
2020-04-30 16:06 ` pelzflorian (Florian Pelz)
1 sibling, 1 reply; 7+ messages in thread
From: pelzflorian (Florian Pelz) @ 2020-04-30 12:46 UTC (permalink / raw)
To: Mathieu Othacehe; +Cc: 40662
On Thu, Apr 16, 2020 at 05:04:36PM +0200, Mathieu Othacehe wrote:
> Hello,
>
> Here's a small serie to add support for efivarfs and fix the issue reported
> here: https://lists.gnu.org/archive/html/bug-guix/2020-04/msg00274.html.
I have no idea why I only ever got the [Patch 0/2] e-mail delivered to
my inbox. I look at <https://issues.guix.info/issue/40662#1> now.
> [PATCH 2/2] file-system: Add efivarfs support.
> […]
> Tools such as efibootmgr rely on the deprecated /sys/firmware/efi/vars API as
> well as on the new /sys/firmware/efi/efivars API. The later needs to be
> mounted.
Typo: The latter needs to be mounted.
Well I had no issues with efivars on install without your patch. I
will try to provoke the error by adding more efivars. I did not yet
manage to create a new efivar via dd or via the efivar program though.
Regards,
Florian
^ permalink raw reply [flat|nested] 7+ messages in thread
* [bug#40662] [PATCH 0/2] Add efivarfs support.
2020-04-30 12:46 ` pelzflorian (Florian Pelz)
@ 2020-04-30 15:41 ` pelzflorian (Florian Pelz)
2020-05-01 9:16 ` Mathieu Othacehe
0 siblings, 1 reply; 7+ messages in thread
From: pelzflorian (Florian Pelz) @ 2020-04-30 15:41 UTC (permalink / raw)
To: Mathieu Othacehe; +Cc: 40662
On Thu, Apr 30, 2020 at 02:46:18PM +0200, pelzflorian (Florian Pelz) wrote:
> On Thu, Apr 16, 2020 at 05:04:36PM +0200, Mathieu Othacehe wrote:
> > Here's a small serie to add support for efivarfs and fix the issue reported
> > here: https://lists.gnu.org/archive/html/bug-guix/2020-04/msg00274.html.
> Well I had no issues with efivars on install without your patch. I
> will try to provoke the error by adding more efivars. I did not yet
> manage to create a new efivar via dd or via the efivar program though.
Actually I see no reason to test after provoking Keyhenge’s error.
How does your patch fix a full NVRAM? I thought Keyhenge resolved
their error by deleting “files” from the full NVRAM. Do I
misunderstand Keyhenge’s issue?
But /sys/firmware/efi/efivars probably should be mounted anyway.
Do you know why
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
is mounted even without your patch once I add %desktop-services to my
config.scm?
Regards,
Florian
^ permalink raw reply [flat|nested] 7+ messages in thread
* [bug#40662] [PATCH 0/2] Add efivarfs support.
2020-04-16 15:04 [bug#40662] [PATCH 0/2] Add efivarfs support Mathieu Othacehe
2020-04-30 12:46 ` pelzflorian (Florian Pelz)
@ 2020-04-30 16:06 ` pelzflorian (Florian Pelz)
2020-05-01 9:39 ` Mathieu Othacehe
1 sibling, 1 reply; 7+ messages in thread
From: pelzflorian (Florian Pelz) @ 2020-04-30 16:06 UTC (permalink / raw)
To: Mathieu Othacehe; +Cc: 40662
On Thu, Apr 16, 2020 at 05:04:36PM +0200, Mathieu Othacehe wrote:
> Here's a small serie to add support for efivarfs and fix the issue reported
> here: https://lists.gnu.org/archive/html/bug-guix/2020-04/msg00274.html.
When I reconfigure the first time with your patch, I get a harmless error:
building /gnu/store/klnbdxbw2jqglrdqyslv87c9y72g80f7-upgrade-shepherd-services.scm.drv
guix system: error: exception caught while executing 'start' on service 'file-system-/sys/firmware/efi/efivars':
Throw to key `match-error' with args `("match" "no matching pattern" ("efivarfs" "/sys/firmware/efi/efivars" "efivarfs" () #f #t #f))
I don’t know why it happens.
Regards,
Florian
^ permalink raw reply [flat|nested] 7+ messages in thread
* [bug#40662] [PATCH 0/2] Add efivarfs support.
2020-04-30 15:41 ` pelzflorian (Florian Pelz)
@ 2020-05-01 9:16 ` Mathieu Othacehe
0 siblings, 0 replies; 7+ messages in thread
From: Mathieu Othacehe @ 2020-05-01 9:16 UTC (permalink / raw)
To: pelzflorian (Florian Pelz); +Cc: 40662
Hey Florian,
Thanks a lot for having a look.
> Actually I see no reason to test after provoking Keyhenge’s error.
> How does your patch fix a full NVRAM? I thought Keyhenge resolved
> their error by deleting “files” from the full NVRAM. Do I
> misunderstand Keyhenge’s issue?
I think the full NVRAM is only one part of the issue. There could also
be errors for variables > 1024 bytes using the legacy sysfs API, see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933523.
> is mounted even without your patch once I add %desktop-services to my
> config.scm?
Oh, it seems that elogind has support to mount efivarfs.
Mathieu
^ permalink raw reply [flat|nested] 7+ messages in thread
* [bug#40662] [PATCH 0/2] Add efivarfs support.
2020-04-30 16:06 ` pelzflorian (Florian Pelz)
@ 2020-05-01 9:39 ` Mathieu Othacehe
2020-07-31 12:19 ` bug#40662: " Mathieu Othacehe
0 siblings, 1 reply; 7+ messages in thread
From: Mathieu Othacehe @ 2020-05-01 9:39 UTC (permalink / raw)
To: pelzflorian (Florian Pelz); +Cc: 40662
> guix system: error: exception caught while executing 'start' on service 'file-system-/sys/firmware/efi/efivars':
> Throw to key `match-error' with args `("match" "no matching pattern" ("efivarfs" "/sys/firmware/efi/efivars" "efivarfs" () #f #t #f))
>
> I don’t know why it happens.
Seems like an ABI incompatibility between the running shepherd and this
patch adding a new field in "file-system->spec" procedure. Not sure it
can be worked around.
Mathieu
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#40662: [PATCH 0/2] Add efivarfs support.
2020-05-01 9:39 ` Mathieu Othacehe
@ 2020-07-31 12:19 ` Mathieu Othacehe
0 siblings, 0 replies; 7+ messages in thread
From: Mathieu Othacehe @ 2020-07-31 12:19 UTC (permalink / raw)
To: 40662-done; +Cc: pelzflorian (Florian Pelz)
Hello,
I just pushed this one to master. Closing!
Mathieu
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2020-07-31 12:20 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-04-16 15:04 [bug#40662] [PATCH 0/2] Add efivarfs support Mathieu Othacehe
2020-04-30 12:46 ` pelzflorian (Florian Pelz)
2020-04-30 15:41 ` pelzflorian (Florian Pelz)
2020-05-01 9:16 ` Mathieu Othacehe
2020-04-30 16:06 ` pelzflorian (Florian Pelz)
2020-05-01 9:39 ` Mathieu Othacehe
2020-07-31 12:19 ` bug#40662: " Mathieu Othacehe
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).