Hi all, I’ve got a problem with grub2 that is going me mad. I had an hard disk with Opensuse Leap 15.1 installed, now I have also installed Tumbleweed. I want to use the Leap’ grub.cfg file in /boot/grub2, but I can’t find out how to do this…
I’ve changed UUID in /boot/efi/EFI/grub.cfg and /boot/efi/opensuse/grub.cfg, but grub2 continue to boot the tumbleweed file. What can i do? Thanks!!
Hi
Leap and Tumbleweed don’t co-exist without some tweaks with the efi file location directory name, unless you created a separate /boot/efi partition for it?
Look down in /boot/efi/EFI and you may only have one directory with opensuse?
What is the output from;
efibootmgr -v
os-prober
But you should be able to add Leap to grub…
Thank you for the fast reply! So, i just would like to re-explain the problem because my english is not too good and i don’t know if i was clear with explanation: in the grub menu, when i boot the pc, i can see tumbleweed and leap both. The problem is that, when i try to modify the OpenSuse Leap’s grub.cfg manually, i can’t see the modifies in the grub menu because it continue to run the Tumbleweed’s file as default.
In /boot/efi/EFI i’ve got 4 folders (because i have other OS that sometimes i use). The folders are BOOT, Microsoft, ubuntu opensuse.
I can only see one EFI partition, i’ve not created a new one.
For efibootmgr -v the answer is
EFI variables are not supported on this system.
while for os-prober is
/dev/sda2:Ubuntu 19.10 (19.10):Ubuntu:linux/dev/sda7:openSUSE Tumbleweed:openSUSE:linux:btrfs:UUID=c0e87b3b-43aa-403d-b532-64fcdee4442c:subvol=@/.snapshots/1/snapshot
because it doesn’t recognize Windows (and this is another problem :D).
I’m on Leap now…
Hi
Sounds like you have a mixture of booting… Legacy and UEFI… not good 
Can you post the output from;
fdisk -l /dev/sda
… i hate partitioninglol!
/dev/sda1 2048 1050623 1048576 512M EFI System
/dev/sda2 1050624 401051647 400001024 190,8G Linux filesystem
/dev/sda3 401051648 820482047 419430400 200G Linux filesystem
/dev/sda4 820482048 1239912447 419430400 200G Microsoft basic data
/dev/sda5 1239912448 1239945215 32768 16M Microsoft reserved
/dev/sda6 1949329408 1953525134 4195727 2G Linux swap
/dev/sda7 1239945216 1491603455 251658240 120G Linux filesystem
/dev/sda8 1659375616 1949329407 289953792 138,3G Linux filesystem
Do you want to make Leap as the default os? Is it what you want.
You can use the boot loader in leap to do this.
Boot leap go to yast2 and rebuild the boot loader
The next boot Leap will be on top of the boot option.
Hi
So how did you boot Leap, from a Live USB? If so you need to boot in UEFI mode, so on the system press the boot menu key for your system (esc, F2, F10 F12 etc) and in here can you select the respective efi boot option? I would suggest tumbleweed
Nono, i booted leap normally from grub2 (the Tumbleweed version of grub).
In yast2 leap is alredy the default, but it isn’t really when i boot. Principally i would like to know why grub2 continue to read the Tumbleweed config file and not the Leap one.
In yast2 leap is alredy the default, but it isn’t really when i boot. Principally i would like to know why grub2 continue to read the Tumbleweed config file and not the Leap one.
Another thing: when i try to press esc at booting, i can see 3 lines: two are normally, one for hard disk and one for dvd, but one line is formed only by strange symbols, not normally characters… there is something strange O.O
That should have worked – if you are using UEFI booting. But it won’t help at all if you are using traditional boot sector booting.
Looking through the entire thread, it seems that you are using traditional boot sector booting, and not UEFI booting.
Without being able to examine your computer, it is hard to know the reason for this. Usually, it is a BIOS setting that decides between UEFI booting and traditional boot sector booting.
So go into your BIOS settings for booting. If there is a choice between UEFI booting and boot sector booting (usually called CSM in recent BIOS – CSM stands for “compatibility support module”), then switch to using UEFI booting.
There’s one other possibility. Some systems use the “pmbr_boot” flag to decide which way to boot. So maybe check that. The output of “parted -l” might show that. In any case, a google search for “pmbr_boot” will turn up useful help on turning off the “pmbr_boot” flag.
mmm i’ve seen that the tumbleweed partition have " ìlegacy_boot" flag, only this partition. It is the same you were talking about?
Although I’ve never investigated further,
I’ve seen GPT documentation that states both UEFI and MBR are supported at once and should now be default (used to be you had to manually configure support for both and not only one or the other).
Had assumed at that point that a UEFI boot would have no problems…
But I also assume that if you’re configured for Secure Boot that might throw an extra wrinkle that MBR might not support…
TSU
I’ve seen the option in BIOS, but if I deactivate it, I can’t see the grub menu at boot…
Maybe it’s time for us to see the output from bootinfoscript.
That’s correct. os-prober imports grub.cfg entries from another system(s) once, when local grub.cfg is generated. If another system’s grub.cfg is modified after that, it is not reflected,
Alternative is to not use os-prober and manually chainload grub from another system. How to do it was explained more than once in this forum; to make any detailed suggestion bootinfoscript output is indeed needed.
Thank you all for the help! You can find the bootinfoscript result here https://github.com/Quiquoqua48/Public/blob/master/bootinfoscript%20result.
This looks like you have Tumbleweed installed in legacy BIOS mode and other systems in EFI mode. At least there are no partition boot blocks identified by BIS other than TW nor can Windows be installed on GPT in Legacy BIOS mode. Also os-prober on TW does not see Windows boot files which is expected (you cannot call EFI loader while in booted in BIOS mode).
To chainload other grub instance both must be for the same platform - either both BIOS or both EFI.
I’ve just finished to reinstall Tumbleweed because i noticed that i had installed it in BIOS mode and not UEFI… now all seems work good 
Thanks to all!rotfl!
I think the problem is half solved, because now Windows boot automatically at start… if i want to enter grub menù, i have to press f11 at boot and enter the opensuse partition…