From: Christophe Pisteur <christophe.pisteur@fsfe.org>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: help guix <help-guix@gnu.org>
Subject: Re: Could not prepare Boot variable
Date: Thu, 09 Jan 2025 20:33:56 +0100 [thread overview]
Message-ID: <435565a763a369fabe4efa8dd07403da8ff0dfe5.camel@fsfe.org> (raw)
In-Reply-To: <87y0zjdccm.fsf@lease-up.com>
Hi Felix,
Thanks a lot for the help.
Apparently, I boot with efi (I have the file /sys/firmware/efi).
I regularly do guix pull then sudo guix system reconfigure
/etc/config.scm, and it goes without a hitch. I don't know what's wrong
this time.
Kind regards,
Christophe
Le jeudi 09 janvier 2025 à 11:19 -0800, Felix Lechner a écrit :
> Hi Christophe,
>
> On Thu, Jan 09 2025, Christophe Pisteur wrote:
>
> > Could not prepare Boot variable [...] efibootmgr n'a pas réussi à
> > enregistrer l'entrée de démarrage: Erreur d'entrée/sortie.
>
> Did you boot in EFI or in legacy mode? I don't read French, but
> 'efibootmgr' and the Boot variables (which look like 0001 and
> determine
> the boot order) are only available in EFI mode.
>
> Kind regards
> Felix
next prev parent reply other threads:[~2025-01-09 19: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 [this message]
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
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
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=435565a763a369fabe4efa8dd07403da8ff0dfe5.camel@fsfe.org \
--to=christophe.pisteur@fsfe.org \
--cc=felix.lechner@lease-up.com \
--cc=help-guix@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).