From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keno Goertz Subject: bug#33656: Hard locks on boot (uefi system) via usb Date: Fri, 26 Jul 2019 13:57:12 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:55013) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hr1JR-0005Rp-Js for bug-guix@gnu.org; Fri, 26 Jul 2019 10:35:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hr1JM-0005YG-4q for bug-guix@gnu.org; Fri, 26 Jul 2019 10:35:09 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:34301) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hr1JK-0005WP-8V for bug-guix@gnu.org; Fri, 26 Jul 2019 10:35:06 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hr1JK-0006qU-0i for bug-guix@gnu.org; Fri, 26 Jul 2019 10:35:06 -0400 In-Reply-To: Sender: "Debbugs-submit" Resent-Message-ID: List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: 33656@debbugs.gnu.org I think I just encountered the same bug today. I got stuck at some completely irrelevant kernel message in the boot screen. Couldn't switch to TTY, nada. I worked around it by adding > modprobe.blacklist=amdgpu To the kernel parameters in grub. But the graphical installer still didn't work because the resolution wasn't right, so I also had to add > vga=792 Now, I can see the installer. I hope this resolves the issue for you, too. I also think that these kernel parameters should be included by default, because 1) amdgpu does not work without binary blobs AFAIK, so it can just be blacklisted 2) vga=792 corresponds to 1024×768x24, which is supported by pretty much any screen I've ever encountered. I'm not sure what happens when the screen doesn't support the resolution specified in the vga kernel parameter, but I think it just falls back to the standard, so it shouldn't do any harm