all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 48649-done@debbugs.gnu.org, Juraj Hlista <juraj@juraj.me>
Subject: bug#48649: Guix doesn't boot with LUKS root partition
Date: Tue, 24 Aug 2021 00:11:23 -0400	[thread overview]
Message-ID: <877dgbtrbo.fsf@gmail.com> (raw)
In-Reply-To: <87wnr46npf.fsf@nckx> (Tobias Geerinckx-Rice's message of "Tue, 08 Jun 2021 23:39:08 +0200")

Hello,

Tobias Geerinckx-Rice <me@tobias.gr> writes:

> Juraj Hlista 写道:
>> Not sure how the i915 module is related to LUKS though.
>
> Not, all all.  You should see the same apparent ‘freeze’ when booting
> the system without LUKS with ‘--repl’ on the kernel command line.
>
> Linux prompts for the LUKS passphrase early, and (obviously :-) before
> the root file system is mounted.  The kernel needs to display this
> prompt.  The root file system contains all drivers. See the deadlock?
>
> Adding i915 to the initrd will ensure that it is loaded before the
> initrd tries to mount / and asks you for the passphrase, so 
> everything will work fine.  Building i915 into the kernel would have
> the same effect.

Seems this issue was about not having a required video driver in the
init RAM disk, rather than LUKS support.

Closing.

Glad you got it solved!

Maxim




      reply	other threads:[~2021-08-24  4:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25  9:24 bug#48649: Guix doesn't boot with LUKS root partition Juraj Hlista
2021-05-25 11:19 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-05-25 12:12   ` Juraj Hlista
2021-05-25 17:19     ` Juraj Hlista
2021-05-26  9:23       ` Juraj Hlista
2021-06-08 17:24         ` Eric Brown
2021-06-08 21:39         ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-08-24  4:11           ` Maxim Cournoyer [this message]

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=877dgbtrbo.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=48649-done@debbugs.gnu.org \
    --cc=juraj@juraj.me \
    --cc=me@tobias.gr \
    /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.