From: Bone Baboon <bone.baboon@disroot.org>
To: guix-devel@gnu.org
Subject: GPU compatibility with Linux-libre
Date: Thu, 13 May 2021 17:25:07 -0400 [thread overview]
Message-ID: <8735uqe37w.fsf@disroot.org> (raw)
This message has two parts about GPU compatibility with Linux-libre.
1) Manual Warning
2) Summary
# Manual Warning
I originally posted the message below on the help mailing list. It is
reposted here for two reasons.
* It was suggested that the help mailing list may not be the correct
mailing list.
https://lists.gnu.org/archive/html/help-guix/2021-04/msg00229.html
* Someone else recently had the same issue with GPU compatibility.
https://issues.guix.gnu.org/issue/48343
From the original message:
```
I found the Hardware Considerations section of the Guix manual very
helpful. I was prepared for the issue of WiFi device compatibility.
However I was surprised by GPU compatibility.
I think it would be helpful to have a warning about GPU compatibility.
This would help someone who is looking at buying a computer by bringing
GPU compatibility to their attention.
I found the WiFi device warning with specific hardware that is known to
work very helpful. Maybe an equivalent could be done for GPUs
...
I appreciate that this extra warning may discourage some people from
trying Guix. I think it would still be good to warn people about
potential problems so that they are not surprised.
```
# Summary
I have been sharing a link to "GPU compatibility with Linux-libre"
https://lists.gnu.org/archive/html/help-guix/2021-04/msg00220.html on
the Guix mailing lists and in #guix when people were asking for help
about getting a graphical environment setup in Guix. The feedback I have
received is that it was helpful. I would appreciate any correction or
additions as I do not want to misinform people.
reply other threads:[~2021-05-13 22:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8735uqe37w.fsf@disroot.org \
--to=bone.baboon@disroot.org \
--cc=guix-devel@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).