From Newsgroup: alt.os.linux


While doing the 'install' run of a 'zypper dup' update I get these
messages repeatedly:

ERROR: Bootloader not detected. /etc/sysconfig/bootloader has LOADER_TYPE="grub2-efi", but only "systemd-boot" or "grub2-bls" are recognized.

Grub is installed and booting works reliably. Doesn't seem to cause any
issues but it is visual polution so I'm wondering how to get rid of it?
--
Nolite Te Bastardes Corborondum


--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On Mon, 31 Aug 2026 06:13:04 -0400, bad sector wrote:

While doing the 'install' run of a 'zypper dup' update I get these
messages repeatedly:

ERROR: Bootloader not detected. /etc/sysconfig/bootloader has LOADER_TYPE="grub2-efi", but only "systemd-boot" or "grub2-bls" are recognized.

Grub is installed and booting works reliably. Doesn't seem to cause any issues but it is visual polution so I'm wondering how to get rid of it?

I see the same LOADER_TYPE but judging from the green dialog it's doing systemd-boot and ignoring the config file. I don't see an error.

I installed Leap 16 on the T480 after SUSE defaulted to systemd-boot, I believe. I recently did an in place upgrade to Tumbleweed.
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On Mon, 31 Aug 2026 06:13:04 -0400, bad sector wrote:

While doing the 'install' run of a 'zypper dup' update I get these
messages repeatedly:

ERROR: Bootloader not detected. /etc/sysconfig/bootloader has LOADER_TYPE="grub2-efi", but only "systemd-boot" or "grub2-bls" are recognized.

At a wild guess: rCLgrub2-blsrCY is rCLGRUB installed via blocklistrCY (not recommended). rCLgrub2-efirCY is of course the UEFI/EFI option common on
modern hardware; shouldnrCOt there also be some kind of rCLlegacyrCY or rCLBIOSrCY option as well? And rCLsystemd-bootrCY is the systemd boot manager <https://systemd.io/ROOTFS_DISCOVERY/>.

Is there some package missing that you need to install to give the
option of installing a bootloader of type rCLgrub2-efirCY?

Grub is installed and booting works reliably. Doesn't seem to cause
any issues but it is visual polution so I'm wondering how to get rid
of it?

Perhaps you have (inadvertently) removed some component needed to
provide the above bootloader option -- either a separate package
(seems unlikely?), or perhaps some file that should be part of the
standard package. Without it, the existing bootloader installation
will continue to work for now, but if you ever need to update it, it
might fail and leave your system unbootable.

Once again: the above is all just a wild guess. Just about all my
knowledge of SuSE is from before the introduction of zypper. And yes,
that was a long time ago.
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On Mon, 8/31/2026 6:13 AM, bad sector wrote:

While doing the 'install' run of a 'zypper dup' update I get these messages repeatedly:

ERROR: Bootloader not detected. /etc/sysconfig/bootloader has LOADER_TYPE="grub2-efi", but only "systemd-boot" or "grub2-bls" are recognized.

Grub is installed and booting works reliably. Doesn't seem to cause any issues but it is visual polution so I'm wondering how to get rid of it?

I entered the description into CoPilot.
CoPilot makes mistakes. Before doing this, you'd want
a backup of sufficient quality to put everything back
as it was.

*************** CoPilot answer *******************

**Short answer:**
Your system is now using the **new sdbootutil-based bootloader detection**, which only recognizes **systemd-boot** and **grub2-bls**. The classic **grub2-efi** setting in /etc/sysconfig/bootloader is no longer valid on current Tumbleweed. You must switch the LOADER_TYPE to one of the
supported values and reinstall the bootloader.

This change is intentional: **GRUB2rCaBLS is now the default bootloader in openSUSE Tumbleweed**

