I formatted my / and /boot/efi according to the default settings by Suse. I have mounted my existing /home accordingly. When the installation is finished Yast throws an error:
I’m pretty sure that “No space left on device” is referring to the part of NVRAM used by UEFI as the device.
You did not say what happened after that message. If you told it to continue, then your system is probably installed, but perhaps not bootable.
If you are planning to retry the install, then click on “Booting” near the top of the summary page. There should be a box “Update NVRAM entry”. Uncheck that box. That avoids writing to NVRAM, and should prevent the error from occurring, but your system might not be bootable.
Either way, if your system isn’t bootable, try booting your install media. And select the entry “Boot from hard drive”. That should get you into your system. From there, you can try to delete some of the NVRAM entries, to see if that makes space available. I’ll give more details on that when you tell us how things have gone.
It tells the system to not attempt to write an NVRAM entry.
It looks as if you already have a suitable NVRAM entry, so the system continues using that. Otherwise it would delete the current entry and then put it back. Leaving that box unchecked should be fine. I also do that.
Can you post the output from:
efibootmgr
This will list all of the boot entries. Maybe there are some that can be removed.
Maybe also look at the output from:
mokutil -l
It will list any enrolled keys. There’s no need to post them. But maybe you could check how many keys are enrolled. Possibly some can be removed.
I was thinking that there might be some stale entries that could be removed, so as to free up NVRAM space. But it seems that I was mistaken about that.
Thanks for providing the information so that I could check.