all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Reg <reg@disroot.org>
Cc: 35875@debbugs.gnu.org
Subject: bug#35875: Guix won't boot after installation with fully encrypted disk
Date: Sun, 29 Mar 2020 13:55:42 +0200	[thread overview]
Message-ID: <20200329115542.lckf6y2eewlml3e2@pelzflorian.localdomain> (raw)
In-Reply-To: <628ea287-d56e-9ce2-8bfc-a6da3721fdb7@disroot.org>

On Sat, Mar 28, 2020 at 10:39:28PM +0100, Reg wrote:
> 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
> 

This is nice to hear.  Thank you for testing; very quick.  BTW your
message did not go through to the bug report; probably it was my
mistake putting the wrong list in Cc.

Now I wonder where this should be documented.  Should there be a
Troubleshooting section in the manual?

Regards,
Florian

  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
2020-03-29 11:55     ` pelzflorian (Florian Pelz) [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200329115542.lckf6y2eewlml3e2@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=35875@debbugs.gnu.org \
    --cc=reg@disroot.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.