From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: kiasoc5 <kiasoc5@disroot.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
58357@debbugs.gnu.org, efraim@flashner.co.il, jbranso@dismail.de
Subject: [bug#58357] [Patch staging ] doc add a recommended system in 'Hardware Considerations'
Date: Sun, 16 Oct 2022 13:53:53 +0200 [thread overview]
Message-ID: <87ilkkouge.fsf@pelzflorian.de> (raw)
In-Reply-To: <87v8oll8oz.fsf@pelzflorian.de> (pelzflorian@pelzflorian.de's message of "Sat, 15 Oct 2022 11:47:40 +0200")
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> writes:
> kiasoc5 <kiasoc5@disroot.org> writes:
>> Also, I tried to run linux-libre on my desktop and it booted but
>> refused to login because it tried to load the nonfree wifi card. Could
>> it be patched so that nonfree modules are ignored, and I could at least
>> get a desktop without wifi? Everything else afaik is free hardware.
>
> Are you sure this is not a graphics lockup? If it were a graphics
> lockup, you could press E in the GRUB menu and add nomodeset to the
> linux boot line.
gnu/system.scm contains
(define %default-modprobe-blacklist
;; List of kernel modules to blacklist by default.
'("usbmouse" ;races with bcm5974, see <https://bugs.gnu.org/35574>
"usbkbd")) ;races with usbhid, see <https://issues.guix.gnu.org/35574#18>
Perhaps send a patch or open a bug to add your wifi’s module to the
default modprobe blacklist.
Regards,
Florian
next prev parent reply other threads:[~2022-10-16 11:55 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 14:50 Planning for a release, for real Ludovic Courtès
2022-10-06 16:02 ` Julien Lepiller
2022-10-07 9:49 ` Ludovic Courtès
2022-10-07 10:14 ` Julien Lepiller
2022-10-06 16:07 ` Maxime Devos
2022-10-07 9:50 ` Ludovic Courtès
2022-10-07 9:53 ` Maxime Devos
2022-10-07 6:20 ` Supported architectures Efraim Flashner
2022-10-07 10:02 ` Ludovic Courtès
2022-10-07 14:24 ` [bug#58357] [Patch staging ] doc add a recommended system in 'Hardware Considerations' Joshua Branson via Guix-patches via
2022-10-08 9:55 ` pelzflorian (Florian Pelz)
2022-10-08 15:33 ` jbranso--- via Guix-patches via
2022-10-10 10:07 ` pelzflorian (Florian Pelz)
2022-10-14 15:12 ` Ludovic Courtès
2022-10-14 15:47 ` kiasoc5 via Guix-patches via
2022-10-15 9:47 ` pelzflorian (Florian Pelz)
2022-10-16 11:53 ` pelzflorian (Florian Pelz) [this message]
2022-10-14 17:09 ` pelzflorian (Florian Pelz)
2022-10-15 15:51 ` pelzflorian (Florian Pelz)
2022-10-17 16:35 ` Ludovic Courtès
2022-10-14 19:28 ` jbranso--- via Guix-patches via
2022-11-03 19:21 ` Ludovic Courtès
2022-11-16 0:22 ` pelzflorian (Florian Pelz)
2022-11-16 23:16 ` jbranso--- via Guix-patches via
2022-11-17 16:26 ` pelzflorian (Florian Pelz)
2022-11-19 14:06 ` Joshua Branson via Guix-patches via
2022-12-08 17:02 ` pelzflorian (Florian Pelz)
2023-03-09 21:06 ` pelzflorian (Florian Pelz)
2023-08-20 17:44 ` pelzflorian (Florian Pelz)
2022-10-10 7:57 ` Supported architectures Csepp
2022-10-12 20:40 ` Vagrant Cascadian
2022-10-13 15:06 ` Ludovic Courtès
2022-10-07 8:26 ` Planning for a release, for real Christopher Baines
2022-10-07 10:09 ` Ludovic Courtès
2022-10-10 10:33 ` zimoun
2022-10-13 15:19 ` Release progress, week 1 Ludovic Courtès
2022-10-13 15:33 ` Efraim Flashner
2022-10-13 15:42 ` Christopher Baines
2022-10-20 13:49 ` Release progress, week 2 Ludovic Courtès
2022-10-20 20:07 ` Efraim Flashner
2022-10-21 8:51 ` Rust on aarch64-linux Ludovic Courtès
2022-10-21 13:42 ` Efraim Flashner
2022-10-22 20:22 ` Efraim Flashner
2022-10-26 9:01 ` Efraim Flashner
[not found] ` <87h6zyo811.fsf@gnu.org>
2022-10-21 8:43 ` Status of armhf-linux and powerpc64le-linux Ludovic Courtès
2022-10-21 9:30 ` Mathieu Othacehe
2022-10-31 17:40 ` Tobias Platen
2022-10-22 12:18 ` Release progress, week 2 Christopher Baines
2022-10-25 9:50 ` Release progress, week 2, release manifest, what builds are failing? Christopher Baines
2022-10-25 11:29 ` Release progress, week 2, release manifest, what builds are failing: gst-plugins-bad Christopher Baines
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=87ilkkouge.fsf@pelzflorian.de \
--to=pelzflorian@pelzflorian.de \
--cc=58357@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=jbranso@dismail.de \
--cc=kiasoc5@disroot.org \
--cc=ludo@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 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.