From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: bug#37492: GUIXSD 1.0.1 install error Date: Fri, 27 Sep 2019 23:08:06 +0200 Message-ID: <874l0xa1mx.fsf@devup.no> References: <4b7c7353-c7b0-8ced-c71d-0d4396096c74@cern.ch> <4d9c1047-b32c-1603-ca32-da57c3326e21@cern.ch> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:57356) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iDxU7-0003QY-HB for bug-guix@gnu.org; Fri, 27 Sep 2019 17:09:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iDxU6-0004Xo-9G for bug-guix@gnu.org; Fri, 27 Sep 2019 17:09:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:39941) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iDxU6-0004Xb-1q for bug-guix@gnu.org; Fri, 27 Sep 2019 17:09:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iDxU5-0003uM-Rd for bug-guix@gnu.org; Fri, 27 Sep 2019 17:09:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <4d9c1047-b32c-1603-ca32-da57c3326e21@cern.ch> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: RAUL H C LOPES , 37492@debbugs.gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello Raul, RAUL H C LOPES writes: > Hi, > > > I've emailed a few hours ago about an error in the GUIXSD installer. It=20 > might be relevant that I was doing encrypted home and root. Very likely=20 > unconnected. > > > I've just tried a new install without encryption. A new failure: > > =C2=A0 .../grub-install- error: efibootmgr failed to register the boot=20 > 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 --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl2OejYACgkQoqBt8qM6 VPpV9gf/UwCID30X8al5II1poa+nTK8hIE7MPSQue4LD5PLnwWe5UGCWI6t8KCGL AYpCEmTgkDLWLG4qkIrekv85vGRKU/N5069khRtIOppuQa2zrr2y4nIwLMEABaRM /xGsMzZC3z+ENq9l/kiVq5/qFGZ0Bp4ahoQfDpB2I3o2zmDF1BB7RYLmYNj8zZ+o GvZ2ovYy9o2szQe9kIgVCjuysjHs1Y3pmt1rthNLBNU2+t7Z/6nDv6EFTRMrmmjp IiL4ydZjyIuNHWB4DjDhoBSoV3IUEFiDg7CBfOA7jU2gB3BvsL568O3vDgYazI4y 4kUzLYJ28CyGFkwgbI76fZFU5hEEYg== =HI34 -----END PGP SIGNATURE----- --=-=-=--