From: Leo Famulari <leo@famulari.name>
To: 53712@debbugs.gnu.org
Subject: bug#53712: Guix System hangs after boot with linux-libre 5.15.17
Date: Sat, 12 Feb 2022 21:06:09 -0500 [thread overview]
Message-ID: <YghnkdV68oua7c2B@jasmine.lan> (raw)
In-Reply-To: <tencent_643527A4DC5BAA14A9B802F1BC53FEBEDE0A@qq.com>
On Fri, Feb 11, 2022 at 04:03:03AM +0800, Squirrel via Bug reports for GNU Guix wrote:
> Blacklisting the iwlwifi kernel module works as a workaround for now, as is
> suggested by Jason Self, the maintainer of the Freesh and libeRTy apt
> repositories of linux-libre kernel. He mentioned it in Trisquel forum at https://trisquel.info/en/forum/trisquel-9-linux-libre-51517-will-not-allow-login
> and at https://lore.kernel.org/all/20220203161959.3edf1d6e@valencia/
Thanks for the info!
I can confirm that adding the modprobe incantation to my
operating-system declaration, reconfiguring, and rebooting does fix the
bug:
(kernel-arguments
'(; https://issues.guix.gnu.org/53712#12
"modprobe.blacklist=pcspkr,snd_pcsp,iwlwifi"))
https://guix.gnu.org/manual/devel/en/html_node/operating_002dsystem-Reference.html#FOOT24
next prev parent reply other threads:[~2022-02-13 2:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 20:39 bug#53712: Guix System hangs after boot with linux-libre 5.15.17 Leo Famulari
2022-02-01 21:11 ` Maxim Cournoyer
2022-02-01 21:58 ` Leo Famulari
2022-02-01 21:44 ` Leo Famulari
2022-02-01 22:09 ` Leo Famulari
2022-02-01 22:11 ` Leo Famulari
2022-02-02 19:51 ` Leo Famulari
2022-02-03 18:06 ` Leo Famulari
2022-02-09 18:23 ` Leo Famulari
2022-02-07 16:54 ` bug#53712: I'm also experiencing this Katherine Cox-Buday
2022-02-07 18:14 ` Leo Famulari
2022-02-10 20:03 ` bug#53712: Guix System hangs after boot with linux-libre 5.15.17 Squirrel via Bug reports for GNU Guix
2022-02-13 2:06 ` Leo Famulari [this message]
2022-02-24 15:08 ` Leo Famulari
[not found] <mailman.37.1645722019.10594.bug-guix@gnu.org>
2022-03-02 15:39 ` Squirrel via Bug reports for GNU Guix
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=YghnkdV68oua7c2B@jasmine.lan \
--to=leo@famulari.name \
--cc=53712@debbugs.gnu.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).