Which means if I turn on my pc I get a grub screen.
Then I can choose, Tumbleweed, leap or windows.
After starting windows 10 which did an update the problem started.
Windows boots, no more grub screen.
I then started tumbleweed through the mother board.
Made sure in yast probe foreign OS was checked and clicked ok.
This used to fix this problem, but not today.
I then tried to change something else in yast, but now my motherboard does not recognize the tumbleweed disk anymore as bootable.
I can only boot from my motherboard, windows or Leap, but not tumbleweed.
From leap I can acces all files from Tumbleweed.
How to fix this ?
(I am posting this from windows 10)
I dont understand what to do ? That page talks about Ubuntu
But a small update I just was able to start tumbleweed by using the install usb, and choose boot from harddisk.
It then asked a few question, but tumbleweed did start.
So I went into yast but again probe foreign os did not solve it.
Because I can’t edit my previous post, I add this reply.
The only way for me to currently start Tumbleweed, is with a tumble weed install USB.
Start rescue system, then I then go to more, and then pick boot a Linux system.
Then the rescue system has a look, and asks if I want to boot Tumbleweed or Leap.
I pick tumble weed, and after two more questions, Tumbleeweed does start.
If I then restart my pc, its again windows that boots.
Although the page talks about Ubuntu, I see nothing that is Ubuntu specific so just give it a try, it is a Microsoft induced problem, that procedure deletes the offending Microsoft SBAT Policy. If it does not work, please detail what you did and where things did go wrong.
There is not that much difference between Linux distributions apart from the package too (zypper/dnf/rpm etc.) and some GUI config tools (Yast…)
I don’t know if it matches your case, but I had a problem with Dell’s BIOS update/settings reset that overwrote my MBR with Windows’ boot loader (and I don’t even have Windows installed…)
However in UEFI settings I could set up a manual boot entry, and chose to boot from /boot/efi/EFI/opensuse/grubx64.efi. Made that the top of the boot list and it worked for me.
If not sure how to use BIOS itself to repair, boot using USB into whichever installed openSUSE system you wish to be in control of boot, the take a look at output from sudo efibootmgr just FYI for reference. Is it obvious there is a Windows entry with priority over as many openSUSE’s as you have? Then use YaST Bootloader to update bootloader, making sure the update NVRAM checkbox is enabled. If it was not and you check it, then you should need do no more than save, exit YaST, and then be able to boot normally into that openSUSE installation.
After you’re successful, compare GRUB_DISTRIBUTOR= in file /etc/default/grub in each openSUSE installation. You’ll probably find they are both equal to null (blank, empty). This in turn would mean in /boot/efi/EFI/ there is only a BOOT directory and one opensuse directory, with nothing for your other openSUSE installation. This is the standard boot usurpation configuration of multiple installations for same vendor. If you change the GRUB_DISTRIBUTOR= to a unique string, such as “opensusetw” for your tW, then on next update to the TW installation’s grub setup, TW would have its own directory in /boot/efi/EFI/, and your BBS menu would have one EFI opensuse and one EFI opensusetw among the other selections.
BBS (Bios Boot Specification) hotkeys:
* Abit F9
* Acer F12 or ESC or F9
* ASRock F11
* Asus F8
* Biostar F9
* Dell F12
* DFI ESC
* eCS F12 or F10
* eMachines F10
* EVGA F7
* Gateway F12 or F10
* Gigabyte F12
* HP/Compaq F9 or ESC or ESC,F9
* Intel F10
* Lenovo F12 or F8 or F10
* MSI F11
* Shuttle ESC or F11 or F7
* Toshiba F12
Are the installed OSes installed in UEFI mode? Did you boot the USB in UEFI mode? When CSM is enabled, many UEFI BIOS will lead you into a legacy boot by default. You may need to take action to boot in UEFI, probably BBS hotkey, or change BIOS setup to disable CSM (legacy) booting. All my PCs that have OSes installed in UEFI mode have CSM disabled, so that such nuisance doesn’t arise here.
@malcolmlewis Looks like link is to same subject as comment #2’s link.
Secureboot is disabled in my bios, I just checked.
I remember why its turned off, it gave me problems with booting windows.
(the irony)
OpenSUSE Tumbeleweed did not have an issue. ( this was years ago, when I build this pc)
When I hit F11, I can choose windows or Leap, Tumbleweed has disappeared from that menu.
I can however still boot Tumbleweed with help from an installation usb stick.
Boot from the usb stick, then choose more and pick boot Linux medium.
Then select Tumbleweed.
When I look in my bios at the boot order, I can’t choose Tumbleweed anymore.
My bios does not seem to recognize the Tumbleweed disk as bootable anymore.
Sure, but first check if CSM legacy support is disabled.
I guess that F11 gives you the UEFI boot. Can you see GRUB when you choose Leap? Is Tumbleweed there?