unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Kete Foy <kete@ninthfloor.org>
Cc: help-guix@gnu.org
Subject: Re: Wrong system time
Date: Mon, 13 Jun 2016 16:35:25 -0400	[thread overview]
Message-ID: <20160613203525.GA11960@jasmine> (raw)
In-Reply-To: <fe1fbe01-e891-f221-6d66-869e2dc635a7@ninthfloor.org>

On Sun, Jun 05, 2016 at 05:48:52PM +0000, Kete Foy wrote:
> Hello, I am trying to install GuixSD, and my system time is much older
> than the present; so the system won't install. It tells me to check the
> system clock.
> 
> Unusual distinction—I chose to encrypt the system. Libreboot is supposed
> to be able to boot an encrypted system. If it makes a difference, my
> config.scm has (bootloader (grub-configuration (device
> "/dev/mapper/cryptsys"))). In the Guix manual, I noticed a section about
> encrypted systems that looked like it was meant for after the
> installation, and Libreboot has its own instructions for the initial
> boot and setting up subsequent boots: decrypting to find the kernel in
> /boot.

I seem to remember an issue with GuixSD on Libreboot x200 machines where
the system clock was set to the Unix epoch. Is that what's going on
here? If so, can you search the guix-devel and bug-guix archives for
more info?

  parent reply	other threads:[~2016-06-13 20:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-05 17:48 Wrong system time Kete Foy
2016-06-05 21:11 ` Grub with encrypted system " Kete Foy
2016-06-13 20:35 ` Leo Famulari [this message]
2016-06-14  1:48   ` Kete Foy
2016-06-14  2:17     ` Leo Famulari
2016-06-14  8:04       ` Ludovic Courtès
2016-07-10 21:26         ` Chris Marusich
2016-07-10 22:39           ` Kete Foy
2016-07-10 22:42             ` Leo Famulari
2016-07-11 11:52               ` Kete Foy
2016-07-11 15:59                 ` Leo Famulari

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=20160613203525.GA11960@jasmine \
    --to=leo@famulari.name \
    --cc=help-guix@gnu.org \
    --cc=kete@ninthfloor.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).