all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: 1.1.0rc1 available for test!
Date: Fri, 10 Apr 2020 14:19:07 +0200	[thread overview]
Message-ID: <87h7xr3550.fsf@gmail.com> (raw)
In-Reply-To: <87lfn3mtx7.fsf@gmail.com>

Hi Mathieu,

Thanks for getting back to me!

Mathieu Othacehe <m.othacehe@gmail.com> writes:

> Hello Alex,
>
> Thanks for your feedback!
>
>> Then the screen flashes back to the beginning of the installer.  Running
>> through the process again results in the disk drive not being available
>> for partitioning.
>
> Are you running the installer on a VM or on real hardware?

Real hardware.

> Could you try the following steps:
>
> * Run the installation until it fails and restart.
> * Press Ctrl-Alt-2.
> * Type "sendkey ctrl-alt-f3".
> * Then press Ctrl-Alt-1 and Enter.
> * Check if there is a /tmp/last-installer-error file and, if yes, report
> its content.

This I could not do: Ctrl-Alt-2 doesn't do anything, but I imagine you
meant Ctrl-Alt-f2?  That takes me to the manual.

However, once the installer reloads, I can hit Ctrl-Alt-f3 and Enter to
get to a prompt.

There is no /tmp/last-installer-error file :-(

I did check /var/log/debug.  There I can trace the configuration
process.

After "running form #<newt-form b7d4c0> ("Configuration file") with 0
clients" I get:
…Service cow-store has been started.
…Service cow-store has been stopped.
…Service guix-daemon has been stopped.
…Service guix-daemon has been started.
…Umounted /remove successfully.
…unmounting "/mnt"
…closing LUKS entry "cryptroot"
…running step 'locale'

The last presumably is the installer restarting.

Hth,

Alex

>
> Thanks,
>
> Mathieu

  reply	other threads:[~2020-04-10 12:19 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-09 20:51 1.1.0rc1 available for test! Ludovic Courtès
2020-04-09 21:33 ` Danny Milosavljevic
2020-04-10  1:56 ` pelzflorian (Florian Pelz)
2020-04-10 10:38   ` Ludovic Courtès
2020-04-10 12:06   ` Mathieu Othacehe
2020-04-10 14:35   ` pelzflorian (Florian Pelz)
2020-04-10 14:47     ` pelzflorian (Florian Pelz)
2020-04-13 18:12       ` pelzflorian (Florian Pelz)
2020-04-10  3:20 ` Vagrant Cascadian
2020-04-10 10:29   ` Ludovic Courtès
2020-04-10 11:24 ` Alex Sassmannshausen
2020-04-10 12:01   ` Mathieu Othacehe
2020-04-10 12:19     ` Alex Sassmannshausen [this message]
2020-04-10 12:07   ` Alex Sassmannshausen
2020-04-10 12:17     ` Mathieu Othacehe
2020-04-10 13:11       ` Alex Sassmannshausen
2020-04-10 13:53       ` Mathieu Othacehe
2020-04-10 14:19         ` Ludovic Courtès
2020-04-10 16:02           ` Alex Sassmannshausen
2020-04-10 15:42 ` Alex Sassmannshausen
2020-04-10 22:38   ` Ludovic Courtès
2020-04-11  9:11     ` alex sassmannshausen
2020-04-11 13:16       ` Amin Bandali
2020-04-11 13:48         ` Pierre Neidhardt
2020-04-10 15:45 ` Alex Sassmannshausen
2020-04-11 10:51 ` Vincent Legoll
2020-04-11 22:26   ` Ludovic Courtès
2020-04-12  6:43     ` Vincent Legoll
2020-04-13 10:50       ` Ludovic Courtès
2020-04-13 11:46         ` Vincent Legoll
2020-04-13 12:36         ` Vincent Legoll
2020-04-13 16:14         ` Vincent Legoll
2020-04-13 20:24           ` Ludovic Courtès

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h7xr3550.fsf@gmail.com \
    --to=alex.sassmannshausen@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=m.othacehe@gmail.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.