From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Ludovic Courtès" <ludo@gnu.org>
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:51:25 +0200 [thread overview]
Message-ID: <20200413205125.texkpflm2t2csny2@pelzflorian.localdomain> (raw)
In-Reply-To: <87pncb3yyk.fsf@gnu.org>
On Mon, Apr 13, 2020 at 10:36:19PM +0200, Ludovic Courtès wrote:
> Florian, could it be uvesafb messing with the graphics card?
Yes, maybe, if amdgpu and uvesafb both try to modeset. Apparently
yes, if it did not happen for rc1.
Please try adding a kernel parameter modprobe.blacklist=amdgpu so only
uvesafb is active. (To do that, press the E key in GRUB and move the
cursor to the end of the line starting with linux. Then type
modprobe.blacklist=amdgpu at the line’s end.)
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.
Regards,
Florian
next prev parent reply other threads:[~2020-04-13 20:52 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) [this message]
2020-04-13 20:56 ` Ludovic Courtès
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=20200413205125.texkpflm2t2csny2@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=40599@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=niels@pdlkrft.eu \
/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).