unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Felix Lechner via <help-guix@gnu.org>
To: post@thomasdanckaert.be
Cc: help-guix@gnu.org
Subject: Re: EFI boot: 'could not prepare Boot variable: Invalid argument'
Date: Sun, 6 Nov 2022 08:25:32 -0800	[thread overview]
Message-ID: <CAFHYt55c-cNaxz20_D8ty9fWwTPEvghSUuDYjn1PLaEVehKzOw@mail.gmail.com> (raw)
In-Reply-To: <da84d317047e90d7c0f8206d4e9da748@thomasdanckaert.be>

Hi,

On Sun, Nov 6, 2022 at 4:58 AM <post@thomasdanckaert.be> wrote:
>
> 'Could not prepare Boot variable: Invalid argument'

You have not yet rebooted, have you?

What do you see with this command?

    ls /sys/firmware/efi/vars/

You can also try 'guix install efivar' and look at the output of that
tool, but please do not attempt to change any settings yourself.

> Does anybody have a guess what can cause this (and what might solve
> it?).

Diagnosing boot problems can be difficult even when sitting in front
of the equipment. I believe your system booted via the legacy boot
sector method instead of UEFI, which made the EFI variables
unavailable.

If so, the only way to fix it is to boot via EFI.

> I fear my system is currently unbootable.

In Guix, you should have old system generations available in the GRUB
menu. That is your preferred method.

You may also be able to manually link the EFI image you wish to load
via the "removable media path". A third option that I have used is to
load your kernel directly via its EFI stub. The two latter options may
require further help from this list and lots of patience. They also
carry a higher risk of failure.

Kind regards
Felix Lechner


  reply	other threads:[~2022-11-06 16:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-06 12:52 EFI boot: 'could not prepare Boot variable: Invalid argument' post
2022-11-06 16:25 ` Felix Lechner via [this message]
2022-11-06 21:04   ` post
2022-11-06 23:21     ` Felix Lechner via
2022-11-07  7:58       ` post

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=CAFHYt55c-cNaxz20_D8ty9fWwTPEvghSUuDYjn1PLaEVehKzOw@mail.gmail.com \
    --to=help-guix@gnu.org \
    --cc=felix.lechner@lease-up.com \
    --cc=post@thomasdanckaert.be \
    /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).