all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: William <willbilly@fedora.email>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: help-guix@gnu.org
Subject: Re: Adding a menu entry on GRUB.
Date: Mon, 22 Apr 2024 21:37:26 +0200	[thread overview]
Message-ID: <20240422213726.000c189b@fedora.email> (raw)
In-Reply-To: <87mspm43q8.fsf@lease-up.com>

On Sun, 21 Apr 2024 17:53:51 -0700
Felix Lechner <felix.lechner@lease-up.com> wrote:

> Hi William,
> 
> On Sun, Apr 21 2024, William wrote:
> 
> > I ran e2fsck, lsblk, blkid and fdisk on a booted system to verify
> > that everything is fine with these partitions, no sign of anything
> > unusal...  
> 
> Are you being bitten by a new incompatibility between GRUB and the new
> default options? [1] 
> 
> Kind regards
> Felix
> 
> [1]
> https://lists.gnu.org/archive/html/guix-devel/2024-04/msg00207.html

Hello.


Yes, this definitely looks like the root of the issue, specially since
other GRUBs I tested such as the ones from Debian or Artix are
unaffected by this issue.

> How did you create your file systems?

The filesystems were created automatically through a Calamares GUI
installer, there's a non-zero chance that the installer created a
filesystem with options that are incompatible due to this bug.

Luckily I can wait until GRUB is patched on Guix as this issue can be
circumvented by closing Guix's GRUB from command line and booting with
another GRUB I have in my machine.


      reply	other threads:[~2024-04-22 19:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11 21:18 Adding a menu entry on GRUB William
2024-04-12 11:04 ` 宋文武
2024-04-12 15:37   ` William
2024-04-12 20:21     ` Felix Lechner via
2024-04-21 15:48       ` William
2024-04-22  0:53         ` Felix Lechner via
2024-04-22 19:37           ` William [this message]

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=20240422213726.000c189b@fedora.email \
    --to=willbilly@fedora.email \
    --cc=felix.lechner@lease-up.com \
    --cc=help-guix@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 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.