[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251028174541.GA1548965@ax162>
Date: Tue, 28 Oct 2025 10:45:41 -0700
From: Nathan Chancellor <nathan@...nel.org>
To: Eugene Shalygin <eugene.shalygin@...il.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Masahiro Yamada <masahiroy@...nel.org>,
linux-kbuild@...r.kernel.org
Subject: Re: Can't boot kernel 6.17.4+ via rEFInd
On Mon, Oct 27, 2025 at 09:41:25PM +0100, Eugene Shalygin wrote:
> Hi Nathan,
>
> On Mon, 27 Oct 2025 at 20:35, Eugene Shalygin <eugene.shalygin@...il.com> wrote:
> > Neither the patch nor 6.18-rc3 work. I'm going to try to revert
> > 5b5cdb1fe434e8adc97d5037e6d05dd386c4c4c6 together with anything that
> > is needed to apply the reversing patch.
>
> Replacing CONFIG_KERNEL_ZSTD with CONFIG_KERNEL_GZIP made the kernel
> bootable. What does that mean?
Hmmmm, I am not sure... That seems rather odd within the context of the
flagged change.
Could you post the output of 'readelf -S vmlinux vmlinux.unstripped'
from the broken and good builds? Does rEFInd have any sort of additional
debugging to see why/what it is complaining about not being able to
find?
Cheers,
Nathan
Powered by blists - more mailing lists