linux-kernel - Re: Can't boot kernel 6.17.4+ via rEFInd

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMj1kXG_kPx5=3Qbn6ZTpKqOYh-mehwrH+d6Bw8QEPqvhZy1nw@mail.gmail.com>
Date: Mon, 3 Nov 2025 22:28:15 +0100
From: Ard Biesheuvel <ardb@...nel.org>
To: Eugene Shalygin <eugene.shalygin@...il.com>
Cc: Nathan Chancellor <nathan@...nel.org>, 
	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, 3 Nov 2025 at 22:22, Eugene Shalygin <eugene.shalygin@...il.com> wrote:
>
> Hi Ard and Nathan,
>
> On Mon, 3 Nov 2025 at 16:00, Ard Biesheuvel <ardb@...nel.org> wrote:
> > Eugene, can you try whether the image can be loaded by the EFI shell
> > directly? You may have to rename the file and give it a .efi
> > extension, but otherwise, you should be able to boot it using
>
> Did that with the kernel file and it loaded up until the non syncing
> VFS error, but I suppose that is enough to state that the firmware can
> boot the kernel image which rEFInd is unable to, and I should look for
> answers with rEFInd author?
>

Indeed. Not saying there isn't anything to fix on the kernel side, but
narrowing it down needs to be done on the side of the loader, it
seems.