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: 40599@debbugs.gnu.org, Niels Felsted <niels@pdlkrft.eu>
Subject: bug#40599: 1.1.0rc2 i686 gui install unreadable
Date: Mon, 13 Apr 2020 22:56:41 +0200	[thread overview]
Message-ID: <875ze33y0m.fsf@gnu.org> (raw)
In-Reply-To: <20200413205125.texkpflm2t2csny2@pelzflorian.localdomain> (pelzflorian@pelzflorian.de's message of "Mon, 13 Apr 2020 22:51:25 +0200")

Hi Florian,

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

> I wonder whether it’s better to
>
> 1) revert uvesafb and break other systems again, including other AMD
> ones,
>
> 2) add modprobe.blacklist=amdgpu to the default kernel parameters,
> although I’m not sure if uvesafb can replace amdgpu for every screen.

It’s a tough choice.  We know what we’d lose with option #1, but we
don’t really know what we’d lose with option #2, right?

Maybe wait and see if passing “modprobe.blacklist=amdgpu” works on
Neils’ machine?

Ludo’.

  reply	other threads:[~2020-04-13 20:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13 14:02 bug#40599: 1.1.0rc2 i686 gui install unreadable Niels Felsted
2020-04-13 20:36 ` Ludovic Courtès
2020-04-13 20:51   ` pelzflorian (Florian Pelz)
2020-04-13 20:56     ` Ludovic Courtès [this message]
2020-04-14  0:48       ` pelzflorian (Florian Pelz)
2020-04-14 13:06   ` Niels Felsted
2020-04-14 13:22     ` pelzflorian (Florian Pelz)
2020-04-14 15:42       ` Ludovic Courtès
2020-04-14 18:20         ` Niels Felsted
2020-04-14 18:48           ` pelzflorian (Florian Pelz)
2020-04-14 20:01             ` Ludovic Courtès
2020-04-13 21:06 ` pelzflorian (Florian Pelz)
2020-04-13 21:48   ` 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=875ze33y0m.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=40599@debbugs.gnu.org \
    --cc=niels@pdlkrft.eu \
    --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).