unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: excalamus--- via <help-guix@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: Help Guix <help-guix@gnu.org>
Subject: Re: Boot logs
Date: Mon, 31 May 2021 19:34:17 +0200 (CEST)	[thread overview]
Message-ID: <Mb2UNsV--3-2@tutanota.com> (raw)
In-Reply-To: <87zgwltsk7.fsf@nckx>

Thank you, Tobias.


> All logs should be in /var/log (most notably the ‘messages’ file). Not everything is logged.
>
> What does the console say during the delay?
>
You're correct.  I'm not precisely seeing in 'messages' what I see during boot.  Overall, there is no single culprit; each message merely takes a few seconds each.  The messages that indicate problems are with ntpd and polkit.  There is a kernel TIME_ERROR which is ultimately resolved down the line (when logged in, the correct time is displayed).  During boot, it slowly steps through various checks (which fail at that time).  'messages' does not display anything beyond "kernel reports TIME_ERROR: 0x41: Clock Unsynchronized".  Polkit throws a "critical error" along with a message about being deblobbed.  'messages' only shows that polkitd was started.  I assume the errors from polkit are expected from the libre kernel?  Installing the polkit package appears to have made no difference in the boot message.  



      reply	other threads:[~2021-05-31 17:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-23 13:54 Boot logs excalamus--- via
2021-05-23 14:48 ` Tobias Geerinckx-Rice
2021-05-31 17:34   ` excalamus--- via [this message]

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=Mb2UNsV--3-2@tutanota.com \
    --to=help-guix@gnu.org \
    --cc=excalamus@tutanota.com \
    --cc=me@tobias.gr \
    /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).