From: "Ludovic Courtès" <ludo@gnu.org>
To: Reg <reg@disroot.org>
Cc: 35875@debbugs.gnu.org
Subject: bug#35875: Guix won't boot after installation with fully encrypted disk
Date: Fri, 24 May 2019 19:00:48 +0200 [thread overview]
Message-ID: <87pno7rdmn.fsf@gnu.org> (raw)
In-Reply-To: <138779ab-830b-32a9-e64a-e1fccabf90ab@disroot.org> (reg@disroot.org's message of "Thu, 23 May 2019 23:41:40 +0200")
Hello,
Reg <reg@disroot.org> skribis:
> Note: There was some discussion about this on IRC a couple of weeks ago.
>
> Guix won't boot on my ThinkPad T430 after an installation with fully encrypted disk:
>
> * First, at the end of the installation, I'm getting the following error message multiple times: "device-mapper: remove ioctl on cryptroot failed: Device or resource busy"
These messages are annoying but really harmless.
> * On boot, I am being prompted for the encryption key. So far so good. The Grub menu is then displayed and disappears after a few seconds – as it should – after which the computer is stuck on the Grub
Weird.
Does your compute have an AMD graphics card that could lead the kernel
(KMS) to wreck havoc during initialization?
Did you have hardware-related problems with other free GNU/Linux distros
on this machine before?
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-05-24 17:04 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 [this message]
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)
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=87pno7rdmn.fsf@gnu.org \
--to=ludo@gnu.org \
--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 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).