public inbox for pmg-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: Alexander Zeidler <a.zeidler@proxmox.com>
Cc: pmg-devel@lists.proxmox.com
Subject: [pmg-devel] applied: [PATCH pmg-docs v2] administration, installation: add chapter "Firmware Updates"
Date: Tue, 13 Feb 2024 11:49:04 +0100	[thread overview]
Message-ID: <20240213114904.5b615ec4@rosa.proxmox.com> (raw)
In-Reply-To: <20240124150148.156990-1-a.zeidler@proxmox.com>

On Wed, 24 Jan 2024 16:01:48 +0100
Thanks for the update!
applied the patch - having consistent docs across our products goes a long
way

one minor nit inline - if you happen to touch this again for another
reason:

Alexander Zeidler <a.zeidler@proxmox.com> wrote:

> and "Debian Firmware Repository", with mutual linking. Largely
> identical to PVE docs, except for:
> - remove mentions of ensuring a safe cluster node reboot
> - adapt internal links for this doc structure
> 
> Firmware updates are important, their existence should not be checked
> only when there are already noticeable problems.
> 
> Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
> ---
> v2:
> * place chapter "Firmware Updates" under chapter "Administration" instead of "Installation", as it is partly a recurring manual task
> * make commit message verbose
> 
> v1: https://lists.proxmox.com/pipermail/pmg-devel/2023-November/002570.html
> 
> 
>  pmg-administration.adoc | 200 ++++++++++++++++++++++++++++++++++++++++
>  pmg-installation.adoc   |  17 ++++
>  2 files changed, 217 insertions(+)
> 
>.. snip..
> +[[pmg_firmware_troubleshooting]]
> +Troubleshooting
> +^^^^^^^^^^^^^^^
> +For debugging purposes, the set up Early OS Microcode Update applied regularly
> +at system boot can be temporarily disabled as follows:
> +
> +. Reboot the host to get to the GRUB menu (hold `SHIFT` if it is hidden)
> +. At the desired {pmg} boot entry press `E`
For the time being we have not only grub as a boot-loader, but also
systemd-boot - while both use `E` as edit-key - we might want to link to
the section where this is described (for pve:
https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysboot_edit_kernel_cmdline
for pmg - I'll try to add it in the coming days)

> ..snip..




      reply	other threads:[~2024-02-13 10:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24 15:01 [pmg-devel] " Alexander Zeidler
2024-02-13 10:49 ` Stoiko Ivanov [this message]

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=20240213114904.5b615ec4@rosa.proxmox.com \
    --to=s.ivanov@proxmox.com \
    --cc=a.zeidler@proxmox.com \
    --cc=pmg-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