From: "Ludovic Courtès" <ludo@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: jbranso@dismail.de, efraim@flashner.co.il, 58357@debbugs.gnu.org
Subject: [bug#58357] [Patch staging ] doc add a recommended system in 'Hardware Considerations'
Date: Fri, 14 Oct 2022 17:12:59 +0200 [thread overview]
Message-ID: <87edval9qc.fsf_-_@gnu.org> (raw)
In-Reply-To: <87pmf0htzb.fsf@pelzflorian.de> (pelzflorian@pelzflorian.de's message of "Mon, 10 Oct 2022 12:07:52 +0200")
Hi!
This discussion and others we had at the Ten Years of Guix event makes
me think we should strive to avoid bad surprises by being more
explicit. Concretely, we could:
• Under “Hardware Considerations”, list common devices known not to
work without non-free {firm,soft}ware, such as Intel Wifi (iwlwifi).
We cannot be exhaustive but we should at least mention common
problems with recent x86_64 laptops.
• Under “Hardware Considerations”, make the list of devices known to
work clearer, in tabular form, perhaps expanding it.
• In the installer, print a message upfront when unusable devices are
found—typically Intel wifi.
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.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2022-10-14 15:29 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 [this message]
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)
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=87edval9qc.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=58357@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=jbranso@dismail.de \
--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).