From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 66746@debbugs.gnu.org
Subject: bug#66746: LUKS password prompt invisible, prompts twice
Date: Sun, 29 Oct 2023 12:48:40 +0100 [thread overview]
Message-ID: <e84c90e90e46ade04254a288dd37a06b@tobias.gr> (raw)
In-Reply-To: <1698234598.24576@bluehome.net>
> I’m also getting this bug (the second decrypt screen not showing up)
> with
> Linux kernel versions 6.5.8 and 6.5.9 (the latest version as of
> writing);
> 6.5.7 does not have the bug for me.
Oh, this might be interesting… At least it's something.
Could you diff a working 6.5.7 and broken 6.5.8 configuration? The
configuration is stored as /gnu/store/…-linux-libre-6.5.x/.config;
there's no need to boot the kernel just to load the config.gz module.
If you use Coreboot or a derivative: do your broken kernels include
<https://git.savannah.gnu.org/cgit/guix.git/commit/?id=6d7e181ba18d11c92409a93936025fb46b9c8171>?
And if they do, have you tried booting with
(initrd-modules (cons "framebuffer-coreboot" %base-initrd-modules))
by any chance?
Kind regards,
T G-R
Sent from a Web browser. Excuse or enjoy my brevity.
next prev parent reply other threads:[~2023-10-29 11:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 11:49 bug#66746: LUKS password prompt invisible, prompts twice Caleb Herbert
2023-10-26 18:44 ` kasper.andersson--- via Bug reports for GNU Guix
2023-10-27 18:44 ` Josselin Poiret via Bug reports for GNU Guix
2023-10-27 19:02 ` Saku Laesvuori via Bug reports for GNU Guix
2023-10-28 11:07 ` kasper.andersson--- via Bug reports for GNU Guix
2023-10-29 8:21 ` Jake
2023-10-29 11:48 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2023-10-30 10:50 ` Jake
2023-10-29 16:04 ` James Smith via Bug reports for GNU Guix
2023-10-30 12:33 ` Jake
2023-10-30 16:49 ` X
2023-11-01 10:03 ` Jake
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=e84c90e90e46ade04254a288dd37a06b@tobias.gr \
--to=bug-guix@gnu.org \
--cc=66746@debbugs.gnu.org \
--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.