From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id AC8581FF141 for ; Mon, 16 Mar 2026 16:49:03 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 3E5E91FED9; Mon, 16 Mar 2026 16:49:13 +0100 (CET) From: Maximiliano Sandoval To: pve-devel@lists.proxmox.com Subject: [PATCH docs v2] firmware-updates: remove documentation regarding fwdup's config Date: Mon, 16 Mar 2026 16:49:06 +0100 Message-ID: <20260316154907.536042-1-m.sandoval@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1773676106796 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.949 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_MSPIKE_H2 0.001 Average reputation (+2) RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.408 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.819 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.903 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: GXXS6DAZCQN4KTAEJWSWNFV57MWRKZNU X-Message-ID-Hash: GXXS6DAZCQN4KTAEJWSWNFV57MWRKZNU X-MailFrom: m.sandoval@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: As a side note regarding daemon.conf, fwupd since Trixie stores its config at /etc/fwupd/fwupd.conf. This was changed in [7fa42274], which first appeared in fwupd [1.9.1]. [7fa42274] https://github.com/fwupd/fwupd/commit/7fa422744c42d5f6a207d43c094d02dece64baf6 [1.9.1] https://github.com/fwupd/fwupd/releases/tag/1.9.1 [#8945] https://github.com/fwupd/fwupd/issues/8945#issuecomment-2993821262 Signed-off-by: Maximiliano Sandoval --- firmware-updates.adoc | 9 +-------- 1 file changed, 1 insertion(+), 8 deletions(-) diff --git a/firmware-updates.adoc b/firmware-updates.adoc index ea31dac..d9025d4 100644 --- a/firmware-updates.adoc +++ b/firmware-updates.adoc @@ -52,14 +52,7 @@ booted via UEFI. {pve} ships its own version of the `fwupd` package to enable Secure Boot Support with the Proxmox signing key. This package consciously dropped the dependency recommendation for the `udisks2` package, due to observed issues with -its use on hypervisors. That means you must explicitly configure the correct -mount point of the EFI partition in `/etc/fwupd/daemon.conf`, for example: - -.File `/etc/fwupd/daemon.conf` ----- -# Override the location used for the EFI system partition (ESP) path. -EspLocation=/boot/efi ----- +its use on hypervisors. TIP: If the update instructions require a host reboot, make sure that it can be done safely. See also xref:ha_manager_node_maintenance[Node Maintenance]. -- 2.47.3