From: Reg <reg@disroot.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 35875@debbugs.gnu.org
Subject: bug#35875: Guix won't boot after installation with fully encrypted disk
Date: Sat, 28 Mar 2020 22:39:28 +0100 [thread overview]
Message-ID: <628ea287-d56e-9ce2-8bfc-a6da3721fdb7@disroot.org> (raw)
In-Reply-To: <20200328124231.hiy6sdixxyj3olrx@pelzflorian.localdomain>
Hi Florian,
Thank you very much for getting back to me! CSM legacy support was
already enabled on my ThinkPad but guess what.. *Disabling* it fixed the
problem! My computer is booting without issues now with a fully
encrypted disk.
Thank you so much!
Best regards,
Reg
On 2020-03-28 13:42, pelzflorian (Florian Pelz) wrote:
> Hello Reg!
>
> On Thu, May 23, 2019 at 11:41:40PM +0200, Reg wrote:
>> Guix won't boot on my ThinkPad T430 after an installation with fully
>> encrypted disk:
>
> A friend had an issue that looked similar on an HP laptop (no
> Thinkpad) in Guix System. GRUB got stuck either after entering the
> encryption key or, without encryption, when booting Guix. The
> resolution was to enable CSM Legacy Support in the UEFI/BIOS settings
> (even though it is a grub-efi-bootloader install). Maybe this is
> something to try if you or someone else has such an issue again.
>
> Regards,
> Florian
>
next prev parent reply other threads:[~2020-03-30 2:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 21:41 bug#35875: Guix won't boot after installation with fully encrypted disk Reg
2019-05-24 17:00 ` Ludovic Courtès
2019-05-25 8:37 ` Giovanni Biscuolo
2019-05-25 12:53 ` Reg
2019-05-29 16:24 ` Giovanni Biscuolo
2019-05-29 20:52 ` Reg
2019-05-30 12:10 ` Giovanni Biscuolo
2019-05-30 13:40 ` Reg
2019-05-31 22:01 ` Ludovic Courtès
2019-06-01 7:19 ` Reg
2020-03-28 12:42 ` pelzflorian (Florian Pelz)
2020-03-28 21:39 ` Reg [this message]
2020-03-29 11:55 ` pelzflorian (Florian Pelz)
2022-10-29 18:28 ` david larsson
2022-10-30 9:05 ` Josselin Poiret via Bug reports for GNU Guix
2022-10-30 12:27 ` david larsson
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=628ea287-d56e-9ce2-8bfc-a6da3721fdb7@disroot.org \
--to=reg@disroot.org \
--cc=35875@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).