I had an update notice for my Dell firmware with a tumbleweed error that it won’t install
“failed to write-firmware: Secure boot is enabled, but shim isn’t installed to EFI/opensuse-tumbleweed/shim.efi”??
Mabye?
Read the relevant hints to copy the file as described in the thread and bugreport.
I gave up and tried leap 16-seems to work ok so far thx
I ran into that on my Dell system.
I actually have two EFI partitions. One of them is on the NVME disk that came with the computer, and the other is on an older hard drive that I installed. I have been using the EFI partition on the NVME disk. But apparently, “fwupd” wants to use the other EFI partition.
I copied “shim” to the appropriate place in that other EFI partition, and it has been working fine since then. I did recopy after a shim update.
i’m having a problem that looks very similar:
failed to write-firmware: Secure boot is enabled, but shim isn't installed to EFI/opensuse-tumbleweed/shim.efi
the contents of my /boot/efi/EFI are:
ls /boot/efi/EFI
Boot Dell fedora Guix opensuse redhat
note, opensuse and not opensuse-tumbleweed.
does anybody know what i can do to get the bios update installed?
maybe the distribution name changed at some stage. can i solve the problem by just creating a copy of opensuse called opensuse-tumbleweed or is there a way to tell fwupdmgr that the distribution name is just opensuse or is this not the actual problem?
Show the output from
rpm -q shim
ls /boot/efi/EFI/opensuse/shim*.efi
We need to verify that the ESP contains the signed shim.
1 Like
I ran into a similar problem. I happen to have two EFI partitions, and the firmware update wanted to use the wrong one.
I just copied “shim.efi” to there, and all has been working since. When I noticed a “shim” update, I repeated the copying.
thank you for your help 
here’s the response:
easy:/boot/efi/EFI # rpm -q shim
shim-16.1-2.1.x86_64
easy:/boot/efi/EFI # ls /boot/efi/EFI/opensuse/shim*.efi
/boot/efi/EFI/opensuse/shim.efi
thanks for your response does that mean i could try creating /boot/efi/EFI/opensuse-tumbleweed and copying the contents of /boot/efi/EFI/opensuse to it, then running fwupdmgr again?
I would try doing that.
many thanks for your help.
i seem to have solved the problem. all i did was restart the fwupd daemon (sudo systemctl restart fwupd.service), clicked on on install in the kde update window and it suggested i restart the computer. i did so and the install ran without a problem
i have no idea why it thought the shim file should be in opensuse-tumbleweed.
1 Like
Glad to read that this is resolved. Your output confirmed the shim was installed in the ESP as expected. Restarting fwupd.service forced it to rescan Secure Boot and EFI state, which is why the update worked afterward. The opensuse-tumbleweed path in the error message is mis-leading. It comes from fwupd’s internal OS ID and doesn’t reflect the actual ESP layout on openSUSE.
2 Likes