unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ian Eure <ian@retrospec.tv>
To: help-guix <help-guix@gnu.org>
Subject: Re: Laptop won’t boot after Guix install
Date: Sat, 13 Jan 2024 13:12:15 -0800	[thread overview]
Message-ID: <87bk9pq6kb.fsf@retrospec.tv> (raw)
In-Reply-To: <D7E9EFB2-9018-47E4-B8CA-E7E1EF514BEE@lepiller.eu>


Julien Lepiller <julien@lepiller.eu> writes:

> Hi Ian,
>
> Something similar happened to me before. After reconfiguring a 
> lot of
> times, the firmaware had no space left for EFI variables. I 
> didn't
> notice the error message at first because guix system did
> succeed. Maybe you have some similar errors that don't lead to a
> failure? What does the last phase say, when installing the 
> bootloader?
>

Thank you for the suggestion.  I’ve run into this problem before 
as well, on different hardware.  I didn’t see any message to this 
effect during the install, or during subsequent `guix system 
reconfigure' invocations, which do seem to update the bootloader. 
Does `guix system init' do more than that?

I did look around the EFI variables, but there are a bajillion of 
them and I have no idea what any of them mean, or which may be 
safe to remove.  I figured resetting all my BIOS settings would 
clear those out.


  reply	other threads:[~2024-01-13 21:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-06  3:41 Laptop won’t boot after Guix install Ian Eure
2024-01-06  7:28 ` Julien Lepiller
2024-01-13 21:12   ` Ian Eure [this message]
2024-02-21  4:38   ` Ian Eure
2024-01-08 19:08 ` Roman Riabenko via
2024-01-09 13:53   ` Felix Lechner via
2024-01-09 14:49     ` Roman Riabenko via
2024-01-13 21:18     ` Ian Eure
2024-01-13 21:15   ` Ian Eure
2024-01-08 21:11 ` Tobias Geerinckx-Rice

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=87bk9pq6kb.fsf@retrospec.tv \
    --to=ian@retrospec.tv \
    --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).