unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: Josselin Poiret <dev@jpoiret.xyz>,
	Antero Mejr <antero@mailbox.org>,
	57760@debbugs.gnu.org
Subject: [bug#57760] [PATCH] system: install: Do not load amdgpu in the installer image.
Date: Thu, 15 Sep 2022 23:56:30 +0200	[thread overview]
Message-ID: <87r10cl2sx.fsf@pelzflorian.de> (raw)
In-Reply-To: <871qscn46w.fsf_-_@gnu.org> (Mathieu Othacehe's message of "Thu,  15 Sep 2022 15:43:35 +0200")

Hi all,

So the issue was that the installer’s display gets stuck at boot when
not blacklisting radeon.  This patch means the same apparently goes for
probably goes for amdgpu?  If there are amdgpu systems that cannot boot
the installer otherwise, this is enough reason for this patch and this
patch is a good idea.

What Denis 'GNUtoo' Carikli wrote at
<https://issues.guix.gnu.org/36786#9> indicates that non-3d graphics
works for some radeon/amdgpu GPUs, because the code that prevents
booting could be removed from linux-libre for these GPUs.  If so (and it
didn’t work for one GPU of mine even though it is listed as freed at
libreplanet), these amdgpu ones would get a lower screen resolution from
uvesafb if this patch were added.  But it is worth the trade-off.

However,

Mathieu Othacehe <othacehe@gnu.org> writes:
> the radeon, amdgpu, r128 and mga DRM drivers are probably relying on
> firmware loading. So we should maybe extend this patch and add the
> latter two drivers, even though they are supporting really old
> hardware.

Back then when we blacklisted radeon, we chose to wait for a report of
amdgpu not working instead of adding amdgpu to the blacklist right away.
Maybe booting is not broken there?

Regards,
Florian




  reply	other threads:[~2022-09-15 21:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13  2:42 [bug#57760] [PATCH] system: install: Do not load amdgpu in the installer image Antero Mejr via Guix-patches via
2022-09-14  7:37 ` Mathieu Othacehe
2022-09-14 10:06   ` Josselin Poiret via Guix-patches via
2022-09-15 13:43     ` Mathieu Othacehe
2022-09-15 21:56       ` pelzflorian (Florian Pelz) [this message]
2022-09-16  8:16         ` bug#57760: " Mathieu Othacehe

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=87r10cl2sx.fsf@pelzflorian.de \
    --to=pelzflorian@pelzflorian.de \
    --cc=57760@debbugs.gnu.org \
    --cc=antero@mailbox.org \
    --cc=dev@jpoiret.xyz \
    --cc=othacehe@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).