Guix won't boot after installation with fully encrypted disk

  • Open
  • quality assurance status badge
Details
6 participants
  • david larsson
  • Josselin Poiret
  • Giovanni Biscuolo
  • Ludovic Courtès
  • pelzflorian (Florian Pelz)
  • Reg
Owner
unassigned
Submitted by
Reg
Severity
normal
R
(address . bug-guix@gnu.org)
138779ab-830b-32a9-e64a-e1fccabf90ab@disroot.org
Hi!

Note: There was some discussion about this on IRC a couple of weeks ago.

Guix won't boot on my ThinkPad T430 after an installation with fully
encrypted disk:

* First, at the end of the installation, I'm getting the following error
message multiple times: "device-mapper: remove ioctl on cryptroot
failed: Device or resource busy"


* On boot, I am being prompted for the encryption key. So far so good.
The Grub menu is then displayed and disappears after a few seconds – as
it should – after which the computer is stuck on the Grub background image:


* Here are the Grub commands:


* As a test, I added an echo command at the very end. It got displayed.
* It happens on both 1.0.0 and 1.0.1.
* It happens both with and without a separate home partition.
* It happens on the two SSDs I had at hand.
* It does not happen if only the home partition is encrypted.
* I also tested this in a virtual machine. The issue did NOT happen.

Thanks,
Reg
Attachment: file
Attachment: stuck.jpg
Attachment: grub_commands.png
L
L
Ludovic Courtès wrote on 24 May 2019 19:00
(name . Reg)(address . reg@disroot.org)(address . 35875@debbugs.gnu.org)
87pno7rdmn.fsf@gnu.org
Hello,

Reg <reg@disroot.org> skribis:

Toggle quote (6 lines)
> Note: There was some discussion about this on IRC a couple of weeks ago.
>
> Guix won't boot on my ThinkPad T430 after an installation with fully encrypted disk:
>
> * First, at the end of the installation, I'm getting the following error message multiple times: "device-mapper: remove ioctl on cryptroot failed: Device or resource busy"

These messages are annoying but really harmless.

Toggle quote (2 lines)
> * On boot, I am being prompted for the encryption key. So far so good. The Grub menu is then displayed and disappears after a few seconds – as it should – after which the computer is stuck on the Grub

Weird.

Does your compute have an AMD graphics card that could lead the kernel
(KMS) to wreck havoc during initialization?

Did you have hardware-related problems with other free GNU/Linux distros
on this machine before?

Thanks,
Ludo’.
G
G
Giovanni Biscuolo wrote on 25 May 2019 10:37
(name . Reg)(address . reg@disroot.org)(address . 35875@debbugs.gnu.org)
877eaf3p6r.fsf@roquette.mug.biscuolo.net
Hello Reg,

Ludovic Courtès <ludo@gnu.org> writes:

[...]

Toggle quote (7 lines)
>> On boot, I am being prompted for the encryption key. So far so
>> good. The Grub menu is then displayed and disappears after a few
>> seconds – as it should – after which the computer is stuck on the
>> Grub
>
> Weird.

The strange behaviour here is that you reported it does not happen if
only the home partition is encrypted: if this is true this could not be
a GPU issue.

I'm going to test a full encrypted root install on bare metal and will
report back on this

Toggle quote (3 lines)
> Does your compute have an AMD graphics card that could lead the kernel
> (KMS) to wreck havoc during initialization?

AFAIU ThinkPad T430 could come with an additional "NVIDIA NVS 5400M" GPU
[1] that is very Linux _unfriendly_; you can check this by booting
your machine as detailed below and doing a "lspci -nnn | grep VGA"

Anyway, to check if GPU is the problem here could you please add
"modprobe.blacklist=radeon" [2] (or vga=791 if this does not work [3])
to the "linux" kernel arguments and report back the error messages, if
any?

