From: kiasoc5 via Guix-patches via <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 58357@debbugs.gnu.org,
"pelzflorian \(Florian Pelz\)" <pelzflorian@pelzflorian.de>,
efraim@flashner.co.il, jbranso@dismail.de
Subject: [bug#58357] [Patch staging ] doc add a recommended system in 'Hardware Considerations'
Date: Fri, 14 Oct 2022 15:47:34 +0000 [thread overview]
Message-ID: <20221014154734.6ac73a89@aria> (raw)
In-Reply-To: <87edval9qc.fsf_-_@gnu.org>
On Fri, Oct 14 2022, 05:12:59 PM +0200
Ludovic Courtès <ludo@gnu.org> wrote:
> I’m not sure how to do this though. Maintaining a list of
> known-bad devices doesn’t sound great, but it’s better than nothing.
> Instrumenting the firmware-loading mechanism would be a good way
> to detect problems, but I think it’s not even getting invoked in
> Linux-libre (or not always). Alternatively, we could tweak
> deblobbing so that it produces a list of known-bad modules or
> devices.
I think automatically generating a list of nonfree modules would work,
as long as we make sure we don't recommend that a user acquire them.
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.
(if this is a separate issue, I can make a bug report)
--
next prev parent reply other threads:[~2022-10-14 15:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Yz/FHD608HeU6iIM@3900XT>
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 [this message]
2022-10-15 9:47 ` pelzflorian (Florian Pelz)
2022-10-16 11:53 ` pelzflorian (Florian Pelz)
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)
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=20221014154734.6ac73a89@aria \
--to=guix-patches@gnu.org \
--cc=58357@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=jbranso@dismail.de \
--cc=kiasoc5@disroot.org \
--cc=ludo@gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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).