From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Christoph Heiss <c.heiss@proxmox.com>
Subject: Re: [pve-devel] [PATCH docs v2] installation: reword `nomodeset` section a bit, add link to it
Date: Wed, 27 Mar 2024 14:43:42 +0100 [thread overview]
Message-ID: <d1a8f7f5-ed1a-4be7-8247-8e1f47b57092@proxmox.com> (raw)
In-Reply-To: <20240226180044.1406827-1-c.heiss@proxmox.com>
Am 26/02/2024 um 18:59 schrieb Christoph Heiss:
> The `nomodeset` section needs some massaging due to the text flow being
> broken a bit. While at it, link to it above at the 'Terminal UI'
> bootloader tip such that readers can find it more easily.
>
> Suggested-by: Alexander Zeidler <a.zeidler@proxmox.com>
> Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
> ---
> Changes v1 -> v2:
> * dropped superflous `the`
> * use `xref` instead of `<< >>` for linking paragraph
>
> pve-installation.adoc | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/pve-installation.adoc b/pve-installation.adoc
> index 6b44fc0..016aa91 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)::
>
> @@ -300,14 +301,14 @@ following command:
> # zpool add <pool-name> log </dev/path_to_fast_ssd>
> ----
>
> +[[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
> --
> 2.43.0
>
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
>
next prev parent reply other threads:[~2024-03-27 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 17:59 Christoph Heiss
2024-03-27 13:43 ` Thomas Lamprecht [this message]
2024-03-27 13:43 ` [pve-devel] applied: " 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=d1a8f7f5-ed1a-4be7-8247-8e1f47b57092@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.