public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Alexander Zeidler <a.zeidler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 5/7] installer: revise boot menu description and introduce sections
Date: Tue,  4 Mar 2025 16:40:59 +0100	[thread overview]
Message-ID: <20250304154101.3-6-a.zeidler@proxmox.com> (raw)
In-Reply-To: <20250304154101.3-1-a.zeidler@proxmox.com>

* Introduce sections and subsections to enable proper readability
* Move existing information up to the introduction and rephrase it where
  appropriate
* Move the TUI screenshot so that it is placed next to both TUI modes

Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
---
 pve-installation.adoc | 37 +++++++++++++++++++++++--------------
 1 file changed, 23 insertions(+), 14 deletions(-)

diff --git a/pve-installation.adoc b/pve-installation.adoc
index 404d66c..3dee709 100644
--- a/pve-installation.adoc
+++ b/pve-installation.adoc
@@ -72,27 +72,40 @@ enable booting from your installation medium (for example, USB) and
 set the desired boot order. When booting an installer prior to {pve}
 8.1, 'Secure Boot' needs to be disabled.
 
-[thumbnail="screenshot/pve-grub-menu.png"]
-
 After choosing the correct entry (for example, 'Boot from USB') the {pve} menu
 will be displayed.
 
 
+{pve} Boot Menu
+~~~~~~~~~~~~~~~
+[thumbnail="screenshot/pve-grub-menu.png"]
 
+There are various boot options available. For a normal installation,
+usually select *Install {pve} (Graphical)*.
 
+The graphical and terminal modes use the same code base for the actual
+installation process to benefit from more than a decade of bug fixes
+and ensure feature parity.
 
+TIP: The 'Terminal UI' options can be used if the 'Graphical'
+installer does not work correctly, e.g., due to driver issues. See
+also xref:nomodeset_kernel_param[adding the `nomodeset` kernel parameter].
 
+Interactive Installation
+^^^^^^^^^^^^^^^^^^^^^^^^
 
 Install {pve} (Graphical)::
 
-Starts the normal installation.
+Starts the normal installation. If there are any problems, try one of
+the other options instead.
 
 TIP: It's possible to use the installation wizard with a keyboard only. Buttons
 can be clicked by pressing the `ALT` key combined with the underlined character
 from the respective button. For example, `ALT + N` to press a `Next` button.
 
 Install {pve} (Terminal UI)::
-
++
+[thumbnail="screenshot/pve-tui-installer.png"]
 Starts the terminal-mode installation wizard. It provides the same overall
 installation experience as the graphical installer, but has generally better
 compatibility with very old and very new hardware.
@@ -104,15 +117,6 @@ kernel to use the (first) serial port of the machine for in- and output. This
 can be used if the machine is completely headless and only has a serial console
 available.
 
-[thumbnail="screenshot/pve-tui-installer.png"]
-
-Both modes use the same code base for the actual installation process to
-benefit from more than a decade of bug fixes and ensure feature parity.
-
-TIP: The 'Terminal UI' option can be used in case the graphical installer does
-not work correctly, due to e.g. driver issues. See also
-xref:nomodeset_kernel_param[adding the `nomodeset` kernel parameter].
-
 Advanced Options: Install {pve} (Graphical, Debug Mode)::
 
 Starts the installation in debug mode. A console will be opened at several
@@ -132,6 +136,9 @@ Advanced Options: Install {pve} (Serial Console Debug Mode)::
 Same the terminal-based debug mode, but additionally sets up the Linux kernel to
 use the (first) serial port of the machine for in- and output.
 
+Automated Installation
+^^^^^^^^^^^^^^^^^^^^^^
+
 Advanced Options: Install {pve} (Automated)::
 
 Starts the installer in unattended mode, even if the ISO has not been
@@ -140,6 +147,9 @@ gather hardware details or might be useful to debug an automated installation
 setup. See xref:installation_unattended[Unattended Installation] for more
 information.
 
+Other Options
+^^^^^^^^^^^^^
+
 Advanced Options: Rescue Boot::
 
 With this option you can boot an existing installation. It searches all attached
@@ -154,7 +164,6 @@ Runs `memtest86+`. This is useful to check if the memory is functional and free
 of errors. Secure Boot must be turned off in the UEFI firmware setup utility to
 run this option.
 
-You normally select *Install {pve} (Graphical)* to start the installation.
 
 [thumbnail="screenshot/pve-select-target-disk.png"]
 
-- 
2.39.5



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  parent reply	other threads:[~2025-03-04 15:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-04 15:40 [pve-devel] [PATCH v1 docs 0/7] Revise installation chapter Alexander Zeidler
2025-03-04 15:40 ` [pve-devel] [PATCH docs 1/7] system-requirements: revise subchapter and provide more details Alexander Zeidler
2025-03-04 16:21   ` Shannon Sterz
2025-03-04 15:40 ` [pve-devel] [PATCH docs 2/7] installation: prepare medium: revise subchapter Alexander Zeidler
2025-03-04 16:34   ` Shannon Sterz
2025-03-04 15:40 ` [pve-devel] [PATCH docs 3/7] installation: revise introduction Alexander Zeidler
2025-03-05  8:35   ` Shannon Sterz
2025-03-04 15:40 ` [pve-devel] [PATCH docs 4/7] installer: " Alexander Zeidler
2025-03-05  8:53   ` Shannon Sterz
2025-03-04 15:40 ` Alexander Zeidler [this message]
2025-03-04 15:41 ` [pve-devel] [PATCH docs 6/7] installer: revise installation steps and introduce sections Alexander Zeidler
2025-03-05  9:25   ` Shannon Sterz
2025-03-04 15:41 ` [pve-devel] [PATCH docs 7/7] installer: revise intro of advanced ZFS/BTRFS configuration options Alexander Zeidler
2025-03-05  9:27   ` Shannon Sterz

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=20250304154101.3-6-a.zeidler@proxmox.com \
    --to=a.zeidler@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal