From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maxim Cournoyer Subject: Re: How can I diagnose a startup failure on a live USB? Date: Sun, 10 Sep 2017 22:55:50 -0400 Message-ID: <87vakq3pvt.fsf@gmail.com> References: <1504875804.3275.1.camel@gmail.com> <20170909195028.GA2455@macbook42.flashner.co.il> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33602) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1drEtC-0000JW-0O for help-guix@gnu.org; Sun, 10 Sep 2017 22:55:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1drEt7-00082D-4M for help-guix@gnu.org; Sun, 10 Sep 2017 22:55:58 -0400 Received: from mail-io0-x235.google.com ([2607:f8b0:4001:c06::235]:34939) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1drEt6-00081w-VE for help-guix@gnu.org; Sun, 10 Sep 2017 22:55:53 -0400 Received: by mail-io0-x235.google.com with SMTP id g32so306600ioj.2 for ; Sun, 10 Sep 2017 19:55:52 -0700 (PDT) In-Reply-To: (Miles Fidelman's message of "Sat, 9 Sep 2017 13:02:33 -0700") List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Miles Fidelman Cc: help-guix@gnu.org Miles Fidelman writes: > On 9/9/17 12:50 PM, Efraim Flashner wrote: > >> On Fri, Sep 08, 2017 at 03:03:24PM +0200, David Seaward wrote: >>> Hi all, >>> >>> I am trying to run Guix SD from a live USB on two machines. On machine >>> A this works: I can select "linux-libre" from GRUB and the startup >>> process runs, ending with a prompt on TTY 1 and documentation on TTY 2. >>> >>> On machine B, the startup process runs but towards the end (ssh- >>> keygen... ncsd...) the screen goes black and I can't switch between >>> TTYs. >>> >>> How can I diagnose the cause of this problem? Even enough to report an >>> error message. >>> >>> > Perhaps see if there's a way to set more verbose logging with a boot > parameter, and find a way to capture the console messages (e.g., use a > serial console, and a software TTY emulator).=C2=A0 That will at least te= ll > you where things stop working.=C2=A0 You can start debugging from there. +1. You could also probably get by via SSH. Check the output of `dmesg' from there. I had a system recently which would blackscreen on me at the login screen. The issue was related to the amdgpu driver (nothing to do with GuixSD though, that was on Debian). Good luck! Maxim