On Mon, Oct 9, 2023 at 2:20 PM Wolfgang Rosenauer <wolfgang@rosenauer.org> wrote:
Am 08.10.23 um 23:45 schrieb Wolfgang Rosenauer:
Hi,
sorry for my double post. Somehow when I write to users@ my mailfilter broke things so thought that my message didn't come through.
(and this one might be not threaded correctly)
Are there any errors or other messages when you try to start opensuse-secureboot? Does your BIOS support "boot from file"? If yes, can you try selecting \EFI\opensuse\shim.efi manually?
I cannot find an option to boot from file. It's a rather new Lenovo Thinkpad with a graphical boot menu containing two options:
opensuse-secureboot NVMe0 .... (which boots Windows)
There is no error visible. After selecting opensuse-secureboot there is a black screen for a second just to go back to the boot menu.
Is \EFI\opensuse still present? What is the content?
it is present and it is empty.
Boot any live linux, post full output of "efibootmgr -v".
Will do so tomorrow and come back. First need to create a USB storage with a TW image and it's getting late here. Thanks for the feedback so far.
Somewhat interesting BootOrder: 0000,001D,001E,001F,0020,0021,0022,0023,0024,0025 Boot0000* opensuse-secureboot HD(1,GPT,f2809dd7-02ba-4b21-a014-a411e8bf0b91,0x800,0x82000)/File(\EFI\opensuse\shim.efi) Boot0001* Windows Boot Manager HD(1,GPT,f2809dd7-02ba-4b21-a014-a411e8bf0b91,0x800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi) Windows bootloader is not in the list of boot options. Which is rather unusual (especially after Windows update that apparently updated the bootloader). Boot001F* NVMe0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400) Educated guess - it has always been this way, you just did not notice it. The NVMe boot entry most likely loads \EFI\Boot\bootx64.efi which was overwritten by Windows update. Prove output of ls -lR /boot/efi (after mounting it in live linux).