public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 4/7] installation: add section about booting with `nomodeset`
Date: Fri, 24 Nov 2023 11:45:59 +0100	[thread overview]
Message-ID: <20231124104605.320052-5-c.heiss@proxmox.com> (raw)
In-Reply-To: <20231124104605.320052-1-c.heiss@proxmox.com>

As the grub entry specific to this was removed with the 8.1 release, add
a separate section for this to link users too.

Unfortunaly it is relatively often needed, due to very old or very new
hardware, or when Nvidia cards are installed.

Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
---
 pve-installation.adoc | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/pve-installation.adoc b/pve-installation.adoc
index 7d4d754..11ec892 100644
--- a/pve-installation.adoc
+++ b/pve-installation.adoc
@@ -299,6 +299,23 @@ following command:
 # zpool add <pool-name> log </dev/path_to_fast_ssd>
 ----
 
+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.
+
+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
+with `linux`, move the cursor to the end of that line and add the
+parameter `nomodeset`, separated by a space from the pre-existing last
+parameter.
+
+Then press `Ctrl-X` or `F10` to boot the configuration.
+
 ifndef::wiki[]
 
 Install {pve} on Debian
-- 
2.42.0





  parent reply	other threads:[~2023-11-24 10:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-24 10:45 [pve-devel] [PATCH docs 0/7] installation and system improvements Christoph Heiss
2023-11-24 10:45 ` [pve-devel] [PATCH docs 1/7] screenshots: update grub menu screenshot Christoph Heiss
2023-11-24 10:45 ` [pve-devel] [PATCH docs 2/7] installation: update installer option wording & description Christoph Heiss
2023-11-24 10:45 ` [pve-devel] [PATCH docs 3/7] installation: add note about memtest86+ incompatibility with secureboot Christoph Heiss
2023-11-24 10:45 ` Christoph Heiss [this message]
2023-11-24 10:46 ` [pve-devel] [PATCH docs 5/7] installation: remove obsolete hint about disabling secure boot Christoph Heiss
2023-11-24 10:46 ` [pve-devel] [PATCH docs 6/7] system-booting: monospace package names needed for " Christoph Heiss
2023-11-24 10:46 ` [pve-devel] [PATCH docs 7/7] tree-wide: unify spelling of GRUB and systemd-boot Christoph Heiss
2024-01-25 11:08 ` [pve-devel] [PATCH docs 0/7] installation and system improvements Christoph Heiss

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=20231124104605.320052-5-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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal