From: Roman Riabenko via <help-guix@gnu.org>
To: Felix Lechner <felix.lechner@lease-up.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 16:49:37 +0200 [thread overview]
Message-ID: <ee3585e74dcc3b392a57d18b24e2a54c4f54c3ff.camel@riabenko.com> (raw)
In-Reply-To: <87frz662b0.fsf@lease-up.com>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
Hi Felix
У вт, 2024-01-09 у 05:53 -0800, Felix Lechner пише:
> On Mon, Jan 08 2024, Roman Riabenko via wrote:
> > 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.
Just to be clear, I do not promote the use of "Secure Boot" in any way.
Instead, I suggest looking again into different options in the firmware
settings and trying some of them, even if they seem irrelevant.
Unfortunately, the firmware is often poorly designed and non-free. In
my anecdotal case, it is possible to edit boot options by specifying
paths from within the EUFI setup only when the "Secure Boot" is on.
Otherwise, the option is not merely greyed out but is absent
altogether. It is also named inappropriately. After configuring the
boot options, I turn off the "Secure Boot" by emptying its password.
Hopefully, the firmware is not this broken on the device which Ian is
trying to use, but I try to be helpful.
Roman
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-01-09 14:50 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
2024-01-09 14:49 ` Roman Riabenko via [this message]
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=ee3585e74dcc3b392a57d18b24e2a54c4f54c3ff.camel@riabenko.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).