From: Miles Fidelman <mfidelman@meetinghouse.net>
To: help-guix@gnu.org
Subject: Re: How can I diagnose a startup failure on a live USB?
Date: Sat, 9 Sep 2017 13:02:33 -0700 [thread overview]
Message-ID: <bc81187d-2b0c-9164-a7a4-0eea14fda2bf@meetinghouse.net> (raw)
In-Reply-To: <20170909195028.GA2455@macbook42.flashner.co.il>
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). That will at least tell
you where things stop working. You can start debugging from there.
A cruder approach: On the system that works, record the sequence of
steps that occur "towards the end." Then work through the configuration
of each of those steps, in turn, for the machine that doesn't work.
(Hunch: There's a subtle mismatch between configuration and the
underlying hardware.)
Miles Fidelman
--
In theory, there is no difference between theory and practice.
In practice, there is. .... Yogi Berra
next prev parent reply other threads:[~2017-09-09 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 13:03 How can I diagnose a startup failure on a live USB? David Seaward
2017-09-09 19:50 ` Efraim Flashner
2017-09-09 20:02 ` Miles Fidelman [this message]
2017-09-11 2:55 ` Maxim Cournoyer
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=bc81187d-2b0c-9164-a7a4-0eea14fda2bf@meetinghouse.net \
--to=mfidelman@meetinghouse.net \
--cc=help-guix@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.
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).