All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Eugene Shalygin <eugene.shalygin@gmail.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Masahiro Yamada <masahiroy@kernel.org>,
	linux-kbuild@vger.kernel.org
Subject: Re: Can't boot kernel 6.17.4+ via rEFInd
Date: Sat, 7 Mar 2026 01:08:52 -0700	[thread overview]
Message-ID: <20260307080852.GA2685454@ax162> (raw)
In-Reply-To: <CAB95QAQyzYTrnGrkrcwXJ7Za37v7VsvwsmUezb1Z4VsF_RdLMQ@mail.gmail.com>

Hi Eugene,

On Sat, Nov 08, 2025 at 10:06:20AM +0100, Eugene Shalygin wrote:
> I've got no response from the rEFInd author yet, but another user
> reported (https://bugzilla.kernel.org/show_bug.cgi?id=220731) a very
> similar problem with GRUB and ZSTD compression.

Small necro bump: I think this might be fixed in mainline now with
commit 8678591b4746 ("kbuild: Split .modinfo out from ELF_DETAILS"). It
should apply relatively cleanly to stable versions (and should make its
way there in due time due to the stable tag).

Cheers,
Nathan

  reply	other threads:[~2026-03-07  8:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-26  8:25 Can't boot kernel 6.17.4+ via rEFInd Eugene Shalygin
2025-10-26 21:13 ` Nathan Chancellor
2025-10-27 19:35   ` Eugene Shalygin
2025-10-27 20:41     ` Eugene Shalygin
2025-10-28 17:45       ` Nathan Chancellor
2025-10-29 20:07         ` Eugene Shalygin
2025-10-31 22:07           ` Nathan Chancellor
2025-11-01  9:28             ` Eugene Shalygin
2025-11-03 15:00             ` Ard Biesheuvel
2025-11-03 21:22               ` Eugene Shalygin
2025-11-03 21:28                 ` Ard Biesheuvel
2025-11-04 15:04                   ` Eugene Shalygin
2025-11-08  9:06                     ` Eugene Shalygin
2026-03-07  8:08                       ` Nathan Chancellor [this message]
2026-03-08 17:59                         ` Eugene Shalygin

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=20260307080852.GA2685454@ax162 \
    --to=nathan@kernel.org \
    --cc=ardb@kernel.org \
    --cc=eugene.shalygin@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.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. 
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.