From: Felix Lechner via <help-guix@gnu.org>
To: Roman Riabenko <roman@riabenko.com>, Ian Eure <ian@retrospec.tv>,
help-guix <help-guix@gnu.org>
Subject: Re: Laptop won’t boot after Guix install
Date: Tue, 09 Jan 2024 05:53:23 -0800 [thread overview]
Message-ID: <87frz662b0.fsf@lease-up.com> (raw)
In-Reply-To: <6dfcb2c84d13432da373c65ffcbf06683668efd7.camel@riabenko.com>
Hi Ian,
On Mon, Jan 08 2024, Roman Riabenko via wrote:
> Sometimes, the installer makes a BIOS-compatible installation which
> fails to run from UEFI.
I like to check 'efibootmgr' inside the installer. Alternatively, you
can look at the NVRAM contents with evivars. (I don't have experience
yet with the newer efivarfs, but I think that's similar.) If you cannot
find the UEFI boot variables, then GRUB cannot either---and the setup
will be defective. It will not boot in UEFI.
Old GRUB boot sectors can make the boot experience even more confusing.
> The fix might be as simple as choosing a different USB boot option
> before running the installer.
That's how all my equipment, which is up to a decade old, works but it's
always a wire act from USB creation to first boot.
> You might want to try enabling it [secure boot]
I do not recommend Secure Boot for average Linux users. It tends to
create more problems and may not provide the security you expect.
Kind regards
Felix
next prev parent reply other threads:[~2024-01-09 13:54 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
2024-02-21 4:38 ` Ian Eure
2024-01-08 19:08 ` Roman Riabenko via
2024-01-09 13:53 ` Felix Lechner via [this message]
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=87frz662b0.fsf@lease-up.com \
--to=help-guix@gnu.org \
--cc=felix.lechner@lease-up.com \
--cc=ian@retrospec.tv \
--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).