From: "Simon Zhang (張元鑫)" <Simon.Zhang@quantatw.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Steve Chang (張瑞廷)" <Steve.Chang@quantatw.com>,
"Henry Yu (于恆立)" <Henry.Yu@quantatw.com>,
"David Chang (張文政)" <David_Chang@quantatw.com>,
"Leo Lin (林振榮)" <Leo-Lin@quantatw.com>,
"Jerry Liu (劉孝睿)" <Jerry_Liu@quantatw.com>,
"Levi Chen (陳駿煬)" <Levi_Chen@quantatw.com>,
"Leeno Li (李胤融)" <Leeno.Li@quantatw.com>,
"Kevin Chou (周宸葳)" <Kevin_Chou@quantatw.com>
Subject: [edk2-devel] [edk2-test] Inquiry About SCT Installation on NVMe SSD
Date: Tue, 13 May 2025 08:41:43 -0700 [thread overview]
Message-ID: <SEZPR04MB826485F9DA408228ADE737108A8BA@SEZPR04MB8264.apcprd04.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
Dear Github Maintainers,
We are currently encountering an issue when attempting to install UEFI-SCT 2.7B on NVMe SSDs.
Although the SCT User Guide specifies that the installation method is USB, it does not explicitly state that only USB is supported.
Our team prefers to use SSDs for SCT installation, and we would like to confirm whether the use of NVMe SSDs is supported.
If it is possible to use NVMe SSD, we would like to understand if this is a known limitation or if specific BIOS/UEFI settings are required for NVMe-based installations.
Any guidance you could provide would be greatly appreciated.
Thanks
Best regards,
Simon Zhang
BU9, Quanta Computer Inc.
Tel: 03-3272345 Ext:60360
E-mail: simon.zhang@quantatw.com<mailto:simon.zhang@quantatw.com>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121336): https://edk2.groups.io/g/devel/message/121336
Mute This Topic: https://groups.io/mt/113092190/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 4735 bytes --]
reply other threads:[~2025-05-13 15:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-list 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=SEZPR04MB826485F9DA408228ADE737108A8BA@SEZPR04MB8264.apcprd04.prod.outlook.com \
--to=devel@edk2.groups.io \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox