Hello, In the Message; Subject : Re: Shim error message about "blocked executable in ESP" Message-ID : <2009245.7nSxpqYiop@silversurfer> Date & Time: Fri, 07 Jun 2024 16:56:40 +0200 Stakanov via openSUSE Users <users@lists.opensuse.org> has written:
In data venerdì 7 giugno 2024 07:00:49 CEST, Masaru Nomiya ha scritto:
[...]
Hello and thank you for your very appreciated help. I actually did suspect that there is something left behind in /boot (and as I will be again in Italy this year, I will take care of it once I have my hands on the machine).
Italy.... When I saw Torre di Pisa, I was impressed that this is where Galileo is said to have conducted his famous experiment.
What is puzzling me is why this did happen to /boot as no dual boot or other OS was installed on the machine.
It is said that this phenomenon can be caused by firmware updates.
Maybe I will be able to have me send the content of the disc as list by the user.
It would be good to know the contents of /boot/efi/EFI/boot.
If I well understood, the fwupd should not attempt by itself to do the update and the rest of the system should update normally? Or should I tell the user to stop doing updates until the issue is resolved?
I see what you mean!! In such case, you need to know if the model the user is using supports the fwupd tool (You can find out on the manufacturer's website.). It is better not to let the user do this, since it would require deleting old efi files left in /boot/efi/EFI/boot, as well as the question of whether fwupd is supported. Sorry, but I don't know what to do if the user's usage model does not support the fwupd tool. Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: m.nomiya+suse @ gmail.com ┃＼／彡 ┗━━┛ "It would probably take decades more to answer with the usual scientific precision the questions we face today about the dangers of chemicals." -- J. V. Rodricks --