To add that kernel argument, you have to enter edit mode in Grub by
pressing "e" before the timeout (or press ESC to stop the timeout) and
edit the "linux" Grub line

If blacklisting radeon module works for you, you should add it to your
(operating-system ...) definition to make it permanent, something like:

(kernel-arguments '("modprobe.blacklist=radeon"))

HTH! Gio'.

[...]



[2] Grub configuration in the installarion ISO have that parameter

[3] should not be the case since the installer worked for you without
that kernel argument


--
Giovanni Biscuolo

Xelera IT Infrastructures
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEERcxjuFJYydVfNLI5030Op87MORIFAlzo/rwACgkQ030Op87M
ORKYjw/9EsD04fKP/jLXrUYn0Df4I2H5aucxUhOV1vz/TG5FOtOV+8YIGMUtG4V5
XuFgmnUYUlBXj8V+4lAkLlyEFtEkfmCObEGLp+6TTCTowPe4Z9yJFk6FZe3GCNlY
9ByJ8mHCviJ0Ti01w5j+cH3MXGgngaTPg12H3u4AKVVkl2qunfX9qQSCAP0k4TwG
KB+fhU8xPSBGZHbyHhdIGnLEuPfQU7PVSUrP9DEVA/msQ0OaMDtsXjAg8eDY6qhB
UfXjN4/dTPFGI4pnMc7ZsZddVgv0Yn072nWoO78EGHSJ9s9impIuxOlHXjOu7yDS
UtAsPxD1pTS0sWrVSqGApw86IyIjU7c42t8Tpu63DlR4X6/71EyidPmGWe5KXGhU
MlvR0W56c4HSdtMVoKKpeQuWlhlmLvdnYDS8z/wJOVNzWnQ9B3ph9d0h6VYl0Q4C
TXlxa7rwbpucaqqGqH3KMYVGTAiIgy4xYr4v3nPZcc2nRaIEAQRhk4oiYfwEUzQB
RPTGtrdKz49wMfRLBa76b2GBdQsD97kAuqUuNS/ho+uD2tQT8iUATwVo5UIbqcy1
h/jxQhrhdJ8JS0TbpQSb1g89e5FjmVOPtodkAanjkw5k/TR89s2K81/Da6et7Y+A
hdLiq7YTmWr/qwpdCuAmpY9pqEP+R/lJ6mirU2M/m11Z6DoZ2HQ=
=YtgW
-----END PGP SIGNATURE-----

R
(address . 35875@debbugs.gnu.org)
bfe65a2b-bbcb-54aa-d5ee-0bb3afa91caa@disroot.org
Hi Ludovic and Giovanni,

Toggle quote (2 lines)
>> Does your compute have an AMD graphics card that could lead the kernel
>> (KMS) to wreck havoc during initialization?
No AMD but...
Toggle quote (3 lines)
> AFAIU ThinkPad T430 could come with an additional "NVIDIA NVS 5400M" GPU
> [1] that is very Linux _unfriendly_; you can check this by booting
> your machine as detailed below and doing a "lspci -nnn | grep VGA"
...indeed:

$ lspci -nnn|grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core
processor Graphics Controller [8086:0166] (rev 09)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108M [NVS
5400M] [10de:0def] (rev a1)
Toggle quote (4 lines)
> Anyway, to check if GPU is the problem here could you please add
> "modprobe.blacklist=radeon" [2] (or vga=791 if this does not work [3])
> to the "linux" kernel arguments and report back the error messages, if
> any?
No error message & still the same issue with both these arguments.

Toggle quote (2 lines)
> Did you have hardware-related problems with other free GNU/Linux distros
> on this machine before?
I've been using Parabola on this computer for several years without
problems, but none of my disks were encrypted.

Thanks for the support,
Reg
Attachment: signature.asc
G
G
Giovanni Biscuolo wrote on 29 May 2019 18:24
(name . Reg)(address . reg@disroot.org)(address . 35875@debbugs.gnu.org)
87o93l1b65.fsf@roquette.mug.biscuolo.net
Hello Reg,

Reg <reg@disroot.org> writes:

[...]

Toggle quote (6 lines)
>> Anyway, to check if GPU is the problem here could you please add
>> "modprobe.blacklist=radeon" [2] (or vga=791 if this does not work [3])
>> to the "linux" kernel arguments and report back the error messages, if
>> any?
> No error message & still the same issue with both these arguments.

OK so it seems this is not related to your GPU but to disk encryption

I cannot reproduce your very same situation: I'm using a manual
partition scheme (not the guided one) since I want to presenve a couple
partitions on my HD

I was able to install and boot Guix on an encrypted BTRFS partition with
no issues, this is what the installer configured for bootloader,
mapped-devices and file-systems:

Toggle snippet (23 lines)
(bootloader
(bootloader-configuration
(bootloader grub-efi-bootloader)
(target "/boot/efi")
(keyboard-layout keyboard-layout)))
(mapped-devices
(list (mapped-device
(source
(uuid "228371e9-9cd7-4bb5-8976-d65029892b8e"))
(target "guix")
(type luks-device-mapping))))
(file-systems
(cons* (file-system
(mount-point "/")
(device "/dev/mapper/guix")
(type "btrfs")
(dependencies mapped-devices))
(file-system
(mount-point "/boot/efi")
(type "vfat"))
%base-file-systems))

I first had to insert the LUKS encryption key to let Grub start, then I
had to enter the same key after Grub booted

Toggle quote (5 lines)
>> Did you have hardware-related problems with other free GNU/Linux distros
>> on this machine before?
> I've been using Parabola on this computer for several years without
> problems, but none of my disks were encrypted.

Please are you able to connect to ssh to your laptop during installation
(before rebooting) [1] and paste here the content of /mnt/etc/config.scm
generated by the installer?

Thanks! Gio'.

[1] you can switch to a console with CTRL-ALT-F3, set the root password
(passwd) and "herd start ssh-daemon"

--
Giovanni Biscuolo

Xelera IT Infrastructures
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEERcxjuFJYydVfNLI5030Op87MORIFAlzusjMACgkQ030Op87M
ORJ1sA//bu33ov+0kr1iFiCV1QUQ1k4qVe4Nkz7hP2XC4zFG9kbVAG/4LILyIoSZ
BYV4ZgiAghKq4lVP5YhX14wbkHRGkWxtTXsnQLbqMsv8TSx8H3bZVauu6q5AzSwI
H/yea8wUknyv8FYxXlyM/k5Hh9V3s1BW6XWuqatBZIdSZ1Ov5lnww+ZeQs0tzSsA
DpIHQn3Wh87/WCoymoDyWD81u1Nwxh62twvPG6DEZ01WPYmKLOiwUqAosxwJsQmn
zWtSz2HuehYR1iFUZ8HArUJcPSX9iuSsU+6z+8barHeEoG5l3orUPK0o5PAtbI1e
ms8oe3KF8/vPXxgzpvXsu8rVljaTctJbIx/umntzFAye/+Kfz3jDZqVTcDHdU6hI
iPqLBpkPFB1o+bo3ZnRIyWtvBBnldbe6W8rqEXqHqJaFCIwm5TM9oZpP8Szf44m/
rwZkA8gxt1ETOv3xgZBzL75MWHXuWCTfiyggTAGMiYILB3epAz55kK/P9iZ6Ab6S
f6O3T2Q8qXZjonjBmI3gAK5jZb3QMbPJD1YGHDhL/dI3FxBCsY9l4mBmH5f5wkBM
IWZcCtqoT/Gv5H1lnRRfuNnn5Y0nHrBKgn/CfiyS6dUyBdlb23hqG8N2Lzoqd6Fh
fdLduXcQRhm2uGO9i5EA64Y1JtRCeAfSK5o+5vnT2oOlcQKlfGk=
=J0dv
-----END PGP SIGNATURE-----

R
(name . Giovanni Biscuolo)(address . g@xelera.eu)(address . 35875@debbugs.gnu.org)
a5b8aed1-98ed-d733-3a95-5b0ccfbcc136@disroot.org
Hi Giovanni,

Here's the content of /mnt/etc/config.scm:

Toggle snippet (57 lines)
;; This is an operating system configuration generated
;; by the graphical installer.

(use-modules (gnu))
(use-service-modules desktop networking ssh xorg)

(operating-system
(locale "en_US.utf8")
(timezone "Europe/Stockholm")
(keyboard-layout (keyboard-layout "fr" "mac"))
(bootloader
(bootloader-configuration
(bootloader grub-efi-bootloader)
(target "/boot/efi")
(keyboard-layout keyboard-layout)))
(mapped-devices
(list (mapped-device
(source
(uuid "e613d30e-c46f-4cb3-8bde-409009be5e2e"))
(target "cryptroot")
(type luks-device-mapping))))
(file-systems
(cons* (file-system
(mount-point "/boot/efi")
(device (uuid "2E91-4865" 'fat32))
(type "vfat"))
(file-system
(mount-point "/")
(device "/dev/mapper/cryptroot")
(type "ext4")
(dependencies mapped-devices))
%base-file-systems))
(host-name "xiu")
(users (cons* (user-account
(name "reg")
(comment "Reg")
(group "users")
(home-directory "/home/reg")
(supplementary-groups
'("wheel" "netdev" "audio" "video")))
%base-user-accounts))
(packages
(append
(list (specification->package "i3-wm")
(specification->package "nss-certs"))
%base-packages))
(services
(append
(list (service gnome-desktop-service-type)
(service openssh-service-type)
(set-xorg-configuration
(xorg-configuration
(keyboard-layout keyboard-layout))))
%desktop-services)))


Thanks for the support,
Reg

Am 2019-05-29 um 18:24 schrieb Giovanni Biscuolo:
Toggle quote (61 lines)
> Hello Reg,
>
> Reg <reg@disroot.org> writes:
>
> [...]
>
>>> Anyway, to check if GPU is the problem here could you please add
>>> "modprobe.blacklist=radeon" [2] (or vga=791 if this does not work [3])
>>> to the "linux" kernel arguments and report back the error messages, if
>>> any?
>> No error message & still the same issue with both these arguments.
> OK so it seems this is not related to your GPU but to disk encryption
>
> I cannot reproduce your very same situation: I'm using a manual
> partition scheme (not the guided one) since I want to presenve a couple
> partitions on my HD
>
> I was able to install and boot Guix on an encrypted BTRFS partition with
> no issues, this is what the installer configured for bootloader,
> mapped-devices and file-systems:
>
> --8<---------------cut here---------------start------------->8---
> (bootloader
> (bootloader-configuration
> (bootloader grub-efi-bootloader)
> (target "/boot/efi")
> (keyboard-layout keyboard-layout)))
> (mapped-devices
> (list (mapped-device
> (source
> (uuid "228371e9-9cd7-4bb5-8976-d65029892b8e"))
> (target "guix")
> (type luks-device-mapping))))
> (file-systems
> (cons* (file-system
> (mount-point "/")
> (device "/dev/mapper/guix")
> (type "btrfs")
> (dependencies mapped-devices))
> (file-system
> (mount-point "/boot/efi")
> (type "vfat"))
> %base-file-systems))
> --8<---------------cut here---------------end--------------->8---
>
> I first had to insert the LUKS encryption key to let Grub start, then I
> had to enter the same key after Grub booted
>
>>> Did you have hardware-related problems with other free GNU/Linux distros
>>> on this machine before?
>> I've been using Parabola on this computer for several years without
>> problems, but none of my disks were encrypted.
> Please are you able to connect to ssh to your laptop during installation
> (before rebooting) [1] and paste here the content of /mnt/etc/config.scm
> generated by the installer?
>
> Thanks! Gio'.
>
> [1] you can switch to a console with CTRL-ALT-F3, set the root password
> (passwd) and "herd start ssh-daemon"
>
Attachment: signature.asc
G
G
Giovanni Biscuolo wrote on 30 May 2019 14:10
(name . Reg)(address . reg@disroot.org)(address . 35875@debbugs.gnu.org)
875zps16tf.fsf@roquette.mug.biscuolo.net
Hello Reg,

Reg <reg@disroot.org> writes:

[...]

Toggle quote (23 lines)
> (bootloader
> (bootloader-configuration
> (bootloader grub-efi-bootloader)
> (target "/boot/efi")
> (keyboard-layout keyboard-layout)))
> (mapped-devices
> (list (mapped-device
> (source
> (uuid "e613d30e-c46f-4cb3-8bde-409009be5e2e"))
> (target "cryptroot")
> (type luks-device-mapping))))
> (file-systems
> (cons* (file-system
> (mount-point "/boot/efi")
> (device (uuid "2E91-4865" 'fat32))
> (type "vfat"))
> (file-system
> (mount-point "/")
> (device "/dev/mapper/cryptroot")
> (type "ext4")
> (dependencies mapped-devices))
> %base-file-systems))

[...]

On a test machine I practically have the very same bootloader,
mapped-device and file-systems configuration and I've no problems
booting

Are you sure your laptop does not boot at all? I mean: can't you switch
to a different tty (CTRL-ALT-F2) and see a console login?

I'm out of ideas here, sorry

HTH! Gio'.

--
Giovanni Biscuolo

Xelera IT Infrastructures
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEERcxjuFJYydVfNLI5030Op87MORIFAlzvyD0ACgkQ030Op87M
ORLswA/5AXW0/azVpZf/x07eIhqW8/MrcgsuooUeGy9Zt1ssaMre7qbTzHs/QHH0
Ev30Ku1zN3VoYV9PatfQmjVTvi1eSyT95nmGgJWwetpBLwuxp5U8lTawqxs/a9VU
9e5F4ehsDL7o9snRAoQYkASldkOMP0M9lVAhcoHANhft3SfwBw4b9uW5V2X3badD
ypT4GyOpbmcF8yi2DupohNLXeAZNPwQh/C174+A0Qznutjv5uHmetZBaC7JeoX3R
vqLt8r3ddlJDTZFOf/w4JZ+F7S+RX05h/hqDeBkejUcdGNI3awD8UHRNSTL3DYCT
QZwI0AjDnXupnp/nuZmAb12qF/v/bN1gq9VwLqWl8b0vVb6MaPg5AvjjycI8tt7k
DcUP5ZXwABVTUhfd0Sl6XUwVRdgMVdjjdnwdcFjeVIWrBh6Qu2aSnNEufu2jOK6l
hOkPiKdDpq7H70Ul3nI+rDcnclQIPgq1OznblcdeqBl3Xy4WS8xIttg2Mud1KT1c
cP/AxVRgQzN4kgWxZ/FE47H6IAymfHEdvGW90NfNXqMUSA7JZdLJCb8h2M0TAfpe
UOrUxsCku65S6hjYxYSJ10HeuO2DMaCdHNKkw9E8gI+0VAmqvg7ZQtZpMlnP8X4J
OT9FV4vgRStLD8E7i+tzvuKdWPx4kT8CNj4y9k6m5RWQH37Uoag=
=IeYd
-----END PGP SIGNATURE-----

R
(name . Giovanni Biscuolo)(address . g@xelera.eu)(address . 35875@debbugs.gnu.org)
0bd6472d-2502-8dc0-5ffa-a32d53c55be1@disroot.org
Hi,

On 2019-05-30 14:10, Giovanni Biscuolo wrote:
Toggle quote (2 lines)
> Are you sure your laptop does not boot at all? I mean: can't you switch
> to a different tty (CTRL-ALT-F2) and see a console login?
Nothing happens when I press CTRL-ALT-F2, F3, ...
The only key combination that has any effect is CTRL-ALT-DEL.

Thanks for the support,
Reg
Attachment: signature.asc
L
L
Ludovic Courtès wrote on 1 Jun 2019 00:01
(name . Reg)(address . reg@disroot.org)
87d0jyl1w9.fsf@gnu.org
Hi Reg,

Reg <reg@disroot.org> skribis:

Toggle quote (6 lines)
> On 2019-05-30 14:10, Giovanni Biscuolo wrote:
>> Are you sure your laptop does not boot at all? I mean: can't you switch
>> to a different tty (CTRL-ALT-F2) and see a console login?
> Nothing happens when I press CTRL-ALT-F2, F3, ...
> The only key combination that has any effect is CTRL-ALT-DEL.

Could it be that it boots but that display is completely broken?

Can you ping it or connect to it over SSH?

Thanks,
Ludo’.
R
(name . Ludovic Courtès)(address . ludo@gnu.org)
9e05fcec-09eb-76bc-8664-e7de0e850456@disroot.org
Hi Ludo,

SSH does not work. No response to ping.

Thanks for the support,
Reg

On 2019-06-01 00:01, Ludovic Courtès wrote:
Toggle quote (15 lines)
> Hi Reg,
>
> Reg <reg@disroot.org> skribis:
>
>> On 2019-05-30 14:10, Giovanni Biscuolo wrote:
>>> Are you sure your laptop does not boot at all? I mean: can't you switch
>>> to a different tty (CTRL-ALT-F2) and see a console login?
>> Nothing happens when I press CTRL-ALT-F2, F3, ...
>> The only key combination that has any effect is CTRL-ALT-DEL.
> Could it be that it boots but that display is completely broken?
>
> Can you ping it or connect to it over SSH?
>
> Thanks,
> Ludo’.
P
P
pelzflorian (Florian Pelz) wrote on 28 Mar 2020 13:42
Re: Guix won't boot after installation with fully encrypted disk
(name . Reg)(address . reg@disroot.org)(address . bug-guix@gnu.org)
20200328124231.hiy6sdixxyj3olrx@pelzflorian.localdomain
Hello Reg!

On Thu, May 23, 2019 at 11:41:40PM +0200, Reg wrote:
Toggle quote (3 lines)
> Guix won't boot on my ThinkPad T430 after an installation with fully
> encrypted disk:

A friend had an issue that looked similar on an HP laptop (no
Thinkpad) in Guix System. GRUB got stuck either after entering the
encryption key or, without encryption, when booting Guix. The
resolution was to enable CSM Legacy Support in the UEFI/BIOS settings
(even though it is a grub-efi-bootloader install). Maybe this is
something to try if you or someone else has such an issue again.

Regards,
Florian
R
(name . pelzflorian (Florian Pelz))(address . pelzflorian@pelzflorian.de)(address . bug-guix@gnu.org)
628ea287-d56e-9ce2-8bfc-a6da3721fdb7@disroot.org
Hi Florian,

Thank you very much for getting back to me! CSM legacy support was
already enabled on my ThinkPad but guess what.. *Disabling* it fixed the
problem! My computer is booting without issues now with a fully
encrypted disk.

Thank you so much!

Best regards,
Reg

On 2020-03-28 13:42, pelzflorian (Florian Pelz) wrote:
Toggle quote (16 lines)
> Hello Reg!
>
> On Thu, May 23, 2019 at 11:41:40PM +0200, Reg wrote:
>> Guix won't boot on my ThinkPad T430 after an installation with fully
>> encrypted disk:
>
> A friend had an issue that looked similar on an HP laptop (no
> Thinkpad) in Guix System. GRUB got stuck either after entering the
> encryption key or, without encryption, when booting Guix. The
> resolution was to enable CSM Legacy Support in the UEFI/BIOS settings
> (even though it is a grub-efi-bootloader install). Maybe this is
> something to try if you or someone else has such an issue again.
>
> Regards,
> Florian
>
P
P
pelzflorian (Florian Pelz) wrote on 29 Mar 2020 13:55
(name . Reg)(address . reg@disroot.org)(address . 35875@debbugs.gnu.org)
20200329115542.lckf6y2eewlml3e2@pelzflorian.localdomain
On Sat, Mar 28, 2020 at 10:39:28PM +0100, Reg wrote:
Toggle quote (12 lines)
> Hi Florian,
>
> Thank you very much for getting back to me! CSM legacy support was already
> enabled on my ThinkPad but guess what.. *Disabling* it fixed the problem! My
> computer is booting without issues now with a fully encrypted disk.
>
> Thank you so much!
>
> Best regards,
> Reg
>

This is nice to hear. Thank you for testing; very quick. BTW your
message did not go through to the bug report; probably it was my
mistake putting the wrong list in Cc.

Now I wonder where this should be documented. Should there be a
Troubleshooting section in the manual?

Regards,
Florian
D
D
david larsson wrote on 29 Oct 2022 20:28
bug#35875: Guix won't boot after installation with fully encrypted disk
(address . bug-guix@gnu.org)
125f409c5b5d92bed3bc2c7d270f2c9e@selfhosted.xyz
Hi,
Im having this exact same issue: I can enter the password once to unlock
the disk, then after selecting the grub entry I am stuck at the Guix
grub screen.

I have used terminal based "manual" install, graphical guided install
for full disk - all on one partition - and graphical guided install with
manually created separate /boot partition.

Only non-encrypted disk works to boot install. Also, btrfs fails, ext4
works.

This is using the current 1.3 installer image.

The reason I attempted this installation is because my
full-disk-encryption installation that's a couple years old or so failed
to boot upon reboot, and I did not have any previous generation that I
could select from the grub menu that would boot either - i.e. my Guix
system broke.

I'm considering using an old 1.2 installer image, but Im not sure
whether I should just wait for a 1.4 release, or if there are other
suggestions?

And, I can't ping or ssh to the machine, after Im stuck at the Guix grub
boot screen.

If this is just me and Reg - it's weird. I mean I suppose the full disk
encryption option has been tested by someone before releasing the
installer?

What should I try next?

Best regards,
David
J
J
Josselin Poiret wrote on 30 Oct 2022 10:05
87leoxu1ey.fsf@jpoiret.xyz
Hi david,

david larsson <david.larsson@selfhosted.xyz> writes:

Toggle quote (2 lines)
> What should I try next?

Can you try the latest installer iso in the meantime, the one at [1]?


Best,
--
Josselin Poiret
D
D
david larsson wrote on 30 Oct 2022 13:27
(name . Josselin Poiret)(address . dev@jpoiret.xyz)(address . 35875@debbugs.gnu.org)
ade72ecdf8af04e4ef073506808f5516@selfhosted.xyz
Hi Josselin,

Thanks for your help with this issue. I tried ur suggestion and got the
same results. However, the comment about CSM legacy support gave me a
hint from which I managed to "solve" it: my laptop uses OSBoot, and I
always boot with the Seabios payload, but booting from the Grub
commandline without loading Seabios actually worked fine. Just never
occured to me to try it until I saw that email reply.

Thanks!

//David

On 2022-10-30 10:05, Josselin Poiret wrote:
Toggle quote (11 lines)
> Hi david,
>
> david larsson <david.larsson@selfhosted.xyz> writes:
>
>> What should I try next?
>
> Can you try the latest installer iso in the meantime, the one at [1]?
>
> [1] https://guix.gnu.org/en/download/latest/
>
> Best,
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 35875@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 35875
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch