diff --git a/pve-installation.adoc b/pve-installation.adoc index 7291420..8e9a7cb 100644 --- a/pve-installation.adoc +++ b/pve-installation.adoc @@ -88,7 +88,8 @@ 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. +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):: @@ -349,14 +350,14 @@ following command: # zpool add log ---- +[[nomodeset_kernel_param]] Adding the `nomodeset` Kernel Parameter ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Problems may arise on very old or very new hardware due to graphics drivers. If -the installation hangs during the boot. In that case, you can try adding the -`nomodeset` parameter. This prevents the Linux kernel from loading any -graphics drivers and forces it to continue using the BIOS/UEFI-provided -framebuffer. +the installation hangs during boot, you can try adding the `nomodeset` +parameter. This prevents the Linux kernel from loading any graphics drivers and +forces it to continue using the BIOS/UEFI-provided framebuffer. On the {pve} bootloader menu, navigate to 'Install {pve} (Terminal UI)' and press `e` to edit the entry. Using the arrow keys, navigate to the line starting