From: "Néstor Arocha" <n@nestorarocha.com>
To: 53459@debbugs.gnu.org
Subject: bug#53459: Update: Tried non efi, independent boot partition and custom boot entry in debian
Date: Sun, 23 Jan 2022 11:29:16 +0000 [thread overview]
Message-ID: <Ye08DKgbQmswMaR2@bananaboat> (raw)
In-Reply-To: <Yex4XUd0rJmAFTA7@bananaboat>
Hi,
I forgot to mention that I am working with current stable guix 1.3.0
I also tried a few things:
* Manual installation doesn't trigger the error at all, but the end result is that it won't boot like before
* an independent boot partition on top of a shared /boot/efi didn't make any difference
* Trying to install guix with the boot-grub loader rather than efi didn't work at all and the boot installed errored
But I am happy to say that (after standard guix install) adding the entry in grub manually in debian
did work:
```
menuentry "Guix" {
insmod part_gpt
insmod chain
set root='(hd0,gpt1)'
chainloader /EFI/Guix/grubx64.efi
}
```
and then running update-grub
For some reason it asks for the encryption password twice.
next prev parent reply other threads:[~2022-01-23 16:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 21:34 bug#53459: error while installing with existing partitions Néstor Arocha
2022-01-23 11:29 ` Néstor Arocha [this message]
2022-01-23 16:37 ` bug#53459: Update: Tried non efi, independent boot partition and custom boot entry in debian Néstor Arocha
2022-01-23 16:59 ` bug#53459: Tried non efi boot, independent boot partition and boot entry from another linux n
2022-01-23 17:51 ` bug#53459: error while installing with existing partitions Maxime Devos
[not found] ` <handler.s.C.164296031827448.transcript@debbugs.gnu.org>
2022-01-23 17:59 ` bug#53459: Processed (with 1 errors): " Maxime Devos
2022-01-23 17:56 ` Maxime Devos
2022-01-24 10:05 ` Nestor Arocha
2022-11-12 13:49 ` bug#53459: installer: uuid->string failure backtrace (again) Mathieu Othacehe
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=Ye08DKgbQmswMaR2@bananaboat \
--to=n@nestorarocha.com \
--cc=53459@debbugs.gnu.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.
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).