Am 09.10.23 um 13:40 schrieb Andrei Borzenkov:
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).
https://paste.opensuse.org/pastes/6d188dbf24b4 Ok, I'm not sure I understand all of the above as my boot knowledge is from the pre-EFI era mainly. Currently when I boot the system it immediately starts to boot Windows (no grub menu). When I stop the boot process and open the boot device selection via F12 I get offered two possibilities (which always was the case): opensuse-secureboot NVMe... The latter always booted Windows directly. The first always brought up the grub boot menu. Until yesterday. (Windows is also part of the grub menu but I could never boot from there as Bitlocker was/is unhappy about that order.) When and what was loaded when, sorry, I have no idea. It more or less worked until yesterday and since this happened now the second time within a few months I try to find a better solution. Next I'll try is to reinstall grub/bootloader as suggested in another part of the thread. Wolfgang