Hi all, I’m not a techie, but I managed to install the Leap 16 in a free partition next to two partitions of the Leap 15.6 on the same 2TB HDD. I managed to install the Nvidia drivers and the cockpit, and I’m starting to learn how to use it. That said, I will ask for help for problems as I encounter them, starting with the fact that the previous grub recognized in addition to Leaps partitions also Windows 10 installed in an SSD, but the new one no longer sees it, I have to boot it from the BIOS, it’s not a big problem because I rarely use Windows, But I would like to fix it if possible. If anyone has any suggestions, it would be greatly appreciated. Thank you
It would be nice if your title above would reflect the question/problem you have. As it is now it is just a statement and those who filter topics to see where they can help by browsing the titles of new threads will probably simply skip this one.
Looks like the Leap 16 installer doesn’t have the “probe foreign OS” option for the bootloader, but the yast2-bootloader module should still be available, so install it and start it.
Then go to the “Bootloader Options” tab and make sure that the “Probe Foreign OS” checkbox is checked. Then “OK” and reboot.
1 Like
@Orso Bruno
thankyou very much .
just are u sure that won’t this break anything? I’ve been spending time and the last thing I want to do is risk it not booting up.
It won’t break
Is GRUB BLS is in use here?
Show
grep ^LOADER_TYPE /etc/sysconfig/bootloader
antum@leap16:~> grep ^LOADER_TYPE /etc/sysconfig/bootloader
LOADER_TYPE=“grub2”
Thanks for clarifying . Proceed with OrsoBruno’s advice.
Does running sudo os-prober manually report the Windows EFI?
Did you set a root password during installation?
no, just one , but usually it accept this one
Add a root password with sudo passwd root and follow the prompts. Then you can launch it graphically.
If you don’t mind using ncurses mode just run it like this: sudo yast2 bootloader
can i give the same password?
For sure you can.
I would have thought just a grep ^GRUB_DISABLE_OS_PROBER /etc/default/grub would show true or false?
But sounds like a Legacy install of openSUSE and a UEFI install of Windows 11 or vis-versa… since it’s “grub2”… not “grub2-efi”
@harlequin please show the output from lsblk
I wondered that as well. FWIW, LOADER_TYPE="grub2" can still be present while the system is booting via UEFI, as such detection is done automatically at boot (based on the actual firmware and ESP). At least we know grub2-bls not in use.
@deano_ferrari My systems have grub-efi except a recent Tumbleweed install, and the default on Leap 16.0 is GRUB_DISABLE_OS_PROBER="false" and os-prober installed (checked on two systems)…
Yes mine don’t, and it doesn’t affect the booting.
The os-prober is the same of course.