( https://news.opensuse.org/2025/11/13/tw-grub2-bls/ )

and sdbootutil only supports **systemdrCaboot** and **grub2rCabls**

( https://deepwiki.com/openSUSE/sdbootutil/4.1-bootloader-management-commands )

---

## Why the error happens
/etc/sysconfig/bootloader still says:

LOADER_TYPE="grub2-efi"

- But sdbootutilrCOs detection logic only recognizes:
- systemd-boot
- grub2-bls
(These are the only BLS-compliant bootloaders supported.)

( https://deepwiki.com/openSUSE/sdbootutil/4.1-bootloader-management-commands )

Since **grub2-efi** is the *old* nonrCaBLS GRUB, sdbootutil reports:

ERROR: Bootloader not detected.

This is expected behavior on modern Tumbleweed.

---

## Fix: Switch to a supported bootloader

### Option 1 rCo Switch to **grub2rCabls** (recommended for Tumbleweed)

This keeps GRUB but uses the new BLS-compatible GRUB binary ( grubbls.efi ). This is the path openSUSE recommends for Tumbleweed going forward.

( https://microos.opensuse.org/blog/2024-10-08-grub2-bls/ )

**Steps:**
1. Install the BLS-enabled GRUB package:

sudo zypper in grub2-x86_64-efi-bls

2. Edit `/etc/sysconfig/bootloader`:

LOADER_TYPE="grub2-bls"

3. Reinstall the bootloader:

sudo sdbootutil install

This will place the unified GRUB2rCaBLS EFI binary into /boot/efi/EFI/opensuse and create BLS entries under /boot/efi/loader/entries

---

### Option 2 - Switch to **systemd-boot**

This is the other supported bootloader and is now default in some Tumbleweed installs.

( https://news.opensuse.org/2025/11/13/tw-grub2-bls/ )

**Steps:**
1. Install systemd-boot:

sudo zypper in systemd-boot

2. Update the bootloader type:

sudo update-bootloader --loader systemd-boot

3. Install systemdrCaboot into the ESP:

sudo bootctl --make-machine-id-directory=yes install

(Procedure confirmed by users switching on Tumbleweed/Leap.)

( https://forums.opensuse.org/t/move-to-systemd-boot-on-tumbleweed/193050 )

---

## Which option should you choose?
| Bootloader | Pros | Cons |
|------------------|----------------------------------------------------------------------------------|-------------------------|
| **grub2-bls** | Compatible with existing GRUB workflows; supports snapshots; fully BLS-compliant | Larger EFI binary |
| **systemd-boot** | Very fast; simple; default for MicroOS; integrates cleanly with systemd tooling | No GRUB scripting; |
| fewer advanced features |
For most Tumbleweed users, **grub2-bls** is the smoothest transition.

---

## After switching
Run:

sudo bootloader

This should now correctly detect either **grub2-bls** or **systemd-boot** (the only supported values).

( https://deepwiki.com/openSUSE/sdbootutil/4.1-bootloader-management-commands )

---

## Want me to walk you through the exact steps for your system (partition layout, ESP location, etc.)?
If you paste the output of:

lsblk -f
cat /etc/sysconfig/bootloader
efibootmgr -v

I can give you a precise, safe sequence tailored to your setup.

*************** End CoPilot answer *******************

Paul
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 2026-09-02 12:07, Paul wrote:

On Mon, 8/31/2026 6:13 AM, bad sector wrote:

While doing the 'install' run of a 'zypper dup' update I get these messages repeatedly:

ERROR: Bootloader not detected. /etc/sysconfig/bootloader has LOADER_TYPE="grub2-efi", but only "systemd-boot" or "grub2-bls" are recognized.

Grub is installed and booting works reliably. Doesn't seem to cause any issues but it is visual polution so I'm wondering how to get rid of it?

I entered the description into CoPilot.
CoPilot makes mistakes. Before doing this, you'd want
a backup of sufficient quality to put everything back
as it was.

I would ask on the openSUSE mail lists.

One or more of the new suported bootloaders puts the kernel in the ESP partition, which is usually not big enough, ending in disaster. I can
not tell specifics about this.
--
Cheers, Carlos.
ESEfc-Efc+, EUEfc-Efc|;
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 9/2/26 6:07 AM, Paul wrote:

### Option 1 rCo Switch to **grub2rCabls** (recommended for Tumbleweed)

This keeps GRUB but uses the new BLS-compatible GRUB binary ( grubbls.efi ). This is the path openSUSE recommends for Tumbleweed going forward.

( https://microos.opensuse.org/blog/2024-10-08-grub2-bls/ )

**Steps:**
1. Install the BLS-enabled GRUB package:

found already aboard

sudo zypper in grub2-x86_64-efi-bls

2. Edit `/etc/sysconfig/bootloader`:

LOADER_TYPE="grub2-bls"

3. Reinstall the bootloader:

sudo sdbootutil install

# sdbootutil install
WARNING: The system has EFI variables but UPDATE_NVRAM is set to "no"

### Option 2 - Switch to **systemd-boot**

cute


--- Synchronet 3.22a-Linux NewsLink 1.2