From debbugs-submit-bounces@debbugs.gnu.org Wed Jul 24 17:23:00 2019 Received: (at 36786) by debbugs.gnu.org; 24 Jul 2019 21:23:00 +0000 Received: from localhost ([127.0.0.1]:38135 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hqOix-0006op-Pg for submit@debbugs.gnu.org; Wed, 24 Jul 2019 17:23:00 -0400 Received: from pelzflorian.de ([5.45.111.108]:46718 helo=mail.pelzflorian.de) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hqOiu-0006og-Nr for 36786@debbugs.gnu.org; Wed, 24 Jul 2019 17:22:57 -0400 Received: from pelzflorian.localdomain (unknown [5.45.111.108]) by mail.pelzflorian.de (Postfix) with ESMTPSA id 59D3C360035; Wed, 24 Jul 2019 23:22:55 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=pelzflorian.de; s=mail; t=1564003375; bh=Kc32N+c57vz22Y5QhzcvpbrN2UKuI4cLUb94S5hpZYI=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=jA3d8eUVBU+ofaSOiA3LdHyBFtux7ipSmrdI1yNXETF3xpWNa7DvM4rMIMjfa8DBT fyZwJ4CiVDvttIXixRiL7ZYvedH2RyrFbiA9LMTly5zyg4p41iafVvxNmzVgU4DtqJ BdmoZLFhVXslKCEnsLuwR8dT47JcTk12O0a6BGvc= Date: Wed, 24 Jul 2019 23:22:54 +0200 From: "pelzflorian (Florian Pelz)" To: Ricardo Wurmus Subject: Re: bug#36786: Warn of AMD GPUs unusable with Guix System Message-ID: <20190724212254.6odl6pfn42y3rytj@pelzflorian.localdomain> References: <20190724145602.vtpnqd6kxexypdmx@pelzflorian.localdomain> <20190724154249.qgd4ganifakxmo2f@pelzflorian.localdomain> <20190724175327.lx2e53it46xnjxz6@pelzflorian.localdomain> <874l3bb6e5.fsf@elephly.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="qj37fyav7bjrqc2l" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <874l3bb6e5.fsf@elephly.net> User-Agent: NeoMutt/20180716 X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 36786 Cc: 36786@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) --qj37fyav7bjrqc2l Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit On Wed, Jul 24, 2019 at 09:05:06PM +0200, Ricardo Wurmus wrote: > Do you think it would be enough if we pointed to h-node.org and > mentioned kernel flags that might be useful in certain generic cases? > Yes, that is a very good suggestion and easiest to do. I did not think about h-node… The manual already points there, but the website should too. Then this bug can be closed, I think. Find attached a patch that mentions the kernel flag in the manual’s Hardware Considerations section. I do not know if a separate section would be better. (The alternative kernel flag “nomodeset” was reported to not work as well, so I did not mention it, see here: ) h-node currently appears to have no information on those video cards. I will take a look at how to add information there later. Regards, Florian --qj37fyav7bjrqc2l Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="0001-doc-Mention-AMD-Radeon-workaround-when-TTYs-are-not-.patch" From e88ee68c09266e1d09d24ff0d1b6ec6a4708841b Mon Sep 17 00:00:00 2001 From: Florian Pelz 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. --- doc/guix.texi | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/doc/guix.texi b/doc/guix.texi index f6d9718f59..b9e18e55c4 100644 --- a/doc/guix.texi +++ b/doc/guix.texi @@ -1879,6 +1879,24 @@ Another useful resource is the @uref{https://www.h-node.org/, H-Node} web site. It contains a catalog of hardware devices with information about their support in GNU/Linux. +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 @node USB Stick and DVD Installation @section USB Stick and DVD Installation -- 2.22.0 --qj37fyav7bjrqc2l--