From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs v2 3/5] installation: add note about memtest86+ incompatibility with secureboot
Date: Thu, 25 Jan 2024 12:06:29 +0100 [thread overview]
Message-ID: <20240125110646.427124-4-c.heiss@proxmox.com> (raw)
In-Reply-To: <20240125110646.427124-1-c.heiss@proxmox.com>
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
---
Changes v1 -> v2:
* no changes
pve-installation.adoc | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/pve-installation.adoc b/pve-installation.adoc
index ccb32be..6e011fa 100644
--- a/pve-installation.adoc
+++ b/pve-installation.adoc
@@ -120,7 +120,8 @@ from the disk.
Advanced Options: Test Memory (memtest86+)::
Runs `memtest86+`. This is useful to check if the memory is functional and free
-of errors.
+of errors. Secure Boot must be turned off in the UEFI firmware setup utility to
+run this option.
[thumbnail="screenshot/pve-select-target-disk.png"]
--
2.42.0
next prev parent reply other threads:[~2024-01-25 11:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 11:06 [pve-devel] [PATCH docs v2 0/5] installation and system improvements Christoph Heiss
2024-01-25 11:06 ` [pve-devel] [PATCH docs v2 1/5] screenshots: update grub menu screenshot Christoph Heiss
2024-01-25 11:06 ` [pve-devel] [PATCH docs v2 2/5] installation: update installer option wording & description Christoph Heiss
2024-01-25 11:06 ` Christoph Heiss [this message]
2024-01-25 11:06 ` [pve-devel] [PATCH docs v2 4/5] installation: add section about booting with `nomodeset` Christoph Heiss
2024-01-25 11:06 ` [pve-devel] [PATCH docs v2 5/5] tree-wide: unify spelling of GRUB and systemd-boot Christoph Heiss
2024-02-20 14:46 ` [pve-devel] applied-series: [PATCH docs v2 0/5] installation and system improvements Thomas Lamprecht
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=20240125110646.427124-4-c.heiss@proxmox.com \
--to=c.heiss@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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