all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Roman Riabenko via <help-guix@gnu.org>
To: Christophe Pisteur <christophe.pisteur@fsfe.org>
Cc: Felix Lechner <felix.lechner@lease-up.com>,
	help guix <help-guix@gnu.org>
Subject: Re: Could not prepare Boot variable
Date: Thu, 9 Jan 2025 23:34:00 +0200	[thread overview]
Message-ID: <20250109233400.30a6ecbdf9565b9e8a85fb9b@riabenko.com> (raw)
In-Reply-To: <b39834701829aca4443629b8ee05ac49c8f5d1ef.camel@fsfe.org>

On Thu, 09 Jan 2025 22:10:07 +0100
Christophe Pisteur <christophe.pisteur@fsfe.org> wrote:

> Le jeudi 09 janvier 2025 à 22:49 +0200, Roman Riabenko a écrit :
> > > 
> > > Is the following console command correct?
> > > sudo rm /sys/firmware/efi/efivars/dump-type0-*
> > 
> > Yes, this is the command that removes the dump files.
> > 
> 
> I deleted the “dump” files from the directory
> /sys/firmware/efi/efivars/, then I ran guix system reconfigure
> /etc/config.scm again, but the command ends with the same error
> message...

That one did not happen to me. efivars directory is an interface that
exposes EFI firmware variables. If you do not see the dump files in the
directory, then EFI should have cleared them. However, in such case the
memory would be freed for new variables, and you would not get the
error when reconfiguring the system anymore.

There are other ways to access the variables. You could try efivar to
see whether the dumps are still reported by UEFI.

$ guix shell efivar
[env]$ efivar --list
[env]$ exit

The tool also allows removing variables, but I did not try that myself.

Roman


  reply	other threads:[~2025-01-09 21:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09 19:01 Could not prepare Boot variable Christophe Pisteur
2025-01-09 19:19 ` Felix Lechner via
2025-01-09 19:33   ` Christophe Pisteur
2025-01-09 19:38     ` Felix Lechner via
2025-01-09 20:04       ` Christophe Pisteur
2025-01-09 20:05 ` Roman Riabenko via
2025-01-09 20:15   ` Christophe Pisteur
2025-01-09 20:24     ` Roman Riabenko via
2025-01-09 20:42       ` Christophe Pisteur
2025-01-09 20:49         ` Roman Riabenko via
2025-01-09 21:10           ` Christophe Pisteur
2025-01-09 21:34             ` Roman Riabenko via [this message]
2025-01-09 22:04               ` Christophe Pisteur
2025-01-09 22:34                 ` Roman Riabenko via
2025-01-09 20:16   ` Felix Lechner via
2025-01-09 20:35     ` Roman Riabenko via
2025-01-09 21:45       ` Felix Lechner via

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=20250109233400.30a6ecbdf9565b9e8a85fb9b@riabenko.com \
    --to=help-guix@gnu.org \
    --cc=christophe.pisteur@fsfe.org \
    --cc=felix.lechner@lease-up.com \
    --cc=roman@riabenko.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.