Your fix could be quite simple. Boot your Linux rescue media in UEFI mode, then run efibootmgr. It will probably be apparent that opensuse is not at the top/front of the boot order. You can move it back to the front/top with efibootmgr -o w,x,y,z, where w, x, y & z are the numbers of the existing boot order. e.g. 0003,0002,0005,0011, with 0011 being opensuse, do efibootmgr -o 11,3,2,5 to move opensuse from fourth to first. At this point, reboot should bring up your TW menu.
It shouldn’t be writing anywhere other than NVRAM. Is your current opensuse (TW) entry in efibootmgr Boot0011*? If not, you need to use whatever the current number is. 11 was my example. I have no idea what yours are numbered unless you first show output from efibootmgr here.
How many entries does efibootmgr produce? If more than 10-12, it’s possible your NVRAM space is cluttered full of stale entries. You may want to visit UEFI BIOS setup, or use efibootmgr, to purge the oldies.
When you install TW, the directory name in /EFI/ on the ESP filesystem is named “opensuse”, and exactly what will show in efibootmgr Boot####* output. Unless you edit /etc/default/grub to assign some string to GRUB_DISTRIBUTOR=, that is what it will remain.
Your boot order is currently Windows (Boot0000*) first. If you want TW first,
@Gps2010 You efi output shows windows on HD1, opensuse (Leap or Tumbleweed) on HD2, so is there a /boot/efi partition on your third HDD? If so this entry can be manually added, maybe via BIOS or via efibootmgr (as root user, not sudo please).
Have you been in UEFI BIOS setup since this started? Do you/did you see anything changed there, such as enabling CSM support, or enabling Windows-only secure boot?
When this started, I went into yast and the bootloader.
That was the last time I was able to start Tumbleweed from the boot menu of my os.
So I made things worse.
I have it happen many times before windows over wrote the mbr, and then instead of getting a grubscreen, I had windows starting.
I then used the bootmenu from my motherboard, to boot Tumblweed.
I then went into yast and made sure probe foreign os was checked.
This time this did not fix the problem.
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 931,5G 0 disk
├─sda1 8:1 0 529M 0 part
├─sda2 8:2 0 99M 0 part
├─sda3 8:3 0 16M 0 part
└─sda4 8:4 0 930,9G 0 part
sdb 8:16 0 931,5G 0 disk
├─sdb1 8:17 0 512M 0 part
├─sdb2 8:18 0 48,8G 0 part
├─sdb3 8:19 0 800,8G 0 part /home/guus/leaphome
├─sdb4 8:20 0 2G 0 part
└─sdb5 8:21 0 79,4G 0 part /home/guus/VMmount
sdc 8:32 1 7,5G 0 disk
├─sdc1 8:33 1 3,4M 0 part
└─sdc2 8:34 1 4,4G 0 part
nvme0n1 259:0 0 931,5G 0 disk
├─nvme0n1p1 259:1 0 512M 0 part /boot/efi
└─nvme0n1p2 259:2 0 931G 0 part /var
/usr/local
/srv
/opt
/root
/home
/boot/grub2/x86_64-efi
/boot/grub2/i386-pc
/.snapshots
/
I kept thinking there was, but over and over kept missing it. My suggestion I wanted to offer, and do now, is to disconnect the Leap and Windows disks to see what happens booting with only the TW disk.
People kept pointing at solutions, that start with turn off secure boot.
Secure boot is off here. Still a windows update was the start of the problems.
Tumbleweed is on the NVMe device and secure boot is off.
How do I start Tumbleweed then? (Because I am typing this from Tumbleweed)
I insert a Tumbleweed installation USB.
Then I click more, and then boot a Linux system.
Then it asks me what I want to boot, leap of Tumbleweed.
When you are at this point of having TW running on NVME started via USB menu, what is output from efibootmgr? Is it different if you do the same with the Leap and Windows disks disconnected?
