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: Fri, 10 Jan 2025 00:34:47 +0200 [thread overview]
Message-ID: <20250110003447.9ef2a1f40477cf236fbba7ad@riabenko.com> (raw)
In-Reply-To: <4d53001d84929255222c2b3775819a11fdddef99.camel@fsfe.org>
On Thu, 09 Jan 2025 23:04:59 +0100
Christophe Pisteur <christophe.pisteur@fsfe.org> wrote:
> [env]$ efivar --list do not report dumps files (cf. below)
>
> should I try logout and login (without rebooting)?
I don't know. I don't think it will have any effect. It is UEFI that
refuses to take a new variable. You need to find a way to make it take
the variable.
The first time it happened, I rebooted and was unable to boot. GRUB
did not show up. And selecting the Guix boot option in UEFI boot menu
failed to load GRUB. I had to use a Guix installation USB drive to
chroot into my installation (section 12 of the guix manual) and fix it.
The second and third time it happend, I cleared the dumps via efivars
directory the way you did. This allowed me to complete reconfiguring
the system each time. It looks like my UEFI behaved better then yours.
I do not know whether you can properly roll back the guix system to the
last (meaning current) configuration, so that the existing boot option
works. Maybe somebody else could comment on this.
Roman
next prev parent reply other threads:[~2025-01-09 23:15 UTC|newest]
Thread overview: 31+ 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
2025-01-09 22:04 ` Christophe Pisteur
2025-01-09 22:34 ` Roman Riabenko via [this message]
2025-01-09 20:16 ` Felix Lechner via
2025-01-09 20:35 ` Roman Riabenko via
2025-01-09 21:45 ` Felix Lechner via
2025-01-10 13:51 ` Roman Riabenko via
2025-01-12 13:33 ` Roman Riabenko via
2025-01-13 17:43 ` Christophe Pisteur
2025-01-13 20:01 ` Roman Riabenko via
2025-01-21 18:58 ` Leo Famulari
2025-01-21 20:17 ` Roman Riabenko via
2025-01-21 20:26 ` Leo Famulari
2025-01-22 7:18 ` Roman Riabenko via
2025-01-22 8:06 ` Efraim Flashner
2025-01-22 20:49 ` Felix Lechner via
2025-01-24 16:18 ` Roman Riabenko via
2025-01-10 16:53 ` Tobias Geerinckx-Rice
2025-01-10 17:22 ` Felix Lechner via
2025-01-11 10:26 ` Roman Riabenko 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250110003447.9ef2a1f40477cf236fbba7ad@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.
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).