I am installing Tumbleweed from a USB drive a DVD snapshot iso. I have an SSD and HDD. The SSD has /boot/efi, btrfs operating system, swap, and a personal partition. The operating system and personal partition are encrypted. The HDD has /home and a personal partition, both of which are lvm and encrypted. See below:
Would show? It looks like the failure is coming trying to install the secure-boot shim, and it could be that there’s not enough space in efivars for the certificates (or for something else that’s needed).
I ran into a similar issue attempting to use fwupdmgr to update the certificate database on my system; had to use the BIOS to delete the existing database before applying the update (the update included everything that was already on the system, but the size was just a little too large to handle applying the update).
When it says “No space left on device”, the device it is referring to is probably the NVRAM where EFI data is saved.
What’s in NVRAM partly depends on the EFI BIOS.
You could perhaps boot from a live rescue USB or DVD, and try:
mokutil --reset
to see if that frees up enough space in NVRAM. After that, you will have to boot again from the live rescue, which should give a blue screen where you can complete the reset.
During install, go to the booting section. There should be a box “Update NVRAM Entry”.
Uncheck that box.
The boot install should then be successful, though it might not actually boot. The effect of unchecking that box, is that it does not try to update efivars. But it still creates the needed files in the EFI partition.
If you happen to already have a suitable NVRAM entry, then it will boot properly. If not, you can still boot it via the install media. Selecting “boot from hard drive” will probably work. If not, then “Boot a linux system” should work.
You can prove out the theory by installing with secure boot disabled, see if the installation finishes.
If it does, then we know that that’s what the issue is. How you clear it out depends on the BIOS on the system. In my case, there was an option to install the default certificates in the system, and that I was able to use fwupdmgr to update to the latest available certificates.
Hi, a search in YaST Software Manager shows no results for fwupdmgr also zypper info fwupdmgr shows
zypper info fwupdmgr
Refreshing service 'openSUSE'.
Loading repository data...
Reading installed packages...
package 'fwupdmgr' not found.
No matching items found.
The command-not-found package installs cnf, which is a very useful tool for finding which package a command comes from if it’s not installed.
cnf fwupdmgr will tell you it’s the fwupd package.
That’s in addition to using YaST to find it, as hui noted.
I would also note that this tool is useful for applying updates to various firmware on the system as well as the certificate store, but it will not clean the certificate store. That has to be done in the system’s BIOS itself, (at least on my system it did).