From: Leo Liang <ycliang@andestech.com>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
Green Wan <green.wan@sifive.com>,
Yong-Xuan Wang <yongxuan.wang@sifive.com>, <u-boot@lists.denx.de>,
Yuri Zaporozhets <yuriz@vodafonemail.de>,
Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH v2 1/1] configs: SiFive Unmatched: add 'nvme scan' to preboot
Date: Thu, 6 Mar 2025 11:38:02 +0800 [thread overview]
Message-ID: <Z8kYmoMNMLWx1KcY@swlinux02> (raw)
In-Reply-To: <20241112102644.37459-1-heinrich.schuchardt@canonical.com>
On Tue, Nov 12, 2024 at 11:26:44AM +0100, Heinrich Schuchardt wrote:
> Without 'nvme scan' the ESP on the NVMe drive is not found early.
> EFI variables cannot be persisted.
>
> Hit any key to stop autoboot: 0
> Cannot persist EFI variables without system partition
> ** Booting bootflow '<NULL>' with efi_mgr
> Loading Boot0000 'mmc 0' failed
> EFI boot manager: Cannot load any image
> Boot failed (err=-14)
> scanning bus for devices...
> ** Booting bootflow 'nvme#1.blk#1.bootdev.part_1' with efi
> Booting /\EFI\BOOT\BOOTRISCV64.EFI
> error: no suitable video mode found.
> GNU GRUB version 2.12
>
> With 'nmve scan' booting works as expected.
>
> Hit any key to stop autoboot: 0
> ** Booting bootflow '<NULL>' with efi_mgr
> Loading Boot0000 'mmc 0' failed
> Loading Boot0001 'nvme 0' failed
> Booting: nvme 1
> error: no suitable video mode found.
> GNU GRUB version 2.12
>
> Reported by Yuri Zaporozhets <yuriz@vodafonemail.de>
> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
> ---
> v2:
> mention board in subject
> ---
> configs/sifive_unmatched_defconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Leo Yu-Chi Liang <ycliang@andestech.com>
prev parent reply other threads:[~2025-03-06 3:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 10:26 [PATCH v2 1/1] configs: SiFive Unmatched: add 'nvme scan' to preboot Heinrich Schuchardt
2024-11-13 13:39 ` Simon Glass
2025-02-07 7:43 ` Heinrich Schuchardt
2025-03-06 3:38 ` Leo Liang [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=Z8kYmoMNMLWx1KcY@swlinux02 \
--to=ycliang@andestech.com \
--cc=green.wan@sifive.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=paul.walmsley@sifive.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=yongxuan.wang@sifive.com \
--cc=yuriz@vodafonemail.de \
/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.