all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 36786@debbugs.gnu.org
Subject: bug#36786: Warn of AMD GPUs unusable with Guix System
Date: Fri, 26 Jul 2019 22:03:26 +0200	[thread overview]
Message-ID: <20190726200325.25npy5xwkjp7m353@pelzflorian.localdomain> (raw)
In-Reply-To: <87o91glrh4.fsf@gnu.org>

On Fri, Jul 26, 2019 at 05:56:23PM +0200, Ludovic Courtès wrote:
> "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
> > While my patch before addresses AMD-specific tweaks in the manual
> > under Hardware Considerations, it is not enough if on the *download
> > page* Guix is claimed to run on “an i686, x86_64, ARMv7, or AArch64
> > machine“ without saying linux-libre *on some hardware, is not
> > supported* and referencing the Hardware Considerations section and
> > h-node, I think.
> 
> Well, ‘Limitations’ and ‘Hardware Considerations’ are the first sections
> one see when following ‘Installation Instructions’ at
> <http://guix.gnu.org/download/>.  We can always move things one level
> higher, but eventually everything ends up at the top level.  :-)
> 

I would rather see a more prominent link to the manual and h-node
where on the downloads page it says “runs on i686, x86_64, ARM”,
because I suppose many people do not read the manual until they know
they need to, and instead expect things to just work, especially now
that there’s a graphical installer.



> > >From e88ee68c09266e1d09d24ff0d1b6ec6a4708841b Mon Sep 17 00:00:00 2001
> > From: Florian Pelz <pelzflorian@pelzflorian.de>
> > Date: Wed, 24 Jul 2019 23:02:21 +0200
> > Subject: [PATCH] doc: Mention AMD Radeon workaround when TTYs are not redrawn.
> > 
> > * doc/guix.texi (Hardware Considerations): Describe workaround.
> 
> […]
> 
> I think this doesn’t fit well here: the previous paragraphs are about
> RYF, h-node.org, and the more general issue.
> 
> Like Ricardo wrote, since this is not Guix-specific, it would be great
> if we could link to other resources on this topic.  Are you aware of any
> such on-line resource?
> 
> If there’s no such thing, then we should definitely add this
> information, but perhaps we should move the paragraph a bit higher (next
> to Wifi), and possibly turn Wifi into an item of this list.  WDYT?
>

Yes, I agree this is not a good place in the manual.  However, I
thought of it more as a list of hardware-specific *and* Guix-specific
tweaks.  Note that the patch does not mention Xorg not working on some
AMD GPUs (h-node is the place for that, even though currently it does
not yet list many AMD Radeons), instead the patch is about
hardware-specific tweaks that can be made.  For example, a
recommendation of thinkfan for Thinkpads could be placed in such a
section too (once there is a Guix service for thinkfan; I do not know
how important thinkfan is and do not own a Thinkpad, it is just an
example).  The Arch wiki for example has articles on various specific
kinds of hardware.

Regards,
Florian

  reply	other threads:[~2019-07-26 20:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-24 14:56 bug#36786: Warn of AMD GPUs unusable with Guix System pelzflorian (Florian Pelz)
2019-07-24 15:42 ` pelzflorian (Florian Pelz)
2019-07-24 17:53   ` pelzflorian (Florian Pelz)
2019-07-24 19:05     ` Ricardo Wurmus
2019-07-24 21:22       ` pelzflorian (Florian Pelz)
2019-07-25 23:04       ` Ludovic Courtès
2019-07-26  5:57         ` pelzflorian (Florian Pelz)
2019-07-26 15:56           ` Ludovic Courtès
2019-07-26 20:03             ` pelzflorian (Florian Pelz) [this message]
2021-12-07 17:42 ` Denis 'GNUtoo' Carikli
2022-11-15 23:28 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190726200325.25npy5xwkjp7m353@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=36786@debbugs.gnu.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.