Well, I installed SuSe Tumbleweed on yet another old computer. It was very hard. I finally got it booting in what I think is probably some sort of legacy mode. That is: I select the physical drive from the BIOS menu to boot it. If I put that drive first in the BIOS list, the computer will by default boot from the disk with Tumbleweed (sda). Make no mistake, I am using Firmware, not software, first. On this strange computer I do not think it is possible or desirable to change this. So by default when turned on the computer will boot up SuSe Tumbleweed. That works. Windows is also installed. But the linux “grub” menu does not have an option to boot Windows. If it did I could use either system without having to hit the BIOS interrupt boot keys and just using the linux/grub boot menu. I know that you can hit E to edit the grub menu, but it is written in something like a scripting language that I know nothing about. How can I change the linux Grub menu to include an option to boot Windows 10?
Should be able to boot Windows from the BIOS. Chance are you have fast boot configured in Windows. Which is incompatible with Linux. Turn it off
Just a thought; this happened to me before: Maybe the Grub2 menu that you are seeing is not the one from your current Linux installation, but from a previous one that is left over and for some reason still does something.
If your previous Linux installation installed Grub2 to the MBR of your first disk (i.e. to /dev/sda), and the current one installed it to its own root partition (say, /dev/sda2) and not to the MBR as well, you could see such symptoms.
You could try to boot from a USB stick with an openSUSE installation ISO on it and then use the “Boot from hard disk” menu entry from there to chain-boot into your Linux and then reinstall Grub2 from there (use the YaST bootloader module).
And if you are using the PC legacy partitioning scheme (a.k.a. MS-DOS as opposed to GPT), check what partition is marked as the active one, i.e. the one that your BIOS tries to boot from. You want the one with Grub2 active.
You might have a completely different problem, but this could be worth a try.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.