You are not logged in.
Pages: 1
I've been trying to update my UEFI dbx through the KDE Discover but it doesn't seem to work, it shows an error message "failed to write-firmware: Blocked executable in the ESP, ensure grub and shim are up to date: failed to load Boot0004: Erro ao abrir arquivo /sys/firmware/efi/efivars/Boot2002-8be4df61-93ca-11d2-aa0d-00e098032b8c: Arquivo ou diretório inexistente", the same happens if I try to update it through the console. Any clues?
Neofetch
tanuki@laptop-arch-tanuki
-------------------------
OS: Arch Linux x86_64
Host: HP Envy x360 2-in-1 Laptop 14-fa0xxx
Kernel: 6.12.1-arch1-1
Uptime: 20 mins
Packages: 1274 (pacman), 34 (brew), 50 (flatpak)
Shell: bash 5.2.37
Resolution: 1920x1200
DE: Plasma 6.2.3
WM: kwin
Theme: Breeze-Dark [GTK2], Breeze [GTK3]
cons: breeze-dark [GTK2/3]
Terminal: kitty
CPU: AMD Ryzen 5 8640HS w/ Radeon 760M Graphics (12) @ 4.971GHz
GPU: AMD ATI 03:00.0 Phoenix3
Memory: 4534MiB / 15279MiB
Offline
Use this to check Boot0004:
efibootmgr -u
The same command can also be used to delete old entries that no longer point to EFI loaders.
This might also help: https://wiki.archlinux.org/title/Unifie … t_efivarfs
Para todos todo, para nosotros nada
Offline
I was using the search engine and am posting here since I have a very similar issue while trying to update UEFI dbx via
fwupdmgr update
This is my error output:
failed to write-firmware: Blocked executable in the ESP, ensure grub and shim are up to date: failed to load /boot/EFI/SYSTEMD/SYSTEMD-BOOTX64.EFI: Error opening file /boot/EFI/SYSTEMD/SYSTEMD-BOOTX64.EFI: No such file or directory
I wonder why it tells me to ensure grub and shim being up to date since grub is not my bootloader.
I'm using systemd-boot.
My output for
efibootmgr -u
is the following:
BootCurrent: 0004
Timeout: 1 seconds
BootOrder: 0004,0005
Boot0004* Linux Boot Manager HD(1,GPT,UUID1,0x800,0x100000)/\EFI\SYSTEMD\SYSTEMD-BOOTX64.EFI
Boot0005* UEFI OS HD(1,GPT,UUID1,0x800,0x100000)/\EFI\BOOT\BOOTX64.EFI
Last edited by evensure (2024-11-30 15:29:18)
Offline
Your error looks slightly different evensure.
Is the EFI system partition mounted under /boot/ when you try to update? Use `lsblk -f` to show all partitions and their mountpoints.
Para todos todo, para nosotros nada
Offline
Your error looks slightly different evensure.
Is the EFI system partition mounted under /boot/ when you try to update? Use `lsblk -f` to show all partitions and their mountpoints.
Yes , my EFI partition is mounted on /boot:
hostname@hostname ~ % lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
nvme0n1
├─nvme0n1p1 vfat FAT32 UUID1 111.3M 78% /boot
└─nvme0n1p2 crypto_LUKS 2 UUID2
└─lvm LVM2_member LVM2 001 UUID3
├─vgevensure-swap swap 1 UUID4 [SWAP]
├─vgevensure-root-real
│ ├─vgevensure-root ext4 1.0 UUID5 70.8G 23% /
│ └─vgevensure-snap1126 ext4 1.0 UUID5
├─vgevensure-snap1126-cow
│ └─vgevensure-snap1126 ext4 1.0 UUID5
└─vgevensure-home ext4 1.0 UUID6 669.9G 3% /home
Offline
Does manually mounting efivarfs help for you?
Para todos todo, para nosotros nada
Offline
Pages: 1