I just installed openuse tumbleweed on my new Bosgame M5, which already has Win11 and Ubuntu server on it. Sadly I had to realise that tw now installs grub2-bls instead of grub2, which just shows a text-only boot-screen in low-res, but even worse it doesnt show any other installed os. Then in the bootloader program I had to realize that there is no button “probe for another os” anymore and I could not change the bootloader to grub2 or system-boot.
Is there an option during install which I missed, where I can choose the bootloader, so that i can use grub2 instead of grub2-bls?
I’m still not able to install Tubleweed properly with multi-boot (with secure boot enabled)!
Here are the steps I tried:
First, I installed TW with grub-bls and selected the existing (100mb) efi partition for “/boot/efi” (without formatting). This partition previously contained the bootloaders for Win11 and Ubuntu-server. During the installation of TW, an error message appeared stating that there was not enough space on the EFI partition, but the installation process was completed anyway (I did not boot TW, however). I then created a second EFI partition with 500 MB. During the next installation attempt, still unaware that grub-bls was not suitable, I had grub-bls installed on that new partition (with formatting). After the successful installation, there were two entries for TW in the BIOS, one of which worked. After I learned from the link provided by “susejunky” that grub-bls is not suitable for dual-boot, I reinstalled TW with grub-efi (instead of grub-bls) and selected the old 100 MB EFI partition again (without formatting). After this installation, however, there was no new entry in the BIOS, and the two old ones no longer worked. I then reinstalled tw, this time with grub2-efi on the 500 MB efi partition (with formatting). After that, there was a new entry in the BIOS again, but when I selected it, I got the error “security violation, check security settings in BIOS” (or something similar).
During installation, as before, I set “Secure boot” to “enable,” “Trusted boot” to “disable,” and “Update nvram” to “enable”!
Interestingly one of the old bios-entries had the addition “secure”, but the newest entry was without that word.
What else can I try?
- Disable secure-boot in your BIOS.
- Use Yast Bootloader, and check the box for “Secure Boot Support”.
- Reboot
- Enable secure-boot in the BIOS, then boot again to make sure that it works.
On the summary screen there is Bootloader link where you normally could change bootlader. The problem is that YaST blocks switching between BLS and non-BLS bootloaders. One possible reason being different disk layout (BLS requires much larger ESP).
Can you try it? If it does not work personally I would state this is a bug and installer must present suitable option to chose.
It is possible that setting ESP size to small enough value may default to grub2-efi instead of grub2-bls. Someone needs to test it.
Hello. I just installed Tumbleweed on a new mini PC along with Win11 and I’m having the same issue: the list of other operating systems does not appear in grub.
How do I update the grub2-bls configuration? Because the command sudo grub2-mkconfig -o /boot/grub2/grub.cfg no longer works.
Thanks
Have you tried to read this topic and mailing list discussion linked there?
grubbls does not support loading Windows. Period. Someone needs to implement it or at least open bug report.
2 Likes
Thank you. You’re right, the whole issue is covered in that mailing list. Best regards and apologies.
I did that, selected “secure boot”, and “update nvram”, but after I switched secure boot back on in bios I got the “security violation” again! Is it possible, that secure boot doesn’t allow two efi-partitions on the same ssd?
During updating of grub via yast bootloader “mokutil” was installed. Shouldn’t then a screen appear at next boot that says something like “Press OK if you want to update keys”?
Show
efibootmgr
lsblk -f -o +partuuid
grep -Ev '^$|^#' /etc/syconfig/bootloader
1 Like
efibootmgr:
BootCurrent: 0006
Timeout: 1 seconds
BootOrder: 0006,0000,0002,0001,0003
Boot0000* Ubuntu HD(1,GPT,3539e9a2-30ea-4435-b245-f458c546c4c9,0x800,0x32000)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* openSUSE Boot Manager (grub2-bls) HD(1,GPT,3539e9a2-30ea-4435-b245-f458c546c4c9,0x800,0x32000)/File(\EFI\opensuse\shim.efi)
Boot0002* Windows Boot Manager HD(1,GPT,3539e9a2-30ea-4435-b245-f458c546c4c9,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d0000004f000100000010000000040000007fff0400
Boot0003* opensuse-secureboot HD(9,GPT,448adfbc-3f0b-4a0e-9067-d7a301ba3976,0x4e23a800,0xfa000)/File(\EFI\opensuse\shim.efi)
Boot0006* openSUSE HD(9,GPT,448adfbc-3f0b-4a0e-9067-d7a301ba3976,0x4e23a800,0xfa000)/File(\EFI\opensuse\grubx64.efi)0000424f
lsblk -f -o +partuuid:
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS PARTUUID
sda ext4 1.0 Backup 27a222f4-8b97-430c-927c-241670cdd103
nvme0n1
│
├─nvme0n1p1
│ vfat FAT32 SYSTEM DC1D-B7F8 3539e9a2-30ea-4435-b245-f458c546c4c9
├─nvme0n1p2
│ 798927af-f922-400b-933e-3ef6be3772a0
├─nvme0n1p3
│ BitLoc 2 BOSGAMEM5 Windows 05.11.2025 da2a406a-54f2-4c3e-945f-c129c940f07e e725fcba-85c7-4033-94da-b8b182a2c574
├─nvme0n1p4
│ ext4 1.0 5c9977a9-267d-42d3-a2e4-63457828ce26 5ab642a2-82fe-4ee3-b4dc-131b38945c9f
├─nvme0n1p5
│ btrfs tw b71f3e21-c4bd-4712-ba99-909b3083e236 49,8G 13% /var 8558d9a7-637b-4fce-aef3-096a3a51f13a
│ /usr/local
│ /srv
│ /root
│ /home
│ /opt
│ /.snapshots
│ /
├─nvme0n1p6
│ exfat 1.0 linux1 36DA-F8CC b120b98b-9fdf-4780-8e30-d9ec2cf8af8e
├─nvme0n1p7
│ exfat 1.0 linux2 1EED-8C06 b30a626a-5953-447b-b29f-91f2b4fdb917
├─nvme0n1p8
│ exfat 1.0 linux3 1862-05C6 444b4f27-f5b7-4dd9-b0a7-a588974503e3
├─nvme0n1p9
│ vfat FAT16 EFI 2468-9CB8 493,7M 1% /boot/efi 448adfbc-3f0b-4a0e-9067-d7a301ba3976
├─nvme0n1p10
│ ext4 1.0 home 1cc24386-c487-41fa-b2ca-53e893f4e11b 34634bb3-1805-4323-a0bd-75ef59fc43b0
├─nvme0n1p11
│ ntfs Recovery B0B21F63B21F2D7A ac94176e-f63f-4777-a14d-268f12e0378d
└─nvme0n1p12
ext4 1.0 boot e803a36f-0f9c-43a8-916e-29802b2082d8 577ba4a4-0b37-4d0a-9914-af17192835c3
grep -Ev ‘^$|^#’ /etc/syconfig/bootloader:
grep: /etc/syconfig/bootloader: Datei oder Verzeichnis nicht gefunden
There is no “bootloader”-file!
The “Boot0003* opensuse-secureboot” entry doesn’t show in bios (anymore), just the other 4 entries!
Typing error!
syconfig needs to be sysconfig
grep -Ev '^$|^#' /etc/sysconfig/bootloader
1 Like
LOADER_TYPE="grub2-efi"
SECURE_BOOT="yes"
TRUSTED_BOOT="yes"
UPDATE_NVRAM="yes"
Maybe I should remove the two unused entries:
Boot0001* openSUSE Boot Manager (grub2-bls)
Boot0003* opensuse-secureboot
but I don’t know how to do that!
efibootmgr -b 0001 -B
should remove
Boot0001* openSUSE Boot Manager (grub2-bls)
and
efibootmgr -o nnnn,mmmm
allows you to set the bootorder.
See man efibootmgr for more information.
2 Likes
When I started yast bootloader, I had to select “secure boot” (it was unselected). Does that mean that it was not enabled during installation. I’m 100% shure that I set
secure boot deactivated (enabled)
in the installation overview
That did it. Now, after removing the grub2-gls-entry efibootmgr is showing this:
Boot0000* Ubuntu HD(1,GPT,3539e9a2-30ea-4435-b245-f458c546c4c9,0x800,0x32000)/File(\EFI\ubuntu\shimx64.efi)
Boot0002* Windows Boot Manager HD(1,GPT,3539e9a2-30ea-4435-b245-f458c546c4c9,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d0000004f000100000010000000040000007fff0400
Boot0003* opensuse-secureboot HD(9,GPT,448adfbc-3f0b-4a0e-9067-d7a301ba3976,0x4e23a800,0xfa000)/File(\EFI\opensuse\shim.efi)
Boot0006* openSUSE HD(9,GPT,448adfbc-3f0b-4a0e-9067-d7a301ba3976,0x4e23a800,0xfa000)/File(\EFI\opensuse\grubx64.efi)0000424f
Boot0007* opensuse-secureboot HD(1,GPT,3539e9a2-30ea-4435-b245-f458c546c4c9,0x800,0x32000)/File(\EFI\opensuse\shim.efi) File(.)
There now is one new opensuse-secureboot -entry and I now have choosen that one (or the old one that now also showed in the boot-menu), after enabling secure boot in bios, and tw is now booting!
THANKS FOR THE HELP!
Now I can boot Windows and Tumbleweed, but not ubuntu. When I choose Ubuntu from the opensuse grub-menu, i’m getting “bad shim lock signature” (but I can still boot ubuntu from the old 100mb-efi, from the ubuntu-grub).