The version of systemd boot in bullseye, tries writing an efivar which
is not writeable on certain (broken) UEFIs (HP thin clients).

The issue was not present in the version in buster (the variable
simply did not get written) and can be worked around by adding
--graceful to the `bootctl install` command.

see also:
https://github.com/systemd/systemd/issues/13603

Signed-off-by: Stoiko Ivanov <[email protected]>
---
originally sent as part of a series:
https://lists.proxmox.com/pipermail/pve-devel/2022-March/052054.html
as:
https://lists.proxmox.com/pipermail/pve-devel/2022-March/052052.html

however since the issue is really unrelated to the series, and causes
(more) issues for systems with (certain) broken UEFI systems I'm resending
it isolated of the series (which IIRC is a bit too large to integrate
currently)

 bin/proxmox-boot-tool | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/bin/proxmox-boot-tool b/bin/proxmox-boot-tool
index fb4e320..6c0ae4f 100755
--- a/bin/proxmox-boot-tool
+++ b/bin/proxmox-boot-tool
@@ -153,7 +153,7 @@ init() {
        if [ -d /sys/firmware/efi ]; then
                echo "Installing systemd-boot.."
                mkdir -p "$esp_mp/$PMX_ESP_DIR"
-               bootctl --path "$esp_mp" install
+               bootctl --graceful --path "$esp_mp" install
 
                echo "Configuring systemd-boot.."
                echo "timeout 3" > "$esp_mp/$PMX_LOADER_CONF.tmp"
-- 
2.30.2



_______________________________________________
pve-devel mailing list
[email protected]
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Reply via email to