From: RAUL H C LOPES <rlopes@cern.ch>
To: Marius Bakke <mbakke@fastmail.com>, 37492@debbugs.gnu.org
Subject: bug#37492: GUIXSD 1.0.1 install error
Date: Fri, 27 Sep 2019 23:50:40 +0100 [thread overview]
Message-ID: <bb5ec33e-692a-c03c-7cad-80e63a492acc@cern.ch> (raw)
In-Reply-To: <874l0xa1mx.fsf@devup.no>
Hi Marius,
I've managed to install GuixSD by chossing msdos instead of gpt.
Coincidence? Is the gpt setup tested?
I've running the system for a few days.
I need now a good manual> I'm suffering for:
- reconfigure stuff that is usually in /etc, like /etc/ssh/sshd_config;
- running a make on an open source project who looks for linux libs
where debian would find them.
Regards, Raul
On 27/09/2019 22:08, Marius Bakke wrote:
> Hello Raul,
>
> RAUL H C LOPES <rlopes@cern.ch> writes:
>
>> Hi,
>>
>>
>> I've emailed a few hours ago about an error in the GUIXSD installer. It
>> might be relevant that I was doing encrypted home and root. Very likely
>> unconnected.
>>
>>
>> I've just tried a new install without encryption. A new failure:
>>
>> .../grub-install- error: efibootmgr failed to register the boot
>> entry: Input/output error.
> This means that GRUB failed to update the UEFI variables on your system.
> Are you using the generated configuration file or a custom one?
>
> The most likely reason for this error is that you are using
> 'grub-efi-bootloader' on a non-EFI system. Changing to
> 'grub-bootloader' should solve it in that case.
>
> HTH,
> Marius
next prev parent reply other threads:[~2019-09-27 23:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 17:21 bug#37492: GUIXSD 1.0.1 install error RAUL H C LOPES
2019-09-23 21:52 ` RAUL H C LOPES
2019-09-27 21:08 ` Marius Bakke
2019-09-27 22:50 ` RAUL H C LOPES [this message]
2019-09-29 12:00 ` Marius Bakke
2019-10-03 21:46 ` RAUL H C LOPES
2019-10-17 11:26 ` RAUL H C LOPES
2019-10-17 20:35 ` Marius Bakke
2022-07-12 14:50 ` 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=bb5ec33e-692a-c03c-7cad-80e63a492acc@cern.ch \
--to=rlopes@cern.ch \
--cc=37492@debbugs.gnu.org \
--cc=mbakke@fastmail.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).