unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 36786@debbugs.gnu.org
Subject: bug#36786: Warn of AMD GPUs unusable with Guix System
Date: Fri, 26 Jul 2019 17:56:23 +0200	[thread overview]
Message-ID: <87o91glrh4.fsf@gnu.org> (raw)
In-Reply-To: <20190726055704.vev4wy56q5osznzi@pelzflorian.localdomain> (pelzflorian@pelzflorian.de's message of "Fri, 26 Jul 2019 07:57:04 +0200")

Hi Florian,

"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:

> On Fri, Jul 26, 2019 at 01:04:40AM +0200, Ludovic Courtès wrote:
>> What about adding a few words under “Hardware Considerations”?

Oops, I hadn’t seen your patch when I replied.

> 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.  :-)

> >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.

[…]

> +Some hardware requires specific tweaks to work better with Guix System.  The
> +following is an incomplete list of known workarounds:
> +
> +@itemize
> +@item
> +Some @emph{AMD Radeon} graphics cards stop redrawing the virtual console TTYs
> +when booting because of an error with Kernel Mode Setting.  The problem
> +disappears when blacklisting the kernel module for the driver.  To do so, you
> +can add @code{modprobe.blacklist=radeon} to the Linux-libre kernel flags,
> +either for only one boot by pressing the @kbd{e} key in the GRUB bootloader
> +and adding this kernel flag to the end of the @code{linux} command-line, or
> +permanently by changing the @code{kernel-arguments} field in your
> +@code{operating-system} declaration, e.g.:
> +
> +@example
> +(kernel-arguments '("quiet" "modprobe.blacklist=radeon"))
> +@end example
> +@end itemize

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?

Thanks,
Ludo’.

  reply	other threads:[~2019-07-26 15:57 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 [this message]
2019-07-26 20:03             ` pelzflorian (Florian Pelz)
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

  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=87o91glrh4.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=36786@debbugs.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).